The Arbitrage Window
Asics runs drones. Your cycle count is still manual.
Warehouse drones cut inventory scan time and error rate. The gap between early movers and laggards is widening faster than most ops teams realize.
Asics is running drones through its warehouses. Not a pilot. Not a press release experiment. Operational inventory scanning, automated. While your team is walking aisles with handheld scanners and clipboards, a competitor in athletic footwear just removed that entire labor layer from its cycle count process. That is the gap. It is not theoretical.
What the drone move actually solves
Manual cycle counts have three failure modes. Speed, accuracy, and frequency. A human team scanning a large DC might complete a full count once a quarter. A drone fleet can run nightly. That frequency delta changes your in-stock visibility from a lagging indicator to something close to real-time. Asics is not doing this for optics. The brand is doing it because inventory inaccuracy has a direct cost in canceled orders, oversell events, and markdown exposure when phantom stock sits on a shelf that shows as available in your system but is not physically there. Every SKU with a location error is a potential service failure. Drones compress the time between error creation and error detection.
Build versus outsource: stop treating it as a binary
Most brands frame the automation question wrong. Build is capital-intensive and slow. Outsource means giving up control. Neither framing is accurate anymore. Third-party drone scanning services now offer per-scan pricing models. You do not buy the hardware. You buy the output, clean location data, cycle count reports, exception flagging. If your DC handles fewer than 50,000 SKU locations, ownership math rarely works in year one or two. Outsourcing the scan layer while keeping your WMS and fulfillment logic in-house is a viable middle path. The right question is not build or outsource. It is which layer of the automation stack do you need to own.
Who loses when they wait
Brands carrying seasonal velocity SKUs take the biggest hit from delayed cycle counts. If your sell-through windows run 8 to 12 weeks, a quarterly manual count means you are potentially operating on stale location data for the entire selling period. That produces two compounding problems. You cannot confidently commit inventory to promotional channels because you do not trust your on-hand numbers. And when you do run a markdown to clear aged units, you may be clearing stock that is already mislocated, triggering pick errors that drive return rates up. The landed cost of that inventory has already been absorbed. The markdown is pure margin destruction on top of a process failure.
The operational unlock for commerce leaders
Better inventory data at the location level is not a warehouse ops problem. It is a commerce problem. When your fulfillment system has accurate slot-level data, your available-to-promise logic improves. That means fewer order cancellations. Fewer customer service contacts. Lower NetPPM erosion on wholesale channels where fill rate penalties are contractual. Asics made this investment in its warehouse not because drones are interesting technology. Because inventory inaccuracy has a direct cost on its revenue line and its retailer relationships. If you sell through third-party retailers and you are under-filling purchase orders because your internal counts are unreliable, you are funding your competitor's shelf position with your own operational sloppiness. That is the real arbitrage window. The brands that fix location accuracy now will own the fill-rate advantage when wholesale buyers finalize their spring 2027 vendor scorecards.
Three questions to pressure-test
First: how many days of lag exist between a pick error occurring in your DC and that error showing up in your WMS as a location discrepancy? If you cannot answer in hours, your cycle count cadence is the problem. Second: what percentage of your wholesale order cancellations last quarter traced back to inventory inaccuracy rather than true stock-outs? Pull the data before you assume it is a demand forecasting issue. Third: if you switched to weekly location-level cycle counts tomorrow, which of your fulfillment partners or 3PLs could actually support that cadence with their current tooling? The answer tells you whether your automation gap is internal, external, or both. Run the audit. Then make the call.
Get The Beacon. Free, every Friday.
You're on the list.
The next edition lands in your inbox on Friday.