Month-end at a spare parts distributor. The system says there are 40 filters in the Quilicura warehouse; the warehouse lead finds 31, spread across three aisles. Accounting asks what the difference is worth, and nobody knows whether to use the last purchase price or the average. The batch that expired in September still shows as available.
If you're looking at SAP Business One inventory management, warehouses and batches are usually why a distributor ends up on this ERP. Or you already run it and feel like the warehouse and the system tell two different stories. Either way, it helps to separate three things: what the standard product handles, what depends on how you configured it, and what needs an add-on. Below is a walk through the warehouse management features SAP ships with the product and the cases where you need something more.
What SAP Business One includes for inventory and warehouses
The inventory module covers what a distribution or light manufacturing company needs to operate. These are the main pieces, according to SAP's documentation:
| Feature | What the standard product does |
|---|---|
| Multiple warehouses | Stock, commitments and orders per warehouse; transfers and transfer requests between warehouses |
| Bin locations | Up to four sublevels per warehouse (zone, aisle, shelf, level), with default bins per item |
| Batches and serial numbers | Tracking by serial number or batch on every movement, with inbound and outbound traceability |
| Valuation | Moving average, standard, FIFO and serial/batch valuation, under perpetual inventory |
| Inventory counting | Counts with one or several counters, item freezing, Excel import and cycle counts with alerts |
| Pick and pack | Release to pick list from sales orders, production orders, transfer requests and reserve invoices |
None of this is an add-on. The details are in the official SAP Business One help and in the SAP Business One... To Go guide, which is from an older release but still explains bin locations and cycle counts well.
Batches and serials: two separate decisions
Managing an item by batch or serial and valuing it by batch or serial are separate choices, and people mix them up all the time.
SAP spells it out in its serial/batch valuation guide: an item valued by FIFO, moving average or standard can still be tracked by batch or serial, but it doesn't have to be. If you choose serial/batch valuation, though, the item must be managed by serial or batch on every transaction, no exceptions.
When does each one make sense?
- Batch tracking with average cost: food, chemicals, cosmetics. You care about which batch went to which customer and when it expires, but you don't need the margin on each batch.
- Serial valuation: high-value equipment where each unit has a different cost (machinery, vehicles, medical devices). SAP's own example is a truck.
- Batch valuation: large volumes of lower-value items where cost changes from one import to the next, such as pharmaceuticals.
A bad choice won't show up in the first month. It shows up at closing, when margin by product doesn't match what sales thinks it's making.
Valuation: you pick the method once and live with it for years
With perpetual inventory turned on, SAP Business One works with four methods: moving average, standard, FIFO and serial/batch. You set the method by item group or by item, and you can also decide whether cost is calculated at company level or per warehouse (the "manage item cost per warehouse" setting).
That last setting causes the most debate. If you have one warehouse in Santiago and another in Antofagasta and freight up north is expensive, costing per warehouse reflects reality better. It also makes transfers and consolidated reports more complicated. There's no universal answer. Sit down with accounting before the initial load, because changing the method later, with stock and movements in place, is delicate work.
To compare scenarios before you decide, SAP includes an inventory valuation report that simulates stock value using moving average, FIFO, a price list or the last evaluated price. Run it on your real data, not a training example.
Counts and variances: where you find out if the setup works
For a distributor, counts are the real test of stock control. SAP Business One lets you create a counting document, freeze items so they don't move during the count, assign one or several counters (individual or team) and then post the variances from that same document. You can import results from Excel, and you can count by batch, by serial number and by unit of measure.
To stop relying on the annual count, there are cycle counts: you assign a frequency by item group or warehouse sublevel, and the system alerts a user when it's time to count. It's the simplest way to move from one big count in December to rotating counts of the items that move most or are worth most.
Two practical tips:
- Post every pending movement before you open the count. If yesterday's delivery note isn't entered, the variance is fake.
- If you enter the count late (the physical count was on the 31st and you enter it on the 3rd), use the actual count date in the document so the variance is calculated against the right stock.
When SAP Business One needs a complement
The standard product handles inventory logic well. What's usually missing sits in the physical warehouse work and in the connections to other systems:
- On the desktop, picking and counting run on documents on screen or on paper. If your warehouse staff need to scan barcodes or QR codes on a mobile device and have stock update on the spot, you normally add an app or a partner solution connected to the ERP.
- In high-volume warehouses, replenishment rules between bins, wave picking, route optimization and dock control fit better in a dedicated WMS than in the inventory module of an SMB ERP.
- An online store, a marketplace or a third-party logistics provider needs to read stock and create orders in the ERP. That's an integration job, through Service Layer or DI API.
- Turnover, coverage, stockouts and slow-moving stock can be queried in the system, but a dashboard that combines sales, purchasing and inventory is usually built separately.
SAP keeps investing in the web client: according to SAP's official community, Feature Package 2602, released in February 2026, added inventory and logistics features to that interface. Before you build anything, check what your version includes; sometimes what used to need custom work is already standard. We covered how to make that call in SAP Business One consultant: when to build custom.
And if you're still on spreadsheets or an older system, order matters: first a reliable physical count, then migration. In SAP Business One migration: what data to bring we explain how to load opening stock and costs without carrying errors over.
Frequently asked questions
Does SAP Business One handle several warehouses and bin locations inside each one?
Yes. You can have multiple warehouses and, inside each, turn on bin locations with up to four sublevels (for example zone, aisle, shelf and level), with a default bin per item.
Can I track batches with expiry dates without valuing by batch?
Yes. An item can be managed by batch and valued with moving average, FIFO or standard. Serial/batch valuation is a separate option and requires the item to be managed by serial or batch on every transaction.
Do I need a WMS on top of SAP Business One?
It depends on volume and on how your warehouse works. For most SMBs, the standard product plus a mobile capture app is enough. A WMS makes sense when you have many bins, a high number of daily shipments and complex replenishment rules.
Next step
If your SAP Business One inventory doesn't match the warehouse, or you need your warehouse staff working with scanners or QR codes connected to the ERP, Disrupsoft builds integrations with Service Layer and DI API, inventory extensions with Power Platform and stock dashboards in Power BI. Let's talk at disrupsoft.cl/en/service/sap.
