Understand the relationships between a product promise, its available stock and the operations that fulfill or return it.
Availability depends on more than a stock count
A retail item may be on hand but reserved, awaiting inspection or unavailable for a particular fulfillment method. Store, warehouse and commerce systems can describe different versions of that position. The customer promise depends on the location, channel, handling constraint and time at which the decision is made.
Retail intelligence connects product identity, inventory state, customer orders and fulfillment events. It helps operations teams understand why a promise is at risk and what evidence supports a response. The approved inventory and order systems retain responsibility for allocation and transaction changes.
What was physically recorded at a location, and when.
Which accepted commitments already depend on that stock.
What the approved rules permit for this channel and fulfillment method.
Connect the order line to its reservation, picking events and shipment plan. Determine whether the issue is missing stock, an incorrect unit, a damaged item or a timing mismatch. Present the relevant alternatives for the authorized team to review under the retailer’s customer and allocation policies.
| Source | Relevant evidence |
|---|---|
| Commerce and order management | Customer promise and selected fulfillment method |
| Warehouse and store systems | Stock state, reservations and pick confirmations |
| Transport events | Dispatch and delivery progress |
| Returns processing | Returned quantity, condition and disposition |
Products, variants, selling units, logistics units and locations carry different meanings. Linking supplier identifiers, internal item codes and channel listings makes those differences visible, including pack sizes and changes to the assortment.
GS1 standards provide identifiers and event models for tracking products across a supply chain. Availability still depends on the stock record's time, location and status, including reservations and inspection holds.

A returned item may require a refund, inspection, inventory adjustment and supplier claim. Those steps have different owners and completion times. Connect the return to the original order and fulfillment evidence so teams can understand which responsibilities remain open.
Customer information and payment references need appropriate access boundaries. An inventory investigator may need a delivery location without access to all customer history. Keep sensitive attributes limited to the purpose of the review and preserve source permissions in any assembled context.

Record the returned unit and link it to the original order.
Decide the appropriate stock disposition through the established procedure.
Check responsibility for refunds or supplier claims independently of the physical receipt.
A store transfer, a split order and a partial return each change the relationship between available stock and customer demand. Pack sizes and selling units add another layer when the same product appears in different systems.
Keeping those relationships visible helps retail teams trace an inventory mismatch to its source, whether it is a unit conversion, a delayed update or an incomplete movement between locations.