Samavāya
समवायEnterprise resource planning · a P9e Microsystems product
Most ERP failures are not crashes. They are half-completed transactions: stock reserved against an order that was never confirmed, a journal entry with no matching receipt, a payment made against a cancelled purchase. Samavāya is built so that a distributed business transaction which fails halfway unwinds itself deterministically, in reverse, with an audit trail of what it undid and why.
- Sagas
- 99, all compensated
- Platform
- Kosha
- Consistency
- Eventual, by design
In a distributed system there is no single transaction to roll back. Either every step has a defined compensation, or your data eventually stops being true.
How it fits together
How we structure a line-of-business platform
Clients talk to one authenticated API surface; domain services own their data and publish events, so integrating an ERP or MES never means reaching into another service's database.
What Samavāya does
99 sagas, with compensation for every step
Order cancellation releases the stock and reverses the receivable and the journal entry. Goods return reverses the payable and the payment. Roughly 900 step compensations, each specified rather than improvised.
Crash recovery, not crash loss
Saga state is persisted as it advances, so a service that dies mid-transaction resumes where it was rather than leaving a half-finished business process behind.
Circuit breakers and bounded retry
Exponential backoff prevents a thundering herd; circuit breakers stop a failing downstream service from cascading through the whole system.
Honest about what cannot be undone
Some things genuinely cannot be compensated — a filed statutory return, a completed bank transfer, stock already in transit. Those are documented as uncompensatable, escalated to a human, and never quietly retried.
Indian statutory and sector modules
GST and banking handled as first-class concerns rather than localisation patches, with sector packs for construction and agriculture.
Who Samavāya is built for
Not a list of industry names — what the product actually does differently in each.
Discrete & process manufacturing
Multi-level BOMs, work orders and routing, production costing against actuals, batch and serial traceability, and quality gates that stop material rather than merely recording that it failed.
Construction & infrastructure
Project accounting to the cost code, subcontractor billing, running-account bills with retention and recovery, work-in-progress against measured quantities, and plant and machinery deployed per site.
Agriculture & agri-business
Procurement from growers with grading and moisture-based rate adjustment, seasonal stock and commodity valuation, mandi and warehouse movement, and settlement against advances.
Trading & distribution
Multi-location stock with transfer control, price lists and scheme handling, credit limits enforced at order entry, and returns that reverse the receivable and the stock together.
Projects & professional services
Timesheets against billable milestones, revenue recognition on percentage completion, and expenses that reach the invoice rather than a spreadsheet.
Every one of them — the statutory layer
GST with e-invoicing and e-way bills, TDS and TCS, banking integration and reconciliation. Treated as first-class concerns rather than a localisation pack bolted onto a foreign product.
Deployed and embedded
- Enterprise Software division — the flagship product
- P9e's own operations — we are the first customer
- Deployed for customers on the Kosha application platform
Where it actually stands
In production. The saga engine and compensation framework are specified end to end and rolling out module by module.
We state maturity on every product page. A claim we cannot defend costs more than the work it wins.
Talk to us about Samavāya.
Deployment, embedding, evaluation licences — tell us the system it has to live inside.