Barcode Warehouse on SAP Business One: Build or Buy?

This guide is for owners, stores managers and IT heads at manufacturers whose SAP Business One stock never quite matches the shelf. You have decided you need barcode scanning in the warehouse. The next question is whether to buy a packaged add-on or have a scanning app built around your process. We build custom warehouse apps, so we have a view — but both options are valid, and the right answer depends on your plant.

First: what a barcode warehouse (WMS) does

WMS stands for warehouse management system. On SAP Business One, it is a mobile layer: staff use handheld scanners to record every stock movement as it happens, and each scan posts to SAP. Typical functions:

• Receiving — scan goods against the purchase order and post the goods receipt (GRPO).
• Putaway — scan items into a bin location, so SAP knows where they are.
• Picking — scan items against the sales order or production order; wrong item or batch is stopped.
• Issues — material issue slips and store requests on the scanner, against cost centres or production orders.
• Transfers — between bins, warehouses and branches.
• Cycle counts — regular scan-based counts instead of a long annual count.
• Batch rules — first-in-first-out (FIFO) or first-expiry-first-out (FEFO) picking for batch industries.

Whichever option you choose, it should use SAP's item master and warehouse definitions as the single source of truth and post through SAP's official interfaces.

Option 1: buy a packaged add-on

A packaged WMS add-on is a ready-made product, sold to many SAP Business One companies, usually with a licence or subscription fee.

Where it is strong

• Standard warehouse functions are already built and tested by many users.
• Can be quicker to start when your process matches the product.
• The vendor maintains the product and releases updates.

Where it can be weak

• Your process has to fit the product's screens. If it doesn't, you either change your process or pay for customisation.
• Industry-specific needs — tile shade and calibre on each pallet, heat numbers on castings, roll-wise textile stock, container loading — may not be covered.
• Connecting a weighbridge, gate or dealer portal usually means another product or more customisation.
• Ongoing licence fees per user or device.

Option 2: build a custom scanning app

A custom app is designed around how your warehouse and plant actually work, and connected to your SAP Business One.

Where it is strong

• Screens match your process and your people — fewer steps for the things you do most.
• Industry-specific data (shade, calibre, grade, heat, roll, lot) can be built in from the start.
• Can join up with the gate, weighbridge, dispatch and dealer portal in one flow.
• Changes as your process changes.

Where it can be weak

• Takes design and testing time before go-live.
• Its quality depends entirely on the team that builds it — and that team must be around to support it.
• If the scope is not controlled, a custom app can grow into a project that never ends.

Side by side

When buying fits

• Your warehouse process is fairly standard: receive, store, pick, ship.
• You don't need weighbridge, gate or dealer-portal links in the same flow.
• You prefer a product with a vendor roadmap, and you are happy to adapt your process to it.

When building fits

• Your stock has industry-specific details — shades, calibres, heats, rolls, lots — that must be scanned and checked.
• Stores, gate, weighbridge and dispatch should work as one flow posting to SAP.
• You have tried a packaged product and spent more on workarounds than on the product.
• Supervisors and pickers need very simple screens in harsh conditions.

Questions to ask either way

1. Does it post to SAP through the Service Layer or DI API — SAP's official interfaces — and never by writing to SAP tables directly?
2. Does it use SAP's item master and warehouses, or keep its own copy?
3. Which scanners does it run on, and how does it behave if Wi-Fi drops in a corner of the godown?
4. Does it work on SAP Business One on both SQL Server and HANA, on premise and in the cloud?
5. Who supports it, during which hours, and is an annual maintenance contract available?
6. Can you see it working in a warehouse like yours?

What we build

Our barcode warehouse runs on rugged Android scanners and web dashboards, using SAP Business One item masters and warehouse definitions as the single source of truth. It covers bin-level stock, FIFO/FEFO picking, material issue slips and store requests, multi-warehouse and inter-branch transfers, and barcode cycle counts — and it can link to our weighbridge and gate integration. It works on SAP Business One SQL Server and HANA, on your server or on our Cloud for SAP. In one tile exporter project, the client measured 99.8% inventory accuracy after go-live (see projects); your result depends on your warehouse and how consistently scanning is followed. Details: barcode WMS for SAP Business One.

If a packaged add-on is the better fit for you, we'll say so in the audit.

Frequently asked questions

Is a custom warehouse app risky when SAP is upgraded?

Not if it connects through SAP's official Service Layer or DI API rather than editing SAP tables. That is how we build ours.

How long does a barcode warehouse take to go live?

Barcode stores are a common first automation stage, typically live in 60–90 days including testing at your plant.

Do we need new SAP licences for scanner users?

Scanner users work in the warehouse app rather than SAP itself, which reduces the number of SAP licences you need — we check your licence position during the audit.

Can we start with one warehouse?

Yes. Many plants start with the main store or finished-goods godown and add others after go-live.

Related: automating goods receipt (GRPO) · custom software vs SaaS · ceramic tile playbook · shop-floor automation.