A real ERPNext training environment

The previous station chose the environment. This one starts it, and installs the habit that separates learning from watching: a database wrecked on purpose and rebuilt every week.

The three routes, and what actually separates them

Route	What it gives	What it withholds	When to pick it
Free cloud trial	A complete system in minutes, with no server to administer	Permanence — 14 days only	The first fortnight
A managed site on subscription	A permanent environment, backups, one-click upgrades	Reading the source and editing it directly	From week three onwards
An install on your machine	Everything: the source, the system logs, and freedom to break things	Your time, and days that may not end at a screen	After station seven

The figures and options are read from the product’s pricing page on 6 September 2026, and are set out with what the page does not say in the ERPNext guide.

The verdict I repeat because it saves a full week: start in the cloud. A local install is not as hard as its reputation, but it consumes your attention on problems outside your field — a language version, a folder permission, a service that will not start — and right now you need all of that attention elsewhere.

The structure that explains everything later

Before any configuration, understand three words. Understand them and you understand why this system upgrades the way it does, and why customisation here is cheaper than elsewhere.

The app. An independent code package. The framework is an app, ERPNext is an app that depends on it, HR is a third separate app. And written customisation — when it becomes necessary at station nine — is a fourth app, never an edit inside the three.

The site. One database with its files and settings. The site is what a company sees, and the apps it needs are installed onto it alone.

The bench. The directory holding the apps and the sites together with the tools that manage them. It is the unit of operation: sites are created from it, apps installed, backups taken.

The consequence that matters right now: one site can carry a complete company, and deleting it touches nothing else. That is what makes deliberate destruction safe, and it is what you are about to do.

The first things to do once it starts

Not opening accounting. The order that produces something:

1. Set the interface language, the time zone and the currency before any document. Changing them after the first movement is theoretically possible and practically irritating.
2. Try Arabic early — today, not in two months. ERPNext ships an Arabic translation file inside the product, and its completeness is measured numerically in the product guide above: roughly one string in five still renders in English. Learn that while training, not while promising it to a client.
3. Read the shape of a document list, then the shape of a single document. Everything in this system follows the same shape: a list, a document, and an activity sidebar. Understand the shape once and you understand it in every module — the fastest win available here.
4. Open one document, submit it, then try to edit it. You will not be able to. These are the five most important seconds of this station, for the reason set out below.
5. Take a backup now, while you own no data worth keeping. Because someone who learns to take a backup when they do not need one takes it when they do.

The three document states — the constraint that irritates everyone

Every ERPNext document has three states: draft, submitted, and cancelled. The move from the first to the second is one-way.

So what if you got a submitted document wrong? You do not edit it. You cancel it, then create an amended copy carrying its number with a suffix marking it as an amendment. The original stays in the record, its cancellation stays in the record, and the new copy stays linked to both.

An arrival from another system reads this as complexity for its own sake. It is in fact the most useful constraint in the product, for three reasons worth writing down now because they return in four later stations:

• An auditor cannot lose a trail. There is no silent edit of a document that produced an entry.
• The accounting entry follows the document literally. Submission creates the entry, cancellation reverses it, and there is no third state in which the document says one thing and the entry another.
• E-invoicing collides with this directly, which is station eight. Understand the constraint now and you understand there why “the system is compliant” is not enough.

Deliberate destruction — half the value of this station

The rule: an environment you are afraid to break teaches you nothing.

Anyone training on a database they fear spoiling avoids experimenting, so they never learn what happens when a document is cancelled after its invoice, or what happens when stock goes negative, or what the refusal message looks like when you close an account that has movement. All three are asked about in interviews and paid for on projects.

So make it a written practice.

1. Create the company and master data as in the next station.
2. Take a backup, named with its date.
3. Try what you are afraid of: cancel a submitted document, delete an account with movement, issue more quantity than the warehouse holds, change the costing method on an item that has a balance.
4. Read the refusal message and do not skip past it. Refusal messages in this system describe the accounting rule they are protecting; reading them is free tuition.
5. Restore the backup, or rebuild from nothing. The fifth rebuild takes half an hour, and it is the best mastery test you own.

What not to do at this station

• Do not switch on everything you can see. Fifteen modules floods the menus and makes every screen look incomplete, because it is waiting on data you never entered.
• Do not enter your real company data. A training environment you deliberately wreck is not a place for customer records.
• Do not start by imitating a complex company. One company, two warehouses, ten items, two customers, two suppliers. Complexity gets added once you understand the simple case, never before.

The acceptance test for this station

1. Open the system and create a working site or trial, and record its expiry date if it is temporary.
2. Set the language, currency and time zone and write down what you chose and why.
3. Submit any document then try to edit it, and write out the refusal text exactly as it appeared.
4. Take a backup and actually restore it. A backup never restored once is not a backup, it is an assumption.
5. Rebuild the environment from nothing once and time it. That figure becomes your reference number at station ten.

What comes next

You have a working system and a database you are free to delete. The next station fills it with something worth having: a complete company with its master data — including the mandatory ordering that, once broken, turns everything after it into correction rather than construction.