Adapt ERPNext to your workflow.
Does your team need tailored fields, clear approvals or a specific report? AIKI configures and extends ERPNext for those tasks. We first check what standard features cover and where custom development is useful.
- Service
- Configuration and extensions
- Approach
- Standard features before custom code
- First step
- Free conversation
- Demo
- Afterwards, on request
What we adapt to your workflow.
Typical tasks. The actual scope depends on your requirements.
- Fields and forms
Capture the data your workflow requires.
- Approvals and roles
Represent responsibilities and permitted actions in the system.
- Reports and views
Make the information you need easy to access.
- Custom functions
Develop where the assessed standard does not cover the requirement.
Test cases, scope and maintainability.
Make an approval requirement testable.
We describe the expected outcome, roles and exceptions with specific test cases so the change can be reviewed before approval.
Understand the change when an update arrives.
Versions, existing extensions and operational ownership inform the plan. Maintenance and testing for future updates are agreed for your project.
Questions before starting your project.
When ERPNext customization makes sense
An existing process requires workarounds: an approval needs another role, a required field is missing, or a report does not answer the question that matters. These situations justify reviewing the requirement; they do not automatically justify developing new software.
Start with the workflow and expected outcome. For an existing ERPNext system, include the version, installed extensions and who operates it. For a new implementation, custom work needs to be scoped alongside the wider project.
Standard features, configuration or custom development?
Standard feature: the required way of working already exists and needs to be understood or introduced operationally. Configuration: existing settings, fields, roles or workflows are adjusted. Development: the requirement needs additional logic or an extension built on ERPNext and Frappe.
This distinction keeps every difference from becoming a development request. External systems and data transfers also need an integration assessment. Scope and feasibility are agreed for the specific case.
Choose the appropriate next step
If the suitability of ERPNext is still unclear, start with consulting. If the whole system is being introduced, scope custom work within the implementation plan. If data needs to move between systems, include an integration assessment.
For the enquiry, describe one concrete workflow and the result you need. AIKI supports ERPNext projects in German and English and replies within two working days.
Make an approval requirement testable
an order above an agreed amount needs approval before processing can continue. The requirement names the threshold, the decision-making role and the status before and after approval.
Test an order below the threshold, one above it and a rejected approval. Also clarify who can change amounts later and what that means for an existing approval. These details make it possible to check whether the change reflects the business process.
What needs to be clear before implementation.
Five details help with the initial discussion: the current workflow, affected data, responsible role, expected outcome and an example with an exception. You do not need a complete technical specification for the first enquiry.
Before implementation, agree on scope, access, test data and who will review the business result. A technically successful change still needs acceptance from the people who use it.
Understand the change when an update arrives
Record which settings and extensions changed and which tests cover them. Those checks can be repeated before an update. A custom extension can still need further work; blanket compatibility promises do not establish otherwise.
Operations, version changes and ongoing maintenance are agreed for the project. Custom development does not automatically include a support contract or guaranteed response times.
What do we agree before implementation?
We first assess standard features and configuration. Custom development is scoped where your workflow requires it.
Starting point: Which workflow needs to change?
Outcome: What should your team be able to do in the system?
Scope: Feasibility, implementation, testing and support are agreed for your project.
Tell us about your workflow.
In a free conversation, we discuss your starting point and the result you need. We can then show you a demo on request. Custom work and integrations are delivered within the agreed project scope.