Use this article to implement Ingrid Transport: what each implementation phase covers for Ingrid Transport, the carrier credentials constraint to plan around, where bookings come from, and why Ingrid Transport is cheaper to implement alongside Ingrid Promise.
This article is for retailers implementing Ingrid Transport (carrier booking and labels), and for their logistics and technical teams. Implementing Ingrid Transport follows the same five implementation phases as any Ingrid implementation. This article covers what is specific to Ingrid Transport.
The implementation phases for Ingrid Transport
The table below shows each implementation phase for Ingrid Transport, who leads it, and what it covers:
Phase | Who leads | What it covers for Ingrid Transport |
Ingrid | Which carrier products you will book, where booking requests come from, and who holds your carrier credentials. | |
Joint | Carriers and carrier credentials, automated booking rules, shipment templates, addresses and shipping-method mapping. | |
You | Connecting your WMS (warehouse management system), ERP (enterprise resource planning) system or e-commerce platform so bookings reach Ingrid. | |
You | Booking on every carrier product, getting labels approved by each carrier, then moving to production. |
The one constraint to plan around: carrier credentials
Ingrid Transport has no fallback for carrier credentials. Ingrid Transport bookings run on your own carrier contracts, so your carrier credentials are always required, for every carrier, in every market. Unlike Ingrid Promise and Ingrid Engage, there is no reduced mode that lets you launch while you wait: without carrier credentials, nothing can be booked and nothing can be tested.
Carrier credentials are frequently held by a 3PL (third-party logistics provider) or logistics team rather than the e-commerce team running the project. Finding out who owns your carrier credentials, and starting the release request, is the single most useful thing you can do in week one. See Carrier credentials.
Where Ingrid Transport bookings come from
Ingrid Transport sits at fulfillment rather than checkout, so it usually integrates with a back-office system. Ingrid Transport bookings come from one of three places:
Your WMS or ERP: the common case. Many WMS and ERP systems already have an Ingrid integration.
Your e-commerce platform: occasionally, in smaller setups.
Manually, in the Ingrid Merchant Platform: a legitimate starting point, and one many merchants keep for exceptions after go-live. See How to book a shipment.
Ingrid generates the shipping label and decides what goes on it. Your system prints the label the same way it does today, so warehouse workflows do not need to change.
Ingrid Transport is cheaper to implement alongside Ingrid Promise
If Ingrid Promise is also in scope, an Ingrid Transport booking needs only the transport order ID and the number of parcels, because Ingrid already holds the delivery data chosen at checkout. Without Ingrid Promise, your systems send full shipping data, and you also have to agree a shipping-method mapping.
This is worth knowing during scoping: implementing Ingrid Transport and Ingrid Promise together removes work rather than adding it.
Getting help with your Ingrid Transport implementation
During implementation: your Ingrid implementation consultant is your first contact.
Technical questions: Iris, Ingrid's AI assistant, in the chat on the Ingrid Help Center. If you can't reach Iris, email [email protected].
API (application programming interface) reference: developer.ingrid.com