Availability and scope
The custom API and signed-webhook workflow are available. Shopify and WooCommerce managed adapters are not currently available. Managed setup and the WordPress package require administrator-approved verification before release.
The extended financial, reconciliation and historical import workflows described here require administrator verification before live use. Begin with a Test connection and a preview.
Choose Ledger for accounting, Supply for physical inventory, or both. Digital and subscription profiles use Ledger without stock. Use one connection per source, seller and environment. The seller/legal entity that issued the sale determines accounting ownership; the bank receiving funds alone does not determine the seller.
Each store has its own connection boundary. Use Manage for configuration and Events to review processing outcomes.
Account details and configuration values are hidden.Before you connect
- Use workspace administrative access and the relevant Ledger or Supply integration permission.
- Confirm Ledger access and, if needed, Supply access.
- Prepare a stable external store or tenant identifier and begin with a separate test connection.
Set up a connection
- Open Workspace settings → Integrations → Commerce and select Add connection.
- Name the connection, select the source and Test environment, and enter the external source identifier. Follow the matching Custom API, Shopify or WordPress and WooCommerce guide for source-specific credentials.
- Choose Physical, Digital or Subscription SaaS. Enable Ledger for accounting, Supply for inventory, or both for physical products.
- Create the connection and copy the one-time signing secret to your secure credential store.
- Open Manage to configure invoice authority, receivable/income/clearing accounts, optional FX/dispute accounts, approved product/variant or service mappings, and optional Supply policies. Create a scoped API key and store it securely when displayed.
- Complete signed test events with your integration administrator. Review outcomes and mappings before activating live processing.
Processing and multi-store behavior
A valid event is accepted before processing. An exact retry returns the existing receipt rather than duplicating the business outcome. Reusing an event identity with materially different data is rejected.
Ledger creates the invoice, payment, credit-note or refund outcome according to connection policy. Supply changes inventory only for mapped products with an explicit fulfillment policy. Ambiguous accounts, products, warehouses or refund treatment require review.
Four stores require four connections. Each keeps its own credentials, external identity, mappings and event history. Pausing one store does not pause another. Plan limits govern connection and credential capacity.
Protect the connection
- Use separate test and live connections and separate credentials for independent applications.
- API keys and signing secrets must be stored securely when displayed. Never publish their values or fragments.
- In Manage → Overview, API credentials shows active capacity and credential history. Select Revoke and confirm to stop access immediately. Revoked keys cannot be re-enabled; keep their history for audit. Expired and revoked keys do not consume active-key capacity.
- Use the supported signed-event contract. Invalid or stale signed requests are rejected.
- Do not send card data through the commerce event workflow.
Monitoring and recovery
Use Manage → Catalog & events or the row-level Events action to inspect accepted, processing, completed and review-required outcomes.
Resolve the underlying mapping or policy issue before retrying a retained event. Event identity checks continue to prevent duplicate effects during replay. If access is unavailable, ask a workspace administrator to review permissions and module entitlements.
A capacity warning appears inside the action dialog. Draft, active and paused connections share the workspace connection allowance, across Test and Live. Reuse an existing connection or review your plan allowance. At the API-key limit, revoke an unused key before creating another; check the connected application first to avoid interrupting synchronization.
Related guides
Ask your workspace administrator for access or contact support with the page name and a sanitized error message.