Under the Hood — a series on how the platform actually works. Part 1 of 4.

From order to escrow to a carrier on the road

Here's a thing that sounds simple and almost never is: a buyer taps order, and somewhere a truck starts moving, money sits safely in the middle, and when the goods arrive everyone gets paid the right amount — automatically, without a human chasing three systems to make them agree.

Walk the chain the way the platform actually runs it:

1. A buyer reserves certified stock in the storefront.
2. Funds move into escrow — held, not paid. The seller can see the commitment; nobody can spend it yet.
3. The order becomes a consignment, and a carrier is dispatched by a deterministic engine that weighs distance, load and availability.
4. The carrier moves. The buyer follows live tracking the whole way.
5. On delivery, escrow releases to the seller, a commission is taken for the carrier, and the whole thing settles on the USN.

The point isn't any single step — payment processors do payments, courier apps do tracking. The point is that all of them are the same participants settling on the same network. There's no handoff to a separate payment rail, no separate logistics integration to reconcile at the end of the day. Reserve → accept → fulfil → release, with real money held in escrow for the entire journey.

Under the hood this is the logistics engine, P0 through P7 — routing, the consignment primitive, five-dimension pricing, dispatch, live carrier tracking, and commissioned payout with real settlement — plus the public buyer storefront sitting on top.

Honest note: the hard part was never any individual step. It's that they compose without turning into a reconciliation nightmare — and that's only possible because it all posts to one ledger. Take that away and this becomes a story about five systems and a spreadsheet trying to keep them honest.

That whole chain only composes because a "client" on this platform isn't code — it's config. Let me show you exactly what I mean.

Next → A New Client Is a Config File, Not a Code Change (Part 2 of 4)