For retail, distribution, manufacturing and service businesses

ERPNext, POS and automation built around how you operate

We implement and customise ERPNext, build Frappe apps and point-of-sale systems, and connect your devices and payments so your team stops re-keying data between systems.

X POS checkout screen: item search results on the left, a three-item cart with discount and total on the right
X POS, our open-source point of sale for ERPNext. Actual product screen with demo data. Explore X POS

Problems we solve

Software we've built and published

Two point-of-sale products and a set of open-source Frappe apps whose code you can read before you hire us.

X POS order history listing paid sales invoices with customer, date and amount

X POS for ERPNext

An open-source point of sale that runs on your ERPNext site. Checkout keeps working offline and syncs in the background, with barcode scanning, split payments, returns and shift reconciliation.

Minu POS

A desktop app for shops that need to keep trading without the internet: inventory, double-entry accounts and a point of sale, with tills sharing one hub on the local network.

Open-source Frappe apps

What we do, and what you get

Four kinds of work make up most of our projects. Each starts from a problem in how your business runs today.

ERPNext implementation and customisation

Stock, sales and accounts spread across spreadsheets and tools that disagree.

  • Configuration of the modules you need
  • Data migration from your current system
  • Custom fields, reports, print formats and training

Frappe app development

A process standard ERPNext doesn't model, or a screen that's too slow for the job.

  • Custom apps with their own data, permissions and reports
  • Focused Vue frontends for specific roles
  • Built as separate apps so ERPNext stays upgradeable

Point-of-sale systems

Tills that stop when the internet does, or sales that don't match your stock.

  • X POS set up on your ERPNext site, or Minu as a standalone desktop system
  • Payment modes, taxes, receipts and permissions per till
  • Sales invoice posting to FBR through our DI app

Integrations and automation

Data typed from one system into another, and approvals chased by hand.

  • Device integrations, such as biometric attendance into ERPNext HR
  • Third-party API and webhook integrations
  • No-code automation rules for repetitive tasks

We also build web and mobile apps and the cloud infrastructure behind them, usually alongside an ERPNext or Frappe project. Web, mobile and cloud work

How a project runs

Four stages, each ending with something you can review before we move on.

  1. Review

    We look at your processes, current system and data, and agree what a good result looks like.

    You get: a written scope and estimate

  2. Design

    Workflows, data structure and screens are agreed before building starts.

    You get: a specification or prototype to sign off

  3. Build and migrate

    We work in short increments with regular demos, and migrate and check your data.

    You get: a working system on a test site

  4. Launch and support

    Go-live, user training, then ongoing support and improvements if you want them.

    You get: a live system and handover notes

Check our work before you hire us

Our code is public

X POS and our other Frappe and ERPNext apps are public on GitHub under the MIT licence, so you can see how we structure and document our work.

We build products, not just projects

We design, release and maintain X POS and Minu ourselves, so we work through the same retail and stock problems our clients bring to us.

Your system stays upgradeable

Customisations go into separate Frappe apps, the same way our own apps are built, rather than edits to ERPNext's core code.

You talk to the builders

Scope, demos and questions go directly between you and the people writing the code.

Tell us how your business runs today

Share what you use now and where it causes trouble. We reply within one business day with questions or a suggested next step.