Overview
In a register-book shop the same order is written three times — once in the order book, once on the invoice, once in the stock register — and they never quite agree. Neev keeps one copy. A customer, a SKU, an order, a payment: each is stored once and every screen reads the same row. Change it in one place and it is changed everywhere. That single shared backbone is what we call the spine.
Where to find it
The spine isn't a screen — it's what every screen runs on. The left sidebar groups the spine into the way a trading day actually flows: Intake (WhatsApp, intake inbox, review), Sell (orders, customers, quotations, standing orders), Fulfill (inventory, shipping, returns, suppliers), Money (invoices, payments, pricing, approvals) and Data (notifications, reports, audit log).
Your Home at /home is the spine at a glance: today's revenue, open orders, receivables, low stock and pending intake all pulled live from the same tables the detail screens use. Everything is on both web and mobile; what shows up in your sidebar depends on your role.
Key concepts
- A tenant is your business — your workspace. It is the row in the
businessestable that every other record hangs off. Your data is yours alone; it is never mixed with another business's. - The spine is the set of shared Core tables — businesses, customers, orders, inventory, invoices and payments — that every module, Pack and report reads from.
- Event-sourced means order, money and stock changes are recorded as an append-only log of what happened, then projected into the live screens. Nothing is silently overwritten, so the audit log and history come for free.
- A module is one part of the system — orders, inventory, invoicing. Modules never reach into each other's data directly; they read through shared queries and write by raising events, which is why the numbers stay consistent.
Common workflows
The point of one spine is that a record you create in one place is already filled in everywhere else. Here is how that plays out.
This is also why new surfaces add depth without a re-setup: future verticals and channels — quick-commerce, D2C storefronts — land on the same orders, inventory and customers tables rather than a separate copy of your business.
Role notes
Everyone works on the same spine, but each role sees and changes a different slice of it. Visibility in the sidebar follows your role, and write access is narrower than view access.
- Owner holds every non-Pack permission across the whole spine and is the only role that can void an invoice, change HSN rates, archive a supplier or toggle a customer blacklist. Pack powers (pharma, dairy, quick-commerce) switch on only when the Owner installs that Pack.
- Manager runs day-to-day operations — orders, returns, intake, customers, inventory, pricing — but cannot void invoices, edit HSN rates, archive suppliers, or touch team, settings or roles.
- Accountant owns the money surface: record payments, generate the invoice PDF, read financial and Tally reports. The Accountant cannot void an invoice, raise (generate) one, or change pricing — and has no access to orders, inventory or returns.
- Sales parses and drafts orders, manages customers and runs quotations end to end, but reads inventory and pricing only and cannot advance an order past draft. Sales has no general invoice access — not even view.
- Operator is the phone-order desk: read across the spine, look up stock and price, key in a draft order. An Operator cannot confirm or dispatch orders, edit the customer master, or touch stock or money.
- Warehouse packs orders and owns stock movement — receive goods, adjustments, batch write-offs, receiving returned goods. Warehouse cannot create, confirm or dispatch orders, edit the product master, or see any invoice or payment.
- Delivery is the most restricted: read-only on exactly two surfaces — orders and invoices — so the rider can see what to deliver and the bill that goes with it. Delivery cannot mark a payment, generate a document, or even dispatch the order.
Seeing a screen does not mean you can act on it. A Delivery rider sees the order but cannot dispatch it; an Operator can key a draft but cannot confirm it; an Accountant sees an invoice but cannot void it. If a button is missing, your role doesn't carry that permission — ask the Owner, don't look for another route.
Tips & time-savers
Because the spine is shared, fix data at the source and it propagates — never patch the same fact on three screens.
Set a customer's credit terms and price list once on the customer record. Every future order for that buyer pulls them in automatically, so the counter operator never has to remember a special rate — it's already on the order.
The sidebar mirrors a real trading day top to bottom — Intake → Sell → Fulfill → Money → Data — so you can walk an order from a WhatsApp message all the way to a collected payment without hunting for the next screen.
Gotchas
The spine keeps one copy of each record, so a downstream document doesn't quietly disagree with the order behind it — but it also means a wrong customer or price keyed at order time flows straight into the invoice and the ledger. Pick the right customer and confirm the price before you advance an order; correcting it after the invoice is raised is a separate, controlled step, not a quiet edit.