---
title: "Transport: integration"
canonical: "https://ingrid-support.refined.site/space/KB/11501609/Transport%3A%20integration"
format: markdown
---
Integration is phase 3 of your [Transport implementation](https://support.ingrid.com/space/KB/444039173/Transport+implementation). **You lead it** — we guide with documentation and our integrations team.

> ℹ️ This page explains **what has to connect, what data Ingrid needs, and what you have to decide**. Your developers will want [developer.ingrid.com](https://developer.ingrid.com/som/) for endpoints, payloads, and code.

## What connects to Transport

Transport sits where your fulfillment happens, so the integration is usually with a warehouse or back-office system rather than your storefront:

- **Your WMS or ERP** — the most common case. Many already have an Ingrid integration; otherwise your team or your vendor builds it.
- **Your e-commerce platform** — occasionally, for smaller setups where the booking happens there instead.

See [WMS integrations](https://support.ingrid.com/space/KB/18219133/WMS+integrations) for systems Ingrid already connects to, including [Ongoing](https://support.ingrid.com/space/KB/11436244/Ongoing+WMS).

## What data Ingrid needs to book

This is the decision that shapes the work, and it depends on whether you also use Ingrid Checkout.

### If you use Ingrid Checkout

Pass the **TOS ID** — the transport order identifier created at checkout. Ingrid already holds the transport data, so a booking needs only the TOS ID and the number of parcels. You can still override any individual value by supplying it in the booking call.

This is significantly less integration work, and it is the main reason Checkout and Transport are cheaper to implement together than separately.

### If you book from another source

You send the full shipping data instead. One field needs particular attention: **the shipping method has to be mapped** from whatever your systems call it to the carrier product's internal name in Ingrid. Getting that mapping wrong is a common cause of failed bookings, so agree it during configuration rather than during testing.

## How booking works

Ingrid's shipment order management service handles booking and tracking of shipments, parcels, and deliveries.

**We recommend the combined create-and-book approach** unless you have an explicit reason to split booking into separate steps. Fewer calls, fewer states to handle, less to go wrong.

The full method list, request formats, and field reference are in the [developer documentation](https://developer.ingrid.com/som/api/#som-api).

## If you book manually instead

Not every setup needs an automated integration. Shipments can be created and booked by hand in the Ingrid Merchant Platform — see [How to book a shipment](https://support.ingrid.com/space/KB/11501799/How+to+book+a+shipment+on+the+Ingrid+Merchant+Platform). Manual booking is a legitimate starting point, and some merchants keep it for exceptions long after go-live.

## What Ingrid does in this phase

- Sets up your account to reflect your requirements
- Guides the data flow between your systems and Ingrid
- Reviews any customization beyond the standard integration

## What you do

- Connect Ingrid to your stack, so communication works between your e-commerce platform, ERP, WMS, and the Ingrid API
- Agree the shipping-method mapping if you are not passing a TOS ID
- Run a first booking test — from order creation through to a generated label — to confirm the flow end to end

## Who you need for this phase

Your technical lead owns it, and the owners of your WMS, ERP, or OMS need to be available from the start rather than consulted late. Integration delays are far more often about availability than difficulty.

## Next

[Phases 4–5: Transport testing and go-live →](https://support.ingrid.com/space/KB/11436104/Transport+testing+and+go-live)