---
title: "Transport: scoping"
canonical: "https://ingrid-support.refined.site/space/KB/11436087/Transport%3A%20scoping"
format: markdown
---
Scoping is phase 1 of your [Transport implementation](https://support.ingrid.com/space/KB/444039173/Transport+implementation). **Ingrid leads it.**

The purpose is to establish which carriers you will book on, where booking requests come from, and who holds the credentials that make any of it possible.

> ⚠️ **Start with carrier credentials.** Transport books on your own carrier contracts, so your credentials are always required and there is no fallback — nothing can be booked or even tested without them. They are frequently held by a 3PL or logistics team rather than your e-commerce team, which is why this belongs in week one and not week nine. See [Carrier credentials](https://support.ingrid.com/space/KB/739868692/Carrier+credentials).

## The SoW and the planning workshop

Two things shape scoping, and they do different jobs.

Your **statement of work** sets the high-level scope and the boundaries of the project — what is in, and what is not. It is the reference point whenever a scope question comes up later.

The **planning workshop** works through the finer detail: 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.

> ℹ️ **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 workshop — they are usually the strongest constraint in the room.
> ℹ️ 
> ℹ️ For Transport specifically, implementing alongside Ingrid Checkout removes work: bookings can then be made with just the transport order ID. Worth factoring into the order you implement in.

## Three things to settle here

1. **Which carrier products you will book.** List them per market. Check the [carrier library](https://carrier.ingrid.com) for what is already integrated, and the [supported carrier products reference](https://developer.ingrid.com/carriers/supported_carrier_products.html) for what supports booking specifically — integration and bookability are not the same thing.
2. **Where bookings come from.** Your WMS or ERP in most cases, occasionally your e-commerce platform, or manually in the platform to begin with. This determines the shape of phase 3.
3. **Whether Ingrid Checkout is also in scope.** If it is, 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

- 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
- Any fixed dates — contract renewals, peak periods, replatforming milestones
- Your project team, named, with owners — see [The team you'll need](https://support.ingrid.com/space/KB/741081090/The+team+you+ll+need). For Transport, the Ingrid administrator is usually an operations person rather than an e-commerce one

## What Ingrid does

- Explains how Transport works and how we run 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
- Provides technical documentation and integration support

## What scoping produces

- An agreed carrier and booking setup
- 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 products are in scope, an agreed order to implement them in

## Next

[Phase 2: Transport configuration →](https://support.ingrid.com/space/KB/11534421/Transport+configuration)