The Tech Stack Powering Modern Ecommerce Fulfilment
A fulfilment operation runs smoothly only when four distinct software layers talk to each other correctly, and most operational failures trace back to the join between two layers rather than a failure within any single system. This piece names the four layers, where the integration points break, and what a growing brand should build against an API versus simply buying off the shelf.
What Are the Four Layers of a Modern Fulfilment Stack?
A fulfilment operation depends on a warehouse management system tracking physical inventory location and movement, an order management system coordinating orders across every sales channel a brand uses, carrier APIs handling shipping label generation and tracking data, and customs and tax systems managing the compliance data required for cross-border orders.
Gonini and providers like it have built their operational advantage largely by making these four layers integrate cleanly, since a brand trying to stitch together separate systems from different vendors often finds the integration work itself harder and more error-prone than any single layer’s core functionality.
Each layer performs a distinct job, and understanding where one layer’s responsibility ends and the next begins reveals where integration problems tend to originate.
- Warehouse management system: tracks exactly where inventory physically sits and manages pick, pack, and stock movement within the warehouse itself
- Order management system: aggregates orders from every sales channel, whether that is a brand’s own site, a marketplace, or a wholesale portal, into a single processing queue
- Carrier APIs: generate shipping labels, retrieve live rates, and provide tracking data back to the customer once a package leaves the warehouse
- Customs and tax systems: manage VAT calculation, IOSS documentation, and the compliance data required for any order crossing an international border
That numbered list covers what each layer does in isolation, but a stack rarely fails at any one layer. It fails at the seams between them, which is where the next section picks up.
Where Do the Integration Points Actually Break, and Why?
The single most common failure point sits between the order management system and the warehouse management system, specifically around inventory synchronisation. An order accepted by the OMS before the WMS has confirmed actual stock availability produces the frustrating scenario where a customer receives an order confirmation for an item that turns out to be out of stock, a failure that damages trust disproportionately relative to how small the underlying technical gap actually is.
A second common break point sits between the carrier API and the customs system on international orders specifically, where a shipping label gets generated before the customs documentation is fully attached, resulting in a package that ships but then stalls in customs processing because the required data never made it into the carrier’s system correctly.
UK Tech News' coverage of Software AG’s webMethods B2B integration launch is worth reading as background on this exact class of integration problem, though it is an older piece worth treating as historical context on B2B integration challenges rather than a current product reference.
What Should a Brand Build Against an API Versus Simply Buy?
Not every part of this stack is worth building custom, and knowing what to buy versus build saves considerable time and reduces the surface area for the integration failures described above.
Buying off the shelf makes sense for carrier integration, since carrier APIs are standardised and well documented, and for core WMS functionality, since building warehouse management software from scratch duplicates work that established providers have already refined over years of operation. Building custom integration makes more sense at the specific join points between systems, the exact place where off-the-shelf products from different vendors need to communicate, since this is where a brand’s specific business rules and edge cases actually live.
Where Does Customs and VAT Data Actually Live Within the Stack, and Why Does It Matter?
VAT and customs data cannot sit as an afterthought bolted onto the order management system late in the process. It needs to be captured and validated early enough in the order flow that the customs system has everything required before a shipping label ever generates, since retrofitting this data after the fact is exactly what produces the stalled-in-customs failure described above.
The UK government’s guidance on the VAT Import One Stop Shop scheme lays out precisely what data needs to be captured and when, useful reference for any brand designing or auditing how their own stack handles this specific data flow.
FAQ
What are the four core layers of a modern ecommerce fulfilment tech stack?
A warehouse management system, an order management system, carrier APIs, and customs and tax systems each handle a distinct responsibility, and most operational problems trace back to the integration points between these layers rather than a failure within any single one.
Where do fulfilment tech stacks most commonly break down?
The join between order management and warehouse management systems is the most common failure point, particularly around inventory synchronisation, followed closely by the join between carrier APIs and customs systems on international orders.
Should a brand build its own warehouse management system?
Generally no. Established WMS providers have refined this functionality over years, and building from scratch duplicates work already solved well. Custom development should focus on specific integration points between systems rather than core functionality.
Why does customs and VAT data need to be captured early in the order flow?
Capturing this data late, after a shipping label has already been generated, is what causes shipments to stall in customs processing. Building it into the earliest stages of the order flow ensures the customs system has everything it needs before the package ships.
