How barcode data bridges the gap most ERPs can't close alone

Ask a plant manager where job #4521 is right now, and you'll usually get one of three answers: a guess, a phone call out to the floor, or someone walking the line to go look. That's not a people problem; it's a data problem. And it's far more common than most operations leaders would like to admit.

According to Zebra Technologies' 2024 Manufacturing Vision Study, only 16% of manufacturing leaders worldwide say they have real-time work-in-process (WIP) monitoring across their entire production process. The other 84% are running the business on a picture of the shop floor that's already out of date by the time anyone looks at it.

If your ERP went in years ago and WIP visibility still feels like a mystery, you're not behind, you're normal. Here's why the gap exists, what it costs, and how barcode data closes it without a system replacement.

What "WIP tracking" means

Work-in-process is everything between raw material and finished goods: the parts sitting at a work center, the sub-assembly waiting on inspection, the lot that's 60% through its routing. Tracking it well means being able to answer, at any moment, where a given job is, how far along it is, how much material and labor it has consumed, and whether it's on schedule, not just where it was as of last night's data load.

That distinction matters more than it sounds like it should, because most ERPs were never built to answer the "right now" version of that question.

Why your ERP wasn't built to close this gap alone

ERP systems are, by design, systems of record for planning and financials. They're excellent at centralizing purchasing, costing, scheduling, and reporting. What they're generally not built for is continuous, minute-by-minute data collection from the shop floor. Status updates typically arrive as transactions, someone keys in a quantity, closes a work order, or runs an end-of-shift batch, which means the ERP's view of WIP is only as current as the last person who updated it.

This isn't a knock on any particular ERP platform. It shows up almost everywhere, and it compounds when data collection depends on paper travelers, whiteboards, or spreadsheets that get reconciled after the fact than captured as work happens. A 2024 Manufacturing Leadership Council survey, cited by industrial software firm Harmoni, found that 53% of manufactures pointed to inconsistent data across systems as a top operational challenge, even though 73% already run an ERP and 82% already collect data from shop-floor PLCs or DCS systems. The systems exist. They just don't talk to each other, or to the floor, in real time.

What the blind spot costs

A WIP visibility gap rarely shows up as one dramatic failure. It shows up as a hundred small ones that add up:

• ‍Inventory drift. A transposed quantity or a late-keyed transaction creates phantom WIP, inventory the ERP thinks exists (or doesn't) that doesn't match the floor.‍
• Expediting chaos. When nobody can confirm a job's real status, "just in case" expediting becomes the default response to every customer call.‍
• Missed promise dates. Planners scheduling against yesterday's data will keep producing schedules that don't match today's reality.‍
• Traceability risk. If a quality issue surfaces downstream, tracing which work centers, operators, and lots touched a given unit is only possible if that movement was captured.

The root cause behind most of these is the same: manual, after-the-fact data entry. Studies on manual keying consistently put the error rate around one mistake per 300 keystrokes. In a plant processing thousand of transactions a day, receipts, operation completions, moves, scrap that error rate compounds into inventory and status records nobody fully trusts, which is exactly the condition that keeps plant mangers walking the floor to double-check what the system already claims to know.

How barcode data closes the gap

The fix isn't a bigger ERP; it's better data at the point where work actually happens. This is what "point-of-activity" data capture means in practice: instead of writing a quantity on a traveler and keying it in later, an operator scans a barcode the moment material is issued, an operation starts, a unit moves, or a job completes. That scan generates the transaction instantly, at the source, with no re-keying step in between.

The accuracy difference is well documented. Operations relying on manual or partially manual data entry typically run inventory accuracy in the 63-85% range; operations with well-implemented barcode scanning routinely reach 95-99.9%. The gap isn't about how careful your team is, it's about how many opportunities the process gives them to make a keying error in the first place.

A barcode-enabled WIP workflow typically looks like this:

• ‍Event : Material issue What gets scanned : Lot/license plate → work order  What it updates : Raw material consumption ‍
• Event : Operation start  What gets scanned : Operator badge + work center + work order What it updates : Labor and routing status‍
• Event : Operation complete / move  What gets scanned : Work order →  next work center or staging location What it updates : WIP location and progress‍
• Event : Scrap or exception What gets scanned : Reason code What it updates : Quality and yield data‍
• Event : Finished goods What gets scanned : Unit/pallet → putaway location What it updates : Inventory and order status

Every one of those scans is a transaction pushed to the ERP or WMS in real time, rather than a note that waits for someone to find their time to enter it.

You don't need to replace your ERP to get this

This is the part that surprises a lot of operations leaders: closing the visibility gap doesn't require ripping out the ERP or host system you already have, including older platforms that weren't designed with real-time shop floor integration in mind. What it requires is a data capture layer, rugged handhelds or vehicle-mounted computers, durable barcode labels built for plant floor conditions, and an integration path into your existing system, sitting between the floor and the ERP, feeding it accurate, timely transactions instead of waiting on manual updates.

The most effective rollouts don't try to instrument the entire plant on day one. They start at the highest-friction handoffs, the points where "we don't actually know where that job is" comes up most often, prove the workflow there, and expand from that foundation.

Where to start

Before evaluating any hardware or software, it's worth mapping your current WIP process honestly:

1. Where do status updates currently get keyed in, and how much time passes between the event and the entry?
2. Which handoffs (receiving, work center transfers, finished goods) generate the most "where is it?" questions?
3. Which of those handoffs already involve a label, traveler, or ID that could carry a barcode?

Those answers usually point straight to where a pilot should start.

The takeaway

Real-time WIP visibility isn't a licensing upgrade or a system replacement, it's a question of how and when data enters your ERP in the first place. Barcode data capture is the layer that turns "we'll find out at shift change" into "we already know," using the system you already have.

If you want a second set of eyes on where your own WIP process loses visibility, Ahearn & Soper has spent decades connecting barcode and mobile data capture into existing ERP, WMS, and host systems for manufacturers and distributors, including the kind of legacy platforms most vendors won't touch.

Sources

Zebra Technologies, "Zebra Study: Only 16% of Manufacturers Have Real-Time Visibility into Manufacturing Production," 2024 Manufacturing Vision Study, June 2024. [^2]:Panorama Consulting Group, "Why Digital Transformation Hasn't Solved Production Visibility In Manufacturing," 2025. [^3]: Harmoni, "What Is Manufacturing Visibility?" citing the Manufacturing Leadership Council's 2024 survey, 2026. [^4]: Advanced Automation, "10Causes of Warehouse Barcode Data Errors and What They're Actually Costing Your Operation," 2026.