Getting Started as a Forwarder
Stand up a forwarder organization in chrt and run your first multi-leg shipment.
Stand up a forwarder organization in chrt and run your first multi-leg shipment.
This guide walks a freight forwarder through the smallest path from sign-up to a multi-leg shipment in motion. By the end you will have a forwarder organization on chrt, a customer connected, a courier network you can dispatch to, a default rate sheet, and your first order built and assigned.
You need:
chrt routes provider sign-ups through subscription checkout before dropping you in the app. Complete checkout to land on the activation checklist.
A forwarder org typically has dispatchers, ops coordinators, and finance people. Invite them now so they can pick up work as it comes in.
See Add an organization member for role definitions and the full invite flow.
A customer is a shipper you forward for. If the shipper is already on chrt, search the directory and connect. If not, record them as an off-platform shipper so you can still build orders that reference them.
See Add a customer for the full flow.
Forwarders need couriers at both ends of every multi-leg shipment. Use the same connections flow to link up with the couriers you dispatch to.
See Managing your courier network for the full network playbook and how to keep partner detail pages current.
A rate sheet defines what work costs and what you’ll earn. As a forwarder you’ll likely want at least two: one for what you charge a shipper, and one for what each of your couriers charges you.
See Set up a rate sheet for the detailed walkthrough.
Forwarders place orders from the same draft builder as shippers, with the multi-leg segments and flight tooling enabled.
Once submitted, the order moves to Staged and each ground task group goes
out to the assigned courier to accept. You’ll see the order at
/orders/<order-ref> with the live map, timeline, and task progress.
Set up notifications early. You want dispatch alerted on driver-assigned, task-completed, and exception events from day one — not after the first shipment slips through.
Configure who on your team hears about which events. Open Notification settings and create groups for dispatch, ops, and finance. Subscribe each group to the relevant events (order staged, courier assigned, task completed, flight arrival, invoice opened) on the right channels (email, SMS, push).
For system-to-system integrations into your TMS, enable webhooks and configure endpoints to receive the event payloads.