Capture with evidence
Idempotent synthetic intake is implemented in source; no live channel is connected.
In sourceShipping operations platform
Shipping operations without guesswork
One controlled workspace for ecommerce orders, exceptions, people, policies, and automation.
DEMO-10428Item weight mismatchFixture A
DEMO-10421Missing HS codeFixture A
DEMO-10419Address invalidFixture B
DEMO-10412Dangerous goods flagFixture C
Roadmap integrationsShopifyAmazon UKManual / APIDPDEvriRoyal Mail
Built for the work between the order and the parcel
Automate the clear path. Hold the uncertain path. Explain both.
Bundles, explicitly
Bundle expansion remains roadmap direction and is not presented as available.
RoadmapRules you can explain
Rules and why-this-matched evidence remain source-backed design direction.
In sourceProvider work, gated
Carrier execution and reconciliation remain discovery work with no active handler.
DiscoveryException librarySYNTHETIC EXAMPLE · ITEM_WEIGHT_MISMATCH
Every reason an order can stop is a named thing
Not a generic error. A reason you can filter, assign, chart, and write a help article for.
Item weight mismatch
Line 2 declares 2.000 kg; the carton scan reports 2.400 kg, outside the tolerance for this service. The order stops before a rate is chosen.
- Caught at
- Validation
- Resolved by
- Packer at the bench
- Evidence kept
- Before/after diff, actor, reason
What the platform refuses to guess
- Incomplete evidenceThe order holds with a reason, owner, and deadline instead of progressing.
- Carrier timeoutThe outcome is unknown and must be reconciled before any retry.
- Policy changeOrders keep the policy version used for their decision; history is not silently rewritten.
- AI suggestionA draft, preview, and named approval—not independent authority over a shipment.
1
canonical record across every approved intake surface
0
silent decisions—uncertain work stops and explains itself
3PL
direction—isolated client workspaces, authority, and audit
ZeroClickShip AI · Qortex
An assistant that helps the team act, not a new authority
Ask, understand, prepare, and hand off. Qortex is a scripted product direction here; this site performs no model inference or shipment action.
Show me everything waiting on address correction at UK-DEMO-1.
READ
list_held_orders(location="UK-DEMO-1")Three held orders, oldest first. Scoped by the server to what the user can already see.
Auditread · 3 synthetic orders · no write · no customer contact
Built for the three people in the room
Direct merchants
Brands running one or many channels and fulfilment locations.
- Fewer manual interventions per order
- A plan for bundles without workarounds
- Room to add channels and sites
Warehouse teams
The people who pick, pack, validate, print, and hand over shipments.
- The next task is always obvious
- Corrections without a spreadsheet
- Consistent evidence through handover
3PLs and operators
Organisations managing multiple isolated client companies at once.
- Client data and authority never mix
- Per-client rules, credentials, and audit
- A configurable operating model
Every sensitive action is explainable, repeatable, and recoverable.
- ScopeServer-owned authority. The browser never chooses its own access.
- IdempotencyReplay protection and version checks stop duplicate or stale operations.
- RecoveryA timeout becomes reconciliation work, never assumed success.
Questions we get asked first
Answered the way we would answer them on a call.
Do we have to move our carrier contracts?
No carrier commercial model is approved or connected today. Ownership, billing, credentials, and acceptance terms would be agreed separately for each future integration.
What happens to orders already in flight when we change a rule?
The design is for an order to stay bound to the rule and policy version used for its decision. A later change must not silently rewrite that history.
Can we review it without connecting live channels?
That is the proposed approach: synthetic or irreversibly redacted order shapes in a sandbox, subject to an agreed data-handling plan. This public site activates no provider.
Is this a warehouse management system?
No. ZeroClickShip is focused on the decision and evidence layer between an order arriving and a parcel being booked; it does not run stock, bins, or pick paths.
What is working today, and what is not?
The repository contains synthetic intake, held-order correction, validation evidence, approval, and local-release foundations. That is source and test evidence, not live customer, channel, carrier, or provider proof.
Start with evidence. Prove value safely. Then expand.
A proposed design-partner pilot would begin with synthetic or irreversibly redacted shapes in a sandbox, with scope and baselines agreed before any provider work.