Kazam WMS · warehouse platform
The warehouse configures itself by talking.
The assistant interviews the people who know the warehouse — areas, flows, product attributes — and prepares a configuration that you verify and approve before it is applied. It is not a closed-answer questionnaire: it gets into the specifics of your industry.
Today the interview is conducted in Italian; the names proposed for areas and views are born in your language.
The right questions come from the trade, not from a form
A configuration form asks “do you need a UDC buffer?”. The assistant asks where you place the pallets ready for loading, then proposes the coherent area type — and you approve it. On attributes it suggests the examples of your industry — tone, choice and calibre in ceramics; batch and expiry in food; melt and job order in metalworking — then the choice remains yours.
Before every question it explains what it is asking and why; before recording an answer, what it will mean in operation. A wrong configuration does not show on day one: it shows a month later, when the operator can no longer find the pallet.
Eight stages, in this order
The first answer determines the questions that follow.
Scope of the flows
Define what to manage: receiving, internal activities and shipping. The next questions adapt to the chosen scope.
Warehouse
State the name, the structure and the criteria by which operators and systems identify the cells.
Containers
Describe pallets, boxes and other formats with dimensions, capacity and default format.
Areas and cells
Collect the zones one at a time; the assistant proposes the coherent type and you confirm it.
Load unit statuses
Define statuses such as to be checked, checked or blocked, and the operational effect of each.
Workflows
Describe putaways, picks, extractions and returns before linking them to the right flow.
Product attributes
State what you need to search, filter, print or use in picking rules.
Final settings
Complete rotations, units of measure, area groups and document types; whatever is not needed is skipped.
At the end you receive a complete summary, including the sections you chose not to configure.
The assistant proposes. You approve
It reads, it does not modify
The assistant consults configuration and plant status in read-only mode. Every change goes through a plan that you approve.
The plan is verified first
The configuration engine validates dependencies and errors before showing you the proposal, preventing deletions or inconsistent references.
Explicit, traceable changes
Creations, updates and deletions are declared in the plan. Nothing is applied until you confirm.
It sets up operators and equipment
The plan can create linked positions and operational users, without administrative privileges and without default passwords.
The views you need, described in words
Describe in words the data you want to see — columns, filters, groupings — and the assistant writes the query for you. It tests it on your database, and if it fails it automatically handles the technical errors and corrects the query. Then it shows you the first rows and records it only after your confirmation, in the Queries menu of the portal and of the desktop client.
Here too it is read-only: queries that read, never write. Dashboard indicators with charts have a dedicated designer today, which stays in your hands.
From the product bar, without leaving your work
Report a problem
Open a report from the header without leaving the screen; severity and context travel with the request.
Propose a feature
The suggestion enters the product team backlog, not a generic mailbox.
The answer comes back into Kazam
A counter signals the answers and keeps the history inside the application.
Gaps are not hidden
If the assistant does not know the answer, it records the question without making things up and forwards it to the team.
Two features in development
KPIs too, not just views
You will describe the indicator in words; the assistant will compose it and record it only after your confirmation.
Assistance that solves itself
The assistant will recognise known cases, propose a fix and open an already-documented report when needed.
These features are not available today and do not yet have a declared release date.
Clear boundaries, stated upfront
It is not a consultant and does not decide for you: it proposes, and applies only after your approval. It does not answer questions unrelated to the warehouse. The interview is conducted in Italian; the names proposed for areas and views are born in the language of the person answering. Assistant and reports are reserved for plant administrators.
And it is not included in the base version: the assistant is activated on request, when Suntech issues the customer token. Where it is not active, the entry does not even appear in the menu.
What we are asked most often
Can the assistant change data on its own?
Do I need to describe the warehouse in technical terms?
If I get an answer wrong, how do I fix it?
Where do reports and questions end up?
See how the assistant would configure your warehouse.
Within one business day an engineer, not a salesperson, replies and opens your access: together you look at the configuration that would come out of it.