How do you plan an ERP integration? A guide for portals and operations software

A dealer portal or operations application reads product, price, and stock information from the ERP and sends orders back to it. This article explains step by step how to plan ERP integration before writing code: master data ownership, method selection, error handling, testing, and go-live.

What is ERP integration, and how does it differ from ERP implementation?

ERP integration is a connection that enables data to flow between a company's ERP and another application in a controlled, traceable way that withstands interruptions. This article addresses the following situation: the ERP continues to handle accounting, stock, and invoicing; a dealer portal, field app, or operations screen is added alongside it, and the new software must reflect the same reality as the ERP.

ERP implementation or migration is a different project: selecting, customizing, and deploying the ERP itself. This is usually handled by the ERP vendor or implementation partner. In integration, the ERP remains in place; the connection to it is designed.

A note before you start: if you use an off-the-shelf e-commerce platform or your ERP's own B2B module meets your needs, first assess the vendor's existing connector; it is often faster and cheaper. Custom integration makes sense when the process is nonstandard, several systems need connecting, or the ready-made connector's rules do not fit your work. We discuss the features expected of the portal itself in our article What is a B2B portal?

Before starting: inventory and owners

The plan starts with an inventory. Which ERP and version are in use; does it run on-premises or in the cloud? What other systems are already connected to the ERP: an authorized service provider for e-Invoice, a bank, warehouse software, or an e-commerce site? Even two companies using the same product, such as Logo, Mikro, or SAP, may have different integration options because of versions, licenses, and years of customization. A product name alone is not enough; what is possible in your installation must be verified.

The second question concerns people: who is responsible for the ERP? The internal IT team or the partner that implemented it? If no one is identified to create the service account, prepare the test environment, and explain field meanings, the integration timeline is not under your control.

Questions for the ERP owner

  • Which product and version are in use; is an upgrade planned soon?
  • Does the ERP provide web services or an API; does this require an additional license or module?
  • Is there a separate test environment with realistic data?
  • Are price, discount, and promotion rules calculated in the ERP or elsewhere?
  • When are maintenance windows, overnight jobs, and month-end close?
  • Who creates the integration account; who responds to change requests, and within what timeframe?

Master record ownership: where is each type of data created?

The heart of the plan is assigning a single authoritative source for each data type: there must be one answer to “which value is correct?” for prices, stock, account limits, or order status. A field editable in both systems will eventually contain two different values.

The table below is an example scenario; it is not a real customer implementation or a list of features available in every ERP. Master record, transfer direction, update conditions, and error ownership are defined together. The order request originates in the portal; the ERP holds the finalized order record.

Example scenario: data ownership and transfer plan for a dealer portal
Data Master system and direction Update Error and owner
Product, unit, VAT rate ERP master record; ERP → portal Change notification or scheduled bulk transfer The latest catalog is shown; the product owner corrects unmatched codes.
Price and discount ERP master record; ERP → portal On change; rechecked at basket confirmation If the price cannot be verified, no finalized order is created; the sales owner reviews the request.
Stock ERP master record; ERP → portal An acceptable data age is defined; reservations are verified separately The update time is visible. Outdated stock is not used to promise delivery; the warehouse owner investigates discrepancies.
Customer and delivery address ERP master record; portal → change request → ERP → portal When an authorized person approves the change The existing record is not overwritten; the customer-record owner decides on the request.
Account, credit limit, balance ERP master record; ERP → portal Scheduled refresh; current limit checked when ordering If the check receives no response, the request waits; an authorized finance owner assesses limit exceptions.
Order Draft in the portal; finalized record in the ERP. Portal → ERP → status response When the request is accepted; the same business identifier is retained If the response is lost, status is queried. If a retry is unsafe, no new record is created; the integration owner reconciles the transaction.
e-Invoice, e-Dispatch Note ERP / service provider master record; document and status → portal When the document is created or its status changes A missing document is not presented as finalized; accounting or the service-provider owner follows it up.
Dealer users and roles Portal master record; no user copy required in ERP When an authorized administrator makes a change Actions with unverified permissions do not run; the portal administrator reviews access.

e-Invoice and e-Dispatch Note require particular care: these statutory documents are issued using one of the methods defined by the Turkish Revenue Administration—direct integration, an authorized service provider, or the GİB portal. For the document type in scope, check GİB's current methods and technical guides (checked: 11 October 2026). If the portal does not need to generate the document, it reads the document number, ETTN, and status from the ERP or service provider and presents the document image to the dealer.

Real-time or periodic?

Not every type of data needs to flow in real time. The test is: what decision will be wrong if this data is stale? A product description updated a day late may cause no harm; stock that is several hours old for a fast-moving product can lead to unfulfillable orders. Connecting every screen to a real-time ERP query also carries risk: if the ERP slows down or stops, the portal is affected. A good balance is often to copy data into the portal periodically and query the ERP only at critical moments, such as checking price and credit limit when confirming the basket.

The roles in the table are examples; assign each to a person or role owner in your organization. The person monitoring technical transfers need not be the person who decides on price, limit, or address changes. Choose update intervals according to the business risk of stale data, rather than by guesswork.

Master data cleanup and mapping

The biggest integration surprises often come from the data itself: products defined twice under old and new codes, items tracked individually in the ERP but sold by the case without a unit conversion, or multiple account records for branches of the same dealer. These mappings should not remain hidden rules inside integration code; keep them in separate mapping tables and assign an owner to each table.

Integration methods: which one, when?

The method depends on what your ERP installation offers and the nature of the data; several methods may be used together in one project.

MethodWhen is it suitable?Points to consider
ERP services / APIWhen the ERP version provides web services; usually the first choiceAdditional licenses and request limits may apply; services may change during upgrades
Middleware and queue (middleware, iPaaS)When connecting several systems or when the ERP is slow or intermittently unavailableAdditional components and operating costs; a monitoring owner must be identified
Database view (read-only)When no service exists and data only needs to be readTable structures may change during upgrades; may be outside vendor support
File transfer, EDIFor bulk and periodic data; when the other party accepts only filesLatency, agreement on file format, incomplete files
Event-based (webhook, message)When the ERP can send notifications as records changePeriodic reconciliation is essential for missed notifications

Writing directly to the ERP database may look like a shortcut, but it bypasses the ERP's rules for stock deductions, account balances, and document numbering. Always write orders using the ERP's own service or import method. If the ERP is old and offers no services, a small service layer may first need to be placed in front of it; this can also be planned as the first step in a software modernization initiative.

The path of an order through the ERP and dealer portal

A hypothetical example: a dealer presses Send twice for the same order; the ERP creates the first record, but the response is lost in transit. If the portal reports an error and resubmits with a new number, two orders may be created. An on-screen error does not prove that the operation never happened in the other system.

  1. Draft and validation. Dealer permissions, price validity, stock, and credit limit are checked. If stale data allows only a request to be captured, this is stated clearly; no claim is made that stock is reserved or a price is final.
  2. One business identifier. A persistent identifier is assigned to the order and retained across all attempts for the same submission. Storing the identifier in the ERP is not enough by itself: record creation and duplicate checking must be tested for safe operation together.
  3. When the outcome is uncertain. The transaction is separated out as “status being verified.” Depending on the ERP's query and retry-safety capabilities, status is looked up using the same identifier. If a safe outcome cannot be established, an owner must review it rather than creating another order.
  4. Confirmation and reconciliation. The ERP number and final status return to the portal. Pending and rejected transactions are listed separately; line items, quantities, and amounts are compared as well as order counts.

A portal showing its catalog while the ERP is down is not the same issue as a phone app operating without internet. Define the offline mobile app scope separately to determine which records remain on field devices and how conflicts are resolved. The technical approach that limits the side effects of retries is explained in the AWS Builders’ Library guide to retry safety (checked: 13 October 2026).

Updating an existing order also requires a separate control. For example, the Business Central order update API does not apply an update if the submitted version tag does not match the current record. This prevents overwriting concurrent changes; it does not replace the control that prevents duplicate creation of a new order. Verify the equivalent of both controls in your ERP (checked: 13 October 2026).

Errors, monitoring, and security

The real test of an integration comes when the ERP is under maintenance, a connection drops, or a record is rejected. The plan must address:

  • Queue. When the ERP is unavailable, show the dealer “received, awaiting transfer” only after the request has been successfully written to a durable queue. If queue writing also fails, do not acknowledge acceptance. Final ERP order confirmation is tracked separately.
  • Retries. For transient errors, transfer is retried at increasing intervals, with limits on both attempts and total elapsed time. Once the limit is reached, the record goes for human review; no continuously running loop is created. Permanent errors, such as a closed account, are not retried indefinitely; they enter someone's work queue.
  • Duplicate prevention. Test concurrent and delayed attempts using the same business identifier. If the ERP or middleware cannot guarantee this control, uncertain transactions are not automatically recreated; use reconciliation and authorized review.
  • Monitoring and alerts. Monitor the number of queued records and the age of the oldest one; send an alert to a named person when a threshold is exceeded.
  • Reconciliation. Compare portal and ERP orders at an agreed frequency by identifier, status, line item, quantity, and amount. Identical totals can conceal different record-level errors; unexplained differences go to the business owner.

For security, create a separate integration service account with only the required permissions; do not use an employee's ERP password. Do not expose an on-premises ERP to the internet; establish the connection through a VPN, IP restriction, or middleware that connects outward from inside. Log each request without unnecessary personal data. For KVKK purposes, document which personal data is copied into which system and do not transfer fields that are not needed; account records for sole-trader dealers may contain a name and Turkish ID number.

Testing, go-live, and rollback plan

A flow that works perfectly on sample records may fail when faced with real pricing conditions and exceptions accumulated over the years. Test using an up-to-date copy in the ERP test environment with personal data masked; list edge cases in advance: zero-stock products, accounts above their credit limits, expired promotions, products sold in multiple units, an ERP restart during transfer, duplicate order submissions, and addresses containing Turkish characters (İ, ş, ğ).

When choosing a cutover window, avoid month-end close, billing periods, and promotion launches. First load the master data and compare it against the ERP; then start with a small pilot dealer group, keeping phone and email channels available during this period.

Go-live checklist

  • The master record ownership and mapping tables have been approved.
  • Edge cases have been tried in the test environment using realistic data.
  • Queues, retries, and alerts have been tested; the alert recipient is known.
  • The initial load is complete and its results have been compared against the ERP.
  • The cutover window has been chosen together with the ERP owner.
  • The pilot group and channels to remain open during transition have been defined.
  • The rollback plan is documented: under what conditions and whose decision will you revert, and how will pending portal orders be transferred to the ERP?

Do two ERP integration quotes cover the same delivery?

Before comparing quotes, align the data flow and acceptance evidence. “Stock and order integration” does not specify which warehouse will be read, who will investigate uncertain orders, or who will maintain the integration when the ERP version changes. Ask both providers to explain the deliverable using the same sample records.

Example evaluation: the same questions and acceptance evidence for two quotes
Topic to clarify in the quoteEvidence to request from both quotesIf excluded from scope
SKU, warehouse, and sales unitApproved mapping list; expected outcomes for units/cases and missing SKUsThe person preparing mappings and the error-correction work are planned separately.
Order with a lost responseComparison of the ERP record and status using the same business identifier after a controlled interruptionDocument the owner and time required for manual review of uncertain records; do not assume automatic retries are safe.
Initial transfer and reconciliationTrial transfer; comparison showing differences in records, line items, quantities, and amountsLegacy data cleanup and migration are treated as separate work.
Transaction load and service limitsTesting with agreed data volumes; queue delay, retry limits, and stop conditionsIdentify who pays for API licenses, service quotas, and hosting.
Maintenance and handoverVersion-change test, alert owner, operations guide, and access handoverBug fixes, new features, and adaptations to vendor changes are priced separately.

Example scenario: Suppose quote A covers only successful stock and order transfers, while quote B also covers investigation of uncertain transactions and maintenance handover. Their totals do not price the same work. Compare them only after adding missing items or explicitly excluding them. This is not a real quote or customer result; it contains no price or timeline assumptions.

Completing tests and obtaining business-owner acceptance are separate steps. Microsoft's guide to test types also treats end-to-end testing and user acceptance testing separately (checked: 18 October 2026). Identify the person who will accept the work and the evidence they will see from the start; do not close unresolved records solely because an API returned success. For general software ownership and maintenance scope, see the guide to comparing custom software quotes.

What determines the timeline, and when does manual bridging make sense?

The ERP product name does not determine the integration timeline. The strongest factors are whether the ERP offers a documented service, master data quality, the availability of a test environment, the number of flows, and access to the ERP owner. Discovery of 1–2 weeks and a first release in 6–12 weeks are example planning ranges for narrowly scoped work with access already available. ERP restrictions or data preparation may require a plan outside these ranges; timing is determined after technical assessment.

Not every first release needs to wait for full integration. In a hypothetical dealer portal, while order volume is still low, prices and stock can be updated several times daily using a file exported from the ERP; the operations team can transfer portal orders into the ERP from their own screen. This reveals whether dealers adopt the portal before the integration is finished. When volume increases, stock changes rapidly, or credit-limit risk is high, the manual bridge becomes a source of errors; full integration becomes the next task. We discuss this decision in detail in our article How do you define MVP scope?

We explain our approach to an ERP-connected portal on the B2B portal development page. Try products, credit limits, and manager approval in the dealer ordering demo. The fictional X Dağıtım workflow runs in your browser; it does not connect to a real ERP or submit orders. The demo's approval step and a real ERP's acceptance of an order are different operations.

With your ERP inventory, we can draft the initial plan together in a 30-minute conversation.

Let's discuss ERP integration

Read on
Related service

B2B Portal Development

Dealer, customer, and supplier portals, including planning price, stock, account, and order flows alongside the ERP.

Other articles
Resources

Explore details for your system

The ERP integration library connects the general plan to Mikro, SAP Business One, and Business Central conditions. For a concrete dealer workflow example, see the Mikro ERP dealer portal; for queue and retry decisions, Business Central 429 diagnosis may help. For access, request limits, or timeouts, explore the troubleshooting guides.