Skip to main content

Integration Patterns

Use these patterns to choose the smallest integration surface for the job. They describe managed-platform contracts, not a replacement deployment of the BoxNCase commerce backend.

Inventory and catalog sync​

Subscribe to product and stock events, normalize the event into your system's identifier model, and write back only the fields your integration owns. Store the event ID before side effects so retries remain safe.

Use:

  • asynchronous webhooks for product and stock changes;
  • metadata for stable external identifiers; and
  • bulk mutations for large, bounded updates.

Order routing​

Subscribe to order lifecycle events and route each order using channel, warehouse, vendor, or shipping-zone data. Treat the BoxNCase order ID as the stable commerce reference and record downstream acknowledgements separately.

See Order privacy and Fulfillment operations.

Tax, shipping, and payment decisions​

Use synchronous events only when checkout must wait for the result. Return a validated response quickly, enforce provider timeouts, and define a safe failure mode before enabling the integration in production.

See Synchronous events.

Dashboard workflow extension​

Use a sandboxed Dashboard view for operator-facing configuration or actions. Keep installation tokens server-side and exchange browser context through the App Bridge.

See Extending Dashboard.

Customer notifications​

Subscribe to the relevant account or order event and send through your approved email or messaging provider. Keep templates, consent rules, delivery state, and provider credentials in your integration boundary.

Choosing the right pattern​

Prefer asynchronous webhooks for durable follow-up work, synchronous events for time-sensitive commerce decisions, and scheduled API reads only when an event does not exist. Ask BoxNCase support to review the production permission set and failure behavior for payment, tax, or other checkout-critical integrations.