---
title: "Transport: configuration"
canonical: "https://ingrid-support.refined.site/space/KB/11534421/Transport%3A%20configuration"
format: markdown
---
Configuration is phase 2 of your [Transport implementation](https://support.ingrid.com/space/KB/444039173/Transport+implementation). **It is joint work** — you bring your carrier setup and booking rules, we configure them with you and coach your team to run it afterward.

> ⚠️ **Your carrier credentials are a hard gate here.** Transport books shipments on your own carrier contracts, so your credentials are always required — and unlike Checkout and Tracking, there is no reduced mode to launch with. Nothing can be booked without them, and nothing can be tested either. If they sit with your 3PL, securing their release is your first action. See [Carrier credentials](https://support.ingrid.com/space/KB/739868692/Carrier+credentials).

## What gets configured

All configuration happens in the Ingrid Merchant Platform.

1. **Carriers and carrier products** — the services you will book on, activated with your credentials. See [Carrier credentials in Ingrid](https://support.ingrid.com/space/KB/591200257/Carrier+credentials+in+Ingrid). Note that [some carrier products need an additional schedule-pickup call](https://support.ingrid.com/space/KB/11469088/Carrier+products+with+an+additional+schedule+pickup+call), which affects how bookings are made.
2. [Automated booking rules](https://support.ingrid.com/space/KB/536838152/Automated+booking+rules) — the logic that picks a carrier per shipment, and falls through to the next option when one fails. This is where you encode whether you optimize for cost, delivery accuracy, or sustainability.
3. [Shipment templates](https://support.ingrid.com/space/KB/11469053/Shipments+templates) — reusable settings that pre-fill the booking flow, for teams doing manual bookings.
4. [Addresses](https://support.ingrid.com/space/KB/11469063/Addresses) — saved sender and recipient addresses that can be reused across bookings.
5. [Multi-parcel shipments](https://support.ingrid.com/space/KB/537329665/Multi-parcel+shipments), if your orders ship in more than one package — each parcel can carry its own weight, dimensions, and line items.
6. **Shipping-method mapping**, if you are not passing a TOS ID from Ingrid Checkout. Whatever your systems call a shipping method has to map to the carrier product's name in Ingrid. Agree this now rather than during testing — mismatches here are a common cause of failed bookings.

### For your warehouse team

Two settings worth configuring before go-live, because they shape daily work rather than the launch:

- [User tags](https://support.ingrid.com/space/KB/11502029/User+tags) — for teams sharing responsibilities across shifts.
- [Watchlist](https://support.ingrid.com/space/KB/11469175/Watchlist) — so a person or group can follow specific shipments by status event.

## What you bring

- **Your carrier contracts and credentials**, released and available
- **Your booking logic** — which carrier should win, under what conditions
- **The people who will own it** — your Ingrid administrator trains during this phase, and for Transport that is usually someone in operations rather than e-commerce

## What Ingrid does

- Sets up your account to reflect your requirements
- Configures carriers and booking rules with you
- Reviews any customization beyond the standard configuration
- Coaches your team so they can change rules themselves afterward

## Where to configure

Configure in **production**. Changes are held as drafts until you publish.

Before go-live, Ingrid replicates your configuration into **staging**, so from launch onward you have a configured staging environment to test changes in. The two environments do not sync, so this is a deliberate copy.

For Transport there is an extra consideration: because bookings run on your real carrier contracts, some verification can only be done against live carrier accounts. Phase 4 covers that.

## Next

[Phase 3: Transport integration →](https://support.ingrid.com/space/KB/11501609/Transport+integration)