Many air freight teams already run CargoWise well enough for rating, job costing and documentation. The remaining pain is operational: airline emails that never become structured events, milestone updates typed twice, and disruption handling that lives in a shared inbox. UpliftOS is designed for that layer.
How the architecture is meant to work
CargoWise ↓ Shipment data ↓ UpliftOS ↓ Exceptions + AI + workflow
CargoWise stays responsible for the commercial file. UpliftOS watches shipments, raises exceptions, recommends recovery and prepares customer communication. We do not claim a certified marketplace partnership or WiseTech endorsement.
Ingestion that already exists in the product
Design partners should know what is implemented versus what is still onboarding work:
- CargoWise inbound. An HTTP endpoint accepts JSON or XML shipment payloads with a shared secret. Adapters normalise the payload onto the same shipment model used everywhere else. Reconciliation is organisation + external system + external shipment id, not MAWB alone.
- Public API.
POST /api/v1/shipmentswith an organisation API key upserts the same way. - CSV / Excel. Operators can import a forwarding extract, map columns, save templates and review history.
- Operational email. The demo classifies airline cargo-roll messages and matches them to shipments. A production mailbox connector is planned with design partners rather than claimed as a self-serve Gmail install.
Connecting a live CargoWise company is onboarding work, not an instant marketplace toggle. Language such as "connect CargoWise instantly" would overstate what is in the product today.
What UpliftOS adds after the data is in
Once a shipment exists, the air freight operations workspace applies health, the Operations Inbox, disruption management and AI-assisted actions. Source badges show whether a file last arrived from CargoWise, API or CSV so operators can trust the lineage.
Export back into a TMS is not a bidirectional certified connector today. Operational events and audit records are the current surface for what happened in UpliftOS.
Who this is for
Air export teams on CargoWise who still run a parallel spreadsheet for exception handling. Branch managers who want one inbox for rolled cargo and missing documents. Operators who should not have to re-find the job every time Qantas or another carrier sends a roll notice.
FAQ
Are you a WiseTech partner?+
No affiliation or endorsement is claimed. CargoWise is a trademark of WiseTech Global. UpliftOS ingests shipment information and provides an operations layer.
Will we have to migrate accounting or ocean?+
No. The design is coexistence. Keep CargoWise for the modules you already run.
CargoWise is a trademark of WiseTech Global. UpliftOS is not affiliated with, endorsed by, or a partner of WiseTech Global.