Skip to main content
Talk to an expert
OroCommerce logo

OroCommerce marketplace integration for ecommerce

Govern B2B orders, stock and pricing across OroCommerce seamlessly iWeb connects OroCommerce with your product data, stock, pricing and order systems so B2B buyers get current merchandise, accurate availability and reliable order handling without manual synchronisation or data drift. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: marketplace connector, feed integration, channel plugin, app.

OroCommerceiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a OroCommerce integration gives you.

B2B customers see current merchandise

Buyers access up-to-date product data, accurate stock and current pricing in OroCommerce without waiting for manual feeds or republication. Channel readiness rules ensure only approved, complete products are visible.

Orders flow to fulfilment without delay

B2B orders placed in OroCommerce are automatically acknowledged in ERP and routed to the correct fulfilment location or supplier. Status updates flow back to customers so visibility is real-time.

Stock stays accurate across channels

Inventory is orchestrated between ERP, OroCommerce, other online channels and branches so you never oversell, and buyers see realistic availability.

Buyer accounts and pricing reconcile

Customer accounts, credit limits, contract pricing and approval workflows are synced between OroCommerce and ERP so account teams and customers see consistent terms.

Multi-channel operations become manageable

With OroCommerce as a B2B channel alongside other storefronts, marketplaces and branches, clear ownership and governed data flows reduce manual reconciliation and channel conflicts.

02 · When it's worth it

Where a OroCommerce integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publishing product catalogues with variant data, pricing tiers and channel-specific readiness rules to OroCommerce
Synchronising stock availability and allocation rules between ERP, OMS and OroCommerce to prevent oversell across channels
Ingesting B2B orders from OroCommerce into ERP and OMS for acknowledgement, fulfilment and invoicing
Managing buyer-specific pricing, contract terms and account visibility across OroCommerce and ERP customer records
Handling returns, credit notes and order status updates flowing back from ERP and fulfilment systems to B2B customers
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

No native multi-channel stock orchestration

OroCommerce does not automatically reserve stock across multiple channels or manage allocation rules with ERP and OMS. Manual configuration or middleware is needed to prevent oversell and keep stock in step across B2B and other sales channels.

Limited contract pricing and approval workflows

Buyer-specific pricing and approval rules must be configured per buyer or account group. Complex contract pricing, tiered discounts, seasonal overrides and approval routing require integration logic to sync with ERP pricing rules and customer records.

Order handoff depends on connector design

OroCommerce can send orders via REST API or webhooks, but acknowledgement, routing to fulfilment, invoice timing and returns workflows must be designed in the integration layer. No default orchestration between OroCommerce order capture and ERP / OMS processing.

Catalogue governance sits outside the platform

OroCommerce stores product data locally but does not enforce completeness rules, approval workflows or channel-readiness checks. These must be owned and monitored by PIM and the integration layer so the catalogue stays trusted.

Search and merchandising require separate indexing

OroCommerce search is basic and does not sync merchandising rules, synonyms, facets or zero-results handling from a central platform. Search governance and performance tuning need integration with a dedicated search system or middleware.

04 · The real work

Ownership of buyer pricing, account rules and order routing between OroCommerce and ERP must be clear from the start; ambiguity here causes pricing disputes, account errors and hidden order delays that are expensive to diagnose after launch.

05 · Where it sits

Where this integration sits in your estate.

OroCommerce holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Built for your platform, not a specific one. OroCommerce integrates with any ecommerce core through the same contract.

System of record
Source / owner
OroCommerce
B2B sales channel and order capture layer
  • B2B buyer portal and storefront experience
  • Buyer session and cart state
  • Order placement UI and workflows
  • Buyer interaction and behaviour within OroCommerce
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Product catalogue display and search
  • Stock availability and allocation visibility
  • Pricing and promotional display
  • Order confirmation and status visibility to buyers
Connected neighbours
Integration layer
PIM
Governs product attributes, completeness, channel readiness and sends catalogue feeds to OroCommerce
Integration layer
ERP
Maintains inventory, base pricing, customer accounts, contracts and order ledger; receives orders from OroCommerce for acknowledgement and fulfillment
Integration layer
OMS
Routes orders from OroCommerce to correct locations, allocates stock and coordinates fulfillment across channels
Integration layer
WMS
Executes picking, packing and dispatch; sends tracking and dispatch confirmations back through OMS and OroCommerce to buyers
Integration layer
Search platform
Indexes OroCommerce products for discovery, relevance and faceted search; manages synonyms and zero-results handling
Integration layer
CRM
Receives buyer activity, supports marketing campaigns and sends segmented offers or alerts back into OroCommerce
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (SAP, NetSuite, Sage, Infor)
  • PIM (Salsify, Syndigo, Contentserv)
  • OMS (Manhattan, Blue Yonder, Kinaxis)
  • WMS (Körber, Knack, Honeywell)
  • Search platform (Elasticsearch, Algolia, Klevu)
  • CRM (Salesforce, HubSpot, Zoho)
  • Tax engine (Avalara, TaxJar)
  • Payment processor (Stripe, Adyen, PayPal)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into ERP AND OMS & ERP & OROCOMMERCE AND SALES CHANNELS
←From ERP AND PIM & ERP AND OMS
Product and pricing feeds: Product attributes, variants, descriptions, images, availability status and buyer-specific pricing flow from PIM and ERP into OroCommerce to keep the B2B catalogue current and channel-ready without manual republication.
Stock and allocation updates: Stock levels, reserved inventory, allocation rules and channel-specific availability feed from ERP or OMS into OroCommerce so B2B customers see accurate stock and the system prevents oversell across channels.
Order ingestion and acknowledgement: B2B orders placed in OroCommerce are sent to ERP and OMS for order acknowledgement, routing, fulfilment instruction and customer invoice generation
Order status and tracking flow back to OroCommerce for buyer visibility.
Customer account and contract data: Buyer account creation, customer classification, credit limits, contract pricing and approval workflows sync between OroCommerce and ERP to ensure account governance and pricing consistency.
Returns and credit notes: Dispatch confirmations, invoices, credit notes and return authorisations flow from ERP and fulfilment systems into OroCommerce and other channels to complete the order lifecycle and keep customers informed.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Define channel-readiness rules for OroCommerce

    iWeb works with your PIM and merchandising teams to define which products, attributes, images and completeness rules apply to OroCommerce. The integration enforces these rules so only approved merchandise enters the channel.

  2. 02
    Design stock orchestration between systems

    iWeb maps stock locations, reservation logic, channel allocation rules and availability thresholds so ERP or OMS owns the inventory position and each channel (including OroCommerce) receives accurate, allocated stock in real-time.

  3. 03
    Build order ingestion and acknowledgement flows

    iWeb handles order capture from OroCommerce, maps buyer and line details into ERP and OMS, manages order acknowledgement timing, and routes dispatch instructions back to the correct fulfilment location or dropship supplier.

  4. 04
    Sync buyer accounts and contract pricing

    iWeb defines how customer accounts, buyer groups, credit limits, contract pricing and approval workflows flow between OroCommerce and ERP so pricing and account governance stay consistent and buyers see their agreed terms.

  5. 05
    Operate integrated monitoring and alerting

    iWeb builds dashboards and alerting so catalogue readiness, stock synchronisation, order flow, exception queues and channel performance are visible to your operations team and senior stakeholders.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataChannel-specific product readiness
Source / ownerPIM
Maintained byMerchandisers and PIM operators
NotesChannel readiness rules determine which products, variants, attributes and images flow to OroCommerce. Integration enforces these rules.
DataProduct catalogue in OroCommerce
Source / ownerPIM (source) / OroCommerce (published copy)
Maintained byPIM team (source governance); integration automation (publication)
NotesProduct data flows from PIM into OroCommerce via scheduled or event-driven feeds. Local edits in OroCommerce are not synced back; PIM is the source of truth.
DataStock availability and allocation
Source / ownerERP or OMS (inventory ledger)
Maintained byOperations and warehouse teams
NotesStock levels, reservations and channel-specific allocation rules originate in ERP or OMS. OroCommerce receives real-time or scheduled updates to prevent oversell.
DataB2B buyer accounts and pricing
Source / ownerERP (customer master and contract pricing)
Maintained byCustomer account and sales teams
NotesCustomer accounts, buyer groups, credit limits and contract pricing are maintained in ERP. OroCommerce receives synced copies and enforces pricing and approval rules from the source.
DataOrders and order status
Source / ownerERP and OMS (transactional record)
Maintained byOrder management and fulfilment teams
NotesOrders placed in OroCommerce flow into ERP and OMS. Acknowledgement, routing, dispatch and invoicing are owned by the operational systems, with status flowing back to OroCommerce for buyer visibility.
DataReturns and credit notes
Source / ownerERP (finance ledger)
Maintained byFinance and customer service teams
NotesReturn authorisations, credit notes and reversal transactions originate in ERP after customer service approves. OroCommerce displays status and refund information to buyers.
DataIntegration transport and exception handling
Source / ownerIntegration platform or middleware
Maintained byiWeb and operations team
NotesData flows, retry logic, dead-letter queues, monitoring and alerting are owned by the integration layer. Operational issues are escalated via named exception queues.
10 · Experienced integrator

Built OroCommerce B2B estates before

iWeb has integrated OroCommerce with ERP, PIM and OMS systems across multiple B2B operations, managing product synchronisation, stock orchestration, buyer account governance and order handoff.

Understands OroCommerce architecture, API contract and how product data, stock levels and buyer account rules flow between the platform and operational systems
Has designed stock allocation rules and channel-readiness governance to prevent oversell and keep OroCommerce catalogue consistent with PIM and ERP
Can build order ingestion pipelines that map OroCommerce orders into ERP and OMS with correct routing, acknowledgement timing and exception handling
Knows how buyer accounts, contract pricing and approval workflows sit between OroCommerce and ERP, and where local configuration versus integration ownership boundaries matter
Has implemented monitoring, alerting and exception queues so catalogue, stock and order flow issues are surfaced before they reach buyers
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify product feed completeness: check that all attributes, images and variants matching channel-readiness rules flow correctly from PIM to OroCommerce and no approved products are missed.
Validate stock allocation logic: confirm that available inventory in OroCommerce respects allocation rules from ERP or OMS and overselling is prevented across channels under peak load.
Test order ingestion and acknowledgement timing: place test B2B orders in OroCommerce and verify they appear in ERP and OMS within expected latency, with correct buyer and line details.
Confirm buyer pricing accuracy: test multiple buyer groups and contracts to ensure contract pricing syncs from ERP to OroCommerce and discounts apply correctly at checkout.
Test exceptional failure paths: stop the integration, place orders and sync updates, then restart to verify queuing, retries and exception handling do not lose data.
Monitor and baseline performance: measure product feed sync latency, order ingestion latency and exception queue clearing time under normal load and establish alerting thresholds.
Verify credit limit enforcement: test buyers against credit limits, confirm checkout blocks orders exceeding limits, and validate that limit changes in ERP propagate to OroCommerce within acceptable time.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Stock oversold across channels

If stock allocation rules are unclear or OeroCommerce does not communicate availability to the OMS or other channels in real-time, orders can be placed against reserved or unavailable inventory. This breaks fulfilment and damages buyer trust.

Orders stuck between OroCommerce and ERP

Order acknowledgement timing, routing rules and exception handling must be owned by the integration layer. If an order is sent but not confirmed, or gets routed to the wrong location, it can remain hidden in queues and delay fulfilment.

Buyer pricing mismatches and confusion

If contract pricing, buyer group rules or seasonal overrides are not synced from ERP into OroCommerce, or if OroCommerce holds local pricing overrides, buyers see conflicting terms. This causes disputes and erodes confidence in B2B ordering.

Product data drift in the catalogue

Without clear ownership and monitoring, product data published to OroCommerce can become stale, incomplete or misaligned with PIM or channel-readiness rules. Buyers encounter missing images, outdated specs or unavailable variants.

Customer account and credit limit confusion

If buyer account records, credit limits or approval workflows are not synced between OroCommerce and ERP, customers may place orders against expired limits or outside their approval authority, leading to post-order disputes or financial risk.

Silent channel outages and data loss

If the integration layer does not have monitoring, alerting and exception queues, failures in product sync, order ingestion or stock updates can go unnoticed until customers complain or orders are missed.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about OroCommerce integrations.

How do product attributes and completeness rules flow into OroCommerce?

Product data flows from PIM via API or scheduled feed. Channel-readiness rules in PIM determine which attributes, images, descriptions and variants are required for OroCommerce. The integration enforces these rules so only complete, approved products are published.

What happens if stock is oversold across OroCommerce and other channels?

Stock allocation rules must be defined in ERP or OMS and enforced by the integration. OroCommerce receives real-time or near-real-time stock updates and must hold allocation rules that prevent sales beyond available inventory. Without clear ownership and real-time sync, oversell is a risk.

How do B2B orders flow from OroCommerce into ERP and OMS?

Orders are captured via OroCommerce API webhooks or scheduled polling and sent to ERP and OMS with buyer details, line items and delivery instructions. Order acknowledgement, routing to the correct fulfilment location and dispatch instruction generation are handled by ERP and OMS. Status and tracking flow back to OroCommerce.

How is buyer account information kept in sync between OroCommerce and ERP?

Customer accounts, buyer groups, credit limits and approval workflows are maintained in ERP. OroCommerce receives synced account data and enforces approval rules and pricing based on the buyer's group or contract. Changes to accounts or credit limits in ERP flow back to OroCommerce so buyers see current terms.

Who owns contract pricing for B2B buyers?

ERP is the source of truth for contract pricing, seasonal overrides and buyer-group discounts. OroCommerce receives pricing updates and applies them to product display and checkout. Local pricing overrides in OroCommerce are avoided to prevent drift; if overrides are needed, they must be designed and monitored as exceptions.

How are returns and credit notes handled?

Returns are authorised by customer service or ERP and recorded as credit transactions in ERP. OroCommerce displays return status and refund information so buyers can track resolution. Refunds or replacement orders flow back into the order system.

What happens if the integration fails during a product sync?

Failed syncs are captured in exception queues and alerted to the operations team. Retries are automatic with exponential backoff. If a retry fails, manual review determines whether to resend, skip, or escalate. Monitoring shows staleness of catalogue data.

Can we handle seasonal pricing or promotional pricing in OroCommerce?

Seasonal and promotional pricing rules can be defined in ERP and synced to OroCommerce as scheduled price updates. The integration manages timing and can apply rules to specific buyer groups. Promotion end dates must be monitored so pricing reverts correctly.

How do we prevent B2B orders from being placed against expired credit limits?

Credit limits are synced from ERP to OroCommerce. The checkout flow in OroCommerce should validate order total against available credit before confirmation. The integration monitors changes to credit limits and propagates them in near-real-time.

What visibility do we have into order flow and exceptions?

Integration dashboards show order volume, acknowledgement latency, routing success rates and exception queue depth. Alerting flags orders stuck in OMS, unrouted orders, and failed order syncs. Senior stakeholders can see channel performance and operational risk in real-time.

How do we handle B2B customers who order across multiple channels?

Customer accounts are unified in ERP by account number or email. Stock is allocated centrally in ERP or OMS so each channel sees available inventory. Order history and account data are linked so customer service and operations see the full relationship.

What happens if OroCommerce goes offline or the API becomes slow?

The integration queues outbound orders and retries with backoff. Inbound product and stock updates are deferred until OroCommerce is available. Monitoring alerts your team to downtime or performance degradation. Buyers see limited functionality (e.g. no checkout) if critical systems are unavailable.

Can we migrate existing B2B customers from another platform into OroCommerce?

Customer account migration from a legacy system to OroCommerce depends on data mapping and ERP acceptance rules. iWeb works with your team to define account structure, pricing, approval rules and master data. Testing ensures no orders or account data are lost during cutover.

Next step

Have a OroCommerce integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →