---
title: "Transport: testing and go-live"
canonical: "https://ingrid-support.refined.site/space/KB/11436104/Transport%3A%20testing%20and%20go-live"
format: markdown
---
Testing and go-live are phases 4 and 5 of your [Transport implementation](https://support.ingrid.com/space/KB/444039173/Transport+implementation). **You lead both.** We support, help resolve what you find, and run hypercare alongside you after launch.

## Phase 4: testing

Transport testing has a characteristic the other products do not: **it ends with the carrier's approval, not ours.** Labels have to be acceptable to the carrier who will scan them, so testing is not complete until each carrier has confirmed what you are producing.

Test thoroughly across every shipping product. A booking flow that works for one carrier tells you very little about the next one.

### What to verify

1. **Every shipping method, end to end** — from transport order through to a generated label, for each carrier product in scope. Not a sample.
2. **The integration and booking flow behave as expected**, including what happens when a booking fails and your automated rules fall through to the next option.
3. **Booking requests, responses, and labels are captured** and shared with each carrier for confirmation.
4. **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.
5. **Customs declarations** for any product shipping beyond the EU. See [Customs declarations](https://support.ingrid.com/space/KB/11436337/Customs+declarations).
6. **Multi-parcel bookings**, where your orders ship in more than one package.

> ⚠️ **Test 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.

### The approval gate

Two sign-offs close this phase, in order:

1. **Each carrier approves the shipments and labels** you have produced.
2. **Ingrid then confirms** you are cleared to use Transport fully on production.

Until both have happened, treat production as verification rather than live operation.

## Phase 5: go-live

- **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. The two environments do not sync, so this is a deliberate copy.
- **Choose your rollout shape.** All carriers and markets at once, or a subset first. Transport is often a good candidate for phasing, because carrier-by-carrier verification is naturally sequential. See [Big bang or phased](https://support.ingrid.com/space/KB/740950018/Big+bang+or+phased).
- **Switch volume across.** You lead the cutover.
- **Hypercare.** Ingrid runs hypercare alongside you afterward. This matters more for Transport than elsewhere: label and booking problems surface at volume, against real carrier systems, on working days.
- **Handover.** When hypercare ends, our Customer Success and Support teams become your ongoing contacts, and your own administrator owns the booking rules from there.

## What go-live produces

- Every carrier product booking correctly on production, with carrier-approved labels
- A configured staging environment for testing future changes
- Booking rules your own team can change without a ticket
- A warehouse workflow that runs the way it did before, with Ingrid deciding what goes on the label