Frequently asked questions

Crator helps you implement ERPNext with AI.

Tell Crator what your business needs in plain English. Crator then builds the workflows, reports, forms, dashboards and integrations for you in ERPNext.

Crator is not itself an ERP. Crator is the tool you use to set up and customise ERPNext, so it matches the way your business operates.

You implement ERPNext without code and without a developer for each change.

You only need to know how your business must work.

Crator asks you questions, shows you its plan and does the technical work.

You can customise every ERPNext module with Crator: CRM, sales, inventory, manufacturing, buying, accounting, HR and projects.

In each module you can create or change:

• Document types and forms
• Approval workflows
• Reports and dashboards
• List, kanban and calendar views
• Roles and permissions
• Integrations and automations
• Custom ERPNext modules

Crator works only with ERPNext, and your ERPNext site must be hosted with Crator.

Crator cannot change an ERPNext site on your own server. If you use ERPNext today and want to move it, contact us. We will help you plan the migration.

Most customers import their data themselves. Crator helps you structure and load it.

If you need help, contact us and we will give you a quote for the migration.

Yes, if the other system has an API.

Give Crator the API documentation and tell it how the two systems must work together. Crator then builds the integration in ERPNext.

Crator builds and tests each change in a test environment first, away from your live ERP.

You review the result. You publish it to your live ERP when you are ready.

Your live ERP stays safe. Crator shows you its plan before it makes a change.

If the result is not correct, discard it. Your ERP goes back to the previous version.

You choose who has access to Crator.

You can limit access to selected administrators or managers. All other employees continue to work in ERPNext as usual.

ERPNext roles and permissions control what each person can see and change.

Yes. You can keep the tools that work for you and replace the rest step by step.

If your software has an API, you can use Crator to connect it to ERPNext.

Start with one workflow or one module, and expand when you are ready.

For example, start with inventory, procurement, CRM, quotations or one approval workflow.

Yes. We built Crator for this.

Instead of hiring a specialist for each customisation, you tell Crator what you need and build it yourself. If you want our team to do part of the implementation, we price that service separately.

Crator is registered in Singapore, so we do not add Indian GST to your invoice.

When a GST-registered Indian company buys Crator, the purchase is usually an import of services. Under the Reverse Charge Mechanism, you calculate the applicable IGST and pay it to the Indian government.

You may be able to claim input tax credit for this IGST. Ask your accountant or tax adviser to confirm the correct treatment.

Crator builds and tests each change in a test environment.

You decide when a change is ready. Publish it to your live ERP, or discard it.

Crator works where ERPNext gives you a good foundation.

ERPNext supports manufacturing, distribution, retail, services, healthcare, education and project-based businesses. If a standard module does not cover one of your processes, use Crator to build a custom module or workflow.

In a traditional implementation, each change can need a specification, a developer and an implementation cycle.

With Crator, you describe the change, review the result and publish it yourself. Your ERP can change as fast as your business.

Start a Crator-hosted ERPNext site and describe the first workflow you want to build.

If you have an ERPNext site on another server, contact us. We will help you move it to Crator.