Tracking, returns, and writeback

These connected post-dispatch workflows are part of the product direction, not current public functionality.

Current boundary. ZeroClickShip does not currently receive carrier tracking, initiate returns, write status back to a storefront, or send customer notifications through the public contract.

Keep the state sources separate

State	Expected future source	Do not infer it from
Locally released	ZeroClickShip’s reviewed local workflow.	Carrier booking or collection.
Booked or labelled	Accepted provider response and reconciliation evidence.	A queued local outbox intent.
In transit or delivered	Carrier events with freshness and ordering rules.	Elapsed time or warehouse handover alone.
Written back	Accepted source-system response for the intended record.	A carrier event or local status change.
Customer notified	Accepted messaging-provider evidence under consent rules.	A prepared message or storefront writeback.
Return accepted	Return policy plus provider or warehouse acceptance.	A customer request alone.

What teams can prepare

Identify the canonical source for every state and field.
Define event freshness, ordering, duplication, and gap handling.
Record who owns the carrier, channel, and messaging relationship.
Separate reversible updates from chargeable or customer-visible actions.
Define reconciliation and support ownership before enabling automation.

When something looks missing

Record the local record revision and expected event type.
Check whether the capability is actually enabled for the workspace.
Do not infer delivery, notification, or return acceptance from a local correction or release.
Escalate through the approved implementation route using safe request references, never raw customer or credential data.

See shipment statuses for the current local state model and integrations and capabilities for availability.