Use this article to scope your Ingrid Transport implementation: decide which carriers you will book on, where booking requests come from, and who holds the carrier credentials that make booking possible.
This article is for merchants and project teams starting an Ingrid Transport implementation. Ingrid Transport scoping is phase 1 of your Ingrid Transport implementation, and Ingrid leads it.
Start with carrier credentials. Ingrid Transport books on your own carrier contracts, so your carrier credentials are always required and there is no fallback. Nothing can be booked or even tested in Ingrid Transport without them. Carrier credentials are frequently held by a 3PL (third-party logistics provider) or a logistics team rather than your e-commerce team, which is why requesting them belongs in week one and not week nine. See Carrier credentials.
The statement of work and the planning workshop in Ingrid Transport scoping
Two things shape Ingrid Transport scoping, and they do different jobs.
Your statement of work (SoW) sets the high-level scope and the boundaries of the Ingrid Transport project: what is in, and what is not. The statement of work is the reference point whenever a scope question comes up later.
The planning workshop works through the finer detail of the Ingrid Transport project: who does what, in what sequence, and what depends on what. This is where the scope becomes a dated plan with named owners on both sides.
Implementing more than one Ingrid product: if you are implementing more than one Ingrid product, sequence matters and it is rarely arbitrary. A contract renewal with an existing provider, a peak trading period, or a replatforming date can all force one product to go live before another. Bring those dates to the planning workshop, because they are usually the strongest constraint in the room.
For Ingrid Transport specifically, implementing alongside Ingrid Promise removes work: bookings can then be made with just the transport order ID. This is worth factoring into the order you implement Ingrid products in.
Three things to settle during Ingrid Transport scoping
Which carrier products you will book with Ingrid Transport. List them per market. Check the carrier library for what is already integrated, and the supported carrier products reference for what supports booking specifically. Integration and bookability are not the same thing.
Where Ingrid Transport bookings come from. In most cases, bookings come from your WMS (warehouse management system) or ERP (enterprise resource planning) system, occasionally from your e-commerce platform, or manually in the Ingrid Merchant Platform to begin with. This determines the shape of phase 3, Ingrid Transport integration.
Whether Ingrid Promise is also in scope. If Ingrid Promise is in scope, Ingrid Transport bookings can be made with just the transport order ID, which removes a substantial amount of integration work. If not, your systems send full shipping data and the shipping-method mapping has to be agreed.
What you bring to Ingrid Transport scoping
Your carrier products and delivery offerings, per market
Who holds each carrier's credentials, and whether they have been requested
Which system will send booking requests to Ingrid Transport
Any fixed dates, such as contract renewals, peak periods, and replatforming milestones
Your project team, named, with owners. See The team you'll need. For Ingrid Transport, the Ingrid administrator is usually an operations person rather than an e-commerce one
What Ingrid does during Ingrid Transport scoping
Explains how Ingrid Transport works and how Ingrid runs the project with you
Reviews your carrier products and flags any that need particular handling, such as those requiring an additional pickup call
Confirms what is needed per carrier to activate booking in Ingrid Transport
Provides technical documentation and integration support
What Ingrid Transport scoping produces
When Ingrid Transport scoping is complete, you have:
An agreed carrier and booking setup
Carrier credential requests in motion for anything held outside your team
A dated plan owned jointly by your team and Ingrid
Named owners on both sides
Where several Ingrid products are in scope, an agreed order to implement them in