Connect Commercetools with Shippo to rate-shop carriers, generate shipping labels, sync tracking back to orders, and cut manual fulfillment work across channels.
• Order and address data is read from the commercetools API and mapped to Shippo shipment fields, including recipient, parcel, and service level inputs.
• Shipment creation is triggered on order state changes or fulfillment events, with idempotency keys preventing duplicate Shippo transactions.
• Purchased label metadata (label URL, tracking number, carrier, rate, and cost) is stored back on the commercetools order as custom fields and/or shipment references.
• Tracking status webhooks from Shippo are validated and translated into commercetools shipment and delivery updates, keeping order state in sync.
• Carrier service codes and shipping methods are mapped with fallback handling when a requested service is unavailable for a destination or parcel.
• Errors, retries, and partial failures are logged per order and shipment, with correlation IDs linking commercetools resources to Shippo objects.
.png)
We use the Commercetools API to push order and address data into Shippo, then return label IDs and shipment details to the order. The flow can run on events (order paid, ready to ship) or via your fulfillment UI.
Yes, Shippo tracking numbers and status updates can be written back to Commercetools as shipping info and order state updates. This keeps tracking visible in the same order timeline your team and customers rely on.
Typical mapping includes ship-from and ship-to addresses, parcel dimensions, weight, service level, and customs fields when needed. We also validate formats to reduce label errors and carrier rejections.
Yes, we can route orders to the right warehouse, select the correct ship-from origin, and apply carrier and service rules per location. This works well for split shipments and region-specific carrier setups.
We build with retries, idempotency keys, and queue-based processing to prevent duplicate labels and missed tracking. scandiweb has delivered 2,100+ eCommerce projects since 2003, so we design integrations for real-world ops, not happy-path demos.














