ERPNext implementation, Frappe apps, POS and integrations
We set up and customise ERPNext, build the apps and point-of-sale systems around it, and connect the devices and services your business depends on. Here's what each service covers and how we run it.
ERPNext implementation and customisation
Set up ERPNext around the way your business actually works, or bring an existing setup back in line with it.
Problems we address
- Stock, sales and accounts kept in separate spreadsheets or tools
- An existing ERPNext site full of workarounds nobody trusts
- Month-end reports that need manual clean-up
- Moving off a legacy system without losing your history
What you get
- A review of your processes, then configuration of the modules you need: selling, buying, stock, accounting, HR or manufacturing
- Data migration from spreadsheets or your current system
- Custom fields, print formats, reports and approval workflows
- User training and support through go-live
Related: Custom ERPNext builds Discuss your setup
Frappe app development
When a process doesn't fit standard ERPNext, we build it as a Frappe app: your own module that sits beside ERPNext instead of changing it.
Problems we address
- A workflow ERPNext doesn't model, such as field service or fuel station operations
- Staff who need a faster, simpler screen than the standard desk
- Customisations edited into core code that break on every update
What you get
- A custom Frappe app with its own data types, permissions and reports
- Focused Vue frontends for specific roles, like cashiers or field staff
- Documentation and a handover so your team can maintain it
Related: Field Service Management Frappe Desk Automated Action
Point-of-sale systems
Point of sale that works with your ERPNext stock, pricing and accounts, keeps selling when the connection drops, and stays quick at a busy counter.
Problems we address
- Checkout that stops when the internet does
- Sales in the POS that don't match stock in ERPNext
- Cash and shift totals reconciled by hand
- Sales invoices that have to be reported to FBR
Related: X POS Minu POS Digital Invoicing
Integrations and automation
Connect the devices and services around your ERP so data arrives on its own, and automate the back-office steps people repeat every day.
Problems we address
- Attendance punched into a biometric device, then typed into payroll
- Invoices re-entered into a tax or payment portal
- Approvals and reminders handled over chat and memory
- Exports and imports between systems done by hand
What you get
- Device integrations, such as ZKTeco BioTime 8.5 attendance into ERPNext HR
- Integrations with third-party APIs and webhooks, built to retry and report failures
- No-code automation rules with triggers, conditions and actions
- Scheduled jobs that keep data in sync
Related: BioTime → ERPNext Automated Action Digital Invoicing
Web, mobile and cloud
Most of our work centres on ERPNext and Frappe, but projects often need more around them. We handle that too, so you don't need a second supplier.
- Web apps and customer portals
- Cross-platform mobile apps
- Desktop apps built with Electron, like Minu
- Hosting, deployment pipelines and monitoring for your Frappe sites
How an engagement runs
The same four stages apply whether you need a full implementation or a single integration.
-
Review
A call and a look at your current system, data and processes. We agree the problem, scope and what a good result looks like.
You get: a written scope and estimate
-
Design
We work out workflows, data structure, screens and integrations with the people who'll use them.
You get: a specification or prototype to sign off
-
Build and migrate
Short increments with regular demos. Data is migrated and checked on a test site before anything goes live.
You get: a working system on a test site
-
Launch and support
Go-live, user training and a handover. Ongoing support and improvements can be agreed afterwards.
You get: a live system and handover notes
What to send us first
You don't need a formal brief. These details help us give you a useful first answer.
- What your business does, and roughly how many users, branches or tills are involved
- What you use today: ERPNext and its version, other software, or spreadsheets
- The processes causing the most trouble, with an example document or report if you can share one
- Any devices or services that need to connect
- Your timeline and any fixed dates, like a branch opening or a filing deadline
Questions clients ask
Can you work on an ERPNext site someone else set up?
Yes. We start by reviewing the current setup: customisations, data quality and integrations. Then we recommend whether to fix, extend or reconfigure it.
Do you change ERPNext's core code?
We avoid it. Customisations go into separate Frappe apps, the same way our own open-source apps are built, so ERPNext can still be updated.
Which ERPNext versions do you work with?
Our current products, including X POS, are built for Frappe and ERPNext version 16. If you run an older version, tell us which one and we'll explain what's involved.
Is X POS free to use?
X POS and several of our Frappe apps are open source under the MIT licence, with code on GitHub. If you'd rather not run it yourself, we can install, configure and support it for you.
Do you provide support after launch?
Yes. Ongoing support and improvements can be agreed once your system is live. Tell us the level of cover you need.
How do we get started?
Use the contact form or email hello@kodlyft.com with the details above. We reply within one business day.
Not sure which service you need?
Describe the problem in a few lines. We'll tell you how we'd approach it, with no obligation.