Integrations
Adapters with explicit source authority, permissions, retries and reconciliation requirements.
- Order channels
- Storefronts and marketplacesin and out
- Manual and file intakeOrders · in and out
- Inventory and warehouses
- Stock authorityin and out
- Warehouse workin and out
- Carrier observationsin and out
- Payments and accounting
- Payment providerin and out
- Tax authorityin and out
- Accountingout
- Agents
- Your agentWorks within the permissions you assign
Order channels
- Storefronts and marketplaces. A configured adapter maps account, order, event and line identities; SKU units; currency; commercial snapshots; and source revision semantics. Verify authentication and signature requirements before accepting deliveries.
- Manual and file intake. Manual orders use generated stable identities and the same commercial checks. File imports need a declared source key and repeat-import test so a repeated file cannot create another obligation.
Inventory and warehouses
- Stock authority. A connection must provide current sellable balances and a reservation protocol that protects units across every competing writer. If it cannot, automatic available-to-promise remains unavailable and the order desk receives an explicit review state.
- Warehouse work. Each request carries a stable external identity and exact line quantities. Acceptance, cancellation and dispatch are separate acknowledgements. An accepted instruction cannot be cancelled locally without the warehouse outcome.
- Carrier observations. Tracking adapters retain event identity, occurrence time and provider state semantics. A delivery update affects the matching shipment; it never consumes another reservation or proves delivery of other packages.
Payments and accounting
- Payment provider. Store references and verified outcomes, never card credentials. Distinguish authorisation, capture, refund and dispute. Refund dispatch requires independent approval, an immutable amount and provider-supported idempotency or a verified equivalent recovery contract.
- Tax authority. The configured channel or tax service supplies the calculation reference and amount. This order system retains that snapshot and its later allocation; it does not establish jurisdictional tax compliance.
- Accounting. Approved financial outcomes may create a credit export for the accounting system. The external acknowledgement establishes acceptance. A pending message does not claim that the general ledger has been posted or reconciled.
How connections are governed
service accounts, audit, pausingStart every adapter in test mode with scoped credentials and a documented version. Persist external commands before sending them, retry unchanged arguments under the original identity and redact secrets from error records. A timeout becomes an unknown result where the provider might already have acted. Reconcile its current object before issuing a new effect or releasing reserved capacity.
Use event identities for duplicate detection and authoritative object reconciliation for conflicting or out-of-order observations. Record compared intervals and cursors. Only activate a channel after positive flows, denied access, duplicates, lost responses and partial failures have been observed in the target environment. Changing mappings or policies increments the configuration version and reruns affected acceptance cases.
Provider workflows differ. For example, Shopify’s fulfilment-order lifecycle, Stripe webhook delivery rules and Stripe idempotent requests describe their respective handoffs and retry behaviour. Match each connection to the provider your business uses.
The API is one more client of the same interface. Your order operations assistant
curl -fsSL https://www.erp.ai/skill.md