<p class="compact-content-paragraph">Most vendors only show you the upside. We'd rather tell you where the work is, where the limits are, and <span class="handbook-highlight-blue">exactly how we protect your investment</span> against the things that usually go wrong in ERP projects. <span class="handbook-highlight-black">Honesty here isn't a risk</span>, it's the reason our clients trust the roadmap we build with them.</p>
<div class="handbook-onboarding-metric-cards handbook-support-metrics handbook-metrics-sm">
<div class="handbook-metric-card"><strong>Config-first</strong><span>Code only when needed</span></div>
<div class="handbook-metric-card"><strong>Core untouched</strong><span>Customizations stay separate</span></div>
<div class="handbook-metric-card"><strong>Honest tiers</strong><span>Mature vs. evolving, stated</span></div>
<div class="handbook-metric-card"><strong>Clean upgrades</strong><span>v15 to v16 path protected</span></div>
</div>
<h2 class="compact-content-heading">Config First, Code Second</h2>
<p class="compact-content-paragraph">Every requirement can be met two ways: by configuration, such as settings, custom fields, scripts, report builders, and permissions; or by code, such as custom apps, server logic, and integrations. We always reach for configuration first, and only write code when your process genuinely needs it. The reason is simple: <span class="handbook-highlight-blue">less custom code means cheaper upgrades, fewer bugs, and easier handover</span> to your team.</p>
<div class="handbook-team-roles-card handbook-config-path-card">
<h3 class="compact-content-heading">Preferred — Config path</h3>
<p class="handbook-team-roles-intro">No code required:</p>
<ul class="handbook-onboarding-check-list">
<li>Custom fields & layouts</li>
<li>Client & print scripts</li>
<li>Report & dashboard builders</li>
<li>Workflow builder & permissions</li>
</ul>
</div>
<div class="handbook-team-roles-card handbook-config-path-card">
<h3 class="compact-content-heading">When truly needed — Code path</h3>
<p class="handbook-team-roles-intro">Custom development:</p>
<ul class="handbook-onboarding-check-list">
<li>Custom apps & server logic</li>
<li>Third-party integrations</li>
<li>Virtual DocTypes & jobs</li>
<li>Bespoke business rules</li>
</ul>
</div>
<div class="handbook-agile-feedback">
<p><strong>Our rule:</strong> if configuration solves it, we don't write code. You pay for fit, not for complexity you'll maintain forever.</p>
</div>
<h2 class="compact-content-heading">Your Customizations Stay Separate</h2>
<p class="compact-content-paragraph">This is the single most important thing we do to protect your upgrade path. <span class="handbook-highlight-black">We never modify the ERPNext core.</span> Everything we build for you lives in a separate custom app that sits alongside the core, so when the platform updates, <span class="handbook-highlight-blue">your customizations don't break and your data stays intact</span>.</p>
<img class="handbook-wide-image" src="/files/seperation-concern.png" width="1999" height="818" alt="Separation of concerns: custom app sitting alongside the untouched ERPNext core" />
<div class="handbook-security-banner handbook-upgrade-note">
<p><strong>Why it matters for you:</strong> Because customizations live in their own app and not in the core, your upgrade path stays clean and predictable. The most common cause of painful, expensive ERP upgrades is avoided by design.</p>
</div>
<h2 class="compact-content-heading">What's Mature vs. What's Evolving</h2>
<p class="compact-content-paragraph">Not every capability in the platform is equally battle-tested, and we won't pretend otherwise. We classify capabilities into three honest tiers so your roadmap rests on solid ground and so you know which features to build on now versus which to plan for.</p>
<div class="handbook-issue-detail-list handbook-maturity-list">
<div class="handbook-issue-detail-card handbook-maturity-card handbook-maturity-card-core"><strong>Core</strong><span>Mature and battle-tested across thousands of production deployments. Build on these with full confidence.</span></div>
<div class="handbook-issue-detail-card handbook-maturity-card handbook-maturity-card-solid"><strong>Solid</strong><span>Dependable and first-party; may have known limits but works well within them. Safe for most needs.</span></div>
<div class="handbook-issue-detail-card handbook-maturity-card handbook-maturity-card-emerging"><strong>Emerging</strong><span>Recent or rapidly evolving. Useful today, with change expected over the next 12 to 18 months.</span></div>
</div>
<h2 class="compact-content-heading">The Capability Honesty Ledger</h2>
<p class="compact-content-paragraph">A sample of how we rate what you'll rely on, by maturity and by how much effort it takes to use.</p>
<div class="handbook-capability-explorer handbook-ledger-explorer">
<div class="handbook-capability-filter" role="group" aria-label="Filter capabilities by maturity">
<button class="handbook-capability-filter-btn is-active" type="button" data-filter="all" aria-pressed="true">All</button>
<button class="handbook-capability-filter-btn" type="button" data-filter="core" aria-pressed="false">Core</button>
<button class="handbook-capability-filter-btn" type="button" data-filter="solid" aria-pressed="false">Solid</button>
<button class="handbook-capability-filter-btn" type="button" data-filter="emerging" aria-pressed="false">Emerging</button>
</div>
<div class="handbook-capability-grid handbook-ledger-grid">
<div class="handbook-capability-card handbook-ledger-card" data-area="core"><span class="handbook-ledger-badge handbook-ledger-badge-core">Core</span><span class="handbook-capability-tagline">Light</span><strong class="handbook-capability-title">Data models, forms & permissions (DocTypes)</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="core"><span class="handbook-ledger-badge handbook-ledger-badge-core">Core</span><span class="handbook-capability-tagline">Zero</span><strong class="handbook-capability-title">Role-based access & audit trail</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="core"><span class="handbook-ledger-badge handbook-ledger-badge-core">Core</span><span class="handbook-capability-tagline">Config</span><strong class="handbook-capability-title">REST API & webhooks</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="core"><span class="handbook-ledger-badge handbook-ledger-badge-core">Core</span><span class="handbook-capability-tagline">Config</span><strong class="handbook-capability-title">State-machine workflows</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="solid"><span class="handbook-ledger-badge handbook-ledger-badge-solid">Solid</span><span class="handbook-capability-tagline">Config</span><strong class="handbook-capability-title">Dashboards & report builder</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="solid"><span class="handbook-ledger-badge handbook-ledger-badge-solid">Solid</span><span class="handbook-capability-tagline">Config</span><strong class="handbook-capability-title">OAuth identity provider / SSO</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="solid"><span class="handbook-ledger-badge handbook-ledger-badge-solid">Solid</span><span class="handbook-capability-tagline">Zero</span><strong class="handbook-capability-title">Mobile PWA experience</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="emerging"><span class="handbook-ledger-badge handbook-ledger-badge-emerging">Emerging</span><span class="handbook-capability-tagline">Light</span><strong class="handbook-capability-title">Newer native mobile tooling</strong></div>
<div class="handbook-capability-card handbook-ledger-card" data-area="emerging"><span class="handbook-ledger-badge handbook-ledger-badge-emerging">Emerging</span><span class="handbook-capability-tagline">Config</span><strong class="handbook-capability-title">Some recently-added BI features</strong></div>
</div>
</div>
<div class="handbook-agile-feedback">
<p><strong>How to read this:</strong> Maturity tells you how proven a capability is. Effort tells you what's involved: Zero is a setting, Config is a few minutes with no code, and Light is a small amount of custom work.</p>
</div>
<h2 class="compact-content-heading">Protecting Your Upgrade Path</h2>
<p class="compact-content-paragraph">ERP platforms evolve. Because we keep your customizations in a separate app and lean on configuration over code, moving between major versions stays controlled rather than risky. Here's how we manage a version upgrade such as v15 to v16 or a newer version.</p>
<img class="handbook-wide-image" src="/files/managed-version.png" width="1999" height="637" alt="Managed version upgrade process from ERPNext v15 to v16" />
<div class="handbook-security-banner handbook-upgrade-note">
<p><strong>We've documented this.</strong> We maintain a detailed v15 to v16 migration guide covering custom DocTypes, server scripts, and API changes, so upgrades follow a tested process, not guesswork.</p>
</div>
<h2 class="compact-content-heading">For Technical Buyers</h2>
<p class="compact-content-paragraph">If you're evaluating ERPNext against an in-house build or a heavier enterprise suite, here's the architecture pattern we recommend for ambitious deployments.</p>
<h3 class="compact-content-heading">Recommended architecture for custom front-ends</h3>
<p class="compact-content-paragraph">For products that need a fully custom user experience on top of ERPNext, we use Frappe as the secure system-of-record and identity provider, with a dedicated front-end talking to it through a thin backend-for-frontend layer.</p>
<img class="handbook-wide-image" src="/files/systeme-architecture.png" width="1999" height="849" alt="System architecture with custom front-end, backend-for-frontend layer, and Frappe core" />
<p class="compact-content-paragraph">This keeps your business data, permissions, and audit trail in a proven core while giving you total freedom over the user-facing experience. You get the productivity of the platform and a bespoke product surface.</p>
<h2 class="compact-content-heading">Frequently Asked Questions</h2>
<div class="handbook-faq-list">
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>Why do you talk about limits at all?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Because hidden limits are what blow up ERP budgets and timelines. Telling you upfront which capabilities are mature, which are evolving, and what needs custom work lets you plan a roadmap that won't surprise you later.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>Does custom code make upgrades risky?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Only if it's done badly. We keep every customization in a separate app that never touches the ERPNext core, and we prefer configuration over code wherever possible.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>What does config first save us?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Money and risk. Configuration changes survive upgrades more easily, are faster to make, and are easier for your own team to maintain.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>How do you handle a major version upgrade?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>We review your custom apps and APIs, test the upgrade on staging, validate workflows and data, then schedule and execute the production upgrade through a documented process.</p></div></div>
<div class="handbook-faq-item"><button class="handbook-faq-question" type="button" aria-expanded="false"><span>Can we build a custom front-end on top of ERPNext?</span><span class="handbook-faq-chevron" aria-hidden="true"></span></button><div class="handbook-faq-answer"><p>Yes. We use Frappe as the secure system-of-record and identity provider, with a custom client talking to it through a backend-for-frontend layer.</p></div></div>
</div>