Target’s Inventory Digital Twin Needs a Physical-to-System Reconciliation Loop

A digital twin can simulate inventory movement with impressive precision, but a model is only as current as the physical events feeding it. If a trailer arrives early, a pallet is short, a case moves to the wrong location, or a damaged unit remains available in the system, the twin begins describing a warehouse that no longer exists.

Target’s Proxima platform shows the opportunity. The retailer uses the digital twin to test how inventory decisions could play out before putting them into operation. The next discipline for any retailer scaling this approach is a closed reconciliation loop: every important physical event must confirm, correct, or reduce confidence in the system state.

Simulation accuracy is not perpetual inventory accuracy

Supply Chain Dive reports that Target used Proxima to simulate flows through its new 1.2 million-square-foot Houston Receive Center with about 98% accuracy before opening. In a smaller pilot covering 63 fresh-food items, simulations helped teams correct issues before launch and improve on-shelf availability by 2.5%.

Those results demonstrate real operational value. They do not mean the inventory record will remain 98% accurate after the model meets live receiving, handling, picking, damage, and shipping activity. A twin predicts what should happen. Reconciliation determines what did happen and updates the state used by the next decision.

The distinction matters because a small error can propagate. One unrecorded short receipt raises system inventory above physical inventory. Replenishment may then be suppressed, an online order may be promised against a nonexistent unit, and a picker may waste time at an empty location. Without a feedback loop, the twin can reproduce the bad state more efficiently.

Build a closed loop around six event families

Retailers should connect each simulated movement to an observable event, a timestamp, an identity, and an expected state transition.

Purchase order events establish the expected item, quantity, supplier, origin, appointment, and arrival window. Changes to quantity or timing must update the twin before the shipment reaches the facility.

Receiving events compare the advance shipment notice and purchase order with scans, counts, weights, and inspection results. Overages, shortages, substitutions, and unidentified units should enter an exception queue rather than silently becoming available.

Location events confirm that inventory reached the directed reserve, forward-pick, staging, or store location. A move is incomplete until the destination scan or another trusted sensor confirms it.

Pick events decrement the source location and connect the unit to an order, tote, pallet, or outbound load. A short pick should immediately lower confidence in the remaining location balance and trigger a targeted count.

Damage and adjustment events change both quantity and disposition. Sellable, hold, repair, return-to-vendor, and waste are different states; a generic adjustment reason destroys the evidence needed to diagnose recurring loss.

Shipment events reconcile packed, manifested, loaded, and departed quantities. The final departure confirmation should close the facility’s custody and transfer the expected state to the next node.

Every event should carry an event ID, item or license-plate ID, facility and location, quantity, event time, capture time, source system, and confidence score. Idempotency controls are essential so a retried message does not receive or ship the same inventory twice.

Let confidence control risky decisions

A retailer should not treat all inventory records as equally trustworthy. Confidence can combine the age of the last observation, capture method, unresolved exception count, sensor agreement, and historical accuracy of the process.

For example, records above 99% confidence may support normal replenishment and customer promises. Records from 97% to 99% could support replenishment planning but require a fresh confirmation before promising the last few units. Below 97%, the system could block scarce-unit promises and launch a cycle count. These are starting thresholds, not universal standards; retailers should calibrate them by item velocity, margin, perishability, and service risk.

Time matters as much as probability. A verified balance can become stale during a busy shift. High-velocity pick faces may need confirmation within minutes, while slow reserve inventory may tolerate hours. Confidence should therefore decay when expected events fail to arrive.

Automation increases the need for this discipline. A 2026 Modern Materials Handling survey of 166 warehouse, distribution, and manufacturing respondents found that 52% already used at least one type of robot and another 32% planned deployment within three years. Among robot users, 74% said projects met business goals, while 89% met or beat expectations for process performance, safety, and investment risk. As machines accelerate physical work, inventory-state errors can also spread faster unless system feedback keeps pace.

Measure accuracy, latency, and recovery

Four KPI groups reveal whether the reconciliation loop is healthy:

• State accuracy: location-level record accuracy, unit variance, lot or serial accuracy, and available-to-promise accuracy.
• Event latency: median and 95th-percentile time from physical action to committed system update for receiving, moves, picks, adjustments, and departures.
• Exception health: exceptions per 1,000 events, unresolved exception age, repeated discrepancies by process or device, and duplicate-event rejection rate.
• Recovery performance: time to detect a mismatch, time to correct it, cycle-count productivity, and the share of corrections completed before a replenishment or promise decision.

Track these metrics by facility, process, item class, shift, device, and integration—not just as a network average. A 99% average can hide one location where delayed events repeatedly corrupt high-volume items. Teams should also compare simulated and actual dwell times, routing choices, and quantities, then feed the variance back into model assumptions.

Make the twin accountable to reality

Target’s results show that digital twins can expose problems before operational change reaches the floor. Sustainable value comes when live operations continuously answer the model: this unit arrived, this pallet moved, this case was damaged, and this order departed.

CXTMS connects orders, inventory-related milestones, shipments, exceptions, and timestamps in a shared operational record, giving logistics teams the evidence to reconcile planned flows with physical execution. Request a CXTMS demo to build a more reliable physical-to-system control loop.