Honest scope (per Doc 01 §9)
Odexy Inventory is beta. We ship the schema + the core primitives — items, warehouses, stock counts, basic movement — and we're growing the surface as design partners need it. If you're shopping for a full WMS today, this isn't it yet. If you're shopping for an integrated inventory that lives next to your CRM, Sales, and Accounting, this is the right starting point.
What ships today
- Items — SKU, name, unit, default cost, supplier link.
- Warehouses — multi-location, address typed.
- Stock count — per-warehouse per-item current quantity.
- Movement — receive / ship / transfer / adjust with reason codes.
- Audit log — every movement recorded with actor + reason.
How it integrates
- Sales — invoice line items can decrement stock on shipment.
- Accounting — cost-of-goods journal entry posted on shipment.
- Forms — supplier-side receiving forms posted via signed public tokens.
How the AI helps (today)
- "Show me items at or below reorder threshold across all warehouses."
- "Draft a transfer from warehouse A to warehouse B for the items running low."
What's queued, not shipped
Per Doc 01 §9, we don't claim what we haven't built:
- Lot / batch tracking
- Serial number tracking
- Multi-tier BOM
- Demand forecasting
- 3PL / shipping carrier integrations
- Cycle counting workflows
These land as design partners pull them in. Roadmap published in the changelog.
Odexy Inventory vs. the category
The category leaders (NetSuite, Cin7, Fishbowl) are full-feature WMS products costing per-seat + per-warehouse. Odexy Inventory's pitch is different: come in for the schema integration with CRM / Sales / Accounting; mature into a full WMS as we grow.
Design-partner take
> "We didn't need a real WMS — we needed our inventory to be in the same place as our invoicing. Odexy was the right fit for that, and we know what's coming next." — Design partner, 6-person e-commerce