How should an international fulfilment workflow be designed?
First decide the destination countries, products, delivery promise, and return responsibility. Then select direct shipping, an overseas warehouse, or marketplace fulfilment. Only after that should the order system integrate rates, labels, customs data, tracking, inventory, and after-sales states. Building an abstract “logistics module” first can produce software that tracks a number but cannot fulfil a real order.
The route for the same product can change with weight and dimensions, customs description, destination, battery or dangerous-goods status, and who bears duties. Wavesteam turns confirmed fulfilment rules into order, inventory, and integration behaviour and validates them with real parcels. The carrier, declarant, and relevant advisers remain responsible for transport eligibility, customs classification, and destination tax.
| Model | Best fit | Advantage | Cost and risk |
|---|---|---|---|
| Per-order origin-country shipping | Testing a market, many SKUs, low or uncertain volume | No advance overseas stock and low exit cost | Longer variable delivery, higher unit and return cost |
| Express direct shipping | High-value, time-sensitive, manageable parcel volume | Clearer tracking and transit | Remote-area, volumetric, customs, and duty additions |
| Third-party overseas warehouse | Stable orders and predictable bestsellers in one market | Faster local delivery and local returns | Stock capital, storage, obsolescence, counts, transfers |
| Marketplace fulfilment | Orders concentrated on one commerce platform | Tight marketplace, warehouse, and support workflow | Platform rules, fees, stock constraints, limited cross-channel control |
Do not generalize that every Western market needs a warehouse or every Southeast Asian market suits direct shipping. Compare one SKU to one destination using landed cost: inbound purchase and freight, duties and import tax, customs service, storage, pick/pack, last mile, failed delivery, return, disposal, and tied-up capital, alongside promised time and successful delivery. There is no universal order threshold for a warehouse.
When evaluating overseas entities, channels, and compliance paths, also compare Should an international product host its servers and data in China or overseas? and How does a cross-border ecommerce site differ from a domestic store?; the linked guidance adds context that should be considered in the same decision.
Preserve a traceable fulfilment chain
Product data needs weight, dimensions, origin, customs description, candidate HS code, battery or dangerous-goods status, and sales restrictions. The order captures validated address, service level, duty treatment, carrier product, and quotation snapshot. Shipment records retain label, tracking number, raw carrier events, normalized state, and estimated delivery. Returns connect refusal, loss, return warehouse, resale, or disposal. Every rate and rule needs a version so finance can explain historical charges.
Carrier APIs expose quotation, shipment creation, labels, and tracking but use different fields and states. DHL's Shipment Tracking API still requires the client system to map carrier events, handle polling or push, deduplicate, flag long silence, and correct terminal outcomes. An aggregator reduces initial integrations but adds dependency; a direct integration offers deeper capability with separate authentication and exception maintenance.
Checkout must state whether price includes import charges, who acts as importer, and what happens when a recipient refuses duty. The EU's IOSS is a specific simplification for eligible imported distance sales—not every parcel. Current European Commission guidance describes conditions including consumer sales of non-excise goods dispatched from outside the EU and not exceeding EUR 150. Store the rule source and effective date and keep a human review route instead of embedding eligibility permanently.
Wavesteam starts with the best-supported destination, representative products, and service levels. Real-order tests cover normal and remote addresses, oversize or incomplete address, batteries where relevant, split/combined shipments, cancellation, loss, and return. We reconcile quoted versus invoiced cost, pickup-to-delivery time, event completeness, first-attempt delivery, support contacts, loss/damage, and contribution margin against carrier invoices, warehouse stock, and customer receipt.
The first deliverable is a country–SKU–fulfilment matrix, followed by carrier adapters, a state dictionary, cost snapshots, and exception work. Before stable real demand exists, a third-party warehouse system or manual route approval can be safer than custom automatic routing.