← All insights

ERPNext vs Business Central: which fits your wholesale and manufacturing work?

Compare the working order, not just the licence. The deciding details are assembly versus production, Microsoft-facing work, support ownership and what happens when a connection fails.

  1. 01Fit
  2. 02Prove
  3. 03Cost
  4. 04Migrate
  5. 05Support
Short answer

Choose ERPNext when open-source control and broad staff access without a product-owner per-user fee fit your business, with funded implementation and maintenance. Choose Business Central when its Microsoft-facing workflows and proposed partner package justify user licensing. For light manufacturing, separate simple assembly from production routing before choosing Essentials or Premium. Neither platform is automatically cheaper overall. Compare the same order, local finance requirements, integrations and ongoing support before signing.

Will the new ERP stop your team chasing orders in spreadsheets—or leave you paying for software while still doing the same work? For a wholesaler that also assembles or manufactures products, the answer depends on how sales, stock, production and finance handle the same difficult order. Microsoft 365 familiarity matters, but it cannot settle that decision on its own.

When is ERPNext or Business Central the better fit?

This comparison is about Microsoft Dynamics 365 Business Central, not Dynamics 365 Finance or Supply Chain Management. ERP means enterprise resource planning: the software connecting orders, purchasing, stock, production and accounts. The reader here is an owner, operations lead or finance manager replacing disconnected tools in a wholesale business with some manufacturing—not selecting a large enterprise group’s entire application estate.

Shortlist ERPNext if control over the application and access for a wider operating team matter, and you can appoint an accountable implementation and support team. Frappe describes ERPNext as free, GPL-3.0 open-source software, with managed hosting or self-hosting options and implementation separately arranged. Open source gives you choices; it does not clean your item list, design your controls or maintain custom work for you.

Shortlist Business Central if its supported Microsoft-facing work removes daily effort and a credible partner can deliver your operating requirements within budget. For example, Microsoft documents an Outlook add-in for viewing customer or vendor financial information and creating documents such as quotes and invoices. That is a specific workflow to test, not a promise that every application bearing a Microsoft name is already connected.

ERPNext is a poor fit if the purchase depends on “free software” but nobody has budget or responsibility for configuration, backups, upgrades and user support. Business Central is a poor fit if essential operating roles cannot be licensed affordably, or the proposal needs extensive extra apps and development to reproduce your main process. Neither should proceed while a required local finance output or production control remains unproved.

What should you compare on the same basis?

Ask each supplier to label every requirement as standard setup, paid app, custom work or unresolved. Name the proposed version, hosting arrangement, edition and country setup. A demonstration that quietly adds a paid extension is not evidence that the base product covers the requirement.

ERPNext and Business Central: documented boundaries and the buyer proof they require
CriterionERPNextBusiness CentralWhat you must prove
Product and recurring chargesFree open-source ERP; hosting and implementation are separate. Frappe Cloud describes resource-based rather than per-user charging.Essentials and Premium are user-based plans; Team Members provides limited rights, not a replacement for every operating user.A role-by-role access and cost schedule, plus apps, capacity, support and implementation exclusions.
Wholesale order to accountsSales Orders connect onward to delivery and invoicing; the actual settings and controls still need design.Core functions include sales, purchasing, inventory and financial reporting.Customer terms, units, partial deliveries, open quantities, credits and period-close reports using your own sample records.
Assembly and manufacturingBills of materials can include operations; Work Orders and Job Cards support production recording.Assembly management is distinct from manufacturing; Premium adds manufacturing and service management.Simple kit assembly versus routed production, component shortages, labour recording, output and costing in the quoted entitlement.
Microsoft-facing sales workSpecify the email or document workflow you need and have the supplier demonstrate its proposed setup; do not assume parity with a Business Central add-in.The documented Outlook add-in has deployment and Microsoft 365 prerequisites and connects to one Business Central environment at a time.A salesperson performs the task with your account, permissions and environment; the resulting ERP record is correct.
External systems and added fieldsThe Frappe REST API exposes document operations; a usable connection still requires mapping and controls.Microsoft provides REST APIs. Adding fields to existing standard APIs is not supported; a custom API may be required.Your required fields can cross the boundary, failed requests are visible and repeat attempts do not create duplicates.
Local finance and supportAgree the country-specific setup, any extra apps and the partner’s responsibilities. Frappe’s Product Warranty excludes functional support.Local functionality may be Microsoft-led or partner-led; identify what your country and apps actually provide.Finance approves required outputs; a named service owner covers daily questions, defects, connections and update testing.

This is not a score awarding one point for every feature name. A missing control that prevents incorrect shipments can outweigh several convenient screens. For US or UK operations, have your finance reviewer approve the actual tax, invoice, banking and reporting requirements for each entity. A country being supported is not proof of your entire accounting process.

Does light manufacturing require Business Central Premium?

Not every activity called manufacturing is the same requirement. Combining bought components into a sellable kit may be assembly. Tracking a sequence of operations, production time and output may require manufacturing. Microsoft’s assembly documentation explicitly describes supplying combined components without using manufacturing features, including assembly linked to sales demand. Do not assume that every kit requires the manufacturing workflow—or that assembly covers a routed factory process.

Microsoft identifies manufacturing as a Premium capability. Its production-order documentation covers materials, routing and production recording. Ask the supplier to demonstrate your process in the exact quoted Essentials or Premium setup, showing where each required screen and posting is entitled. A feature visible in a trial is not enough.

Do not budget Premium only for the planner and assume all other full users in that company can remain on Essentials. Microsoft states that Essentials users cannot sign into a company using the Premium experience. Have the partner confirm the current licensing arrangement for every role, including limited-access users. Changing the experience setting does not assign a licence.

ERPNext’s BOM—bill of materials, the component recipe—can include operations, and its Work Order records materials and production work. That avoids this Essentials/Premium manufacturing decision, not the work of validating your production method. Prove the required scheduling, stock movement, labour and cost results rather than treating “manufacturing included” as acceptance.

How would both systems handle the same difficult order?

Consider an illustrative wholesaler selling stocked parts and assembled service kits through a trade portal. Staff use Microsoft 365. One customer orders kits, but a component shortage means only part of the order can ship. A kit may need simple packing, or it may need a separately tracked assembly-and-test operation. That distinction changes the evaluation. This is a constructed buying scenario, not a reported client project or hands-on product test.

One order, shared responsibilities: use this script in both demonstrations
Business eventOwner and recordRequired resultFailure to expose
Portal sends an approved customer order.Sales owns order acceptance; ERP holds the accepted order with portal reference, customer, item, unit, price and requested date.Correct customer terms and one accepted ERP order; rejected items remain visible for correction.A timeout creates another order, or portal prices overwrite an agreed ERP rule.
A component is short.Planner owns the assembly or production record and shortage decision; purchasing owns the replenishment order.A credible remaining quantity and date; the shortage is not hidden by a complete-looking sales header.The demonstration assumes components are available or silently substitutes a different item.
The available kits are completed.Warehouse records consumption and finished stock; production lead records operations if required.Component use, output and agreed labour/cost records reconcile. Both suppliers explain their chosen assembly or production route.Simple assembly is shown despite a requirement to track separate operations and actual work.
Only the ready quantity ships.Warehouse owns dispatch evidence; finance owns invoicing; portal receives ERP-owned fulfilment status.Delivered, invoiced and still-open quantities remain distinct. The customer is not told the whole order shipped.A header status conceals the backorder, or invoice posting is treated as proof of dispatch.
A shipped kit comes back damaged.Warehouse owns return receipt and disposition; finance approves the credit and any refund.Returned goods are assessed before resale; a credit note and cash refund are separately traceable.Raising a credit automatically makes damaged stock sellable or marks a refund paid without payment evidence.

Let the finance manager follow that order into stock value, customer balance and margin. Let the planner change the component availability. Let sales answer the customer without asking someone to rebuild a spreadsheet. The useful comparison is how much work remains and which controls survive—not how quickly a presenter clicks through the happy path.

Is ERPNext cheaper once implementation and support are included?

It can be, particularly when broader staff access matters, but the licence difference cannot settle the total. Compare one agreed planning period, such as three years, with the same entities, warehouses, production scope, roles, integrations and service hours. Use supplier quotes rather than multiplying a headline rate by everyone in the company or treating missing figures as zero.

Cost worksheet: ask each supplier for an amount, inclusion boundary and accountable owner
Cost lineERPNext questionBusiness Central question
Software and capacityWhich host and capacity support peak work, test environments, backups and required custom apps? What does the plan exclude?Which user rights does each role require? Essentials or Premium company scope? Which app, capacity or other subscription charges remain?
ImplementationWho prices configuration, clean data, manufacturing setup, reports, finance checks and role-based training?Who prices those same deliverables, including apps and entitlement-specific setup rather than only standard installation?
Connections and changesWhich integrations or custom apps require a build, monitoring, maintenance and version testing?Which connections are supported as quoted? Do custom fields require another API or extension? Who maintains each app?
Ongoing operationWho answers user questions, restores backups, handles product bugs and tests host/framework/app updates?What does the partner support agreement cover, and who tests ERP, extensions and connected workflows after updates?
Your team and exitWho can take over settings, code, hosting access and exports? Budget staff time for data ownership and handover.What data, app configuration, documentation and contractual access can a replacement partner obtain? Budget the same internal responsibilities.

Microsoft’s published plans are user-based and distinguish limited Team Members rights from Essentials and Premium. Prices depend on market and purchase terms; ask for a current local quote. Frappe’s pricing explanation separates hosting from implementation and distinguishes product bug support from functional help. Neither source is an all-in price for your business.

Run a second cost case with the user mix or manufacturing scope you expect next, not just today’s minimum. Ask what changes if simple kits become routed production, another warehouse goes live or more staff need posting rights. The ERP implementation quote-comparison guide provides a fuller way to expose scope and change charges.

What would migration and integration actually involve?

Start with ownership, not a connector purchase. The customer account, item code, unit, warehouse and accepted order need stable identities. Decide whether the portal proposes a price or the ERP recalculates it; whether finance must approve a new account; and which system may change an accepted order. Do not let two systems independently edit the same financial rule.

A practical connection design to ask either implementation team to explain
Record or updateOwner and triggerTechnical route to scopeRecovery and duplicate control
Customer and item mappingFinance approves customer terms; operations owns item/unit/location mapping before orders are accepted.Keep a controlled cross-reference between source IDs and ERP IDs; reject unmapped values.Do not match by name alone. Route an unknown customer or unit to a named owner without creating guessed records.
Accepted orderSales owns acceptance when the portal submits a confirmed order.Validate required fields and send through the agreed API with source order and line references; record the ERP response.Reserve a unique source-order key before creation. After a timeout, check for the existing ERP order before retrying; prevent two workers creating it together.
Order changes and fulfilmentSales approves changes; warehouse confirms dispatch; the ERP sends line quantities and references outward.Use a monitored queue of pending updates, including source reference, last attempt and result; agree polling or event triggers and acceptable delay.Check record version or update sequence so an old message cannot undo a later change. Retry the failed update against the existing order, not a replacement order.
Credits, payments and reconciliationFinance owns posting and the daily comparison of ERP records with channel records.Map invoice, credit and payment references separately; reconcile totals and unresolved exceptions.A repeat credit or payment reference is investigated, not posted again. Flag missing records even when no technical error was reported.

These are implementation requirements, not promises that either product’s default API supplies a complete duplicate-prevention service. Frappe documents REST document operations and authenticated access. Microsoft documents Business Central APIs, including the limit on adding fields to standard APIs. Have the technical lead prove required fields, permissions, status transitions and recovery on the proposed versions. Keep credentials outside code and give the connection only the access it needs.

For migration, load approved masters first: accounts, customers, suppliers, items, units, warehouses and BOMs. Then load agreed opening records, outstanding receivables/payables, stock and open orders using the appropriate supported route for each record. Finance signs off balances and stock value; operations signs off quantities, BOMs and open-order lines. Keep selected history read-only if rebuilding it would add cost without a business need.

ERPNext’s Data Import distinguishes new records from updates and uses existing IDs for updates. Retain those IDs when correcting an import. Business Central’s configuration packages support initial company setup; Microsoft warns they are not intended for companies already in production. Neither is a reason to upload everything directly into live trading. Rehearse imports and opening-balance posting in a test company, preserve error logs and reconcile against signed source reports.

If this implementation is part of a wider commerce connection, the systems integration service describes that work. A quoted connector must still prove your order, return and recovery paths; its product name is not a completed design.

What should each supplier prove before you choose?

Provide the same masked sample records to both teams, and have your staff perform the work. Mark each result Pass, Unresolved or Fail. Attach the record reference, proposed edition/app and owner of any fix. Do not average away a failed essential control with a better-looking dashboard.

Buyer demonstration checklist: require evidence, not a promised feature
TestPass evidenceDecision owner
Handle the complete illustrative order and shortage.One order, correct remaining quantities and traceable purchasing or production; correct consumption, output and costs.Operations and production lead.
Prove assembly versus manufacturing entitlement.Required operations run in the quoted setup; all affected users have an agreed lawful access plan.Sponsor and supplier licensing lead.
Have sales work from an Outlook email.Proposed workflow produces the right customer/document with approved access, without a presenter doing hidden rekeying.Sales lead and Microsoft 365 administrator.
Repeat an order request after a simulated lost response.Only one accepted order, visible attempt history and a safe recovery procedure.Integration owner.
Part-ship, return damaged goods and issue a credit.Stock disposition, open quantity, invoice/credit and any cash refund remain separately explainable.Warehouse and finance.
Import, correct and reconcile opening records.No duplicate accounts/items; signed balances, stock value and open documents agree with the source.Finance and data owners.
Refuse an unauthorised release and test a relevant update.The control applies to screen and connected orders; the team can rerun and record the same checks after changes.Control owner and support lead.

If a must-have result is Unresolved, buy a bounded proof exercise before a full implementation—not an assurance that it can be customized later. The ERP testing guide for manufacturers expands this into end-to-end acceptance rather than a sales demonstration.

How should you control go-live, rollback and support?

Implementation gates: move forward on accepted evidence, not an assumed timetable
  1. 01
    Agree the operating scope

    Sponsor and finance sign the entities, roles, production route, required outputs, cost boundaries and acceptance cases. Name the people providing data and decisions.

  2. 02
    Accept a working prototype

    Operations, sales and finance run the difficult order in the proposed edition, with each app and custom change identified. Close essential gaps before scaling setup.

  3. 03
    Rehearse data and connections

    Data owners approve mappings and reconciled opening reports. Integration owner proves duplicates, missing records and failed-update recovery in an isolated test environment.

  4. 04
    Approve cutover or stop

    Sponsor checks training, signed balances, access, recovery rehearsal and support cover. Freeze legacy edits at an agreed time; capture the final changes, load them and reconcile before enabling order traffic.

  5. 05
    Stabilise with named support

    Team leads review daily orders, stock, invoices and connection exceptions. One incident lead coordinates ERP, host, app and connector suppliers; agree service hours, escalation and return-to-normal authority.

Write the rollback decision before cutover. If opening records fail reconciliation before trading starts, stop and return to the agreed legacy process. Once real orders, shipments or payments have occurred, restoring an old database can erase valid work. Pause affected connections, preserve the transaction and message logs, reconcile what happened, and have finance and operations approve recovery or controlled correction. A backup is not a complete business rollback plan.

Require a handover containing record mappings, settings, code or package locations and agreed access, restore instructions, daily exception checks, test cases and supplier contacts. Separate user help, product defects, custom-code defects and update work in the support contract. For ERPNext, distinguish host and product warranty from functional support. For Business Central, distinguish the Microsoft service from the partner’s obligations and each app publisher’s support.

How do you make the final choice without buying the wrong scope?

Choose the proposal that passes the essential work with acceptable staff effort, a funded ownership model and fewer unresolved dependencies. ERPNext earns its place when open-source control, operational access and the proposed team fit together. Business Central earns its place when the proven Microsoft-facing workflow, correct entitlement and partner-delivered operating model justify their combined cost. Neither wins because of its licence label alone.

Bring one difficult customer order, a BOM or assembly recipe, a finance report and a list of connected systems to your next supplier conversation. Ask for a written fit-and-gap decision before a full build. Harmatiq’s ERPNext implementation and integration service and ERP and manufacturing discovery cover that operating work. If the required proof points favour Business Central, let that evidence lead the selection rather than forcing ERPNext into the scope.

Find the handoff that needs fixing.

Bring one real order, the systems it crosses and the exceptions your team handles manually. We can turn that journey into an implementation scope.

Discuss your workflow