Questions we answer every week

Through your account engineer. Configuration changes — fields, approvals, roles, formats, taxes — are usually same-week. Larger module work is scoped and scheduled.

Yes, including the layout your buyers and auditors already accept. Bring a sample of each printed document to the discovery call.

Open every module and every report, filter, drill down and inspect documents. Forms open so you can see the fields, but nothing you type is saved — the data resets so the next visitor sees a clean plant.

No. It runs in the browser, on a laptop or a phone. The demo login is on the login page itself.

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.

A standard manufacturing deployment runs four to eight weeks: masters and opening balances first, then live documents module by module. A customised build depends on scope and is quoted after a discovery call.

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.

Item masters, buyers and suppliers, opening stock and opening balances, plus one person per department who knows the real process. We do the loading and validation.

Yes — role-based sessions for each department, plus a written workflow document and an in-app standard-operating-procedure page your staff can open any time.

Per plant, with a user band included in each plan. You are not penalised for giving a supervisor or a store keeper their own login — which is exactly what makes the data trustworthy.

Yearly billing gives you two months free compared with monthly — the toggle on the pricing table shows the exact figure per plan.

The live demo is open with no form and no time limit. When you are serious, we load a trial environment with your own masters so you can test with your real items and buyers.

Data migration from an old system, on-site training and custom development are quoted separately, because they depend entirely on what you already have. Hosting, backups, SSL and updates are included.

Yes. A one-time licence with optional annual support is available, and source-code handover or escrow can be arranged for Enterprise and custom builds.

On the hosting you choose: our managed cloud, your own cloud account, or your server inside the plant. Nothing is shared between tenants — every customer gets a separate database.

Roles are defined per department with view, create, edit and delete rights per module, and every request is checked on the server. Hiding a menu is not our security model.

Posted documents are never silently deleted. Cancellation reverses the stock and ledger effect and stays on the record with a reason and the user who did it.