Availability and Resilience

Deducto is built to be highly available, and interruptions are rare. But because the API sits in the critical path of your checkout – your storefront calls Verify to price the cart and Record to commit promotion usage at order completion – it's worth understanding what happens in the unlikely event that Deducto can't be reached, whether due to a service incident or a network problem between your store and the API.

First, confirm where the problem is

If checkout is behaving unexpectedly, check the Deducto status page first. A green status page means there's no known platform-wide issue, so the cause is more likely a network timeout or a configuration problem on your side. An active incident there will describe what's affected.

Shopify and other full integrations

For Shopify-connected stores, the integration manages the checkout calls for you. If Deducto is temporarily unreachable, promotions may not apply to affected carts, but the integration is designed so that customers can still complete their purchase. Once connectivity is restored, normal promotion evaluation resumes automatically.

Custom storefronts: you control the fallback

If you call the Deducto API directly, your backend decides what happens when a Verify or Record call fails. You have two broad choices:

• Fail open – let the order proceed without applying promotions. This protects your conversion rate at the cost of a missed discount.
• Fail closed – block or delay checkout until the call succeeds. This guarantees correct pricing but risks lost sales during an interruption.

Which approach is right depends on what matters more to you: keeping orders flowing, or making sure every order honours the promotions you've marketed. Whichever you choose, showing the customer an explicit message at checkout that promotions are temporarily unavailable keeps the experience transparent and sets clear expectations. For implementation guidance, see the Custom Storefront integration guide.

If you suspect an interruption that isn't shown on the status page, follow Reporting Issues and include timestamps and, for checkout problems, a HAR file.