Refund policy

It is a working ERP that runs a European towel manufacturing plant today. The public demo is the same build, loaded with four months of documents — sales orders, production, quality, payroll, vouchers — so you are judging the real thing, not a slide deck.

Yes. The engine underneath — documents, stock ledger, double-entry accounting, approvals, roles, reporting — is industry agnostic. We reshape the modules, forms, documents and reports around your process. Tell us how you work and we will show you the shape it would take.

Any language you need, including right-to-left scripts. The interface is fully translatable and we deliver the language files with your deployment. Documents and reports can print in a different language from the interface if your buyers need that.

No. Most plants start with stores, purchase and sales, then bring production, quality and payroll in once the floor is comfortable. Approvals are switched on module by module when you are ready.

Implementation is staged by department. The first department typically goes live in four to six weeks, with the rest following every two to three weeks. The timeline depends on how quickly you can provide masters and opening balances, and how much time your team can devote to training.

We build integrations for e-invoicing portals on request, provided the portal offers a REST API or file-based submission. You will need to give us the API credentials, a test environment, and a sample invoice payload. The integration is quoted separately and built after the core ERP is live.