All projects
e commerce

Yeprem Jewellery — Selling Luxury Online Without Overselling or Losing Trust

Luxury E-Commerce · ERP Integration · Transaction Locking · RTL

Client
Yeprem Jewellery
Industry
Luxury Retail
Location
International
Year
2024
Preview the live site
Project media

See the work in context.

Move through the published screens and walkthroughs. Images open at full size; videos play with their own controls.

Desktop interface

0

Overselling incidents

since launch

<10s

Boutique-to-web sync latency

ERP webhook driven

100%

Transaction integrity

DB-level locking

0

Customer-facing oversell messages

caught before payment

Project brief
Client
Yeprem Jewellery
Industry
Luxury Retail
Location
International
Work included
Web Development

A piece of jewellery can sell in a boutique while a customer is mid-checkout online. For a luxury brand, that's a serious problem — not just a logistics headache. We built real-time ERP sync and database-level transaction locking that makes overselling physically impossible.

01 / Project Overview

The situation

Yeprem is a luxury jewellery brand with boutiques across the Middle East and a clientele that does not respond well to the phrase 'we're sorry, that item was actually sold in our Dubai boutique.' The e-commerce platform had to be held to a standard appropriate for what it sells: absolute inventory accuracy, zero transaction errors, and a purchasing experience that communicates the same premium quality as a physical boutique visit. The core technical challenge is this: Yeprem's boutiques sell in real time. A sales associate in Riyadh can complete a sale on a piece that a customer in London has in their checkout basket. Without real-time inventory sync and checkout-time stock reservation, that London customer completes payment — and then gets an apology email. We built two things to prevent this. First, real-time ERP integration: every boutique sale triggers a webhook that updates the web store's inventory within seconds. Second, database-level transaction locking on the checkout flow itself: when a customer initiates payment, their selected items are locked at the database row level for the duration of the transaction — no concurrent checkout can touch them. If the lock can't be acquired (someone else is checking out the same item), the customer is told immediately before payment, not after. The result is a platform where it is technically impossible to sell a piece of jewellery twice.

02 / The Challenge

What had to change

Boutique sales happen in real time, independently of the web store. Previous system updated web inventory on a 24-hour batch sync — meaning items could appear available online for up to a day after being sold in-store. High-ticket item overselling was an occasional reality that damaged client relationships and required manual intervention every time.

03 / Our Solution

What we changed

Webhook-driven ERP integration: boutique systems fire events on every completed sale, updating web store inventory within seconds. SELECT FOR UPDATE transaction locking at payment initiation — the row-level lock is held for the transaction duration. Concurrent checkout attempts on the same item fail early (before payment) with a clear message. Zero oversells since launch.

04 / Deliverables & outcomes

What the client gained

  • 01 Physically impossible to oversell — row-level DB locking
  • 02 Real-time ERP sync — boutique sales reflected in seconds
  • 03 Arabic RTL and English storefronts both first-class
  • 04 Security-first API design for luxury-scale transactions
Bring the next constraint

Have a project that needs a clearer way forward?

Discuss the project

1 / 2