FAQ

A draft is an in-progress shipment you’re building in the draft builder — it isn’t live until you submit. An order is the submitted shipment that all parties can see and act on. A task group is one leg of an order assigned to one provider — a single-leg ground order has one task group, a ground + flight + ground shipment has three. See Orders for the full model.

Open chrt.com/orders/drafts/new, pick a forwarder or courier on the Order setup tab, add cargo, add segments and stops, then submit from the Preview tab. The Creating shipments guide walks through the draft builder tab by tab.

Yes — the AI order builder lives on the Order setup tab of a new draft and reads freeform text (emails, quotes, Slack threads) to populate cargo, stops, and segments. Review every field before you submit. See AI order builder.

Multi-leg orders use the Segments tab to chain a ground pickup, a flight, and a ground recovery (or any mix). For NFO, search the Flights tab with Next 6 hr to find the soonest commercial flight. See Multi-leg orders and Next flight out.

A record of a forwarder or courier who isn’t on chrt yet. You can still build orders that reference them — you just won’t get in-app dispatch and updates from them. See Off-platform providers.

Open the order at /orders/<order-ref> and switch to the Map tab. Once the driver taps Start driving in the driver app, you’ll see their location update live alongside the planned route. See Tracking shipments.

chrt derives the ETA from the driver’s live location plus Mapbox driving directions, with a small buffer between tasks. Flight legs use FlightAware actual / estimated / predicted / scheduled times in that priority order. See Tracking concept for the full calculation.

On the order, click Actions > Share tracking to generate a public link at https://chrt.com/orders/public/<order-ref>. Recipients see the live map without a chrt account. See Public tracking links.

For orders, yes — reopen the Share tracking dialog and turn off all segments. For standalone tracker sessions, no — once made public, the session stays public until you delete it. See Public tracking links.

The task group ran without a matching rate sheet. Confirm the connection has a default rate sheet, or attach one directly to the task group. See Rate sheets and Billing primitives.

Open the statement detail page, find the line item, and use the Adjust dialog to enter the delta and a short comment. Adjustments leave an audit trail. You can only adjust before the statement is paid — paid statements are immutable. See Billing.

A ledger groups statements over a defined billing period for one connection — useful for weekly or monthly rolling invoicing instead of settling one statement at a time. Open the period to roll outstanding statements into a consolidated invoice. See Billing.

You need a Stripe Connect account to receive payments through chrt’s payment processor. Shippers paying providers don’t need Stripe Connect to pay — chrt uses Stripe Checkout for that. Forwarders and couriers typically need it on both sides. See Billing for forwarders.

Three rate sheet kinds: Standard per-piece, Per-piece per-distance, and Per-piece per-pickup. The kind you pick depends on how you price work. See Rate sheets for field-by-field breakdowns.

Creating a shipper organization and connecting with a provider is free. You only pay for the shipments you place. Provider organizations (couriers and forwarders) go through subscription checkout during onboarding. See Getting started as a shipper.

Pricing details for provider subscriptions and trackers are at chrt.com. Contact hi@chrt.com if you need a custom plan.

The full reference lives under the API tab. Browse endpoints by domain — orders, tracking, billing, connections, devices — each with request and response schemas and code samples.

TypeScript, Swift, and Java SDKs are published from the API spec. See the SDKs page for install instructions and code samples in each language.

Enable webhooks at chrt.com/settings/webhooks, then configure an HTTPS endpoint and subscribe it to the event types you care about. Delivery is powered by Svix and includes signed payloads, retries, and a delivery log. See Notifications.

Drivers use the mobile app to receive assignments, share live location, complete stops, and capture proof of delivery (photos, signatures, barcodes). It’s available for iOS and Android — install from chrt.com/driver-app.

Drivers use the same invite flow as any other teammate. Open Members settings, click Invite user, and choose Member as the role — that’s the right role for anyone who only needs the driver app. See Add an organization member.

The Android driver app has full offline mode — drivers can accept, work, and capture POD without a connection, and changes sync when they come back online. iOS does not currently have offline mode.

Standalone trackers run their own tracking sessions, independent of any chrt order — good for one-off shipments or cargo on orders that live outside chrt. On-order trackers attach to cargo on a chrt order and show up alongside driver location on the order map. See Trackers overview.

By default a session ends after 3 days. You can pick a specific termination date, or choose No auto termination to keep recording until you stop it manually. Longer or open-ended sessions may incur additional charges. See Standalone trackers.

First pings typically appear within about 15 minutes. If nothing shows after 30 minutes, contact trackers@chrt.com. See Standalone trackers.

chrt does not sell trackers self-serve. Email trackers@chrt.com to request devices, ask about pricing, or check whether a specific model fits your operation.

Open Members settings, click Invite user, enter their email, and pick a role. Owner has full access; Admin manages members, settings, and billing; Operator is for dispatchers and coordinators; Member is for drivers and limited-access teammates. See Add an organization member.

Files are encrypted at rest with AES-GCM (256-bit), each with a unique key wrapped by a rotated main key. All traffic uses HTTPS with TLS 1.3 (TLS 1.2 supported for older browsers). See Security for the full breakdown.

We usually say “chart”, but “c-h-r-t” works too.

We ship bits and atoms, and the name has half its origin in each. In the world of atoms, “chrt” is short for “chart”, which originally meant “map for the use of navigators” in the 1500s. In the world of bits, chrt is the Linux command for manipulating the real-time scheduling attributes of a process.