How the platform actually works
One connected system, not twelve separate applications with a shared login screen.
This page explains the architecture underneath the 12 modules — how they share data, how workflows move across module boundaries, and how access, reporting, and multi-company operation are governed centrally.
- Accounting
- Procurement
- Sales
- CRM
- Stock
- Manufacturing
What it is
Vercentlabs ERP is a multi-tenant, multi-company operational ERP: 12 connected modules — covering revenue, operations, finance, people and service, and delivery — sharing one data model, one role and permission system, one governed approval engine, and one immutable audit trail, instead of five separate tools that happen to export to the same spreadsheet.
Who it's for
Built for businesses that outgrew a single-purpose tool.
Growing manufacturers coordinating production and inventory, distributors and multi-location retailers keeping stock and point-of-sale in sync, and project-based service businesses that need to know project profitability before the invoice goes out — not after.
What makes it a connected ERP
A record moves through the business without being re-typed.
A CRM opportunity becomes a Sales quotation by reference, not by copy. A confirmed order generates an Accounting invoice request through an idempotent, auditable handoff. A Manufacturing work order posts real, FK-linked movements into the same Stock ledger Point of Sale checkout deducts from live. These are confirmed, wired connections in the codebase, not a marketing diagram of how ERPs are supposed to work.
Five operational domains
Twelve modules, grouped the way your teams actually think about the business.
Revenue
CRM, Sales, and Point of Sale — from first contact to the till.
Operations
Procurement, Stock, Manufacturing, and Quality — what you build, buy, and ship.
Finance
Accounting and Assets — the books and the assets that back them.
People & Service
HR & Payroll and Support — the people running the business and the customers they serve.
Delivery
Projects — billable work tracked against budget and margin while it's still in progress.
Shared data, not synced data
Modules read and write the same tables — there's no sync job that can fail.
When Manufacturing posts a finished-goods receipt, it's the same Stock ledger row Point of Sale checks before a sale. There's no overnight batch process reconciling two separate inventory systems, because there's only one.
How workflows are automated
A governed command registry, not a maze of if-statements per module.
Approval routing, separation-of-duties enforcement, and status-transition guards are built on reusable primitives shared across Accounting, Sales, CRM, HR, Assets, Projects, POS, and Support — not reinvented per module. See the automation page for the full picture.
Access and governance
Role-based, time-bound, and scoped — not all-or-nothing.
Twelve seeded system roles carry framework-neutral permission-key packages per module. Role assignments can expire automatically and be scoped to a specific company, branch, or department. See the security page for the full architecture.
How reporting works
Reports read from the same live data every module writes to.
Module dashboards and cross-module reports aren't a separate warehouse that's a day behind — they query the same operational data in real time. See the analytics page for the reporting framework.
Multi-company and localisation
Structural isolation between companies and branches, with India-default localisation.
Company and branch scoping is enforced at the data layer, not filtered in the application. Localisation defaults to en-IN, Asia/Kolkata, INR, and an April-start fiscal year — matching Indian GST and statutory compliance needs out of the box.
Mobile and integrations
Native mobile where it matters most, and a real API surface for the rest.
CRM leads, opportunities, activities, and pipeline are native and offline-capable on mobile. Selected Procurement and platform workspaces use a secure-browser handoff. See the mobile and integrations pages for the honest current scope.
Getting live
A configurable platform still needs a structured rollout.
Organisation bootstrap seeds 12 roles and around 29 numbering series in one transaction, but a real go-live still means discovery, configuration, data migration, and phased rollout — see the module pages for what each one specifically needs.
Buyer questions
Questions about the system, answered without theatre.
Platform scope, architecture and deployment questions sit here so buyers can inspect the system before a demo.
Is Vercentlabs one application or twelve separate products bundled together?
One application — 12 modules run on one shared platform and data model. Module access is entitlement-gated per organisation, so you can enable what you need now and add more later without switching systems.
How does Vercentlabs handle multiple companies or branches?
Multi-company and branch-level data isolation is structural, enforced at the database layer — not an application-layer filter that could be bypassed by a bug.
Can we adopt modules gradually instead of all at once?
Yes — module access is entitlement-gated per organisation, so you can start with the modules you need and add more as you grow, on the same underlying platform and data model.