Why OMS change became unavoidable
La Vie en Rose’s legacy OMS was not failing in subtle ways. It was failing in predictable ways under peak conditions.
Throughput ceiling
The homegrown system could not process more than 300 transactions per hour.
Queue backlog
When volume exceeded capacity, transactions moved into a queue, hour after hour. Champagne walked through the math: If 500 transactions arrive in an hour and only 300 are processed, the next hour begins with 200 already waiting. Over a full peak day, that backlog can stretch into days.
Inventory distortion and cancellations
The queue did not only delay processing. It unbalanced inventory, because the system could not recognize that queued items were already sold. That led stores to chase inventory that was no longer there and forced the business to cancel orders after the fact.
Blunt fulfillment logic
The legacy environment also made it harder to integrate regional fulfillment logic and prevent cross-country shipping that inflated cost and slowed delivery. For a high-promotion business, those gaps compound quickly at peak.
The principles behind the selection
When la Vie en Rose committed to replacing its homegrown OMS, Champagne insisted the selection process be business-led and disciplined. The goal was to find a system that could handle peak pressure, protect inventory integrity and support the omnichannel experience the business was already trying to deliver.
That discipline showed up early in the RFP. Champagne estimated the team documented “between 600 and 700 lines” of requirements. Then they tested vendors against those requirements through demos and due diligence, treating every claim as something that had to hold up under real-world scenarios.
The five non-negotiable categories
Inventory thresholds by SKU
One of the first requirements Champagne outlined was the ability to set availability thresholds at the SKU level. The idea was simple: Do not promise inventory that cannot be fulfilled. If the OMS cannot reflect real-time conditions and enforce clear rules about what is sellable, every downstream decision becomes reactive.
Regional routing logic
La Vie en Rose needed regionality embedded into fulfillment logic so the business could stop shipping across the country unnecessarily. Under the legacy environment, the system tended to allocate orders to the store with the most inventory rather than making smarter location decisions. Over time, that translates into higher shipping cost, slower delivery and more store friction.
Capacity that could be stress-tested
Capacity was the breaking point for the legacy system, so the replacement had to perform at a different level altogether. Champagne described a target of processing more than 2,000 transactions per hour during Black Friday-level demand. That benchmark was a practical stress test designed to eliminate the “queue problem” that had been distorting inventory and driving cancellations.
A SaaS foundation with strong SLAs and integration readiness
From a governance standpoint, Champagne wanted the reliability and security expectations that come with a mature SaaS platform, supported by strong service levels. He also stressed the need for a portfolio of APIs, particularly to connect with carriers and the broader retail stack.
POS alignment and transactional complexity
Finally, the OMS had to integrate cleanly with the store environment and handle the realities of la Vie en Rose’s transactions. That included correct tax calculation and the ability to support promotion-heavy baskets, including buy-one-get-one structures and multiple promotions applied to the same bill.
