Partners
What you can rely on
Production paths, soft-fail channels, and what is explicitly not supported. Written for operators who need honesty over marketing.
Reliable
Paths we treat as production SLA. Use these for critical partner flows.
Soft-fail
Available when configured. Never block core shipping if they are offline.
Not supported
Explicitly out of scope. Do not plan integrations against these.
Reliable
- REST API with validated API keys (X-API-Key / Bearer)
- Order create / list / cancel / status (idempotency on key money/status routes)
- Tracking (public track with PIN unlock for PII)
- HMAC connector webhooks for Shopify and WooCommerce order intake (fail-closed when secrets unset)
- Outbound webhooks with encrypt-at-rest secrets and SSRF URL checks
- Carrier dashboard accept / reject / POD flows
Soft-fail
| Channel | Behavior |
|---|---|
| Skipped when unconfigured; treat as non-SLA | |
| Web push | Soft-fails without VAPID; readiness shown in carrier settings |
| AI (planned) | Not product surface; stream disabled when off |
| Duty estimate | Informational / non-binding stub only |
| Mobile money / cash | Not selectable payout rails; COD not supported |
| Consolidations | MVP groupage only |
Not supported
- Cash-on-delivery (COD) settlement
- Full multi-leg / hub handoff logistics OS
- Public Shopify App Store / Woo plugin listings (partner-linked installs ≠ marketplace apps)
- Multi-org shipper portal (Partner desk is API-key scoped until Pass B)
Canonical write-up in docs/PARTNER_RELIABILITY.md