Lists of Magento’s benefits all say the same things: flexible, scalable, open source. This post tests them against a store we built on Magento, Al Majed for Oud’s bilingual fragrance store in Saudi Arabia. It shows which parts of the platform earned their keep, which had to be designed by hand, and when we would point a store elsewhere.
What a fragrance house asked of its platform
Al Majed for Oud sells perfumes, oud, incense, perfume oils, home fragrance, accessories and gift sets. Its customers shop in Arabic and in English, and they choose fragrance by scent, mood and occasion more than by product name. Much of the year’s demand arrives with gifting seasons and offers.
Those facts set the brief before any platform question. The store had to carry a large catalogue across very different categories, let customers browse by fragrance character, read naturally in both directions, give gifting its own routes and take payment the way customers in the region expect. The full record is in the Al Majed for Oud case study.
Brief against platform: where the work really went
Here is each requirement from the brief, what Magento brings to it out of the box, and what still had to be designed. The third column is the part the benefit lists leave out.
| Requirement | What Magento provides | What still has to be designed |
|---|---|---|
| A large, mixed catalogue | Attribute sets, so incense and gift sets can carry different product fields in one catalogue | Which attributes each category needs, and which ones customers will actually filter on |
| Shopping by scent | Layered navigation that can filter on any attribute you mark as filterable | The scent vocabulary itself: the families and notes a customer recognises, applied consistently across every product |
| Arabic and English | Store views, each with its own locale, translations and content | A theme that mirrors properly for right-to-left reading; the default Luma theme was not built for it |
| Gifting and offers | Categories, cart price rules and catalogue price rules | Where gift sets and seasonal offers live in the navigation, so they are found rather than stumbled on |
| Regional checkout | A checkout that accepts payment extensions | Which payment methods to offer, and testing every one in both languages |
The pattern is the same in every row. Magento’s real benefit is that it does not stop you building what the business needs. It does not build it for you, and the time goes into the third column.
Selling by scent: catalogue structure before design
A customer who loves a scent rarely knows the product name. The case record describes the result as navigation by scent: customers explore by fragrance character as well as by product type, and a favourite scent leads to the products that share it. That only works if the catalogue data is right underneath it.
The order we recommend for any catalogue sold by character rather than by name:
- Write the vocabulary first. Agree the scent families and notes with the people who sell the product, in both languages, before anyone opens the admin.
- Decide which values are filters and which are description. A filter with forty values helps nobody.
- Apply the values to every product, including the old and the slow-selling ones. A filter that misses a third of the range teaches customers not to trust it.
- Then design the navigation around the filters people use, and test it with real browsing before launch.
Most of that work is merchandising, not development. On Magento it pays off because the platform will filter, index and display whatever structure you give it, at catalogue scale.
Two reading directions: the checks we run
Bilingual stores often treat one language as a translation of the other. The brief for this store was the opposite: Arabic and English as equals, each reading naturally. Translating the strings is the easy half. These are the checks we run on every page type before a right-to-left store launches:
- The whole layout mirrors: navigation, product gallery, filters and breadcrumbs start from the right.
- Arrows, chevrons and progress steps point the way the reader moves.
- Prices, sizes and order numbers stay readable where Arabic text and Latin digits sit in one line.
- Product names that stay in English inside Arabic copy do not break the line or the punctuation.
- Checkout fields, error messages and order emails are written in each language, not machine-filled.
- Search and filters return the same products whichever language the customer browses in.
Each item is small. Missed together, they make a store feel translated, and customers notice that before they notice anything else.
When Magento is the wrong choice
Magento suits a catalogue that breaks simpler platforms and a business willing to run it properly. It carries a real running cost, and we itemise it before a client commits. Our Magento builds take months, not weeks.
- 1Is the catalogue big or complex enough to break simpler platforms?NoSmall and simple: point the store elsewhere
- 2Does a hosted platform fall short of the requirements?NoIf a hosted platform covers them, use it
- 3Will someone own and run the platform after launch?NoAn unpatched Magento store is a target
- 4Have you itemised the running cost and the engineering retainer?NoItemise both before committing; builds take months, not weeks
An unpatched Magento store is a target. A properly run store needs an engineering retainer after launch: security patches on a schedule, integration upkeep, and someone watching index, cron and cache health.
We would point a store elsewhere when the catalogue is small and simple, when nobody will own the platform after launch, or when a hosted platform covers the requirements. A platform is not a lifetime decision either: Al Majed for Oud has since moved its store to Salla.
If you are weighing a move yourself, our guide on when to migrate an ecommerce platform separates platform limits from problems a move will not fix. Scope and fixed-quote shapes are on our Magento development page.
