Use this article to plan your Ingrid Transport integration: what has to connect to Ingrid Transport, what data Ingrid needs to book shipments, and what you have to decide.
This article is for technical leads, developers, and system owners on an Ingrid Transport implementation. Ingrid Transport integration is phase 3 of your Ingrid Transport implementation. You lead it, and Ingrid guides you with documentation and the Ingrid integrations team.
Where to find developer details: this article explains what has to connect, what data Ingrid needs, and what you have to decide. Your developers will want developer.ingrid.com for Ingrid Transport endpoints, payloads, and code.
What connects to Ingrid Transport
Ingrid Transport sits where your fulfillment happens, so the Ingrid Transport integration is usually with a warehouse or back-office system rather than your storefront:
Your WMS (warehouse management system) or ERP (enterprise resource planning) system: the most common case. Many already have an Ingrid integration; otherwise your team or your vendor builds it.
Your e-commerce platform: occasionally, for smaller setups where the booking happens there instead.
For a WMS that Ingrid Transport already connects to, see Ongoing (WMS).
What data Ingrid Transport needs to book
The data you send to Ingrid Transport is the decision that shapes the integration work, and it depends on whether you also use Ingrid Promise.
Ingrid Transport booking data if you use Ingrid Promise
Pass the TOS ID, the transport order identifier created at checkout. Ingrid already holds the transport data, so an Ingrid Transport booking needs only the TOS ID and the number of parcels. You can still override any individual value by supplying it in the booking call.
This is significantly less integration work, and it is the main reason Ingrid Promise and Ingrid Transport are cheaper to implement together than separately.
Ingrid Transport booking data if you book from another source
If you do not use Ingrid Promise, you send the full shipping data to Ingrid Transport instead. One field needs particular attention: the shipping method has to be mapped from whatever your systems call it to the carrier product's internal name in Ingrid. Getting that mapping wrong is a common cause of failed bookings, so agree it during Ingrid Transport configuration rather than during testing.
How booking works in Ingrid Transport
Ingrid's shipment order management service handles booking and tracking of shipments, parcels, and deliveries.
Ingrid recommends the combined create-and-book approach unless you have an explicit reason to split booking into separate steps. Fewer calls, fewer states to handle, less to go wrong.
The full method list, request formats, and field reference for Ingrid Transport booking are in the developer documentation.
Booking manually in Ingrid Transport instead of integrating
Not every Ingrid Transport setup needs an automated integration. Shipments can be created and booked by hand in the Ingrid Merchant Platform. See How to book a shipment. Manual booking is a legitimate starting point, and some merchants keep it for exceptions long after go-live.
What Ingrid does during Ingrid Transport integration
Sets up your account to reflect your requirements
Guides the data flow between your systems and Ingrid
Reviews any customization beyond the standard Ingrid Transport integration
What you do during Ingrid Transport integration
Connect Ingrid to your stack, so communication works between your e-commerce platform, ERP, WMS, and the Ingrid API (application programming interface).
Agree the shipping-method mapping if you are not passing a TOS ID.
Run a first Ingrid Transport booking test, from order creation through to a generated label, to confirm the flow end to end.
Who you need for Ingrid Transport integration
Your technical lead owns Ingrid Transport integration, and the owners of your WMS, ERP, or OMS (order management system) need to be available from the start rather than consulted late. Integration delays are far more often about availability than difficulty.
