EN
E-Commerce Nov 17, 2026

ERP Connectors or Custom Integration: Handling Real B2B Exceptions

ERP Connectors or Custom Integration: Handling Real B2B Exceptions

Time to read: 7 minutes

Content

  1. Connector, extension or custom build: when each route wins
  2. Agree what “correct” means before testing
  3. One hard order separates the routes
  4. Counterexample: a different prebuilt connector fits
  5. Keep a fit-gap record that distinguishes evidence
  6. Dealer channels: one more boundary each route must carry
  7. Compare the full scope, then choose the next step
Bookmark

A connector can pass a demo. But does it give your buyer the contract price, reserve the right stock and recover an uncertain order without creating another one? For a B2B distributor adding a channel, that is the useful comparison—not “standard software versus flexible code.”

A supported connector is enough when it carries the required price, reservation and order identity, and testing confirms that repeats and uncertain outcomes do not create extra orders or holds. Check configuration and documented extension points before building custom for a remaining gap. A failed demonstration is a reason to investigate, not proof that the platform cannot cope or the ERP needs replacing.

Connector, extension or custom build: when each route wins

An API is an interface; a connector uses interfaces to exchange data. Middleware supplies a runtime for connecting and coordinating systems and may host both prebuilt connectors and custom logic. Batch and event-driven processing describe timing, not competing product categories.

Use/configure a supported connector, current first and alternatives next. It wins when supported mappings and testing cover the required business effects. Stop treating the current product as sufficient if a required warehouse hold remains unsupported after configuration checks—but evaluate another prebuilt candidate before assuming custom. Name who owns vendor support, switching/migration, upgrades and regression testing.

Extend a connector or middleware flow. It wins when a documented extension point and approved interfaces can carry the missing behavior. It loses when the necessary operation is unavailable or support boundaries are unclear. Identify the connector, runtime and added logic separately, and state where vendor support ends and extension maintenance begins.

Build bounded custom integration. It fits an evidenced effect that remains uncovered and can be implemented through approved interfaces. It loses when it merely reimplements supported behavior or cannot access the required operation. Include ownership of code, hosting/runtime, compatibility, monitoring and recovery.

Neither yet is a legitimate conclusion when configuration, access or the outcome of a test remains unresolved. One mismatch is not a documented capability exclusion. Custom work does not automatically handle exceptions; someone still specifies, implements and tests them. Contract pricing or multiple warehouses alone is not a custom-build justification.

Switching to a different prebuilt connector is still implementation work. Verify installed ERP/commerce versions, mappings, data/flow migration, in-flight order reconciliation and vendor support. Compare switching, testing and license overlap—not subscription price alone.

Agree what “correct” means before testing

“ERP is the master” is not a complete specification. A proposed split to validate is ERP authority for contract prices, inventory, reservations and order status, with the storefront owning content/cart and an agreed customer-identity mapping. It is not universal: a PIM may own product descriptions. Assign authority and permitted write direction by object and field. Unavailable ERP access is a gap to resolve, not permission to appoint another source silently.

Assign authority by object and fieldA proposed authority split to validate: ERP for contract prices, inventory, reservations and order status, the storefront for content and cart, an agreed mapping for customer identity and a PIM for product descriptions.Assign authorityby object and fieldA proposed split to validateERPcontract prices, inventory,reservations, order statusStorefrontcontent and cartAgreed mappingcustomer identity across systemsPIM, where presentmay own product descriptions

For price, include the ERP customer ID, commerce company/account, list/contract, currency, quantity, unit, website and discount rules. Verify where the price is calculated and the fallback if that source cannot be reached. Adobe Commerce B2B pricing documentation describes shared-catalog custom/tier pricing, website scope and company assignment. This establishes platform capabilities—not connector support or their presence in your installation.

For stock, distinguish physical on hand, available to sell and a reservation. Agree whether a hold belongs to a stock pool or a warehouse and which system creates/releases it. Set freshness separately for price, availability and order/status updates, including measurement and stale-data behavior. “Real time” alone is not an acceptance criterion; the required decision and sustainable interfaces determine whether faster exchange is useful.

One hard order separates the routes

The following is hypothetical, not a client incident or executed test. Buyer A orders eight cartons of SKU Y at EUR 42.50 per carton before tax. Under the assumed merchant policy, W2 reserves five cartons and three remain on backorder while credit review is open. That policy permits reservation during review, not fulfillment release without authorization. No carton-to-each conversion or actual ERP capability is assumed. The storefront sends B2B-2207, but its response times out.

One order, split expected quantitiesFictional untested B2B-2207 requirement: eight cartons of SKU Y at EUR 42.50 per carton. Five reserved at W2, three backordered, one business order. Credit review remains open and does not authorize fulfillment release. Fictional · expected, untestedB2B-2207 · 8 cartonsEUR 42.50/carton · before tax Orange: 5 reserved at W2Gray: 3 backorderedCredit review: openNo fulfillment release implied.

Give every candidate the same required effects:

Collect the approved rule, environment/versions, sanitized mappings, timestamps, operation references and resulting business state. If a test shows a different price, first check account, list and carton basis. The mismatch is evidence of disagreement, not its cause.

Ask whether the endpoint provides reliable order lookup, what duplicate protection covers and for how long, whether the connector conveys the warehouse hold, and who resolves uncertainty. AWS's timeouts and retries explanation notes that timeout does not establish the absence of side effects. Verified acceptance calls for linking/reconciling the existing order; verified non-acceptance still needs the contract's safe retry conditions; unresolved outcomes stay with an authorized owner. If the cause of a failed order is still unclear, trace that one order to its first evidenced divergence before comparing routes. This is not a production replay procedure.

Counterexample: a different prebuilt connector fits

Suppose versioned documentation confirms that the current connector cannot create W2's required hold and checks rule out a mapping/configuration fix. A different supported candidate demonstrates that hold on the installed versions through ordinary configuration. Replacement is then a candidate—not an automatic custom build. Price, partial/backorder handling, credit status, identity and recovery still need separate evidence.

If the original issue was instead an incorrect company assignment and the current connector passes the agreed effects after correction, configuration can be enough. Neither hypothetical conclusion proves coverage of every account or order type; define the remaining sample.

Keep a fit-gap record that distinguishes evidence

For each candidate, record the requirement; documented support or exclusion with its source/version; observed agreement or mismatch with its test reference; unresolved question and next check; and maintenance owner. Keep each prebuilt candidate separate. Mark any test you have not run as not yet tested; don't count it as support. Use no weighted score to turn unknowns into a winner.

One fit-gap record per candidateA fit-gap record per candidate: requirement, documented support or exclusion, observed result, open question and owner; a test not yet run is never counted as support.One fit-gap recordper candidateNo weighted score for unknownsRequirementthe business effect to carryDocumented supportor exclusion, with source andversionObserved resultagreement or mismatch, with testreferenceOpen questionthe next check and the maintenanceownerNot yet testednever counted as support

Include these real B2B exceptions where they apply. They are questions for your business, ERP and policy owners—not claims that your ERP supports a rule.

Exception Potential break Check to agree
Credit hold/limit Commerce accepts; ERP holds Visible hold and approved reservation/release policy
Partial shipment/backorder Split quantity loses identity One linked order; no duplicate reservation
MOQ/unit conversion Carton and each are mixed Documented conversion for quantity, minimum and price
Tax-exempt account Authorized status is lost Correct jurisdiction-specific treatment and approved total
Return/credit note Reverse flow loses reference Named system owner and original-order link

Dealer channels: one more boundary each route must carry

If you also sell through dealers, add that channel to the same fit-gap record: each candidate route must preserve partner identity, catalog entitlement and the order's route into B2B. Test permitted and denied cross-partner actions in an authorized environment; login success is not evidence of isolation. Record who owns access approvals and secret provisioning, rotation and revocation under each route.

There is a distinct dealer-channel scope in Dinarys' SanMar B2B2C website-builder case: a WordPress/WooCommerce partner-store builder synchronized with the existing Magento B2B platform and routed microsite orders to its central B2B panel. This is the same client as the ERP case, not a second independent customer or proof of every prospect's access and recovery tests. Use it as a reference point when asking how each route would carry dealer storefronts and central order routing.

Compare the full scope, then choose the next step

Have finance compare the same channel, effects, horizon and operating assumptions. Include repair/configuration or switching, migration, extension/development and tests; retained/new licenses and overlap, hosting/runtime; monitoring and manual reconciliation; support/upgrades/regression tests; and handover/exit responsibilities. Keep known quotes, estimates and missing inputs separate. Lower initial cost does not prove lower total cost, and owning custom code does not remove maintenance.

Dinarys' SanMar ERP case describes a format-converting custom API connector for Magento B2B/B2C product and order exchange. It is a bounded interface example, not a reason to replace your supported connector. The ERP product is not named, and the public narrative does not supply your price–reservation–retry acceptance evidence.

Once a gap is evidenced, use ERP integration services to discuss an acceptance pack: approved rules and mappings, expected/observed order and reservation states, recovery evidence, responsibilities and support boundaries. Operations owns the business outcome, commerce/ERP owners accept the interfaces, and the authorized signer approves spend.

First ask the current connector owner to demonstrate coverage. To discuss a remaining gap with Dinarys, bring one sanitized order trace, price/reservation rules, component versions, failure evidence and the people who own the result. Establish what needs checking before assuming custom development is the answer.

Lassen Sie Profis Ihre Herausforderung meistern

Unsere zertifizierten Spezialisten finden die optimale Lösung für Ihr Unternehmen.

Bitte einen gültigen Namen eingeben
Bitte geben Sie ein gültiges Unternehmen ein
Bitte geben Sie eine gültige Telefonnummer an
Bitte geben Sie eine gültige E-Mail-Adresse ein
Kurze Botschaft

    Ihre Nachricht wurde erfolgreich verschickt. Wir melden uns in Kürze! Success icon