In Stock Is Not a Promise Date: Reading Availability on an Export Supplier Website
By Daoyu Guan
A supplier's site displays 100 pieces in stock. A buyer requests 80 for immediate dispatch. The warehouse has the pieces, but 30 belong to other orders and another 20 are awaiting quality release. A confirmed receipt may make more available next week.
The website's number can be physically accurate while the buyer's conclusion is wrong. Inventory on hand, inventory available for a new order, an available-to-promise calculation and a confirmed shipping commitment answer different questions. An export page should identify which one it actually reports.
Separate presence from availability
Physical on-hand quantity describes inventory recorded as physically present under the system's chosen scope. Available quantity applies rules about what can be used for the decision in question. The result depends on the product, location, status, reservations and other relevant dimensions.
Microsoft's inventory on-hand documentation distinguishes physical inventory, physical reservations and available physical inventory. It also explains that filters and displayed dimensions affect the results. A total without its scope can therefore hide a commercially important difference.
A page might aggregate two warehouses even though only one serves the buyer's destination. It might show a product family while the requested variant is unavailable. It might count stock in a status that cannot be shipped. These are questions to resolve in the implementation, not proof that any specific supplier has made those mistakes.
The useful public statement identifies the item, unit, location or fulfilment scope where appropriate, time and meaning of the availability label. “Stock information last updated at…” is still only as reliable as the underlying record and refresh process.
Available-to-promise adds a time dimension
Available-to-promise, commonly ATP, concerns the quantity that a system can promise under its configured rules for a date or period. It can consider future supply and demand as well as current uncommitted stock.
Microsoft's order-promising guidance distinguishes ATP from a simple sales lead-time method and describes the role of uncommitted inventory, lead times, receipts and issues. The SAP glossary's simplified expression combines warehouse stock with planned receipts and subtracts planned issues.
Those descriptions explain the concept; they do not create one universal formula for every ERP system or seller. Scope, planning horizon, included statuses and confirmation rules must be specified. A receipt expected by procurement is not automatically eligible supply for a customer commitment.
ATP also differs from capable-to-promise calculations that consider a production-capability context. A factory's advertised monthly capacity is neither a live ATP balance nor proof that an uncommitted production slot exists for this order.
Follow a fictional stock record
Assume a single item, one declared piece unit and one fulfilment location. This invented policy excludes allocated stock and quality-held stock from new promises. The groups below are assumed to be separate, so no unit is deducted twice.
| Event or status | Quantity | Role in this example |
|---|---|---|
| Physical on hand now | 100 pieces | Starting physical quantity |
| Allocated to earlier orders | 30 pieces | Unavailable to the new buyer |
| Quality hold | 20 pieces | Excluded until authorized release |
| Eligible confirmed receipt next week | 40 pieces | Future supply under the declared policy |
| Earlier future commitments against that receipt | 10 pieces | Future demand to preserve |
The available quantity today is `100 − 30 − 20 = 50 pieces`. After the assumed receipt and earlier future commitments, the simplified future balance is `50 + 40 − 10 = 80 pieces`.
A request for 80 pieces cannot therefore be described as immediately covered by the 100-piece physical figure under these assumptions. The later balance could support a different discussion, but it does not by itself establish a confirmed dispatch date, completion of inspection or transport arrival.
If the receipt is delayed or no longer qualifies under the policy, the future result changes. If the quality-held stock is already excluded from the starting measure, subtracting it again would understate availability. That is why the definition of the starting quantity matters as much as the arithmetic.
The example is not a description of Dynamics, SAP or a real warehouse configuration. It is an explicit worksheet illustrating the distinction between stock presence, eligibility and time.
A date needs an event label
“Available Friday” might mean a supplier expects incoming material, expects a completed product, expects quality release, can hand goods to a carrier, or expects delivery to the buyer. Those events occur at different points in the order journey.
A confirmation should label the event and the relevant conditions. If a date depends on drawing approval, payment, material receipt or another prerequisite, connect that dependency to the estimate. A desired delivery date entered by the buyer is not automatically the supplier's committed date.
The order-promising method also needs to match what the system does. A fixed sales lead time can produce a date without checking actual supply. Calling that output “live availability” would give the buyer a different impression from the underlying method.
Transport time and destination conditions require their own treatment. A date on which goods are available at the supplier is not automatically the date on which the buyer can use them. The existing guide to FOB and delivery dates addresses the event and commercial-term distinction; confirm the agreed transport and trade terms for the actual offer.
Decide what the public website can responsibly show
An exporter does not need a real-time stock widget to publish useful information. A stable catalogue with a clearly scoped availability statement and a reliable human confirmation route may serve a business whose inventory is project-specific or whose quotes require technical review.
If the site shows a live number, define the record behind it. Which item and variant does the value concern? Which location and status filters apply? What is the unit? When was it calculated? How are reservations, failed updates and stale values handled? A timestamp without a valid calculation does not make the number trustworthy.
If the page shows a broad label such as “normally stocked,” explain what the buyer should do to confirm the required quantity and timing. Do not convert that planning description into an unconditional immediate-shipment claim.
For a public AI answer, a restrained sentence can preserve the distinction: “The supplier lists this item as normally stocked; quantity and dispatch date require order confirmation.” That wording should reflect the actual page and process. It is not permission to add an availability claim where none has been approved.
Test a proposed availability feature
- Define the decision. Decide whether the feature reports physical presence, eligible stock, a dated ATP result or an order-specific commitment. Use the same definition in its label and help text.
- Choose a controlled item. Use an authorized test environment or approved non-customer example with known unit, location and status relationships.
- Introduce one change at a time. Examine a reservation, hold, eligible receipt and delayed receipt separately. Check whether the displayed quantity and date follow the declared rules.
- Inspect the buyer's route. Confirm that the item, unit, requested quantity and desired date reach the responsible person or system without becoming an accepted promise merely through submission.
- Check the fallback. If the data is unavailable or outside its freshness limit, show the agreed uncertainty and confirmation route rather than retaining a confident stale badge.
These are proposed acceptance exercises. They do not imply that any product, supplier or integration has passed them. A buyer should obtain the actual feature scope, configuration and operating responsibilities before commissioning a connection.
Keep the website and sales team on the same definition
A useful handoff preserves both the buyer's request and the website statement that prompted it. The responding person should know the requested item, quantity, unit and timing, as well as any unresolved specification or location condition.
Do not silently turn a forecast into a firm order or an enquiry into an allocation. Those transitions need the seller's actual commercial process. A website confirmation can acknowledge receipt while leaving stock, technical suitability and delivery subject to the relevant review.
Xindar's B2B export marketing scope includes buyer information and website enquiry paths with human handoff. It does not establish real-time ERP stock integration, autonomous quotations or automated CRM writing. For a manufacturer needing those functions, identify a separate, explicit software and implementation scope.
GEO content can help a buyer ask a better question: “Can you confirm 80 pieces of this variant for dispatch on the required date?” It cannot convert an aggregate stock number into a commercial commitment that the supplier has not made.
FAQ
Does “100 in stock” mean I can order 100 for immediate dispatch?
Only if the displayed measure and the seller's terms support that interpretation. Reservations, status, item scope and dispatch requirements need to be resolved.
Is ATP the same as physical inventory?
No. ATP is a dated promise calculation under configured rules and may consider future receipts and demand. Physical inventory is one possible input.
Should a website hide all stock information?
No. Publish the measure the business can support, with a useful definition, freshness treatment and appropriate confirmation route. Avoid a label stronger than the underlying process.
Can an AI search answer confirm my delivery date?
A search answer can report a published statement with its conditions. A current order-specific commitment must come from the authorized supplier process.
Sources and method
The linked Microsoft and SAP primary material was reviewed on November 11, 2026. The stock quantities, eligibility policy and receipt timing are fictional. No warehouse, ERP connection, order allocation or delivery outcome was tested for this article.