ERPNext Training
An ERP is only adopted when each team can complete its own work in it without asking for help.
Why It Matters
Each session is hands-on. Everyone is logged in under their own role and posts their own documents while we are in the room, so the first time a purchase manager raises a real order is not the first time they have seen the screen.
The administrator track covers the routine work that otherwise becomes a support ticket every week: adding users and permissions, adjusting a print format, editing a workflow, checking background jobs and knowing where to look when something fails.
We list who does what in the system and build a track for each role.
A training copy of your instance is set up with your data and real logins.
Short hands-on sessions per role, with practice work in between.
Each team runs a full cycle on its own, and we note where people still hesitate.
Guides and recordings are handed over, with a refresher after go-live.
Invoices, payments, journal entries, tax handling, bank entries and the period close.
Receipts, transfers, delivery notes, batch and serial handling and stock counts.
Quotations, orders, approval limits, price lists and converting documents correctly.
Bills of material, work orders, job cards, material issue and subcontracting.
Employee records, leave and attendance, shift handling and the payroll run.
Users, permissions, workflows, print formats, backups and first-line diagnosis.
The people teaching your team are the ones who configure ERPNext, so the answers are specific.
Sessions run on a copy of your setup, which also exposes configuration gaps early.
Two hours with practice in between beats two days that nobody retains.
A track is finished when the team completes a cycle unaided, not when the slides end.
We aim to make your administrator self-sufficient for routine changes.
Everyone who will enter or approve a transaction, split by role rather than trained as one large group. Finance, stores and dispatch, purchase, sales, production and HR each get their own session, plus a separate deeper session for whoever will administer the system internally.
Yours, on a training copy of your configured instance. People learn far faster when the item codes, customers and approval rules on screen are the ones they already recognise, and it surfaces configuration gaps while there is still time to fix them.
Most rollouts need 5 to 10 sessions spread across two to three weeks, each about two to three hours. Short sessions with practice in between work much better than a two-day marathon nobody remembers.
Yes. The administrator track covers users and role permissions, naming series, print formats, workflows, the customize view, background jobs, backups and where to look when something fails. The aim is that routine changes stop needing us at all.
You keep the recorded sessions and the role guides written against your own configuration, which covers most new joiners. We also run refresher or new-hire sessions on request, and they are included in the change hours on our support plans.
Yes. We start by reviewing your instance so the training matches how it is actually configured rather than a generic ERPNext course. If we find setup problems that would confuse users, we flag them before the sessions begin.
Related
The other services in this section, and related pages from TCB Infotech.
No commitment. A practical look at what your team needs to learn.
