Start with the quantity you can actually promise
A warehouse count answers how many units are physically present. A customer needs to know how many can still be supplied to a new order. Those numbers differ when products are already committed, temporarily held, damaged or awaiting inspection. Sending a field called “stock” between systems leaves the most important rule unresolved.
Shopify, for example, distinguishes on-hand, available, committed, unavailable and incoming inventory. Its available quantity excludes committed and unavailable units, as well as incoming stock. Map the meanings in your actual products before mapping their field names. An ERP may group the same business situations differently.
For a hypothetical distributor, imagine five units of one product at the warehouse: two committed to accepted orders, one held for an unpaid quote, one damaged and one free to sell. There is one unit available for a new promise. Record each exclusion once; if a system already includes the quote hold in its committed total, subtracting the hold again understates availability.
Test two requests for the last unit
Continue the distributor example. An online buyer and a sales representative both see the remaining unit. If each channel accepts its order locally and sends an update later, both can promise it before either receives the other’s message. A shorter synchronization interval narrows the window but does not settle which request wins.
One design is to make both channels request an allocation from the same authority before confirming stock. That authority must check availability and record the allocation as one indivisible operation. In this example, the first accepted request claims the unit and the second receives an unavailable response. The storefront can still display a cached quantity, but the final stock commitment cannot rely on that display alone.
If the products cannot support a shared decision at that point, consider separate channel allocations. For example, a quantity assigned exclusively to online sales is removed from the pool that sales staff may promise. Reallocations then need their own controlled process. This sacrifices some flexibility and may leave stock idle in one channel, but makes the operating boundary explicit.
Choose between these options by testing supported product capabilities, checkout constraints and failure behavior. A custom coordination layer may fill a specific gap, but it cannot make independent channels safe if they can bypass the agreed allocation rules.
A quote needs an explicit hold policy
Decide whether a quote reserves anything, who may create a hold, how long it lasts and what ends it. Shopify’s draft-order documentation illustrates the distinction: items remain available unless inventory is explicitly reserved; reservation requires inventory tracking and can have an expiry. Verify how your connector represents that reservation outside Shopify.
For the distributor, suppose a quote holds one unit until an agreed deadline. If payment arrives after the hold expires, the order must request stock again before making a delivery commitment. If payment and expiry arrive together, the allocation authority must resolve them consistently. Sending a payment confirmation and releasing stock independently can create two incompatible answers.
Cancellation and returns need separate rules too. Release only the allocation that still belongs to the cancelled order. A refunded item that has already shipped is not automatically back on the shelf; receiving and inspection determine whether it can be sold again. Keep payment, allocation and physical movement as distinct facts.
Choose the behavior when the answer is uncertain
Define what happens when allocation cannot be confirmed. For scarce stock, a useful policy might keep the request pending, pause checkout for the affected item or offer a clearly stated backorder. Choose the behavior with the commercial owner and make payment handling consistent with it. Do not quietly replace “unknown” with the last successful stock count.
Shopify documents that webhook messages can arrive out of order and that delivery is not guaranteed. It recommends periodic reconciliation against source data. Treat these notifications as a way to update views and trigger checks, not as proof that every channel has already accepted the same stock decision.
Name an operator for discrepancies. Give that person the product, location, order and allocation references, the last confirmed state and a supported recovery action. Reconciliation should compare the relevant commitments as well as totals: two systems can display the same quantity while disagreeing about which customer owns it.
Ask the supplier to demonstrate these cases
| Test | Required outcome for the proposed design |
|---|---|
| Two channels request the last unit together | Only one stock allocation succeeds; the other channel shows the agreed alternative. |
| An allocation succeeds but its response is lost | The same request identifies the original allocation without claiming another unit; its current state is checked before confirming stock. |
| An older stock update arrives after a new order | It cannot overwrite a newer commitment and reopen the unit for sale. |
| A quote expires as payment arrives | One consistent allocation result and a visible payment exception if stock is no longer available. |
| An order is cancelled, or a shipped item is refunded | Only eligible stock becomes available; a refund alone does not imply a received return. |
| The connection is unavailable | Customers and staff see the agreed pending, stop or backorder behavior; an operator can reconcile and resume safely. |
Scope the first release around one complete stock journey
Begin with a representative product, location and pair of selling channels. Agree the unit of measure, product and location mapping, availability definition, commitment point, hold expiry and exception owner. Test existing ERP and commerce features before estimating custom work.
The deliverable is a flow people can operate from request through allocation, payment, dispatch and cancellation, including the failure cases above. Expand to bundles, transfers and additional locations only after defining their stock rules. This gives a commerce integration a concrete acceptance standard: each promise is supported by a traceable allocation, and uncertainty has an agreed response.
Sources and further reading
Make the stock promise part of the design.
Bring one product journey and the systems involved. We can help define allocation, exceptions and the focused commerce integration your team needs.
Discuss your commerce workflow


