The whole trade, without buying a module
The full physical cycle — receive, put away, pick, pack, ship, transfer, count — is on from day one, and so is everything that actually makes it work. Pick waves, min/max replenishment, splitting cartons into single pieces, carrier records, labels, layered valuation, lots and serials, alerts: they come together because together is how they work — picking with waves, shipping with carriers, receiving with valuation. Italian compliance comes with them, for an even stronger reason: being compliant is part of the product, in every configuration.
- Pick waves, zone picking, guided packing and multi-parcel shipping
- Min/max replenishment, with the jobs generated on its own
- Cartons and display units broken into singles, with the lot and the cost following them
- Carrier records, barcode labels, delivery notes numbered without gaps
- Lots, expiry dates, FEFO picking and serials: traceability from receipt to delivery, included
- VAT registers, valued statutory inventory and invoice issuing, always on
- RECEIVINGAgainst an order or blind, with inbound quality controlalways
- WAVES AND PICKINGWaves by route, zone picking, replenishment, guided packingalways
- SHIPPINGMulti-parcel, carriers, labels, delivery notes numbered without gapsalways
- LOTS AND SERIALSTraceability from receipt to delivery, expiry dates, FEFO pickingcompliance
- REGISTERS AND INVOICEVAT registers, valued statutory inventory, invoice issuingcompliance
All of it on from day one, in every configuration: the first three because they are the trade itself, the last two because being compliant is part of the product.
Modules say what, limits say how much
The same software serves the small operator with one warehouse and the logistics provider working for ten clients: what tells them apart is which modules are on, plus five numbers on the customer row. Modules answer “what can it do”; limits answer “how much of it do you do”. A limit left empty means unlimited, not zero — and lowering one below what you are already using is refused, with a list of what exceeds it: a ceiling cannot retroactively make illegal what you already have.
- Everybody gets the same features: what changes is how much of them you use, not which ones you have
- WarehousesThe depots, stores or physical sites you actually runraised the day you open another one
- UsersThe people who work inside the productactive ones count, not the ones never deleted
- Monthly ordersThe volume that goes through the warehousemeasured on real data, not guessed
- ConnectorsThe channels you link: the online store, a second store, an upstream systemone per channel
- OwnersThe clients served in the same warehouseonly if you hold goods on behalf of others
A limit can also be absent: where no ceiling is needed, none is set.
Switching a module on is one row, not a project
Every module’s tables exist in your schema from the day it is provisioned, including the ones that are off. Switching on is not a data migration: it is a row in the control plane, and the module starts answering. Propagation takes seconds and does not depend on the token in your pocket, so nobody has to sign in again and a revocation does not wait for anything to expire. The reverse holds too: a module that is off means its screens are not there, not that the rest stops working. The server always decides — the front end hides buttons, and hiding a button is not protecting it.
- No data migration to switch on: the tables are already there
- Propagation is a matter of seconds, not of the next sign-in
- Module off means the rest still works, by design rather than by luck
- Switching off does not delete: the data stays, and switching back on shows it again
- The back end checks the entitlement on every call, not the browser
- Changing your configuration needs no downtime and no night window
- The row goes onIn the control plane, on your tenant. The module’s tables were already in your schema from the day it was provisioned: there is no data migration to run.
- It answers within secondsPropagation does not depend on the token in your pocket: nobody signs in again, and in the same way a revocation waits for nothing to expire.
- The screens appearWith the same items, stock and locations as before, because nothing moved. Switch it off and those screens stop answering while the data stays.
Where you start, and what you add later
The four modules are not four steps up a ladder: they are four different trades, and each goes on when that trade walks into the building. Three of them sit on top of the warehouse and add screens — selling, keeping the books, looking at the numbers. Third-party logistics does not: it is the only genuinely orthogonal one, because it does not add a trade, it changes a dimension of the data model. From that moment every stock line also says whose goods these are.
- In any order, at any time: no combination is compulsory
| Module | What it adds | What stays as it was |
|---|---|---|
| Warehouse alone | Receive, pick, ship, trace lots and issue the delivery note | Already a complete configuration: the whole trade is there |
| Sales | The order is born here: price list, customer, line-level tax, payments, online store | The warehouse stays the only authority on stock |
| Accounting | Double entry, suppliers and purchasing: the entry comes from the document | VAT registers and invoicing were already there: compliance, not a module |
| Analytics | Analysis and dashboards on a star schema that reconciles itself | The figures stay the ones your system produces, not a second program’s |
| Third-party logistics | The owner on every line, segregated stock and service invoicing | The column was already in the data model: no migration, no downtime |
Frequently asked questions
Can I buy the warehouse on its own?
Yes, and it is a complete configuration: the warehouse is the product. Full physical cycle, waves, replenishment, carton splitting, carriers, labels, valuation, lots and serials. Italian compliance comes with it and stays active in every configuration: delivery notes, VAT registers, valued statutory inventory, lot traceability and invoice issuing.
If I switch a module off later, do I lose what I put into it?
No. The tables live in your schema and stay there: switching off means that module’s screens and calls stop answering, not that the data is deleted. Switch it back on and you find what was there. It is the same property that makes switching one on painless: nothing moves, in either direction.
Is there a basic edition and an advanced one?
There is a single plan, and everybody runs the exact same software: what changes is which modules are on plus the five numbers on your row. The practical benefit is that if something exists, it exists for everybody — no feature unlocks by moving up a step — and if you need a module you switch it on without reopening the rest.
How much does a module cost?
The figure comes out of your own numbers — how many warehouses, how many people, how many orders a month, how many channels, how many owners — and out of which modules you actually need. Tell us how you work and we will do the arithmetic on your case: half an hour is usually enough, and what comes out fits you rather than an average customer who does not exist.
Do I have to decide now which modules I will need?
No, and it is better not to. Adding a module later costs the same as adding it now, because there is no data migration behind it: the tables already exist in your schema. The only decision to make today is the one you are working on today; the rest goes on the day that trade genuinely arrives.
Who checks that I really have a module?
The back end does, on every call, at the entry point of every function that belongs to a module. The front end hides the menu entries that do not concern you — a courtesy to the people working, not a defence — but a client that called a switched-off function anyway would be refused. Compliance functions are explicitly exempt from that check and stay reachable at all times.