Does available stock in a configurator mean it is reserved?
Distinguish stock visibility from reservation when connecting a configurator to inventory, including stale data, competing orders and acknowledgements.
Table of contents
Showing an available component does not necessarily reserve it. A configurator may display information from an inventory system while another process controls allocation. Before buying an integration, define when availability is checked, when a reservation occurs and what happens if the receiving system rejects the request.
Name the stock quantity being displayed
On-hand quantity, unallocated quantity and available-to-promise information can mean different things in a company's workflow. Ask the inventory team to define the field the configurator will use. Identify the source, update time and any location or account restrictions.
A customer-facing message should reflect that meaning. A value copied from yesterday's export should not be presented as a confirmed allocation for an order being accepted now.
| Event | Required decision |
|---|---|
| Product browsing | Is stock information shown, and how current is it? |
| Saved draft | Does saving request any allocation? |
| Quotation issue | Is availability rechecked? |
| Order acceptance | Which system confirms reservation? |
| Failed reservation | What status and next action are retained? |
Test two orders competing for one component
In an agreed test environment, use a component quantity sufficient for only one of two orders. Prepare both configurations, then attempt the relevant acceptance step. Check how the second request is handled and whether the customer or salesperson receives a misleading confirmation.
The objective is not to make the browser calculate inventory independently. It is to verify that the agreed authority makes the allocation decision and that the application handles its response correctly.
Make stale information and failures visible
An unavailable integration should produce an understandable state. Decide whether the customer can continue an enquiry, whether a salesperson must check stock or whether order acceptance pauses. Keeping the selected configuration is useful; silently changing it to a different product is a separate commercial decision.
Request the receiving-system acknowledgement and a way for staff to investigate unresolved requests. An email saying an order was submitted is not the same as an inventory reservation.
Scope the Configurix inventory connection
For a Configurix ERP integration, specify fields, direction, timing and error handling. Bring your inventory definitions and an accepted order example so the implementation can distinguish selection, quotation and allocation.
Should a configurator maintain its own stock figures?
Only where that is the agreed architecture. Avoid creating a competing inventory authority unintentionally. Your receiving-system owner should approve the relationship.
Can customers still ask for unavailable products?
That can be a valid enquiry workflow. Clearly distinguish a request for information from a promise that stock has been allocated or delivery confirmed.
Book a private Configurix demo
Bring your product range, price list and a representative quote. We can define the configuration and sales workflow around your business.
Book a private Configurix demo →Related articles
What should a configurator proof of concept prove?
Define a configurator proof of concept around a risky rule, saved revision and receiving-system output, with clear pass conditions.
Does every configured size need a separate SKU?
Define model identity, continuous dimensions, component references and order records without creating a SKU for every possible configuration.
What maintenance is needed when products change every week?
Specify configurator maintenance for frequent catalogue changes, distinguishing editable data, application changes, tests and emergency corrections.
What order status should customers see after configuration?
Design customer-facing order tracking that explains progress and next actions without exposing internal production notes or unrelated customer records.