Help centre · Availability
Integrations, honestly mapped.
The product is being shaped around reliable intake, validation, correction, authority, and evidence. Capability labels keep current source behaviour separate from provider research and roadmap intent.
| Capability | Status | What that means |
|---|---|---|
| Synthetic intake and held-order review | In source | A private workflow can model typed intake, correction, validation, approval, and local release using synthetic records. |
| Authenticated workspace selection | Private preview | Source and test evidence exists for explicit scope; public provisioning is unavailable. |
| Rules and policy administration | Discovery | The operating model is documented; no public configuration or simulation product is released. |
| Store and marketplace intake | Roadmap | No live Shopify, Amazon, or other channel connection is advertised. |
| Carrier services and rates | Roadmap | No live account connection, rate response, service eligibility, or certification is advertised. |
| Booking, labels, manifests, pickups | Unavailable | The current runtime has no live provider handler and performs no carrier-visible action. |
| Tracking, returns, notifications, writeback | Roadmap | The public site is not a tracking, returns, messaging, or source-system update service. |
| CLI and MCP | Design preview | No distributed binary, install command, server endpoint, or callable tool catalogue exists. |
Questions to answer for each future integration
- Who owns the provider account, credentials, commercial contract, and support relationship?
- Which records and fields may enter the workspace, and in which residency boundary?
- Which operation is read-only, reversible, chargeable, or customer-visible?
- How are idempotency, throttling, timeouts, partial failure, and unknown outcomes reconciled?
- Which provider evidence proves acceptance, and how is it attached to the canonical record?
- What sandbox, certification, rollout, rollback, and monitoring evidence is required before activation?
Before a private evaluation
- Agree the workspace, workflow, and success criteria.
- Use synthetic or irreversibly redacted records until a separate written data scope is approved.
- List every source, provider, operation, and expected outcome without sharing credentials.
- Mark which results are local evidence and which would require external acceptance.
- Record open questions before designing a production dependency.
Need a capability? Start a conversation with the workflow, source system, and outcome you need. The local contact form does not transmit data or create an account.