StackLift
Integration · CRM & ERP

ERPNext integration: cost, timeline and how it works.

Connecting ERPNext means talking to the Frappe framework underneath it. Every business record is a DocType with an automatic REST endpoint, so a web store, app, or reporting tool can create and read orders, items, and invoices using a token. The real planning questions are your custom DocTypes, document states, and where the site is hosted.

From the estimate

What an ERPNext integration adds to a project

StackLift's free estimate prices every integration by the engineering it takes. These are its numbers for a typical setup; your data, volumes and edge cases move them.

Typical effort

76 hours

About 10 working days of engineering

Catalog group

ERP

Open-source ERP for accounting, inventory, CRM, HR, projects, manufacturing, and custom workflows.

Used in

1 project type

The complete guide

ERPNext integration: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

Connecting ERPNext means talking to the Frappe framework underneath it. Every business record is a DocType with an automatic REST endpoint, so a web store, app, or reporting tool can create and read orders, items, and invoices using a token. The real planning questions are your custom DocTypes, document states, and where the site is hosted.

Why connect ERPNext to anything else?

ERPNext is an open-source ERP with modules for accounting, stock, selling, buying, manufacturing, HR, and projects. Companies that run on it still have outside tools: a storefront, a field app, a customer portal, a BI dashboard. An integration removes the re-keying between them.

  • Turn a storefront checkout into a Sales Order and Customer record.
  • Publish Item prices and warehouse quantities to a website.
  • Capture web-form enquiries as Leads.
  • Post payments received elsewhere as Payment Entries.
  • Let a partner system react the moment an invoice is submitted.
  • Feed accounting and stock data into a warehouse for analysis.

What does the Frappe API look like?

Frappe generates a REST resource for each DocType, so listing, reading, creating, updating, and deleting records follows one predictable pattern. For logic that is not plain CRUD, a whitelisted Python method in a Frappe app can be called as its own endpoint.

For service-to-service calls, an API key and secret are generated on a user and sent in the Authorization header as a token. Frappe also supports OAuth 2.0 for apps acting for people, and session cookies for browser use. Whichever you pick, the user's roles and permission rules decide what succeeds, so a narrow service user is the sensible default.

Outbound events come from the Webhook DocType: you choose a DocType, an event, and a URL, and Frappe posts JSON when it fires. Frappe's documentation for your release has the current paths and options. For the wider idea, see system integration.

Why do document states matter so much?

Many ERPNext documents move from draft to submitted, and from submitted to cancelled or amended. A submitted invoice is part of the ledger and cannot simply be overwritten. An integration that treats every record as freely editable will hit validation errors.

Decide per document type which side creates drafts, who submits, and what a correction looks like. Often the answer is a cancel-and-amend path rather than an edit, and the integration has to know it.

Which records travel, and who is the source of truth?

Common ERPNext integration flows
RecordTypical ownerPath
Sales OrderStorefront or app createsInto ERPNext on checkout
Item and Item PriceERPNextOut to the website
Bin quantities per warehouseERPNextOut, polled or pushed
Customer and LeadWhichever captured it firstInto ERPNext, deduplicated
Sales Invoice statusERPNextOut through a webhook
Payment EntryPayment systemInto ERPNext, linked to the invoice

What changes the scope of an ERPNext integration?

A stock ERPNext site is simple to reach. The typical effort shown above rises with local changes.

  • Custom DocTypes and fields, plus client or server scripts that run on save.
  • Workflows that gate which users may move a document to the next state.
  • More than one company, warehouse, price list, or currency.
  • Item variants, batches, serial numbers, and units of measure.
  • Hosting on Frappe Cloud, a managed provider, or your own bench, which changes access and upgrade routines.
  • Whether a custom Frappe app is justified for logic that belongs inside the ERP.

For typical ranges across ERP and CRM work, see the CRM and ERP cost guide.

Where do ERPNext integrations usually break?

  • A write is refused because the target document is already submitted.
  • The service user holds the System Manager role because it was quick, which is far too broad.
  • A webhook fires on a change the integration itself made, and the two systems echo forever.
  • Item codes differ between the store and ERPNext, so lines fail to match.
  • A scheduled upgrade renames fields or alters validation, and nobody retests.
  • Thousands of single requests where a filtered list call would do.

When is a connector enough?

Zapier and Make can call a Frappe REST endpoint through an HTTP step. That is fine for notifying a channel when a Lead appears.

Deciding between a connector and code
SignalLean toward a connectorLean toward code
Only standard DocTypesYesNot required
Orders with taxes and multiple warehousesGets awkwardYes
Custom DocTypes with required child tablesHard to mapYes
Needs replay after an outageRarelyQueue with retries
Logic must run inside ERPNextNoA Frappe app

See iPaaS for the trade-offs in general.

What does a careful launch involve?

  1. Stand up a staging site cloned from production data that has been scrubbed.
  2. Create the integration user, give it the minimum roles, and generate its key and secret.
  3. Map Items, units, tax templates, and custom fields in both directions.
  4. Try a submitted document, a cancelled one, a duplicate, and an expired key.
  5. Reconcile a trial backfill with the finance team.
  6. Upgrade staging and rerun every flow.
  7. Go live with one flow, watch the logs, and keep a way back.

How does StackLift plan this work?

StackLift treats ERPNext as a system we integrate with, not a partner relationship. A senior architect reviews your DocTypes, workflows, and hosting before the scope becomes a commitment. Start with the free estimate and add ERPNext as a feature.

Engineers and agents work on feature branches, with no production secrets in agent hands. The delivery plan carries CI/CD, observability, and rollback from sprint one.

Questions people ask

How do I authenticate to the ERPNext API?

Generate an API key and secret for a dedicated user and send them as a token in the Authorization header. OAuth 2.0 is available when an app acts on behalf of people.

Can ERPNext notify my other systems?

Yes. A Webhook record posts JSON to a URL you choose when a document event happens.

Do I need to write a Frappe app?

Not for ordinary record work. Write one when logic should run inside ERPNext or you need an endpoint the standard API does not offer.

Is ERPNext or Odoo easier to integrate?

Both are workable. The honest difference is in your own customizations and hosting, so read the Odoo page and judge by your data.

How long does an ERPNext integration take?

Most first versions take 6 to 16 weeks depending on scope. A 3-day Scope Sprint gives you a detailed plan first.

Sources

Official ERPNext documentation

The vendor's own reference for the APIs, limits and authentication this guide describes. Check it for the current version before you build.