The CRM that runs the whole business.
Pipeline and deals, stock across warehouses, customer and supplier ledgers, the people doing the selling, and the reports the office files. One record, one state, and everyone who touches it sees the same one.
Not a sales tool bolted onto an ERP
Most businesses end up running a CRM for the pipeline, a spreadsheet for stock and an accountant's package for the ledger, then spend the month reconciling the three. zedy is the one place all of it already agrees.
- Modules in one tree
- 24Modules in one tree
- Enforced JS budget
- 135 KBEnforced JS budget
- Minimum tap target
- 48 pxMinimum tap target
- Interface tests
- 361Interface tests
- Orders with real states: dispatch, deliver, hold, reject
- Stock across every warehouse, with alert levels
- Customer and supplier ledgers, true in sequence
- Cash book, bank book, general ledger and cash flow
- Field teams with route plans and GPS attendance
- Twenty-odd printable reports, laid out for A4
What zedy covers
Twenty-four modules in one navigation tree. These are the six that most businesses move onto first.
capabilities
Sales and orders
An order pipeline with states that mean something — confirm, dispatch, deliver, hold, reject — plus an approval queue and a dispatch queue. Orders carry an ordered and a pending quantity, so a short delivery is visible rather than quietly billed.
Stock and warehouses
What came in against a supplier's invoice, what went out, what is on the shelf now and what has fallen under its own alert level — across every location, with a separate raw-material store alongside it.
Customers and suppliers
A running balance that is true in sequence, receipts and payments filed against the voucher that moved them, and balances never clamped, so an overdraft stays visible instead of reading as zero.
Accounts and transactions
Cash book, bank book, general ledger, cash flow, cash movement summary, income and expenditure, yearly report and opening balances, over bank, cash and employee transaction registers.
The people selling
A national-to-territory hierarchy with team tree, monthly targets, weekly route plans, a visited report and GPS-stamped attendance with location history — so field performance is a record, not a phone call.
Roles and access
A permission matrix per role and territory, enforced by the API rather than by the menu. Hiding a row is explicitly not what protects it.
Twenty-four modules, one navigation tree.
Not twenty-four products stitched together. One record that every module reads from and writes to, so a dispatch moves the stock and the ledger without anyone re-keying it.
Sell
06- Sale
- Order
- Customer
- Supplier
- Return
- Secondary sales
Stock
05- Product
- Warehouse
- Purchase
- Packaging
- Raw material
Money
06- Accounts
- Transaction
- Bank management
- Expense
- Loan management
- Investor management
People
04- Sales force
- HRM
- Payroll
- Role & permission
Run it
05- Report
- Shops
- Distributor assignment
- Asset management
- Settings
Reports the office can actually file
A report that only exists as a screen is useless to a business that still files on paper. Every zedy report is laid out as a document — letterhead, the period covered, totals at the foot — and prints correctly the first time.
Laid out for A4
Landscape where a sheet is too wide, with repeating headers across page breaks.
Mono-printer safe
Figures stated in words as well as colour, so a black-and-white printer loses nothing.
Tenant letterhead
Your own name and logo on every sheet, pulled from workspace branding.
Export as well as print
Every report also exports, so the same numbers reach a spreadsheet without re-keying.
Built for the slowest connection you have
The people entering most of the data are on a mid-range Android phone on a patchy connection, standing in a shop. Almost every design decision in zedy follows from that, and the constraints are enforced by the build rather than remembered.
A budget the build enforces
135 KB of JavaScript, checked on every build. Exceed it and the build fails.
Nothing typed is lost
Fields keep their values until a submit has actually succeeded, and a dropped connection says so instead of spinning.
Readable where it is used
A 48px minimum tap target, every contrast pairing measured, and no photographs or icon fonts to download.
Installable
Adds to the home screen and opens like an app, with no store and no update to chase.
A back office for running it as a service
zedy ships with the vendor panel as well as the product, so an operator can run many businesses on one deployment without a database console.
Workspaces on their own slug
Create a tenant, upload its logo, and sign-in and letterheads are white-labelled from that moment.
Plans that ration real things
Seventeen entitlements — users, warehouses, products, invoices per month, storage and feature flags.
Lifecycle, not deletion
Archive and restore tenants and users, with nothing destroyed on the way.
A full audit log
Operator actions recorded and reviewable, alongside demo requests and password resets.
How it goes live.
Your workspace
A tenant on its own address, with your name, your logo and your currency, invoice format and voucher prefix.
Your opening position
Products, warehouses, customers, suppliers and opening balances loaded, so the ledger starts true rather than from zero.
Your people
Roles and territories defined, users created against them, and the field hierarchy built out to territory level.
Then it just runs
Orders move through their states, stock and ledgers follow automatically, and the month-end reports are already written.
Who runs on zedy.
Distributors
Primary and secondary sales in one view, distributor inventory and statements, and a field force whose day is a record rather than a report.
Manufacturers
Raw material in, finished goods out, packaging tracked as its own stock, and a purchase-to-invoice chain that reconciles itself.
Retail and wholesale chains
Stock across every outlet, credit customers with a visible balance, and collection assigned to the person who is actually going.
Field-sales organisations
Route plans, targets, visited reports and GPS attendance, so territory performance is measurable without anyone filling in a form twice.
See it on
your own numbers.
Send a month of real orders, stock movements and ledger entries. We will load them into a workspace and show you the reports your office would have filed.
Got questions? We’ve got answers.
Does it work on a slow connection?
That is the design constraint, not an afterthought. Pages are server-rendered under a 135 KB JavaScript budget the build enforces, there are no photographs or icon fonts to download, and nothing is disabled for being offline — a dropped connection says the network is gone and keeps everything you typed.
Can it replace our accounting package?
For most distribution and retail businesses, yes. zedy carries cash book, bank book, general ledger, cash flow, cash movement summary, income and expenditure, yearly reports and opening balances, over bank, cash and employee transaction registers, with asset, loan and investor registers on the same ledger machinery.
How does it handle money the way we read it?
Amounts are grouped in lakh and crore rather than thousands, rendered in words on vouchers, and the currency list, voucher prefix and invoice format are all configurable per workspace.
Can we restrict what a territory manager sees?
Yes, and the restriction is real. Permissions are defined per role and per territory and enforced by the API, not by hiding menu entries — hiding a row is explicitly not what protects it.
Can we run it for multiple companies?
Yes. The platform panel creates each business as its own tenant on its own address, with its own logo on sign-in and letterheads, one of four plans rationing seventeen entitlements, archive and restore rather than deletion, and a full operator audit log.