Logistics Integrations
A logistics integration connects Order Management System to a third-party logistics (3PL) provider — the company that stores and ships your physical goods. Integrations power the file-based fulfillment round-trip and, where supported, fully automatic fulfillment.
Supported providers
| Capability | ShipBob | NextSmartShip |
|---|---|---|
| Order export format | ✓ | ✓ |
| Bulk fulfill format | ✓ | ✓ |
| Automatic fulfillment | ✓ | — |
Automatic fulfillment is currently available for ShipBob. Support for automatic fulfillment with NextSmartShip is planned. See Automatic Fulfillment for how submitted orders flow to your provider and come back fulfilled.
Completing the auto-fulfillment setup
After you create an integration with auto-fulfillment enabled (Settings > Integrations in the Orders view), its detail page shows a Webhook URL with a copy button. Shipment updates flow back through this webhook — it is how Order Management System learns that the provider shipped an order and records the fulfillment with its tracking details.
To connect the webhook:
- Copy the Webhook URL and register it as a webhook endpoint in your provider's system.
- The provider issues a signing secret for that webhook. Copy the secret from the provider's webhook settings.
- Paste it into the integration's Webhook Secret field in Order Management System and save.
Order Management System uses the secret to verify that incoming shipment updates genuinely come from your provider.
Product mappings
When you export orders in a provider's format, each item in the file must reference a product the provider can find in its own catalog. Each provider matches products by a different value:
- ShipBob matches by product name — the offer name in Order Management System must match the product name in your ShipBob catalog.
- NextSmartShip matches by SKU — the offer SKU must match the product SKU in NextSmartShip.
Without product mappings, exports use these values as-is: items are referenced by offer name for ShipBob and by SKU for NextSmartShip.
If your offer names or SKUs do not match the provider's catalog, add product mappings on the integration's detail page. A mapping links an offer SKU to the value the provider expects — a ShipBob product name or a NextSmartShip SKU — and exports then use the mapped value instead.