Why Your Warehouse Stops the Moment SAP Does

“Once it leaves the dock, the data simply ends,” one VP of Operations at a manufacturing company put it. “SAP records the shipment, then it’s a source of belief, not fact.” The same thing is true before the dock: SAP knows what it was told to expect on the floor. It does not know what actually happened there, and when the ERP goes down for a maintenance window or an unplanned outage, most warehouse floors have no offline fallback at all. Picking, packing, and shipping stop cold, typically for four to six hours per incident, because there’s no system to keep work moving without it.

The Last 2 Percent Is the Expensive Part

Downtime is the dramatic version of the problem. The expensive version is quieter. Most warehouses hit somewhere around 97 to 98 percent pick accuracy, which sounds close to done. It isn’t. The last 2 percent is the most expensive part of the number, because every mis-ship at that level triggers a customer chargeback or an SLA penalty, and those eat margin faster than almost anything else in warehouse operations.

Paper and spreadsheets make it worse. A pick sheet or cycle count logged on paper is stale the moment it’s written, and batch uploads mean SAP is working from yesterday’s floor, not today’s. A meaningful share of warehouse labor goes to walking and searching for inventory that a live system would show instantly. Some sites have already tried fixing this with RFID, and the pilots usually work, technically. They stall in production because the integration back to SAP was custom-built in ABAP code, and every SAP upgrade, especially a migration to S/4HANA, tends to break it again.

Two Different Layers, Doing Two Different Jobs

The fix is two connected layers, not a bigger system. Data collection, sometimes called an Automated Data Collection System, is the capture layer: it reads every physical event on the floor- barcode, RFID, IoT, mobile, at the point of work and writes it back into the ERP in real time, covering goods receipt, put-away, pick, pack, ship, cycle counts, and serialization scans. That layer answers one question: what just happened? A Warehouse Execution System sits on top of it and answers the next one: what should happen next? It directs operators to the right bin, sequences the next pick, and confirms the work was done correctly before moving on. Capture without direction still leaves operators deciding what to do next on their own. Direction without capture means errors go undetected. Together, every move is directed, every move is confirmed, and the ERP stays current in both directions, not just when someone remembers to update it.

What Gartner Says About Which Warehouses Need What

Gartner has mapped this problem independently. In a June 2025 research note, “Choose the Right Software and Services for Low-Complexity and Pop-Up Operations” (G00835142), Gartner ranks warehouse operations across five levels of complexity, from a basic storeroom to a fully automated facility, and finds that traditional WMS platforms are built for the upper end of that range. Gartner’s own language: “This therefore leaves a very large number of warehouses for which WMS vendors’ primary offerings are not the best fit for their environments.” For that large middle group, too complex for spreadsheets but not complex enough to justify a full WMS, Gartner recommends mobile data collection instead, specifically because it works with the ERP investment a company already has rather than replacing it, and because SAP integration is the deciding factor in whether it delivers value. ACSIS is named in Gartner’s recommended sample of mobile data collection vendors for manufacturing and warehouse environments.

The Numbers

In production, this combination gets warehouses to 99.9 percent order accuracy, a 30 percent gain in site productivity, and 24/7 uptime that survives ERP downtime instead of stopping with it. Across regulated-industry deployments, the financial case adds up further: 15 to 25 percent labor cost reduction within 12 to 18 months, 2 to 5 percent of COGS recovered within about 18 months from eliminated shrinkage and excess safety stock, roughly 20 percent more order volume on the same headcount within 12 to 24 months, and $250,000 to $1 million or more per year in avoided compliance penalty exposure, starting immediately.

Proof: Three Ways This Plays Out

A global pharmaceutical company tracking medical devices across distribution centers, 3PLs, hospitals, and clinics worldwide was running more than 100 disparate, disconnected tracking systems with no central data and no SAP integration, and locating a device for scheduled maintenance was often impossible, which directly affected medicine sales tied to those devices. ACSIS replaced all of it with a single system combining data collection with returnable asset management, giving the company real-time visibility of every device and automated maintenance scheduling instead of a reactive, after-the-fact process.

A U.S. pharmaceutical manufacturer producing generic and branded specialty injectables had a different version of the same problem: BPCS as its ERP, Optel handling serialization, and a warehouse system that didn’t talk cleanly to either, with no automated, tamper-proof audit trail to support DSCSA compliance. ACSIS deployed its Edge Warehouse system as the operational backbone between ERP and serialization, including custom workflows for animal health products that fall outside standard DSCSA scope, across two manufacturing sites in under three months. “Antares Vision Group gave us more than just a replacement system,” the company’s Director of Supply Chain Operations said. “They delivered a complete solution that aligns with our business, ensures compliance, and supports the high volumes we process daily.”

The capture layer isn’t only a warehouse-floor story, either. It’s the same underlying data collection technology behind Hershey’s traceability program, applied to a food-safety problem rather than a pick-and-pack one. Hershey, one of the largest chocolate manufacturers in the world, was struggling to trace almonds used across multiple brands back to their production batch, with manual data capture creating errors and delays and putting FSMA 204 compliance at risk. ACSIS introduced RFID-based batch identification, automating data capture on fixed and handheld readers and integrating it with the production system in real time, giving Hershey complete batch-level traceability, forward and backward, with full confidence in the data. “Tech-enabled traceability has become an imperative for food and beverage businesses, particularly with the advent of FSMA 204,” said John DiPalo, ACSIS’s Chief Strategy Officer. “We help companies meet new requirements with ease, establishing an efficient and trusted traceability system.”

If your warehouse still depends on SAP being up, ABAP code holding an integration together, or a spreadsheet catching what a scanner should have caught, that’s the exact gap ACSIS closes. Talk to ACSIS about what closing it would look like at your sites.