Help centre · Evaluation guide
Getting started
ZeroClickShip is designed to make the operational work between an incoming order and provider execution legible, reviewable, and recoverable.
Current availability. The implemented workflow is a private synthetic preview. This public site does not create an account, connect a store or carrier, submit an order, book a shipment, print a label, or send customer data.
1. Choose one operating problem
Start with a bounded problem such as an incomplete address, a weight mismatch, or a correction that needs named approval. Define the current owner, input, safe next action, and evidence required to explain the decision.
2. Define the evaluation boundary
| Decision | What to record |
|---|---|
| Workspace | The company and location included in the evaluation. |
| Data | Synthetic or irreversibly redacted shapes; no credentials or raw customer payloads. |
| Authority | Who may read, correct, validate, approve, and review evidence. |
| Outcome | What local state proves success and what remains outside scope. |
| Baseline | How the team handles the same exception today. |
3. Walk the controlled flow
- Confirm the active authenticated workspace.
- Open the held record and read its named reason.
- Apply only the bounded correction under review.
- Run validation against the current revision.
- Complete any required local approval.
- Review the evidence and local-release record.
Local release does not prove provider execution. See held-order guidance and workflow statuses.
4. Keep access and support safe
- Use least privilege and let the server resolve workspace scope.
- Keep credentials in an approved secret store.
- Do not paste customer data, labels, provider payloads, or authentication material into this site or a support message.
- When reporting a problem, include the page, local state, approximate time, and a safe request reference—not sensitive payload contents.
5. Plan integrations separately
Channel, carrier, booking, label, tracking, return, notification, and writeback work each require their own contract and acceptance evidence. Review integration availability before planning a dependency.