Kazam WMS partner programme
Kazam is also built for those who build solutions for their own customers: integrators, system providers, software houses. The partner programme gives access to the sources, dedicated training and a direct line to the people who develop the product. This page does not ask you to trust us: it gives you the numbers and the terms to do the maths.
The offer in three lines
You resell Kazam to your customers, under your brand or ours, paying Sun Tech a royalty of 10% on the software you invoice. The services you deliver — analysis, configuration, integration, go-live, training, support — stay entirely yours and outside the calculation.
You receive the sources under a confidentiality agreement, so you can adapt the product to out-of-standard requests without opening a ticket and waiting. Behind you are the people who wrote the code.
It is the model designed for those who sell projects, not licences: the margin is in the service, the software is the base you build it on.
Royalty and reference price list
The partner pays Kazam a royalty equal to 10% of software revenue, calculated on amounts net of VAT, discounts and credit notes. Analysis, configuration, integration, go-live, training and support delivered by the partner are excluded from the royalty.
Example. If the partner invoices €5,900 for the Kazam software licence, the royalty is €590. Professional services invoiced separately by the partner are not part of the calculation.
The treatment of SaaS renewals, on-premise updates, maintenance, bundles of software and services, existing customers, territories and leads is governed by the partner agreement.
The public list you start from to build your own price is on Kazam WMS pricing: SaaS from €149/month, on-premise licence from €2,900 one-off, VAT excluded.
Who holds the contract with the end customer
In the resale model the contract with the end customer is yours: you invoice the licence and the services, and you are the commercial counterpart. Sun Tech stays behind, as the software supplier and as second-line support. That is why the royalty is calculated on what you invoice and not on a price list of ours.
What remains to be settled in the agreement are the edge cases, and it is better to fix them before rather than after: a customer who comes to you from us, a customer who was already ours, a project where Sun Tech steps in directly at your request.
Support: who handles first line, and within what times
The split is the usual one for a channel: first line is yours. You configured the warehouse, you know its rules, and you answer the customer's phone. What escalates to Sun Tech is second line: product defects, behaviour the configuration cannot explain, change requests.
What differs from a traditional channel is who you find when you escalate: the person who wrote that part of the product, not a switchboard that forwards the ticket. Partners also receive new versions and fixes in advance, so you can check them before they reach your customers.
A typical rollout: duration and person-days on the partner
The phases are always the same, and in this order: analysis of the flows, definition of areas and goods attributes, configuration, integration with the customer's business system, trial on real data across a portion of the warehouse, assisted go-live, extension to the rest. The initial configuration is the phase the assistant shortens most, because it interviews the people who know the warehouse and prepares a plan instead of requiring a series of translation meetings.
How much each phase weighs depends on two variables, and neither of them is the software: how tidy the customer's data is and how much automation there is to connect.
What you can change in the code, and within what limits
The sources are available to partners under a confidentiality agreement: you read them, compile them, customise and extend them to your customers' specifications. That is what lets you answer «yes, it can be done» in front of an out-of-standard request.
Three limits apply all the same, and it is worth knowing them before signing. The first is redistribution: the licence is not open source in the OSI sense and resale goes through this agreement, not through the code itself — what source-available means, and does not mean, is set out on the source-available model of Kazam WMS. The second is the licences of the commercial components: Kazam uses Syncfusion and DevExpress components, and whoever compiles in house buys them. The third is maintainability: a change made outside the intended extension points has to be carried over by hand at every update, and becomes a recurring cost of yours.
Skills required in house
The profile depends on how far you want to go. To resell and roll out you need warehouse analysis, configuration and integration with your customers' business systems, plus the ability to follow a go-live on site. To customise the code you need a team working with the Kazam stack: .NET, the web application, the mobile application and SQL Server. For projects with automation you also need the industrial skills: PLC, OPC-UA, Modbus, FINS and VDA 5050 for AGVs and AMRs.
How you become a partner, step by step
Write to us
Fill in the form below or write to partnership@kazam.it with a short introduction to the company, the sectors you cover and the kind of collaboration you have in mind. We answer within one business day.
Application review
We look at technical skills, projects delivered and overlaps with active partners. It is also when we show you the product on your typical scenario, not on a generic demo.
Signature and onboarding
A collaboration agreement with the terms of use of the sources, confidentiality, royalty and support levels. Signature is followed by access to the repository and the documentation.
Kick-off
Training sessions on architecture, modules, configuration and integration, tailored to the people who will follow them. From there on you stay in direct contact with the people who develop the product.
Apply as a partner
Tell us who you are and what projects you deliver. An engineer reads it, not a salesperson, and the answer comes within one business day.
Application received
An engineer will reply within one business day. If in the meantime you want to see the product, access to Kazam Web arrives in sixty seconds from request access.
Kazam WMS · warehouse platform