Load the catalog
Products, units, minimums and the warehouses and locations you actually have.

When stock lives in spreadsheets, every physical count is an argument. This module makes the system the single source of truth for what you have and where.

With one warehouse, inventory is a list. With several, it is a coordination problem: transfers, availability, and the question of which site should serve which order. The module answers that from data instead of a phone call.
Companies with more than one storage point, or one warehouse that keeps disagreeing with the system. If a physical count takes a full day and still leaves doubts, the module pays for itself in the first cycle.
You stop keeping a parallel spreadsheet, stop calling the warehouse to confirm availability, and stop discovering shrinkage only at the annual count. The system records who moved what, when and why.
The module is not an island. Movements feed purchasing and suppliers, consumption feeds per-order costing, and stock levels feed invoicing and accounts. That is the difference between an inventory list and an ERP: the same movement is counted once and read everywhere it matters.
If you already run accounting or an e-commerce platform, we integrate them so stock does not have to be reconciled by hand every month.
The inventory module is +$700 USD on top of any NEOS tier, which start at $7,500 USD. One-time payment; the annual fee from year two covers server, backups, support and maintenance.
Your current catalog, the list of warehouses and locations, opening stock, and the rules you already follow for transfers and adjustments. If that exists in spreadsheets, we migrate it; if it exists only in experience, we write it down with you during the diagnostic.
Three repeat constantly when inventory lives in spreadsheets: a transfer recorded in one file but not the other, a sale that shipped from a site the system still shows as full, and a minimum nobody looked at until the product ran out. All three are structural, not personal, and all three disappear when a single movement is recorded once.
Stock accuracy against a physical count, the time needed to answer availability, and the number of manual adjustments per month. Those three numbers usually improve within the first closed cycle.
Products, units, minimums and the warehouses and locations you actually have.
We migrate the opening inventory and reconcile it against a physical count.
Transfers, adjustments, approvals and who may move what.
Availability by site, valuation and alerts, without a phone call to the warehouse.
| Design X AI (custom) | Per-user SaaS | |
|---|---|---|
| Availability | Answered in seconds, by location | A call to whoever has the file |
| Transfers | Recorded with responsible user | A note, a message, a guess |
| Traceability | By lot or serial when quoted separately | Reconstructed from memory |
| Valuation | Calculated from movements | Retyped at month end |
| Errors | Caught when they happen | Found at the annual count |
| Reconciliation | Automatic with purchasing and invoicing | Manual, by hand, every period |
+$700 USD on top of the NEOS tier, which starts at $7,500 USD. One-time payment.
Yes. Stock, transfers and availability are managed per warehouse and per location.
No. Traceability by lot or serial number is not part of the standard inventory module; it is quoted separately according to scope.
Yes. We import the initial inventory from your spreadsheets or current system and reconcile it against a count.
The system is designed around your process; if your sites have connectivity limits, we discuss the operating procedure during the diagnostic.
Role-based access defines who may record entries, exits, transfers and adjustments, and every movement keeps the responsible user.
Tell us how prospects currently arrive and where they get lost. We return a fixed-scope proposal with no commitment.