Station 1 of 10
Where to start with ERPNext and why
What you leave this station with
A written decision on track and environment, a weekly plan that tells you what to do each day, and an honest estimate of the time before you invest it.
With every other system, learning starts at “how do I get a copy?”. With ERPNext that question is answered before you ask it: the source is complete and open, the cloud trial runs fourteen days at no cost, and no module hides behind a higher tier.
Which produces the paradox that defeats most beginners: when the barrier to entry disappears, so does the thing that used to impose an order. Someone who opens the system and finds accounting, inventory, manufacturing, projects, quality, point of sale and HR all available in the first minute opens all of them — and concludes two weeks later that ERPNext is incomplete. It is not incomplete. There was no order.
This station opens no screen at all. It settles three decisions that make the next fifteen hours produce something rather than evaporate.
Decision one: functional track or technical
ERPNext is two layers, not one, and this is the first thing to understand because more than half the published material about it conflates them and sends the reader to the wrong layer.
| Frappe Framework | ERPNext | |
|---|---|---|
| What it is | A framework for building business applications | The ERP built on top of it |
| What you learn in it | Data models, permissions, scripted reports, APIs | Document cycles, accounting, inventory, localisation |
| Who gets hired on it | An application developer | An implementation consultant |
| Its licence in the repository | MIT | GNU GPL version 3 |
The rule I would give without hesitation: the functional track always precedes the technical one. Anyone who learns the framework before the document cycle builds elegant applications for problems that do not exist, and writes a modification that runs, looks right, and corrupts stock balances silently.
So write your goal down before you continue.
| Your goal | What you actually need | What you can ignore for now |
|---|---|---|
| A consultant job at a partner | Every station, and the functional certification | The framework and app building |
| Running your own company on it | Stations 2 through 8 | The certification, deep customisation |
| A framework developer track | All of the above, then the framework after it | Nothing — the ordering here binds rather than suggests |
| Evaluating the system before adopting it | Stations 2, 3 and 8, then the product guide | The rest of the path |
Decision two: which environment
Here sits the most common error in learning ERPNext specifically, and it is an error that does not exist in closed systems: because the source is available, the beginner assumes the right route is to install it on their own machine.
A manual install is an excellent lesson — in server administration. You learn the command-line tool, the database server, the job queue, and the front web server. You learn nothing whatsoever about enterprise resource planning. And it is the single most common point at which learners stop before seeing one screen.
The three options and the verdict on each:
| Environment | When it is right | What it costs |
|---|---|---|
| Frappe Cloud trial | Always at the start, for the first two weeks | Zero — the trial runs 14 days |
| A managed site on Frappe Cloud | When you want a permanent environment to build your portfolio in | From $5 a month |
| An install on your own machine | When you enter the framework at station nine or later | Your time, which is the most expensive thing you have right now |
The figures are read from the official ERPNext pricing page on 6 September 2026, and are set out in full — with what the page does not say — in the ERPNext guide.
The practical rule: start in the cloud, and defer the local install until after station seven. By the time you reach it you will understand what you are installing, and it becomes half an hour instead of a week.
Decision three: what you decide not to learn yet
Nobody makes this decision, and it is the most useful of the three.
The system ships a great many modules: accounting, purchasing, sales, inventory, manufacturing, projects, point of sale, quality and support, with HR and payroll in a separate application. Nobody learns them all at once, and anyone who tries masters none.
The backbone people are hired on is only four: master data, purchasing, sales, and inventory with its accounting. Everything else — manufacturing, projects, point of sale, quality — builds easily on those four once they are solid, and is impossible to understand before them. Open a work-order screen before you understand how one stock movement is valued and you are memorising buttons.
So write this line into your file: I will not open manufacturing, point of sale or HR before station seven. Holding to it is half the difference between finishing the path and abandoning it.
The weekly plan
An executable plan, not a suggestion, assuming one hour a day.
| Week | Stations | What exists by the end of it |
|---|---|---|
| One | 1 and 2 | ERPNext running in front of you, on a database you own |
| Two | 3 | A complete company: chart of accounts, warehouses, items, taxes |
| Three | 4 and 5 | A purchase cycle and a sales cycle, executed end to end by you |
| Four | 6 | A measured difference between the two costing methods, and its margin effect |
| Five | 7 | A bank reconciliation, a closed period, statements you read with confidence |
| Six | 8 | A settled answer on e-invoicing in your own country |
| Seven | 9 | A written line between what data solves and what earns code |
| Eight | 10 | A delivered project, a portfolio, and a decision about the certification |
Eight weeks reaches a real operating standard. Reaching assessment standard takes roughly twice that, and the estimate is honest rather than encouraging.
The one thing to know before line one
A single non-negotiable prerequisite: double-entry basics. You do not need to be an accountant. You do need to know what debit and credit mean, why every movement has two sides, and the difference between a balance-sheet account and a profit-and-loss account.
The reason is more pressing here than on any other system on this site, because ERPNext puts two ledgers in front of you after every movement — the stock ledger and the general ledger — and expects you to read the relationship between them. Without double entry you see two reports and cannot tell which explains the other, so you stop opening them, and you lose the one feature that makes this system an excellent school.
If that foundation is missing, read the ledger and the close before the next station. Two hours there saves twenty here.
The acceptance test for this station
- Write your goal in one line and pick your row from the goals table above.
- Write the environment decision with the date your free trial expires, because fourteen days pass faster than you expect.
- Write the list of what you will not open before station seven, and keep it in front of you.
- Fix an hour in your day — the same hour every day, not whatever is left over.
- Revise double-entry basics and confirm you can state both sides of a cash purchase entry before moving on.
What comes next
The next station is entirely hands-on: an ERPNext environment running in front of you, the difference between the three routes, and why the first thing to do after starting it is wreck it deliberately so you learn how to rebuild it.