A separate warehouse system, or barcodes inside the ERP?
Version 1.0 — Last updated:
Separate warehouse system or barcodes inside the ERP? If your warehouse work is shipment checks, picking, stock counts and transfers, a barcode add-on that writes to the ERP's own stock records avoids duplicate data and integration work. If goods receipt, put-away or carrier integration are central, a separate warehouse system may fit better.
When a company running Workcube or any other ERP decides to take its warehouse off paper, the first question is usually this: do we add a separate warehouse system next to the ERP, or work with barcodes inside the ERP? This post, by the founder of Turkey-based Gramoni, sets out four vendor-neutral criteria for that decision. It then explains where our own product sits, including what it does not do.
Common ground: the barcode
Whichever route you take, the warehouse speaks in barcodes. According to GS1, barcodes carry identifiers such as product, shipment and location, and attributes such as batch/lot numbers, serial numbers and dates, in a form that can be scanned electronically. GS1's Global Trade Item Number (GTIN) can be used by a company to uniquely identify all of its trade items.
So the decision is not whether to use barcodes. It is which system, and which record, a scan is written to.
Criterion 1: Data duplication
A separate warehouse system keeps its own product card, its own location master and often its own stock quantity. The ERP holds the same products and the same stock. The two must be synchronised, and when synchronisation lags or one side fails, the question becomes "which stock figure is right?"
With barcodes inside the ERP, stock lives in one place: a movement made on the device is written straight to the ERP's stock records.
Question to ask: Which system will be the single source of truth for stock?
Criterion 2: Integration
Eurostat defines internal integration as sharing information electronically and automatically between a company's business functions, and describes ERP as software that does this through modules. Choose a separate warehouse system and that integration becomes a project item: orders must flow from the ERP to the warehouse system, and shipped quantities back. An interface is built, an error queue is monitored, and the interface is retested whenever either system is upgraded.
A barcode add-on inside the ERP has no such interface with the ERP; it works on the ERP's own records.
Question to ask: Who builds the interface between the two systems, who monitors it, and who retests it after an upgrade?
Criterion 3: Licence model
A separate system usually brings its own licence and its own maintenance contract, and the licence may scale with users, devices or transactions. If the warehouse team grows in peak season, or several group companies share a warehouse, that difference changes the sums.
Question to ask: What does the licence scale with: users, devices, companies? Will maintenance be two separate contracts?
Criterion 4: Process depth
This criterion can favour a separate system. If goods receipt, put-away, packing, carrier integration and route optimisation are at the centre of daily warehouse work, a separate warehouse management system (WMS) designed to handle these processes in depth may be the better fit. In that case the integration cost above is taken on deliberately.
If warehouse work is mainly shipment checks, picking, stock counts and transfers, that depth is often not needed.
Question to ask: Where does most warehouse time go, and are those tasks within the scope of a barcode add-on to the ERP?
Side by side
| Criterion | Barcodes inside the ERP | Separate warehouse system |
|---|---|---|
| Stock record | One place: the ERP | Two places; synchronisation needed |
| Integration | No separate interface with the ERP | Interface for orders and shipments, built and monitored |
| Licence | Depends on the add-on's model | Separate licence and separate maintenance |
| Process depth | Limited to the add-on's scope | Can go deeper in goods receipt, put-away and similar processes |
Where WAMS Logistics sits
WAMS (Workcube Advanced Manufacturing System) Logistics is an example of the first route, and it is not a warehouse management system. It is an add-on for Workcube, a Turkish ERP platform, that moves warehouse and field work from paper to a barcode device. It is delivered as a browser-installed PWA, the kind of installable web application defined by the W3C.
What it does:
- Barcode shipment checks: product barcode, shelf location, lot and quantity are scanned in turn.
- Allocation-based picking: the office plans the shelf, lot and quantity allocation, the floor carries it out, and the picked quantity is written back to Workcube.
- Stock counts and warehouse transfers from the device; a count arrives in Workcube as a document awaiting approval.
- Transfers are queued when there is no connection.
- Pallet management and labels.
- Every movement is written to Workcube's own stock and period records; no separate warehouse system is needed alongside Workcube.
What it does not do:
- Goods receipt, put-away and packing.
- Creating dispatch notes or invoices.
- Serial-number tracking.
- Correcting stock directly from a count.
- Store apps, carrier integration and route optimisation.
Licence: perpetual system licence (no user or company limit within the same installation), setup and training, and an annual maintenance and update contract (LYKP).
So if your warehouse work is mainly shipments, picking, counts and transfers, and you run Workcube, WAMS Logistics gives you the advantages of the first route on these four criteria. If the processes on the "does not do" list are central for you, that is worth discussing up front.
Before you decide
According to the Turkish Statistical Institute (TÜİK), 28.3% of enterprises with 10 or more employees used ERP software in 2025. For a company without an ERP the question is different: first choose the system that will hold stock, then decide on the warehouse. Our ERP selection guide can help with that step.
For a company that already has an ERP, a practical suggestion: before deciding, spend a week or two noting where the warehouse team's time goes: shipment checks, picking, counts, transfers, goods receipt, put-away, packing. Also mark where stock differences most often appear. That list shows, without debate, which of the four criteria weighs most for you. Check the master data too: if product cards have no barcodes and the warehouse has no shelf locations defined, that will be the first job whichever route you take.
If you run Workcube and want to assess your warehouse against these criteria, book a call.
Frequently asked questions
When is a separate warehouse system the better choice?
When processes such as goods receipt, put-away, packing, carrier integration or route optimisation are at the centre of daily warehouse work. These can go beyond the scope of a barcode add-on inside the ERP, and the integration between the two systems then becomes part of the project.
What is the main advantage of barcodes inside the ERP?
Stock lives in one place. A movement made on the device is written to the ERP's own stock records, so there is no stock synchronisation between systems, no second product card and no separate integration to maintain.
Is WAMS Logistics a warehouse management system (WMS)?
No. WAMS Logistics is a Workcube ERP add-on that moves warehouse and field work onto a barcode device. It handles shipment checks, allocation-based picking, stock counts and warehouse transfers, and writes each movement to Workcube's own stock records.
What does WAMS Logistics not do?
It does not do goods receipt, put-away or packing; it does not create dispatch notes or invoices; it does not track serial numbers; and a stock count does not correct stock directly but arrives as a document awaiting approval. Store apps, carrier integration and route optimisation are also out of scope.
How is WAMS Logistics licensed?
With a perpetual system licence, with no user or company limit within the same installation, plus setup and training and an annual maintenance and update contract (LYKP). Figures are quoted per project.
Sources
- GS1 Barcodes — GS1
- GS1 — Global Trade Item Number (GTIN) — GS1
- Eurostat — E-business integration (2025 data) — Eurostat
- TÜİK — Girişimlerde Bilişim Teknolojileri Kullanım Araştırması, 2025 (ICT usage in enterprises) — Turkish Statistical Institute (TÜİK)
- W3C — Web Application Manifest — World Wide Web Consortium