“Shipping integration is complete” sometimes means only that a label can be printed. Customers care about the right products reaching the right address and understanding the order's progress. Without clear relationships between orders, parcels, carriers and notifications, the integration can remain incomplete. Scope the workflow from preparation through delivery exceptions.
Define when a shipment is allowed to begin
Creating an order does not mean every business should immediately create a shipment. Payment checks, stock preparation or address verification may come first. Document the status that triggers shipping and which system makes that decision.
Make manual operational steps visible too. Generating a label before an order is prepared may trigger an early customer message. Agree whether “shipped” refers to label creation or the actual handover to the carrier. Those events should not silently share a meaning.
Distinguish an order from its parcels
An order may leave in several parcels or from different warehouses. If nobody knows which items a tracking number covers, a customer receiving one parcel may assume the whole order has arrived. Preserve the relationship between parcels and order lines.
Imagine two items dispatched on different days. The first tracking message should explain that the shipment is partial, with separate information for the second parcel. This hypothetical journey should not mark the entire order delivered after the first package arrives. Include it in basic integration testing.
Map responsibility across the systems
For each step, identify the source and the evidence that verifies the result. Check supported fields with the selected shipping provider separately.
| Step | Relationship required | Verification |
|---|---|---|
| Preparation | Order, payment and stock status | Unready records do not trigger dispatch |
| Parcel creation | Order lines and parcel identifier | The intended items belong to the parcel |
| Label | Address, carrier and shipment | The label matches the actual package |
| Tracking | Parcel and tracking number | The customer opens the correct shipment |
| Notification | Status and message timing | The message does not claim an event too early |
| Exception | Cancellation, address issue or return | The responsible team sees the action record |
Verify how tracking information returns
Shopify's order-tracking guidance explains how tracking information can support status pages and notifications. With third-party fulfilment, the way it is added depends on the integration. Do not assume every provider automatically supplies the same tracking detail.
Make the source and freshness of customer-facing status understandable. Avoid a definitive delivery claim when the carrier has not supplied the relevant update. Support staff should see the same underlying record so customers do not receive contradictory explanations through different channels.
Test exceptions and repeated processing
Prepare cases for label cancellation, repeated shipment processing, address corrections and partial dispatch. Check whether a retry creates a second shipment or notification. Verify the behaviour during acceptance testing instead of leaving it as an assumption about the system.
Assign an owner and review process for failed transfers after launch. Integration should connect the order accurately with physical parcel movement as well as reduce manual entry. Customer messages belong to that verified workflow.