Case study · Warehouse integration

Moving a multi-warehouse retailer onto an enterprise WMS without stopping order intake.

A long-time e-commerce client had outgrown the warehouse tools built into its custom storefront. We connected the storefront to an enterprise warehouse management system and switched over in a single morning, with customer orders coming in the whole time.

  • About 6 monthsFrom kickoff to go-live
  • One morningCutover window
  • No pauseIn customer order intake

The situation

The client is a national online retailer that ships from more than one warehouse. We have built and maintained its custom Ruby on Rails and Solidus storefront for more than a decade, including the shipping, inventory, and fulfillment logic behind it.

That homegrown warehouse logic had served the business well, but the operation had grown past it. The company chose an enterprise warehouse management system (WMS) to run its warehouses, and the storefront needed to work with it.

The catch was timing. The storefront takes orders around the clock, and shutting down order intake for a cutover weekend was not an option.

What we did

  • Mapped every flow first. Before writing integration code, we traced how orders, inventory, and shipments moved between the storefront, the warehouses, and the carriers, including the exceptions staff handled by hand.
  • Built the integration into the storefront. Orders flow from the storefront to the WMS, and inventory levels and shipment updates flow back, so customers and staff see accurate stock and tracking.
  • Left the existing process running. The current fulfillment path kept working while the integration was built and tested, so nothing changed for customers or warehouse staff until go-live.
  • Kept the cutover small. Go-live was planned as a short, specific sequence of steps rather than a big switch-over weekend.

Go-live

On the morning of go-live, current storefront data was pushed into the WMS and the warehouses switched over. Customers kept placing orders throughout, and those orders went straight into the new system.

The result

The warehouses now run on an enterprise WMS, and the storefront and WMS stay in sync without manual re-entry. The project went from kickoff to go-live in about six months, and the client’s management and warehouse team were pleased with how smoothly the switch went.

Why it worked

Most of the risk in a warehouse migration comes from what nobody wrote down: the special cases, manual workarounds, and assumptions buried in old code. Having maintained this platform for years, we already knew where those were. That made it possible to plan a cutover measured in hours instead of days.