Inventory Management Software Warehouse

The distinction between inventory management and warehouse management is the most useful thing to get straight before buying anything. Inventory management answers what you own. A warehouse management system answers where it is and how work moves through the building. Small operations need the first. Once picking labour becomes a real cost, the second is what actually changes the numbers.

We sell source code you clone and run yourself, so there is nothing hosted here. This page is about which of the two you are shopping for.

Inventory management or warehouse management

Buying a WMS for a stockroom with two hundred SKUs is a common and expensive mistake, because the implementation cost is mostly in defining locations and processes rather than in the licence. Buying inventory software for an operation picking a thousand orders a day is the opposite mistake and shows up as overtime.

What a WMS actually does for the labour cost

Three mechanisms, and they are worth knowing by name because they are what you are paying for.

Bin locations are the prerequisite for all of it

Everything above depends on knowing where things are at a granularity finer than the building. That means naming every location, labelling it, and maintaining the discipline that stock does not move without a scan.

This is the part that fails. The software is not the hard bit; the hard bit is that a warehouse where people put things down in convenient places will defeat any system within a month. Before committing to a WMS, it is worth being honest about whether the operation is ready to enforce scanning, because a partially scanned warehouse produces data that is worse than no data.

Free and low-cost options

For inventory management, the free tiers are genuinely capable and cover a stockroom comfortably. For warehouse management, free options are thinner, and the open source end usually means Odoo, whose warehouse module handles bins and picking within a larger platform.

The costs that surprise people are hardware and labelling rather than software: rugged scanners, label printers, and the initial exercise of labelling every location.

When people build

Not a WMS. What gets built around one is common: a portal for customers of a third-party logistics business, where each client sees their own stock, orders, and dispatch status without seeing anyone else's.

That is a multi-tenant application on top of whatever runs the warehouse, and it is a reasonable build because the WMS products serve the operator rather than the operator's customers.

What you would start from here

There is no inventory or warehouse capability in this stack. No products, no stock, no locations, no bins, no picking, no scanning, and no cycle counts.

What the Vault template provides for the client portal case is the tenancy: organizations so each client of the logistics operation is isolated, roles and invitations, a Hono backend with Prisma and Kysely on Postgres, an admin app, and Stripe billing for charging clients.

You would write the read models that expose stock and order status per client, and the integration with the system that actually runs the floor. Keep the portal read-mostly if you can; letting customers write directly into warehouse operations is where these projects get complicated.

For the warehouse itself, buy. The packs below are the customer-facing layer around it.