Variant handling across size and concentration
30ml, 50ml, 100ml, EDP, EDT, extrait — one fragrance is twelve purchasable items with different stock.
Everything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
PERFUME AND OUD · ECOMMERCE DEVELOPMENT
Customers buy by scent family and gift by occasion, and no template handles either. A product page built for a single 50ml bottle falls apart the moment the same fragrance needs to sell as a 30ml, a 100ml and a discovery set, each with its own stock count.
A build here means solving the specific catalogue problem: variants that behave as separate stock items instead of one SKU with a dropdown, discovery sets that let a customer try before committing to a full bottle, and a gifting flow built for the volume that actually drives Gulf perfume sales. You own the code, the server and the data once it ships.
WHAT ACTUALLY BREAKS
Five problems specific to how fragrance is bought and gifted, not generic complaints with the industry name swapped into an identical sentence.
30ml, 50ml, 100ml, EDP, EDT, extrait — one fragrance is twelve purchasable items with different stock.
A customer will not spend on a 100ml bottle of an oud they have never smelled.
Oud, amber, musk, floral — how people actually search for perfume.
A large share of Gulf perfume volume is gifted rather than self-purchased.
A single fortnight can carry a quarter of the annual volume, and stock rules have to change with it.
Each of these is handled once, in the build, rather than left to a variant plugin that stops getting updated the day the company that made it moves on to something else.
WHAT WE BUILD
Four components, built together rather than bolted on as separate tools that do not share data.
A fragrance entered once with its variants is the same product the discovery set draws samples from and the same product the gifting flow wraps. Four components that share one data model, not four separate tools stitched together after the fact.
PROOF
Beauty and cosmetics, not perfume specifically, but the same variant and delivery problem.
A beauty and cosmetics store built with multi-vendor delivery.
Payment handling built to the store's own requirements, not a generic plugin.
Tested the same way as everything else we build.
WHAT IT COSTS
A range, not a fixed price, because catalogue size and variant complexity move the number.
Third-party services, including payment processing, are billed at cost. We do not mark up other people's software.
Depending on catalogue size and variant complexity.
10 with the integration.
Code, server and data, from handover.
Process, timeline, and what we need from you to move a variant-heavy catalogue without losing rankings.
STRAIGHT ANSWERS
The ones that come up on almost every call with a fragrance brand or retailer.
Yes. Each size and concentration — 30ml, 50ml, 100ml, EDP, EDT, extrait — is handled as its own purchasable item with its own stock count, not as a dropdown sitting on top of one shared inventory number. A sellout of the 50ml EDP does not touch the 100ml EDT.
Yes. Discovery sets and samples sit alongside full-size bottles in the catalogue, because most customers will not spend on a 100ml bottle of an oud they have never smelled. It is built as a normal product with its own variant, not a workaround.
Stock and delivery rules are built to change for peak periods, since a single fortnight can carry a quarter of a perfume store’s annual volume. That is a configuration the store supports directly, set once in advance, not a manual scramble the team repeats by hand every single year.
Between
A technical review covers speed, security, how search engines see your catalogue, and what your current setup really costs each year. Two days, no charge, no obligation, and you keep the report whether or not you hire us.
Perfume and oud sits alongside flowers and gifting and chocolate and dates, three industries selling a perishable or occasion-driven product where gifting volume outweighs self-purchase.
One tap, then your app opens with it written.