Loading…
Loading…
The handful of ERPNext Settings toggles that quietly shape how your accounts, stock, sales, buying and production behave — worth deciding deliberately before your first live transaction, not after.
31 checks · 6 sections
Most of ERPNext's behaviour is governed by a small set of Settings doctypes — Accounts Settings, Stock Settings, Selling Settings, Buying Settings, Manufacturing Settings — plus a few foundational choices like valuation method and naming. Individually each is one switch; together they decide whether your team is warned or blocked, whether stock can go negative, how rates flow through a cycle, and how documents are numbered. Change some of them after go-live and you're fighting historical data. This reference walks the settings that are genuinely worth a decision up front, grouped by module, with what each one actually does so you can choose on purpose rather than inherit the default. It reflects the real field names and behaviour in the current ERPNext source — use it as a conversation guide with your implementation partner.
Check Supplier invoice number uniqueness + 4 more
Allow negative stock + 4 more
Is Sales Order required to create Sales Invoice/Delivery Note? + 4 more
Is Purchase Order required for Purchase Invoice & Receipt creation? + 4 more
Backflush Raw Materials Based On + 4 more
Default Valuation Method (Stock Settings) + 5 more
All 31 checks across 6 sections as a clean branded Excel — each item with the guidance for why it matters, ready to share with your team. Free, no email required.
Several of them shape historical data. Valuation method, item and party naming, and immutable ledger become entangled with every transaction you post, so changing them later means reworking data or living with inconsistency. Behaviour toggles like 'maintain same rate' or 'allow negative stock' are easier to flip, but even those are best set intentionally so your team learns one consistent way of working from day one.
The foundational ones: Default Valuation Method, Item Naming By, Customer/Supplier Naming By, and to a lesser extent Enable Immutable Ledger and Accounting Dimensions. These define the structure of your masters and ledgers. Module toggles such as 'Purchase Order required', 'maintain same rate', or the manufacturing backflush method can be adjusted more freely, though changing them mid-stream can confuse users.
Both Selling and Buying Settings let the same-rate check either Stop the transaction or just Warn. Choose Stop when rate integrity is critical and you want a hard block; choose Warn when you need flexibility for genuine price changes but still want users nudged. It's a control-versus-agility trade-off specific to how disciplined your pricing needs to be.
No — these are the ones most worth a deliberate decision before go-live. ERPNext's Settings doctypes contain many more options, and there are also framework-level System Settings (number/date formats, session limits, and so on). This reference focuses on the toggles that most directly change day-to-day accounting, stock, sales, buying and production behaviour. Your implementation partner will help you work through the rest in context.
Get a clear plan, an honest timeline, and a fixed scope. Talk to a real expert today — whether or not you work with us.
Kochi (Kadavanthra & Infopark) · Thiruvananthapuram · across India & overseas · In business since 2011