Custom ERP Software Development: What Should You Build, Extend or Integrate?

A distributor may have reliable accounting software but still confirm orders by email. A manufacturer may track production in one system and stock in another. Neither situation automatically calls for a new ERP. Before choosing software, identify the transactions that are breaking down, the records that must remain authoritative, and the work a replacement would create. This guide walks through those decisions.

When is custom ERP development worth considering?

Start by checking what the existing ERP can already do. Standard purchasing, accounting and inventory workflows may be well served by a configured product. Rebuilding those features introduces work without necessarily improving the operation.

Custom engineering becomes worth discussing when important rules cannot be handled reliably through configuration. Think of production sequences tied to unusual material constraints, approval chains spanning several companies, or dealer prices calculated under contract-specific rules.

That does not always mean replacing the ERP. A smaller application can handle the exceptional workflow while the established system retains accounting and stock records. Compare configuration, an extension and full replacement against the same operational examples. A claim that one will be cheaper or safer needs evidence from your own environment.

What to verify

  • Identify the workflow that standard configuration cannot support
  • Confirm which installed ERP modules have already been evaluated
  • Compare the migration and maintenance obligations of all three approaches

Choose ERP modules by following a real transaction

Take an actual purchase or sales order and follow it through the company. In manufacturing, it may touch a bill of materials, raw-material stock, work orders and finished-goods availability. In distribution, the same exercise may expose warehouse allocation, negotiated prices, credit approval and returns.

For every step, record who enters information, who can approve it and which application stores the accepted result. Only then decide whether inventory, purchasing, production, sales, reporting or finance integrations belong in the first release.

A report that reads stock has a different risk profile from a service that changes stock. Keep that distinction visible in both the architecture and the access rules.

What to verify

  • Trace one purchase-to-pay and one order-to-cash transaction
  • Name the authoritative owner of products, customers, stock and finance records
  • List the modules deliberately excluded from the first release

ERP integrations need rules for errors, not just working APIs

Imagine a dealer places an order and the connection drops before the portal receives confirmation. Did the ERP accept the order? Retrying without checking could create a duplicate. The interface needs a clear distinction between request received, ERP accepted and order confirmed.

Define who owns each piece of data, which direction it travels and how quickly it must update. For write operations, test authentication, tenant permissions, timeouts, duplicate requests and reconciliation. Durable queues and idempotency keys may be appropriate, but the design depends on the ERP interface and business requirements.

A familiar vendor name does not establish compatibility. SAP, Logo and Mikro products differ by version, modules, licensing and available APIs. Ask for documentation and authorized test access before promising any connector or integration timeline.

What to verify

  • Document each permitted read and write operation
  • Agree on acceptable delays and the handling of uncertain order outcomes
  • Prove a small integration against the exact ERP edition in a sandbox

Where does a B2B dealer portal fit?

Dealers need to find products, see the prices agreed for their accounts and understand when an order has actually been accepted. Those are customer-facing tasks. They do not require every ERP function to be exposed through the portal.

The ERP might own the contract price, available stock, customer credit and final order number. The portal can handle product discovery and order requests while a controlled integration enforces those boundaries. The details matter: reserved stock is not always saleable stock, and an order request is not an invoice.

Our ERP-integrated B2B dealer portal guide covers those boundaries in more depth, including branch permissions, price consistency and recovery when an ERP does not respond.

What to verify

  • Follow a dealer order from submission to ERP confirmation
  • Test an account-specific price and a cross-account access attempt
  • Assign responsibility for stock mismatches and delayed acknowledgements

Decide who can see, change and approve each record

A branch buyer, finance approver and system administrator should not share the same privileges. Access rules may also depend on the dealer account, warehouse or legal entity. Changing an API identifier must never expose another account's orders or prices.

Document authorization checks, approval limits, audit events, backup recovery and data retention. Verify that they work in the deployed environment, including failed and retried transactions. A demonstration or a handful of automated checks is useful evidence for a feature, not a security certification.

What to verify

  • Test roles, branches and dealer-account isolation
  • Assign owners to audits, backups, retention and privileged access
  • Include incident handling and updates in the support agreement

How to estimate custom ERP software development costs

An ERP quote without a scope tells you little. A two-module extension on documented APIs and a multi-company ERP replacement with historical data migration are different projects, even if both are called custom ERP development.

Ask suppliers to identify the work behind their figures: discovery, modules, licensing, integrations, data cleanup, testing, training, support and eventual migration away from the system. Compare these over the same period and against the same acceptance criteria.

Keep assumptions visible. An untested connector or undocumented data model can change the estimate substantially. Until those dependencies have been checked, a single fixed price would be misleading.

What to verify

  • Set one scope and time horizon for competing options
  • Request assumptions, exclusions and named acceptance criteria
  • Include support, software changes and exit costs

A delivery sequence that tests the risky parts first

Begin with sample orders, inventory movements, approval exceptions and interface documentation. Walk through them with the people who will use and maintain the system. The first output should be a process map and a list of unanswered technical questions.

Next, test a narrow but important path end to end. For example: retrieve a dealer price, submit an order, receive ERP confirmation and recover from a timeout. This reveals more about feasibility than a polished dashboard demo.

Only then plan migration and rollout. Reconcile a small data set, confirm access controls, prepare training and test rollback before expanding to additional modules. Mihenk can scope this work with you, but schedule and commercial terms depend on the systems and responsibilities identified during discovery.

What to verify

  • Define one critical transaction and its acceptance tests
  • Name the business and technical owners of the rollout
  • Rehearse reconciliation and rollback before changing production workflows

Questions before procurement

Should we build a custom ERP or buy an existing ERP?

Evaluate existing products and configuration first. If a specific workflow still cannot be supported reliably, compare a focused extension with full replacement. Use representative transactions and lifecycle costs rather than a feature-count comparison.

Can a custom ERP connect to an existing B2B dealer portal?

It can when the systems provide suitable authorized interfaces. First establish who owns prices, stock, customer credit and confirmed orders, then test permissions, retries and reconciliation.

What affects custom ERP software development cost?

Module complexity, integration access, data quality, migration, approval rules, testing and support all affect the work. A useful estimate starts with a bounded scope and checked technical assumptions.

Can ERP integrations work with SAP, Logo or Mikro?

That depends on the specific product, version, enabled modules, licensing and available interfaces. We do not claim a universal or certified connector based on a vendor name.

How long does a custom ERP project take?

There is no dependable timeline without discovery. Estimate process analysis, integration proof, data migration and user acceptance separately, then agree on rollout phases.