Use this article to test your Ingrid Transport setup, pass the carrier and Ingrid approval gate, and go live with Ingrid Transport on production.
This article is for merchants, operations teams, and technical leads finishing an Ingrid Transport implementation. Ingrid Transport testing and go-live are phases 4 and 5 of your Ingrid Transport implementation. You lead both. Ingrid supports, helps resolve what you find, and runs hypercare alongside you after launch.
Phase 4: Ingrid Transport testing
Ingrid Transport testing has a characteristic the other Ingrid products do not: it ends with the carrier's approval, not Ingrid's. Labels have to be acceptable to the carrier who will scan them, so Ingrid Transport testing is not complete until each carrier has confirmed what you are producing.
Test Ingrid Transport thoroughly across every shipping product. A booking flow that works for one carrier tells you very little about the next one.
What to verify during Ingrid Transport testing
Every shipping method, end to end: from transport order through to a generated label, for each carrier product in scope. Not a sample.
The integration and booking flow behave as expected, including what happens when a booking fails and your automated booking rules fall through to the next option.
Booking requests, responses, and labels are captured and shared with each carrier for confirmation.
Label output is correct: size, format, fonts, and the information printed on it. Confirm this with each carrier contact individually rather than assuming a label that looks right is right.
Customs declarations for any product shipping beyond the EU (European Union). See Customs declarations.
Multi-parcel bookings, where your orders ship in more than one package.
Test Ingrid Transport with real bookings. Carriers differ in what they accept and what they return, and some problems only appear against a live carrier account. Plan for verification bookings before you switch volume across to Ingrid Transport.
The Ingrid Transport approval gate
Two sign-offs close Ingrid Transport testing, in this order:
Each carrier approves the shipments and labels you have produced.
Ingrid then confirms you are cleared to use Ingrid Transport fully on production.
Until both sign-offs have happened, treat Ingrid Transport on production as verification rather than live operation.
Phase 5: Ingrid Transport go-live
Ingrid Transport go-live covers the following steps:
Replicate your configuration into staging. Ingrid copies your carriers, booking rules, and templates across before launch, so from go-live onward you have a configured staging environment to test changes in. Production and staging do not sync, so this is a deliberate copy.
Choose your rollout shape. Roll out all carriers and markets at once, or a subset first. Ingrid Transport is often a good candidate for phasing, because carrier-by-carrier verification is naturally sequential. See Big bang or phased.
Switch volume across. You lead the cutover to Ingrid Transport.
Hypercare. Ingrid runs hypercare alongside you afterward. Hypercare matters more for Ingrid Transport than for other Ingrid products: label and booking problems surface at volume, against real carrier systems, on working days.
Handover. When hypercare ends, the Ingrid Customer Success and Support teams become your ongoing contacts, and your own Ingrid administrator owns the booking rules from there.
What Ingrid Transport go-live produces
When Ingrid Transport go-live is complete, you have:
Every carrier product booking correctly on production, with carrier-approved labels
A configured staging environment for testing future Ingrid Transport changes
Booking rules your own team can change without a ticket
A warehouse workflow that runs the way it did before, with Ingrid Transport deciding what goes on the label