Publish Date :
Shopping Agents Are Coming: Is Your Stock Data Ready?
An agent cannot make a dependable purchase decision from stock data that mixes physical, reserved and incoming quantities. For a Merchmix team, readiness starts with a consistent usable-stock view and an accountable response to the exceptions it reveals.
THE MERCHMIX DECISION / Core Plus + Yukti
Which units are usable today?
Keep reservations and future receipts out of the wrong availability basis.
Worked retail example. Independent of the reported company records. Financial scenario amounts are USD.
Apparel SKU / current and future supply
Reserved and unavailable groups do not overlap in this worked example.
The location has 80 units physically on hand.
THE KEY IDEA
Agent readiness is an inventory-definition problem before it is a new interface. Use the correct units, time and ownership basis, then decide which supported action the team should approve.
Discovery and checkout have different dates
Zalando’s 3 November 2026 announcement introduces Zalando Extended, adding products from other online shops to its platform. The company places its own agent’s checkout on customers’ behalf in 2027. That distinction matters: the announcement should not be described as evidence that every proposed checkout capability is already live.
This is a data-readiness article, not a claim that Merchmix connects directly to Zalando Extended or to every shopping agent. Any channel publication or promise capability depends on the supported connected systems.
One stock number can conceal several meanings
Physical on hand, usable stock, reserved quantities and expected receipts answer different questions. A total that includes tomorrow’s receipt cannot safely be used as proof that a product can be fulfilled today.
The same issue applies to product identity. A style total does not identify the requested size and colour at the location or channel expected to supply it. Start with the record and the timing before considering the agent experience.
A stock exception needs an owner as well as a calculation. Identify the affected product, size, location and update time so the inventory team can establish which record needs attention. A clean-looking total without those definitions can travel through another channel faster than the underlying discrepancy is resolved.
A positive stock count can still overstate availability
A separate apparel retailer counts 80 units physically held. Twenty are reserved for other orders and five are unavailable for sale. The usable, uncommitted quantity is therefore 55. A further 40 are expected next week but do not increase today’s usable stock.
Publishing 120 as if it were immediately available would combine incompatible time bases. Even publishing 80 would ignore reservations and unavailable stock. The example assumes no other stock movements and matching product identifiers; it is not a universal available-to-promise formula.
THE FIGURES BEHIND THE DECISION
| Stock component | Units | Meaning |
|---|---|---|
| Physical on hand | 80 | Counted today |
| Reserved | 20 | Already committed |
| Unavailable | 5 | Not usable |
| Usable / uncommitted | 55 | Current review basis |
| Expected next week | 40 | Future supply |
80 physical − 20 reserved − 5 unavailable = 55 usable
Reconcile stock before distributing another unit
Core Plus supports allocation, replenishment and transfers by store and size. A proposed stock response needs the correct availability scope and already incoming supply; it should not be driven by an inflated style-level total.
Confirm where reservations and fulfilment promises are maintained in the retailer’s connected stack. Merchmix planning and stock decisions do not replace the ERP or order system’s role in the live transaction.
Turn a data discrepancy into an owned stock question
When the correct usable-stock basis reveals a shortage, Yukti can support a proposed response for review. The question is which permitted stock action fits the demand and location, with the relevant reasoning and approval context.
The example does not show Yukti purchasing on a consumer’s behalf. Shopper-facing agents and an internal retail agent have different users, permissions and responsibilities, even when both depend on trustworthy data.
Make the stock definition explicit before scaling discovery
The subtraction works because reserved and unavailable units are separate, non-overlapping groups in this example. If a system already includes damaged reserved stock within its unavailable total, subtracting both full totals again would understate usable supply. A reconciliation needs a defined calculation, location scope and update time, not just a reassuring positive balance.
Future supply also needs its own date and status. An expected receipt is not physical stock, and physical stock is not necessarily ready for another commitment. Core Plus provides the inventory context for this review. Yukti can help frame a bounded exception for the responsible team; that is different from claiming that a shopping agent is connected to Merchmix or authorised to transact against its stock.
| Signal | Merchmix workspace | Decision to review |
|---|---|---|
| Physical and usable totals differ | Core Plus / stock position | Reconcile reservation and availability definitions without double counting. |
| Future intake is included as current | Core Plus / incoming supply | Keep the expected receipt and its timing separate from usable stock today. |
| A discrepancy needs investigation | Yukti / operational proposal | Identify the SKU, location and question for review without asserting an integration. |
Test the edge cases before relying on the feed
Check a partial reservation, a delayed receipt, an unavailable unit and a size sold in more than one channel. Trace one product from its source record to the availability view and the proposed next stock decision.
The useful outcome is a clear owner for the discrepancy and a verified connected workflow. Do not promise real-time agent checkout simply because a report contains a recently refreshed stock field.
BEFORE THE NEXT DECISION
- Inventory team
Reconcile physical, reserved and unavailable units using non-overlapping definitions.
- Supply team
Confirm the status and date of the forty expected units without adding them to usable stock today.
- Decision owner
Resolve the identified SKU and location discrepancy before relying on its availability.
Common questions
Is Zalando’s agent checkout already fully live?
The official announcement places checkout on behalf of customers in 2027. Discovery and future checkout should not be conflated.
Can incoming units be advertised as available now?
Not simply because they appear on a purchase order. The usable availability date and connected promise rules matter.
Is 55 a universal available-to-promise calculation?
No. It is the result of the explicit assumptions in this worked example.
Does this announce a Merchmix–Zalando integration?
No. No such integration or customer relationship is claimed.
Which stock quantity should a downstream service receive?
That depends on its agreed availability definition and fulfilment scope. Reconcile usable stock, reservations, exclusions and timing first; a physical count alone is not a promise to fulfil.
FROM THE ARTICLE TO YOUR OWN RETAIL PLAN
Review the decision.
See the workflow.
Bring your planning questions to a demo, or explore a proof of concept on your own data.