In short
Many Italian SMEs running SAP Business One still manage receiving, picking and stocktaking on paper or in spreadsheets: an operator prints a pick list, works through it by hand, and reloads the movements into SAP B1 at the end of the shift or the day. This works fine at low volumes. It stops scaling once SKU count or daily order volume grows, or once lot traceability requirements come into play — paper handles those poorly. This article lists the concrete signs to watch for and explains what genuinely changes — not in generic terms — when moving to a mobile-first WMS natively integrated with SAP B1.
How a paper-based warehouse on SAP B1 actually works
The most common pattern is simple: the order is generated in SAP Business One, an operator prints the pick list, walks the warehouse with it, and marks quantities picked and any substitutions or shortages by hand. At the end of the day (or shift, in more structured warehouses), someone manually reloads the movements — picks, receipts, adjustments — into SAP B1.
At low volumes, with few SKUs and few daily orders, this works: occasional errors get absorbed, the evening reload takes minutes, and nobody feels the need to change something that “mostly works.”
The hidden cost of the paper-to-ERP double step
The problem isn’t slowness by itself. For hours every day, there are two sources of truth: what actually happened in the warehouse, and what SAP B1 believes happened.
The consequences show up in practice:
- Unreliable stock levels for sales: a salesperson can promise goods that are already committed but not yet deducted in the system, because this morning’s pick hasn’t been reloaded yet.
- Transcription errors: quantities, item codes or lots mis-copied by hand become a wrong movement in SAP B1, often only discovered at the next stocktaking.
- Wasted operator time: someone has to spend part of the day just reloading data — an activity that adds no value and scales linearly with volume.
- Late discovery of expiry dates: without an automatic FEFO/FIFO check at pick time, an expiring lot can sit forgotten in a bin location until it becomes a real problem.
The signs that paper has stopped scaling
Not every warehouse needs to go digital. But a few signs clearly indicate that the paper-to-ERP double step has started costing more than it saves:
- The paper pick list has become too long or too frequent to manage by hand, due to growing SKU count or daily order volume.
- The sector requires lot and expiry traceability (food, pharma, cosmetics) and paper can’t reliably enforce a block on non-compliant lots.
- Order fulfillment errors (shipped different from ordered) are increasing and starting to generate returns or complaints.
- Cycle counting needs to happen by zone or ABC class without stopping operations — something nearly impossible to coordinate well on paper.
What changes with a mobile WMS integrated via Service Layer
A mobile-first WMS that talks to SAP Business One through the Service Layer removes the double step: every warehouse operation is reflected in SAP B1 the moment it happens, not at the end of the day.
Guided receiving and putaway
Receiving starts from the supplier’s delivery note: the operator counts goods with a barcode scanner, the system automatically flags anomalies (quantity different from expected, unexpected item), and putaway suggests the most suitable bin location. Internal labeling, when needed, happens right away, not later.
Picking with scanners and bin locations
Guided picking takes the operator straight to the correct bin locations via the scanner, and every pick confirmation is reflected immediately in SAP B1. There’s no evening reload: once the operator confirms on the terminal, the movement is already written to the ERP.
Lots, expiry dates and cycle counting
FEFO/FIFO logic is automatic: the system suggests the correct lot to pick and blocks non-compliant or expired ones. Cycle counting can be scheduled by zone, item or ABC class, counting in stages without stopping day-to-day warehouse operations.
Comparison table
| Dimension | Paper warehouse with evening reload | Mobile WMS integrated with SAP B1 |
|---|---|---|
| SAP B1 stock update | End of day/shift | Real-time on every confirmation |
| Lot and expiry traceability | Manual, error-prone | Automatic (FEFO/FIFO), with non-compliant lot blocking |
| Transcription errors | Frequent on quantities and codes | Reduced by barcode scanning |
| Time spent on data reload | Grows with volume | Doesn’t exist as a separate activity |
| Real-time visibility for sales | Low, data hours old | High, aligned with the actual warehouse |
| Cycle counting without stopping operations | Hard to coordinate | Schedulable by zone/item/ABC class |
When paper can still be enough
To be honest about it: not every warehouse needs a mobile WMS. If volumes are low, SKU count is small and stable, there are no lot or expiry traceability requirements, and no near-term growth is expected, the paper-to-ERP double step can remain the simplest and cheapest choice. Every MTF.Warehouse installation is dedicated to the customer that adopts it — there’s no point digitising a process that already works well at current volumes.
Frequently asked questions
How long does it take to move from paper to a mobile WMS on SAP B1?
It depends on how many processes are involved in the transition (picking only, or also receiving and stocktaking) and on the complexity of the existing warehouse. You can start with a single flow and expand later, to keep the first go-live contained.
Do I need new warehouse hardware, or do scanners work on the existing network?
In most cases, terminals with barcode scanners compatible with the existing warehouse Wi-Fi are enough. Replacing the network infrastructure is rarely necessary to get started.
What happens to stock levels during the transition?
The transition should be handled with an alignment stocktake at the start, so that SAP B1 stock levels match physical stock before switching current flows over to the mobile WMS.
Does the mobile WMS work on SAP B1 running on HANA too?
Yes. MTF.Warehouse is compatible with SAP B1 10.0+ on both Microsoft SQL Server and SAP HANA.
Can I start with just one process and add the rest later?
Yes, and it’s often the more prudent choice: teams typically start with picking, which has the most immediate impact on stock accuracy, and then extend to receiving and cycle counting.
What MTF does here
MTF is a SAP Silver Partner and has been implementing SAP Business One for Italian SMEs since 2017. When a warehouse outgrows what paper can manage — growing SKU counts, lot traceability requirements, the need for cycle counting without stopping operations — we use MTF.Warehouse, our mobile solution for receiving, bin locations, picking, lots and expiry dates, natively integrated with SAP Business One through the Service Layer.