01 · Source lineage
One operational truth
The target model keeps one canonical record while preserving field lineage. Live channel ingestion is not connected.
Product
One command centre, from held-order intake to local evidence
Synthetic orders, exceptions, correction, validation, approvals, local release, and audit are the source-backed foundation. Work management, rules, and provider execution remain later stages.
ORDERHOLD REASONCREATED
DEMO-10428Item weight mismatch22 AUGDEMO-10421Missing HS code24 AUGDEMO-10419Address invalid24 AUGDEMO-10412Dangerous goods flag23 AUGDEMO-10405Value exceeds limit23 AUGCORRECTION · DEMO-10428 · V4
FIELDBEFOREAFTER
Line 2 — item weight2.000 kg2.400 kg
Total order weight3.600 kg4.000 kg
HS code9503003595030035
Run validationMark readySOURCE HOLD UNRESOLVED
Automate the clear path. Hold the uncertain path.
The synthetic source preserves its original capture. Clear local state may move; incomplete work stops and exposes the reason.
02 · Exception handling
Exception-first
Correct a held shipment with a reason, rerun validation, and keep the original capture untouched.
03 · Human control
Human control
Permissions, versioned policies, and approvals make every sensitive action accountable.
Capability by area
Status reflects controlled evidence, source awaiting composed proof, and future provider work. It does not imply live customer or carrier traffic.
| Area | Capability | Status |
|---|---|---|
| intake | Structured intake Capture shipping intent in a consistent workflow. Capabilities reflect current source contract. | In source |
| bundles | Bundle planning Group shipment work into clear operational units. Roadmap direction, not a live claim. | Roadmap |
| dispatch | Correction workflows Review and correct held order details before release. Source-backed workflow; authenticated application state required. | In source |
| workload | Workload visibility Make operational workload legible. Roadmap direction, not an SLA guarantee. | Roadmap |
| rules | Rules Express operational rules with explicit outcomes. Source-backed design direction. | In source |
| policies | Policies and approvals Keep sensitive actions reviewable and governed. No public authority is implied. | In source |
| carriers | Carrier execution Prepare controlled carrier integrations. Discovery only; no carrier execution is promised. | Discovery |
| tracking | Tracking and returns Explore a coherent post-dispatch experience. Roadmap direction, not live data. | Roadmap |
| developer | Developer platform Publish stable bounded developer references. Controlled documentation evidence, not external traffic. | Demonstrated |
| direction | Qortex direction A future direction for intelligent operational assistance. Discovery only; no availability implied. | Discovery |
No live channel or carrier connection is active. Any future provider work requires separate authorisation and acceptance evidence before its status changes.
ZeroClickShip AI · Qortex
AI that helps the team act, not a new authority system
Designed to cut the time people spend finding information, interpreting exceptions, and preparing repetitive changes — without giving the model independent authority over shipments, money, or customer communication.
YOUShow me the oldest held orders.
QORTEXScoped to your current workspace. Three held orders need attention; nothing has been changed.
YOUWhy is DEMO-10428 held?
QORTEXThe item weight differs from the source capture. I can explain the evidence, but I cannot release the order.
YOUPrepare a correction preview.
QORTEXDraft ready for review: update the bounded weight field, preserve the source value, and rerun validation.
YOUApply the correction.
QORTEXWaiting for a named person with permission to approve. The action remains a preview until then.
Flexible enough for one brand, structured enough for a multi-client operator
The source models server-derived company, client, and location scope. This is a synthetic application boundary, not proof of live customer provisioning.
Company · Source model
Operating boundary
The source keeps company authority explicit; carrier accounts are not connected.
Client workspace · Source model
Separate client work
Scoped application paths are designed to keep client authority and data separate by default.
Location · Source model
Local scope
Location is part of the server-derived scope. Printers and provider defaults remain future work.
Review it against safe order shapes
A proposed pilot would start with synthetic or irreversibly redacted examples and an agreed data-handling plan.