About us
Who is behind CargoNode
CargoNode is an IVEmind product: a cooperative based in Bolzano, Italy, building management software for the Italian market. The code is ours from the first line and whoever answers when you write is the person who writes it; the multi-customer foundations underneath CargoNode are the same ones holding up rivedi.ai and hermesflows, in production before CargoNode existed.
IVEmind is a cooperative based in Bolzano, northern Italy. We develop management software, we do not resell it.
The multi-customer core underneath CargoNode is already in production underneath three other IVEmind products — rivedi.ai and hermesflows among them: keeping data apart, creating an environment, upgrading the database are ground already covered.
Delivery notes, VAT registers, statutory inventory and e-invoicing are written into the product, not bolted onto software born elsewhere.
Cloud infrastructure in the European Frankfurt region, with a separate database schema for every customer.
A warehouse management system is software you marry: you walk into it every morning for years, and replacing it costs more than choosing it. So before looking at features it is worth knowing who builds it, what it is built on and where the data ends up. This page answers those three questions, and answers each of them with something we can show you.
A cooperative that writes management software
IVEmind builds management software for retail and healthcare, and it is a cooperative: the legal form is not decoration, it is how the people who work on the product answer for it. Other products came before CargoNode on the same platform — rivedi.ai for optical practices and stores, hermesflows for email marketing — and each came out of the same method: look at how that trade actually works, and build on that instead of bending a generic system into shape.
- Built in-house: the code is ours, not a third-party platform resold
- Based in Bolzano; the product and the support are in Italian
- Sister products already in production: rivedi.ai for optics, hermesflows for email marketing
- Whoever answers your email knows the code you are talking about
- rivedi.aiOptical practices and storesin the house
- hermesflowsEmail marketingin the house
- CargoNodeThe warehouse, and the system growing around itthe one you are looking at
Underneath, the same multi-customer core: one database schema per customer, environment creation, upgrades, the record of who did what. Above it, different trades, built one at a time.
The fourth product on the same foundations, the first about the warehouse
The parts that make multi-customer software risky — keeping one customer’s data apart from another’s, creating a new environment, applying database upgrades, keeping a record of who did what — were not rewritten for CargoNode: they are the same shared core that carries the other IVEmind products, already used and already tested in the field. What is new, and written from scratch for this trade, is the warehouse itself: the movement ledger, reservations, shortest-shelf-life-first allocation, the task engine behind the handheld, the activity metering behind third-party billing.
- Multi-customer by construction: each customer has their own database schema, not a column telling them apart
- Shared foundations, already proven on other products in the house
- The warehouse domain is new: ledger, reservations, tasks, handheld, activity metering
- Warehouse and owner are columns of the data model from day one, even for those who only have one
| The part | Where it comes from | Already in use |
|---|---|---|
| Keeping one customer’s data apart from another’s | shared core | yes |
| Creating a new environment for a customer | shared core | yes |
| Applying database upgrades | shared core | yes |
| Keeping the record of who did what | shared core | yes |
| The movement ledger and stock | written for the warehouse | no |
| Reservations and shortest-shelf-life-first allocation | written for the warehouse | no |
| The task engine behind the handheld | written for the warehouse | no |
| Activity metering for third-party billing | written for the warehouse | no |
The hard decisions are written down, and can be read back
The choices that cannot be changed later — a movement ledger that is never edited, the isolation of one customer’s data from another’s, the fact that stock is a consequence and not a field — are recorded decisions, with the date and the reason they were taken. That is not internal bureaucracy: it is what stops somebody, three years from now, from “fixing” a stock figure with a direct edit because that day it was quicker. The things that keep a warehouse honest only hold if they are written down and defended.
- The movement ledger is never edited and never deleted: you correct it by adding
- An adjustment goes through a proposal and an approval, with who and when
- Each customer’s data sits in a schema of its own: no query can see two of them
- Every handheld operation carries its own identifier: a resend doubles nothing
- DECISIONThe movement ledger is never edited and never deletedwith the date it was taken
- WHYA stock figure corrected by hand leaves behind neither who nor whenand that is where a warehouse stops being honest
- SOYou correct it by adding: an adjustment proposed, and approved by somebody elseproposing and approving are two different permissions
Every choice that cannot be changed later is written down like this. It is not internal bureaucracy: it is what will stop somebody, three years from now, from “fixing” a stock figure because that day it was quicker.
Compliance is never sold separately
It is a rule we set ourselves and it holds in every configuration: delivery notes, VAT registers, valued statutory inventory, lot traceability and invoice issuing are always active, even in the smallest setup, and cannot be lost by switching a module off. On sending invoices to the Italian tax authority the division of labour is stated: CargoNode produces the XML and runs the official checks on it before it goes anywhere, then you pick the route — a connected provider, which files the invoice on its own and brings ten-year archiving with it, or the checked XML to send through the route you use today.
- Italian statutory obligations are not a module and not an extra
- Lot traceability is compliance, so it never switches off
- You choose how to transmit: a connected provider, or the checked XML sent your own way
- With a provider connected you get ten-year legal archiving: the provider brings it
- CargoNode produces the XMLThe invoice comes out in the format the tax authority accepts.
- And checks it firstThe official checks are applied before the document leaves, not after it is rejected.
- Then you chooseConnect a provider and the invoice leaves on its own, or download it and send it through the route you already have.
- The provider brings the archivingTen-year legal archiving comes with the provider you connect, for the documents that go through it.
Where your data lives, and whose it is
The infrastructure is cloud, in the European Frankfurt region, and every customer has their own database schema, separate from the others: it is not a filter applied by the queries, it is a separation that sits underneath them. The data stays yours. Lists, registers and movements can be downloaded as CSV or Excel whenever your accountant, an audit or simply you need them, and backups are ours to run, not something you have to remember.
- Cloud infrastructure in the European Union, Frankfurt region
- One database schema per customer: isolation is structural, not a condition in a query
- Backup and restore are part of the service, not your chore
- CSV and Excel export of lists, registers and movements
- REGIONEuropean Union, Frankfurt regioncloud infrastructure
- ISOLATIONOne database schema per customerit sits under the queries, not inside them
- BACKUPBackup and restore are part of the servicenot your chore
- EXPORTLists, registers and movements as CSV or Excelwhenever your accountant, an audit or you need them
The data stays yours, and the door to take it out is open from day one: it is a condition for trusting somebody, not a feature to ask for.
Every sentence on this site can be shown running
What these pages carry is what the software does, and every claim matches something that is built: the movement ledger that is never rewritten, the invoice checked before it leaves, the handheld that keeps working when coverage disappears at the end of the aisle. That is a choice of method, because a sentence that cannot be shown is of no use to somebody who has to decide, and it is also why the demo runs on your own cases rather than on made-up data: what you see in half an hour is the real product. A customer’s name goes on this site only with that customer’s permission: instead of logos, what you get here is the software running on your own figures — which is the thing you actually have to decide on.
- Every claim matches a built feature, and can be watched running
- The demo runs on your own cases: an order of yours, a receipt of yours, your stocktake
- Customers are named only with their permission: references are asked for, not written by us
- The quote is made on your configuration: the modules switched on and the five numbers
- EVERY CLAIMMatches something that is builtshown to you against your own cases
- THE DEMORuns on the real software, with your numbersan order of yours, a receipt of yours, your stocktake
- THE QUOTEIs made on your configurationmodules switched on and five numbers, in writing
Half an hour is what it takes to check for yourself, line by line, what you have read here: it is how we prefer to show the product.
Frequently asked questions
Are you a software company or a reseller?
We develop. CargoNode is written by us, from the movement ledger to the handheld app, and it sits on a platform core that is also ours and that carries the other IVEmind products. When you report a problem there is no supplier in the middle to forward the request to.
Where is the data hosted?
On cloud infrastructure in the European Frankfurt region. Every customer has a separate database schema: the isolation is in the structure, not in a filter somebody could forget. Backups are part of the service.
Who answers when I write from the site?
The people who build CargoNode. There is no switchboard, no newsletter, and the message does not go to a reseller network: it reaches somebody who can answer on the substance, usually within one working day.
Do you build other software?
Yes. rivedi.ai is the management system for optical practices and stores, hermesflows does email marketing. Underneath sits the same multi-customer platform; above it they are different trades, built one at a time. CargoNode is the fourth product on those foundations.
Can I talk to the people who build it, not only to a salesperson?
Yes, and it is how we prefer to work. The questions that matter — what the system does when two orders compete for the last unit, what happens if the handheld loses the network halfway through a pick — have technical answers, and technical answers come from whoever wrote that part.
Keep reading
Tell us how you work
The quickest way to see whether CargoNode fits is to look at it against your warehouse: how you receive, where you pick, what wastes your time today. Half an hour of that shows more than any deck.
Talk to us