ERPNext Africa
Open-source ERP for African manufacturers

Enterprise-grade ERP.African economics.

The licence fee is R0, forever. The method is published in the open. We move South African manufacturers and distributors off SysPro, Sage, Dynamics and spreadsheets onto ERPNext — and we prove it works next to your current system before you commit.

R0 per-user licensing SA-localised · VAT · PAYE · POPIA Hosted in Johannesburg or Cape Town AI-ready by architecture

01

The renewal letter arrives every year. It's never smaller.

The mid-market squeeze, as we find it in almost every first conversation:

a.

Licensing built for another economy

Per-user, per-module fees that track hard currency and grow every time your team does. You pay this year's bill again next year — plus the increase — for the system you already have.

recurring, escalating
b.

Excel is the real ERP

Multi-warehouse stock, production planning and the month-end pack stitched together by spreadsheets and one heroic person who knows how they join.

fragile, person-dependent
c.

Decisions on stale data

The management pack lands weeks after month-end, hand-built from extracts. Every meeting starts with whose number is right.

slow, contested
d.

Manufacturing priced as premium

Multi-level BOMs, variants, costing and shop-floor capture — sold as add-on modules by legacy vendors, too much for spreadsheets to fake.

add-ons, per seat

02

This isn't cheaper ERP. It's a different ownership model.

ERPNext is open source — the same codebase run by tens of thousands of companies worldwide, maintained by a profitable product company and 600+ contributors. You don't rent permission to use your own system of record. You own it, and pay for the work of making it fit.

The rental model

Licensed ERP

  • Pay per user, per module, per year — forever
  • Upgrades priced as projects, on the vendor's clock
  • Customisation deepens lock-in with every change
  • Your data behind proprietary schemas and API tiers
  • Exit cost high — by design
The ownership model

ERPNext, done properly

  • R0 licensing — seat #80 costs what seat #8 did: nothing
  • Upgrades are routine maintenance, on your schedule
  • Customisation survives upgrades by design — no fork
  • Your data in your database, full API included
  • Any capable partner can take over — which keeps us honest

03

Already running Africa's factories, farms and warehouses.

Production deployments, not pilots. Named walkthroughs and reference calls are arranged on request — we don't put clients' names on websites.

South Africa · furniture

Bespoke furniture manufacturer

Two trading entities live on ERPNext with a Shopify storefront, CAD-to-BOM import and live CNC machine telemetry feeding the factory floor.

Steel · distribution

Steel manufacturing & distribution

10+ warehouses, 500+ customers, 100+ staff — migrated off QuickBooks and Excel onto one stock and finance core.

Food · make-to-order

Make-to-order food processing

109 users across 7 modules, multi-level BOMs driving order-based production.

Agri · retail

Multi-branch agri distribution

4 branches, 9,000+ SKUs, 400+ B2B accounts and 10,000+ walk-in customers on one system.

A solutions architectwho builds and runs ERPNext systems in production, AI layer included
A fractional CFOwho has closed month-ends inside the companies these systems run
A shop-floor engineerwho wires CNC machines and CAD exports into the ERP the floor actually uses

Our entire method is published. Read it before you pay anyone — including us.

The Playbook is our working methodology in the open: migration guides per source system, the manufacturing patterns, the platform case, and the honest commercial model. No sales gate, no email capture. That's the point.

Or skip the reading — tell us what you run and we'll bring the right playbook to the conversation.


04

The honest boundaries.

Your own research will find these, so here they are from us first — each with how it's actually covered.

No finite-capacity APS in the box

ERPNext gives capacity visibility, not constraint-based auto-scheduling. Most plants our size run better on visible load + a human sequencer — and if the proof-of-concept says otherwise, open-source APS integrates over the API.

One storefront is standard; more is a build

The Shopify connector is single-store. Additional storefronts are a well-trodden, scoped integration build — real work, honestly priced, never a checkbox.

Sometimes migration isn't the answer

If your accounting genuinely works in Xero, integration may beat migration — and our Xero playbook says exactly that.

The gate can say no

Our proof-of-concept ends at a go/no-go review with written success criteria. Sometimes the answer is no — better to find out for the cost of a POC than a migration.


05

You buy a proof, not a promise.

The same evidence-gated sequence every time — sized to you, priced fixed-fee per phase, stoppable at every gate.

Read the playbook

The method is public. Start with the guide for your current system — it's the same one we deliver with.

The working session

A half-day: we model two of your real products as live BOMs in a demo instance and run an order through to dispatch.

Proof of concept

ERPNext stands up beside your current ERP, models a representative slice of your business, and is judged against written criteria.

Phased migration

Only after the gate: fixed-fee phases, a factory pilot on real orders, cutover when the numbers reconcile to the cent.

Nothing is migrated until the gate passes. Your current system stays live and authoritative throughout — the only exposure is the cost of the proof, never business continuity.

06

Talk to us.

Tell us what you make and what you run today. We reply within a business day — usually with the right playbook attached, and an offer to model two of your real products in a live demo instance.

Prefer reading first? The Playbook is open.