Soknab Oudh
A premium storefront with pricing and packaging logic no site builder could express.
- Engagement
- Client engagement
- Industry
- Luxury Retail
- Year
- 2025
The challenge
A premium oudh oil brand needed to sell online, but their pricing depended on volume, packaging and presentation combinations that off-the-shelf builders model as separate products. Forcing the catalog into a template would have made a luxury product look like a commodity listing.
Our approach
We modeled the pricing logic properly in the data layer instead of flattening it into product variants. The storefront uses generous spacing, restrained type and plenty of room for product photography. For a luxury brand, the layout supports the price, so it received the same attention as the checkout.
What it had to achieve
- Present a premium product at a premium standard
- Express real pricing and packaging logic in the catalog
- Manage orders without exporting to a spreadsheet
- Deploy somewhere reproducible rather than a shared host
Architecture
The decisions that made the rest possible.
Pricing modeled in the schema, not in variants
Volume, packaging and presentation are first-class attributes, so a new combination is data rather than a duplicated product entry.
Order workflow with explicit states
Orders move through defined stages in the admin dashboard, keeping fulfilment inside the system instead of in a spreadsheet export.
Dockerized deployment
The app ships as a container, so staging and production behave identically and a redeploy is reproducible.
What we delivered
- Custom Next.js storefront designed for premium presentation
- Prisma-backed catalog expressing volume and packaging pricing
- Order workflow and admin dashboard
- Dockerized deployment with reproducible environments
Outcomes
What changed once it was live.
- Product presentation matches the brand's price point
- Pricing combinations are configuration, not duplicated listings
- Orders are managed in one place through to fulfilment
What we would do differently
Every project teaches something. Publishing it is how you tell whether a team is reflecting or just selling.
- Modeling pricing correctly in the schema was worth the extra design time. Flattening it into variants would have made every future SKU a manual chore.
Let's find out if this is worth building.
A 45-minute discovery call, free. You describe the problem, we tell you honestly what it takes, what it costs, and whether you should build it at all.