Kazam WMS · warehouse platform
TeamSystem is a leading Italian ERP, and among the most widely used in small and medium companies. But when the warehouse grows — more order lines, more operators, perhaps a first conveyor or an automated zone — running it on screens and spreadsheets stops working: you need handhelds, guided missions, stock by location. That is where Kazam comes in, without replacing the ERP.
How the integration works
Kazam talks to TeamSystem through a two-way data exchange (APIs and record layouts defined during the analysis phase, according to the TeamSystem product in use):
- From the ERP to Kazam: item, customer and supplier master data, orders to be received and orders to be fulfilled.
- From Kazam to the ERP: confirmed goods receipts, picks and shipments completed, inventory adjustments, batches and expiry dates moved.
The ERP remains the administrative and accounting reference; Kazam becomes the operational truth of the warehouse: who did what, where every parcel is, what is ready to leave.
Why smaller companies choose this pairing
For a company that is already paying for its ERP, moving the warehouse onto Zebra or Android handhelds does not add a fee that grows with the number of operators on the register: the plan depends on concurrent usage, across every route by which you can take Kazam (the figures). And the platform grows with the warehouse: the WMS with handhelds first, then WES and WCS when complex priorities or automation arrive, without changing system.
It is not the right choice for everyone, though. If the warehouse is small and predictable — a few lines a day, no automation — the ERP module may well be enough, and adding a WMS would complicate matters without giving anything back. Kazam starts to pay off when volumes grow or the first automation arrives.
What is needed from your side
Many smaller companies stop before they start, fearing a project that will tie up IT for months. The point is that in-house IT is often one person. Sometimes it is the consultant who looks after the ERP.
What is actually needed is less than you would expect: somewhere for TeamSystem to deposit the data and a way to read back the outcomes. The first is an exchange area, a database kept separate from the warehouse one. The ERP writes to it whatever it has to pass on, without knowing anything about how the warehouse works inside. The second is an interface that answers by quoting the ERP's own document numbers.
Whoever knows TeamSystem does not have to learn Kazam, and the other way round. The two sides meet on the record layouts, agreed once during analysis. From then on the ERP stays configured by the people who configure it today, with the same contacts as always. That is why the initial analysis counts for more than the technical link: once you have decided what the two sides exchange, the rest is mechanics.
What crosses over, and how often
From the ERP come the master records — items, customers, delivery addresses — the work documents with their lines, and the load units. A listening service reads the exchange area every few seconds and brings in whatever it finds. This is not an overnight import: there is no one-day gap between what the ERP says and what the warehouse sees.
Every record deposited has a status, and that is the part that saves you the headaches imports usually bring. If something breaks off, only the records not yet processed are picked up on restart. No duplicates appear and there is nothing to rebuild by hand. If the same item is amended several times in a row, the most recent version goes in and the others stay tracked as superseded.
The return direction works on request. The ERP asks for the status of a document quoting its own number and gets back what has been received, picked or shipped. Nobody has to copy anything out again, and that is precisely the point: double entry does not disappear because people work better, it disappears because it is no longer needed.
Frequently asked questions
Do we have to give up TeamSystem?
No, quite the opposite: the integration exists precisely to keep TeamSystem where it belongs (administration, accounting, invoicing) and to give the warehouse a dedicated operational tool.
How long does it take to go live?
It depends on the flows to be mapped; the initial analysis with a Sun Tech engineer settles the record layouts, the timescale and the scope. Get in touch for an assessment.
Do you handle batches and expiry dates?
Yes: traceability by batch, serial number and expiry date is native to Kazam, and the data goes back into the ERP with the confirmations.
Is any special hardware needed?
Any Android 9+ handheld with a scanner; deep integration with Zebra terminals through DataWedge.
Kazam is the source-available platform that covers WMS and WES and integrates with Sun Tech WCS. Talk to an engineer about connecting it to your TeamSystem.