Omnichannel Without the Chaos: The Retailer's Commerce OS

The Business

A 20-store home-and-living retailer that launched online two years ago, then added two marketplaces. Sales grew — but so did the chaos. The website team, store teams, and marketplace team each run their own inventory, pricing, and customer lists.

The owner describes it honestly: “We’re 20 stores, one website, and two marketplaces — but it feels like 23 different companies.”

The Modeled Case Study

A modeled scenario showing what happens when omnichannel grows faster than the operations behind it — and how one Commerce OS brings it together.

The chaos

1. Three prices, one product: the store, website, and marketplace each price differently because nobody updates all three.
2. Inventory conflicts: a marketplace order confirms stock that the website just sold. Someone, somewhere, has to cancel.
3. Split customers: the same customer exists in the store CRM, the website, and the marketplace — with three different order histories.
4. No single source of truth: at the end of the month, three teams produce three different “inventory” numbers.

What Mera unifies

One catalog — every channel reads the same product, price, and availability. Change once, propagate everywhere.

One inventory — a single ledger for store stock, website stock, and marketplace listings. Marketplace listings update automatically; no overselling across channels.

One customer — identity resolution merges store, web, and marketplace activity into a single record. A customer who browsed online, bought in-store, and ordered on the marketplace is one person — with one history.

One order pipeline — orders from every channel flow into the same state machine. Allocation, picking, dispatch, and returns behave identically whether the order came from the store, the website, or the marketplace.

The workflow in practice

1. A customer orders a sofa on the marketplace.
2. Mera checks combined store + warehouse availability, allocates, and routes fulfillment to the nearest location.
3. The store picks and dispatches using the same scanner used for store sales.
4. The customer’s record merges across channels.
5. A return initiated in-store flows back through the same pipeline — no phone calls.

The result

• One source of truth — three teams, one set of numbers.
• Overselling gone — channels share the same ledger.
• Customer value unlocked — one history enables retention programs that were impossible with split records.
• Operations, not firefighting — the team works the business instead of reconciling it.

The stack

Before	With Mera
Store + web + marketplace (separate)	One catalog + inventory core
Three pricing efforts	Single source of truth
Split customer records	Unified customer identity
Manual cross-channel reconciliation	Automatic