Use this article to configure Ingrid Transport: activate your carriers and carrier products, set up booking rules and templates, and prepare your team to run Ingrid Transport after go-live.
This article is for merchants, operations teams, and Ingrid administrators working through an Ingrid Transport implementation. Ingrid Transport configuration is phase 2 of your Ingrid Transport implementation. It is joint work: you bring your carrier setup and booking rules, and Ingrid configures them with you and coaches your team to run Ingrid Transport afterward.
Your carrier credentials are a hard gate for Ingrid Transport configuration. Ingrid Transport books shipments on your own carrier contracts, so your carrier credentials are always required. Unlike Ingrid Promise and Ingrid Engage, Ingrid Transport has no reduced mode to launch with. Nothing can be booked without carrier credentials, and nothing can be tested either. If your carrier credentials sit with your 3PL (third-party logistics provider), securing their release is your first action. See Carrier credentials.
What gets configured in Ingrid Transport
All Ingrid Transport configuration happens in the Ingrid Merchant Platform. You configure the following:
Carriers and carrier products: the services you will book on with Ingrid Transport, activated with your carrier credentials. See Carrier credentials in Ingrid. Note that some carrier products need an additional schedule-pickup call, which affects how bookings are made.
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 Ingrid Transport optimizes for cost, delivery accuracy, or sustainability.
Shipment templates: reusable settings that pre-fill the Ingrid Transport booking flow, for teams doing manual bookings.
Addresses: saved sender and recipient addresses that can be reused across bookings.
Multi-parcel shipments: if your orders ship in more than one package, each parcel can carry its own weight, dimensions, and line items.
Shipping-method mapping: needed if you are not passing a TOS ID from Ingrid Promise. Whatever your systems call a shipping method has to map to the carrier product's name in Ingrid. Agree this mapping during Ingrid Transport configuration rather than during testing, because mismatches here are a common cause of failed bookings.
Ingrid Transport settings for your warehouse team
Two Ingrid Transport settings are worth configuring before go-live, because they shape daily warehouse work rather than the launch:
What you bring to Ingrid Transport configuration
Your carrier contracts and credentials, released and available
Your booking logic: which carrier should win, under what conditions
The people who will own Ingrid Transport: your Ingrid administrator trains during this phase, and for Ingrid Transport that is usually someone in operations rather than e-commerce
What Ingrid does during Ingrid Transport configuration
Sets up your account to reflect your requirements
Configures carriers and booking rules with you
Reviews any customization beyond the standard Ingrid Transport configuration
Coaches your team so they can change booking rules themselves afterward
Where to configure Ingrid Transport: production and staging
Configure Ingrid Transport in production. Changes are held as drafts until you publish.
Before go-live, Ingrid replicates your Ingrid Transport configuration into staging, so from launch onward you have a configured staging environment to test changes in. Production and staging do not sync, so this is a deliberate copy.
For Ingrid 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, Ingrid Transport testing, covers that.