Integrations and source ownership

• Payment provider. Import the provider’s authorization, capture, refund and void events with its own event identifier, amount and reference. Finance Reviewer verifies the evidence before using it in reconciliation.
• Fulfillment source. Map allocated, picked, shipped, delivered and returned product events to the intended parent order. Keep the external event identifier and occurrence time.
• Identity provider. Map staff accounts to team members and organizations. A staff departure or reassignment needs a corresponding access change.
• Menu source. If product definitions are maintained elsewhere, agree which system owns codes, active states and standard prices before import.

Each connection needs a source owner, identifier mapping and retry rule. An external acknowledgement is evidence of that source’s action, not a substitute for checking the local order and review decision. When a provider call times out, inspect the operation receipt and the provider event before trying again. Keep a failed operation receipt visible with its original reference and reason.

Run a pilot with a duplicate provider event, an unmatched delivery quantity and a revoked staff account. Reconcile imported events and pending operation receipts with their source before enabling a regular import schedule. Grant connections only the access they need and keep credentials in the approved secret store.

Plan the rollout.