---
title: "Transport implementation"
canonical: "https://ingrid-support.refined.site/space/KB/444039173/Transport%20implementation"
format: markdown
---
Implementing Ingrid Transport follows the same [five phases](https://support.ingrid.com/space/KB/18219063/Implementation) as any Ingrid project. This page covers what is specific to Transport: the credentials constraint, where bookings come from, and how much cheaper it gets alongside Checkout.

## The phases for Transport

| Phase | Who leads | What it covers for Transport |
| --- | --- | --- |
| [1. Scoping](https://support.ingrid.com/space/KB/11436087/Transport+scoping) | Ingrid | Which carrier products you will book, where booking requests come from, and who holds your carrier credentials. |
| [2. Configuration](https://support.ingrid.com/space/KB/11534421/Transport+configuration) | Joint | Carriers and credentials, automated booking rules, shipment templates, addresses, and shipping-method mapping. |
| [3. Integration](https://support.ingrid.com/space/KB/11501609/Transport+integration) | You | Connecting your WMS, ERP, or e-commerce platform so bookings reach Ingrid. |
| [4–5. Testing and go-live](https://support.ingrid.com/space/KB/11436104/Transport+testing+and+go-live) | You | Booking on every carrier product, getting labels approved by each carrier, then moving to production. |

## The one constraint to plan around

> ⚠️ **Transport has no fallback for carrier credentials.** Bookings run on your own carrier contracts, so your credentials are always required — for every carrier, in every market. Unlike Checkout and Tracking, there is no reduced mode that lets you launch while you wait: nothing can be booked, and nothing can be tested.
> ⚠️ 
> ⚠️ Credentials are frequently held by a 3PL or logistics team rather than the e-commerce team running the project. Finding out who owns them, and starting the release request, is the single most useful thing you can do in week one. See [Carrier credentials](https://support.ingrid.com/space/KB/739868692/Carrier+credentials).

## Where bookings come from

Transport sits at fulfillment rather than checkout, so it usually integrates with a back-office system:

- **Your WMS or ERP** — the common case. Many already have an Ingrid integration.
- **Your e-commerce platform** — occasionally, in smaller setups.
- **Manually, in the platform** — a legitimate starting point, and one many merchants keep for exceptions after go-live. See [How to book a shipment](https://support.ingrid.com/space/KB/11501799/How+to+book+a+shipment+on+the+Ingrid+Merchant+Platform).

Ingrid generates the label and decides what goes on it. Your system prints it, the same way it does today — warehouse workflows do not need to change.

## Transport is cheaper alongside Checkout

If Ingrid Checkout is also in scope, a booking needs only the transport order ID and the number of parcels, because Ingrid already holds the delivery data chosen at checkout. Without Checkout, your systems send full shipping data and you also have to agree a shipping-method mapping.

This is worth knowing during scoping: implementing the two together removes work rather than adding it.

## Need help

- **During implementation:** your implementation consultant is your first contact.
- **Technical questions:** [support@ingrid.com](mailto:support@ingrid.com)
- **API reference:** [developer.ingrid.com](https://developer.ingrid.com/som/)