How it works
One shipment, five roles, three stages. Everything below is what the beta actually does, walked live end to end on real phones against a real backend on 2026-09-14.
Synthetic data only. Every shipment in the beta is a test fixture. CruzLink does not accept real commercial shipments in Phase I.
Who's in it
Four roles are real beta testers. A fifth exists so the corridor walk can show the review step.
Shipper
Files the shipment: commercial invoice, packing list, bill of lading, and declared value.
Carrier
Records pickup and handoff custody events as the shipment moves.
Port operator
Confirms arrival and final receipt at Port Saint Croix.
Broker / finance
Closes the shipment and acknowledges the payment-eligibility milestone.
Customs reviewer Demo role
Held by GoalSight staff for the beta, not a role beta testers sign up for. No CBP officer uses this app; it demonstrates where a review step belongs.
1. File and prepare
The shipper attaches the commercial invoice, packing list, and bill of lading, enters price, freight, insurance, and currency, and files. Filing pins the shipment to the rate rules in effect that day, so every later calculation can be traced back to the exact numbers used.
2. Review and clear
The customs reviewer opens the packet, sees a landed-cost estimate computed from the pinned rules, and approves or holds. Approval and hold both require a biometric or device-passcode confirmation on the reviewer's own phone before the decision is recorded. Filing also triggers aSimulated submission to a stand-in for U.S. Customs' ACE system: a plausible entry summary out, a plausible acknowledgment back, both labeled simulated everywhere they surface. No live ACE filing happens in Phase I.
3. Move and settle
The carrier and port operator record custody events, each carrying a GPS fix, a timestamp, the device that captured it, and (where relevant) a photo. Every event is cryptographically chained to the one before it, so the sequence cannot be reordered or edited after the fact without breaking the chain. When the shipment reaches "received," a payment-eligibility milestone is created automatically. Broker/finance reviews the server-computed landed cost and acknowledges the milestone with a biometric confirmation of their own.
No money moves inside the app. The milestone records that a payment is now eligible to be made; it is an event, not a transfer. Phase I proves the trigger works. Actually settling funds is a later phase.
See it happen in the demo hub, or read the field-level detail in the developer docs.