Kazam WMS · warehouse platform
Your ERP stays yours. The warehouse becomes Kazam.
Kazam does not replace your ERP: it takes on the operational work of the warehouse and hands back to the ERP what has been received, moved, picked and shipped. Formats and exchange rules are agreed with you during the analysis.
What comes into Kazam, what goes back to the ERP
Scroll sideways to see all the columns →
| Stays in the ERP | Moves to Kazam | Goes back to the ERP |
|---|---|---|
| Master data and orders | Items, customers, suppliers, purchase and sales orders | — |
| Administration | Accounting, invoicing, fixed assets: Kazam does not touch them | — |
| Warehouse | Receiving, put-away, picking, stock counts, shipping | Quantities moved, adjustments, parcels shipped, traceability |
Two routes, one rule
The choice follows what your ERP is able to do, not what we would prefer.
Exchange area
The ERP drops its documents into a dedicated database; Kazam picks them up and updates the status of every record. Later versions replace earlier ones without creating duplicates.
API
When an immediate answer is needed, Kazam exposes token-authenticated APIs. The ERP can query the status of a document using its own number, without knowing Kazam's internal identifiers.
Correlation key
Every header and every line keeps the reference to the ERP document that generated the movement. If something does not add up, the origin stays explicit and can be queried.
Shared formats
Fields, formats and rules are defined during the analysis. If you change ERP in the future, what changes is the system that reads and writes the data contract, not the way the warehouse works.
Documented cases and bespoke integrations
SAP
What goes through the standard interfaces and what is agreed case by case.
Read the SAP case →TeamSystem
The most common pairing in Italian SMEs: the ERP stays, the warehouse moves onto the handhelds.
Read the TeamSystem case →Zucchetti
The warehouse stays independent of whatever you decide about the ERP later on.
Read the Zucchetti case →Microsoft Dynamics
Business Central and earlier installations, on the same data contract logic.
Read the Dynamics case →Odoo
Odoo covers the company, Kazam the warehouse: when it makes sense to keep them together.
Compare Kazam and Odoo →Bespoke ERPs
All your ERP has to do is write into an agreed area or call an API.
Talk to an engineer →Machines, not just documents
Where there is automation, Kazam talks straight to the plant: PLCs and industrial systems over OPC-UA, Modbus and FINS, autonomous guided vehicles over VDA 5050. This part does not go to the cloud, and that is not a commercial decision: it sits on the plant network because it has to answer in milliseconds. The layer that drives the machines is called Sun Tech WCS, and it is open source under the Apache License 2.0.
Everything else — e-commerce, carriers, analytics tools — goes through the same two routes as the ERP: exchange area or API. How the platform is built.
Bring us your ERP.
Thirty minutes with an engineer to establish what your ERP exposes and how to build the exchange. If the integration is not feasible the way you picture it, we say so within that half hour.