Skip to Content

eCommerce Integration in Switzerland: ERP, OMS, WMS & 3PL

November 16, 2026 by
eCommerce Integration in Switzerland: ERP, OMS, WMS & 3PL
Lazhar Cader

Why a flawed ecommerce integration becomes an operational problem

In 2026, 76% of surveyed consumers consider better availability of products as an important criterion when shopping online.

A company can keep its ERP and e-commerce store while connecting to an outsourced warehouse or switching 3PL providers. In this context, the project goes beyond simply connecting two software systems. It must ensure continuity in orders, reservations, available inventory, shipments, and returns (incidentally, 85% of respondents say clear return policies are important, according to La Poste).

75% consider online tracking important, compared to 30% for same-day delivery and 26% for delivery within 2 hours. according to Handelsverband. A break in flow can create duplicate orders, publish outdated availability, or prevent the retrieval of a tracking number. It can also produce a discrepancy between the physical stock in the warehouse and the quantities recorded in the ERP, OMS, or sales channels. Teams must then correct multiple systems without always knowing the missing event.

 

The project must address 4 operational questions:

  • Which system holds each data point and each business decision?
  • How do events flow between the channels, the ERP, the OMS, the WMS, and the 3PL?
  • How to handle an error, a delay, a duplicate, or a stock discrepancy?
  • How to switch to a new 3PL with explicit acceptance criteria and a fallback plan?

 

For flows between Switzerland and the European Union (see Passar 2026), the architecture can also carry the data necessary for import or customs clearance. It must follow the handoffs between the warehouse, the carrier, and the last mile. Swiss and European requirements remain distinct and must be addressed according to the relevant market.

E-commerce integration therefore involves architecture, data governance, and operations. An API or connector alone does not guarantee operational continuity, the frequency of updates, or proper recovery after an error.

Roles of systems and essential vocabulary

What drives the store, the ERP, the OMS, the WMS, the middleware, and the 3PL


Orders via ERP and EDI each represent a relevant sales channel for 24% of B2B respondents, and 64% of them consider email relevant according to the Post. Shopify, WooCommerce, or another store presents the catalog and receives the sales request. The platform collects the order, the address, the delivery method, and the necessary payment information.

The ERP holds the management data retained by the company, such as items, prices, customers, billing, or stock entries. The OMS coordinates orders between channels. It can maintain operational records, reserve stock, apply allocation rules, and transmit instructions to execution systems. This separation between OMS, ERP, WMS, and TMS avoids confusing decision and execution.[1].

The WMS manages locations, physical movements, the preparation, and inventories. The 3PL carries out the agreed operations, such as receiving, storing, picking, packing, shipping, and returns. A TMS can manage transport selection, labels, and tracking.

The middleware transforms formats, routes messages, and supervises their processing. It can also apply technical controls, without necessarily becoming the owner of the data.

The same software can fulfill multiple roles. An ERP can, for example, integrate an order management module. The company must nevertheless designate a unique owner for each data point and each decision. The Swiss ERP guide deepens this distribution.

For your information, 19% of stores use an internally developed solution, compared to 16% for WooCommerce and 11% for Shopify.


 

Operational glossary


  • Reference system : system whose value is authoritative for a given object.
  • API : interface that allows systems to automatically exchange data. Its presence does not guarantee completeness, frequency, or error management.
  • Webhook : notification sent when a defined event occurs.
  • Idempotence : property that allows reprocessing a request without recreating its effect.
  • Reservation : quantity allocated to an order before physical movement.
  • Available stock : quantity that can be published after applying reservations, blocks, and safety rules.
  • Physical stock : quantity actually present in a location.
  • Exception queue : list of messages that require correction or a decision.
  • Resumption : controlled resumption of a interrupted exchange.
  • Cutover : period and procedure for switching to the new organization.
  • Return : flow from the return request to receipt, inspection, and final decision.
  • Acceptance criteria : verifiable condition that authorizes validation or switching.

 

Le guide d’intégration e-commerce et WMS détaille le raccordement opérationnel entre un site et l’entrepôt.

Define data ownership and target architecture

A matrix of ownership before any interface


There is no universal owner for an order, a reservation, or available stock. The choice depends on active modules, business rules, and available interfaces. Before any development, the company must define the reference system, writing rights, the flow direction, and the conflict rule.

The ERP often serves as a natural candidate for references and management data. The OMS can handle the orchestration of orders and reservations. The WMS or 3PL produces the physical movements. This distribution remains an architectural decision, especially if the ERP already has an order management module.

▣ Data

◉ Reference

✎ Writing

⇄ Update

⚠ Conflict

▣ Products

◉ To decide by the company, often ERP

✎ ERP or designated product tool

⇄ Creation, modification, deactivation

⚠ The designated source prevails

▣ Customer Data

◉ To decide according to usage

✎ Store, ERP, authorized customer service

⇄ Creation, correction, merging

⚠ Priority according to the field and validated date

▣ Price

◉ To decide, often ERP

✎ ERP or pricing engine

⇄ New rate, promotion, end of validity

⚠ The approved pricing rule prevails

▣ Orders

◉ OMS or ERP depending on the architecture

✎ Channel at creation, then designated system

⇄ Validation, modification, cancellation

⚠ Immutable external identifier

▣ Reservations

◉ OMS or ERP according to the rule

✎ Designated orchestration system

⇄ Validation, allocation, release

⚠ Only one active reservation per line

▣ Available stock

◉ Designated calculation system

✎ OMS, ERP or availability service

⇄ Movement, reservation, blocking

⚠ Recalculation from authorized statuses

▣ Shipments

◉ WMS or 3PL

✎ WMS, TMS or authorized carrier

⇄ Preparation, shipping, delivery

⚠ The confirmed physical event prevails

▣ Returns

◉ OMS, ERP or WMS according to the process

✎ Channel, customer service, WMS

⇄ Request, receipt, control, closure

⚠ The most advanced and validated status prevails

The matrix must specify the rules at the field level when multiple applications contribute to the same object. An address may come from the store, while the customer's accounting status remains managed in the ERP.

 


The technical flow to represent


A target flow can be represented as follows:

  1. Sales channel → middleware or OMS : creation or cancellation.
  2. Middleware or OMS → ERP and WMS according to the rule : control, reservation and allocation.
  3. ERP or OMS → 3PL : preparation request and instructions.
  4. 3PL → carrier : shipping and transport data.
  5. Carrier → OMS, ERP and channels : tracking and delivery.
  6. Channels or 3PL → OMS, ERP and WMS : request, receipt and return decision.

 

ERP connectors and solutions can link an e-commerce platform to WMS, OMS, and TMS systems. They remain components of the transportation or processing workflow, not a complete architecture. Their use must be supplemented by a data matrix, controls, and an operational procedure.

An API integration between ERP and logistics provider must specify the covered events, authentication, limits, responses and retries. Connecting an ERP to an outsourced warehouse also requires verifying the software version and the interfaces actually exposed. The presence of a current product is not sufficient to confirm its compatibility.

Example Shopify : the GraphQL Admin API limits the exchanges to 100 cost points per second on the Standard offer, compared to 1,000 on Shopify Plus. An ERP–WMS integration must therefore manage quotas, queues and retries to avoid synchronization delays (source : Shopify).

Example WooCommerce : a webhook can be automatically disabled after more than five consecutive failures. Without monitoring or recovery procedures, orders may not reach the logistics provider (source : WooCommerce).

Synchronize the orders, inventory and shipments end to end

Order lifecycle


The cycle begins when the channel validates the order. The coordination system checks the mandatory data, detects any duplicates and reserves the inventory. It then allocates the order to a warehouse, then transmits the lines and instructions to the WMS or the 3PL.

The WMS organizes picking and packing. After handing over to the carrier, it sends back the shipping confirmation, the quantities shipped, and the tracking number. 3PL integration flows commonly cover preparation requests, stock updates, shipping confirmations, receipts, and returns [2].

An order can produce multiple shipments. A partial delivery, a consolidation, a line cancellation, or a reshipment breaks the simple relationship between an order and a package. The data model must therefore identify each line, each quantity, and each shipment.

Example: partial shipment from a Swiss 3PL

A Shopify order contains 5 items, but the logistics provider only has 3 available immediately. The WMS confirms a first shipment of 3 items with its tracking number. The 2 remaining items are shipped later with a second tracking number. The integration must retain the shipped and remaining quantities without prematurely closing the order.

▣ Step

◷ Event

→ Source

← Target

✓ Control

▣ Order validated

◷ Creation

→ Sales channel

← OMS, middleware or ERP

✓ Field and identifier control

▣ Deduplication

◷ Order received

→ Coordination system

← Event log

✓ Verification of the idempotence key

▣ Reservation

◷ Stock reserved

→ OMS or ERP

← ERP, WMS and channels

✓ Quantity reserved and availability recalculated

▣ Allocation

◷ Warehouse assigned

→ OMS or ERP

← WMS or 3PL

✓ Site, service and instructions validated

▣ Preparation

◷ Picking started or completed

→ WMS

← OMS or ERP

✓ Quantities prepared and discrepancies reported

▣ Packaging

◷ Package constituted

→ WMS or 3PL

← OMS, ERP or TMS

✓ Lines, weights and packages matched

▣ Shipping

◷ Package handed over

→ WMS, 3PL or TMS

← OMS, ERP and channel

✓ Quantities shipped and duplicates checked

▣ Tracking

◷ Tracking number created

→ Carrier or TMS

← OMS, ERP and channel

✓ Carrier, package and order correlated

▣ Delivery

◷ Delivery confirmed

→ Carrier

← OMS or ERP

✓ Delivery status recorded

▣ Cancellation

◷ Total or partial cancellation

→ Channel, OMS or ERP

← WMS or 3PL

✓ Preparation status checked before release

▣ Return received

◷ Return received

→ WMS or 3PL

← OMS and ERP

✓ Quantity and physical condition checked

▣ Return closed

◷ Return decision

→ ERP, OMS or authorized service

← Channel and relevant systems

✓ Restock, block or other decision

Events that modify stock and status


The physical stock corresponds to the items present. The reserved stock is allocated to orders. The stock available for sale results from a rule that also takes into account blocked stock. The stock in transit has not yet been received, while the return stock awaits inspection before being made available.

Each event must update the relevant statuses. A cancellation before preparation can release a reservation. After preparation, it requires an instruction to the WMS and a confirmation before republishing. A received return only becomes sellable after the planned decision.

The synchronization of ERP and warehouse orders must thus cover orders, stock levels, shipping statuses, products, and returns. An update can be event-driven or scheduled. The term "real-time" only applies if the necessary webhooks or events are supported and monitored.

Manage a shared stock and recover exceptions

B2B, B2C, and marketplace reservations


A common stock can support a B2B operation, a B2C store, and multiple marketplaces. The company must set priorities, safety thresholds, reservations, and any dedicated stock. It also defines the publication frequency for each channel.

Channels should not recalculate their availability separately from different data. They receive a quantity published according to the central rule, for example after deducting reservations and blocked stock. A B2B order can reserve a future volume, while a marketplace expects an immediately executable quantity. These usages must be distinguished in the model. Moreover Shopify will modify its inventory model on 5.08.2026.

Shopify Example : a Swiss warehouse holds 100 units of a product, of which 15 are reserved, 5 damaged, and 10 allocated to safety stock. Only 70 units are available for sale. The ERP–WMS integration must convey this commercial availability, not just the 100 physical units.

For marketplaces, Emaloja offers a interface between marketplaces and WMS that covers order processing and return management. The project architecture still needs to determine who owns the reservation and how availability is published.

Swiss providers generally offer storage, order processing, shipping, and return services. Some offerings also cover import or customs clearance. Choosing a service does not replace the definition of data ownership and control mechanisms.

 


Controls against duplicates, delays, and discrepancies


Each order must carry an immutable external identifier and each line a distinct identifier. An idempotency key prevents a new attempt to recreate the order. The log retains the event, its timestamp, its status, the acknowledgment, and the correlation between request and response.

When a webhook arrives late, the system checks the order of statuses before applying it. A failed API call triggers a limited number of new logged attempts. After failure, the message joins an exceptions queue assigned to a responsible party. This person corrects the cause, validates the data, and restarts the same process without creating a new order. Shopify for example, does not guarantee that webhooks arrive in order.

Stock reconciliation between ERP and WMS compares, at a defined cadence, the physical quantities from the WMS or 3PL to the numerical quantities from the ERP or OMS. The analysis isolates the discrepancies by SKU, location and status. The team then searches for the missing event, and records any approved adjustment with its reason and author.

Connecting an existing ERP to an outsourced warehouse

The framing of exchanges


Start by inventorying the systems, interfaces, files, channels, identifiers, and manual operations. Add the stock rules, carriers, returns, and dependencies that could interrupt the flow.

The mapping sheet must cover the SKUs, barcodes, units, locations, and stock statuses. It also includes the identifiers for orders and lines, addresses, carrier services, tracking, cancellation and return reasons. Add lots or serial numbers when the scope requires them.

 

For each exchange, document:

  • the trigger and the flow direction;
  • the frequency or event;
  • the authentication and validations;
  • the error owner;
  • the proof of receipt.

 

A complete test starts from an order created in the ERP. It must reach the WMS with the correct lines, reservations, and instructions. After preparation, the WMS returns the shipment, tracking, and any noted discrepancies.

 


The operating contract between the company and the 3PL


The operating contract describes the responsibilities that begin after commissioning. It sets the owners of alerts, the escalation channels, processing schedules, and evidence to retain. It also specifies who can correct an item, replay a transaction, or approve an adjustment.

The reconciliation of inventory between ERP and WMS must be included in this system with its frequency, format, and approval process. The Shopify, WooCommerce, or Odoo environments require a verification suitable for the versions and modules used. The article on connecting Shopify, WooCommerce, and Odoo to a 3PL provides additional information for these configurations.

Migrating to a new 3PL without losing control of the flows

Audit, requirements, and mapping


The initial audit covers contracts, exit conditions, and operational dates. It lists the systems, connections, channels, volumes, identifiers, stock rules, and responsibilities. It also determines which historical data must remain accessible.

The requirements of the new 3PL specify the mode of exchange, whether it is API, EDI, or files. They cover authentication, technical limits, the testing environment, and expected processing times. They describe the management of cancellations, breaks, returns, inventories, and escalations.

The versioned mapping sheet associates the SKUs, barcodes, statuses, locations, orders, lines, carrier services, tracking, and addresses. For each API field, it indicates the format, null values, transformations, and rejection rules.

Example: changing logistics provider in Switzerland

A company uses Shopify and wants to entrust its orders to a new warehouse. Before the change, it checks which orders are still being processed by the old provider and which can be transferred. It also checks the available stock in the new warehouse to avoid duplicate orders, stock errors, and missing shipments.

▣ Phase

▤ Deliverable / control

◉ Pilot

✓ Validation

⇄ Plan B

▣ Audit

▤ Inventory of systems, contracts, flows, and dependencies

◉ Company

✓ Scope validated by the managers

⇄ Temporary maintenance of existing flows

▣ Requirements

▤ Specification of exchanges and exceptions

◉ Company and new 3PL

✓ Roles and cases validated

⇄ Reduction to the controllable scope

▣ Mapping

▤ Versioned sheet of fields and statuses

◉ Integrator and data managers

✓ Samples transformed unambiguously

⇄ Return to the previous version

▣ Control

▤ Physical and digital inventory reconciled

◉ Company, old and new 3PL

✓ Discrepancies resolved or explicitly reported

⇄ Stock maintained under control of the old system

▣ Tests

▤ Results of end-to-end scenarios

◉ Integrator / Operations

✓ Expected cases and errors handled

⇄ Correction then new campaign

▣ Cutover

▤ Journal over and validations

◉ Designated over director

✓ Decision criteria met

⇄ Stop new flows and manual procedure

▣ Post-launch monitoring

▤ Table of orders, inventory, and exceptions

◉ Joint operation

✓ Events monitored and incidents assigned

⇄ Controlled replay and targeted reconciliation

Stock transfer, over and fallback plan


Before the transfer, the parties establish a signed physical inventory and a digital stock by status. They list the goods in transit, open orders, and pending returns. Each discrepancy must be resolved or deferred with an owner and a documented decision.

The tests cover B2C, B2B, marketplace, and multi-line orders. They also check for insufficient stock, partial delivery, cancellation before or after preparation, return, duplicate, and API error. Carrier tracking and cross-border passage are added when the flow uses them.

The cutover provides for a limited freeze on changes to the catalog or inventory. A final controlled export feeds the new organization. The flows are gradually activated after validation of the acceptance criteria.

The fallback plan names the person authorized to stop the exchanges. It designates the source of truth during the incident and describes the temporary manual processing. It lists the orders to replay, the data to reconcile, and the condition that allows for resumption.

The integration of e-commerce orders with a 3PL provider must allow a message to be resent without duplicating its effect. It must also retain proof of each receipt and each correction.

Example: transfer to a new warehouse in Switzerland

A company transfers 2,000 items to a new logistics provider. Before the change, it checks the quantities and the orders still in progress. During the transfer, it temporarily suspends certain operations to avoid stock errors.

After commissioning, it places several test orders to verify that the items are prepared, shipped, and tracked correctly. If a problem arises, it suspends new exchanges and uses the backup procedure until it is resolved.

 

 

Acceptance criteria and monitoring after launch


The migration must reconnect each channel and each intermediate tool. The rules specific to marketplaces and the custom integrations require appropriate testing, as this 3PL change checklist reminds us.[3].

After the launch, check each day the orders transmitted, accepted, prepared, and shipped. Track exceptions, their age, stock discrepancies, missing tracking, and unresolved returns. The acceptable threshold depends on the volume, service level, and the consequences of each anomaly.

An acceptance criterion must be measurable in the logs or systems. It may require that a test order appears with its correct lines, that a partial shipment is reported without closing the remaining lines, or that a duplicate is rejected without side effects.

2 orchestration scenarios to adapt to your architecture

Scenario A: multichannel merchant with outsourced inventory


This illustrative scenario concerns a merchant who sells on Shopify, via a B2B channel and on marketplaces. An ERP manages the management data, while an OMS or middleware coordinates the exchanges. The physical stock is located in a warehouse operated using an outsourced WMS.

 

The flow in corridors follows this sequence :

  1. Shopify, B2B or marketplace → OMS/middleware : creation and control of the order.
  2. OMS/middleware → ERP : management recording according to the chosen rule.
  3. OMS → WMS/3PL : reservation, allocation and preparation request.
  4. WMS/3PL → carrier : package and shipping instruction.
  5. Carrier → OMS/middleware : tracking and delivery.
  6. OMS/middleware → ERP and channels : statuses, quantities shipped and availability updated.
  7. Channels → OMS → WMS/3PL : return request and processing.

 

The company must decide whether the OMS or the ERP holds the reservations. It must then publish a common availability for the three channels, with appropriate thresholds or allocations. Each channel consumes this value without rebuilding its own calculation.

Any research into Shopify-Odoo integration in Switzerland or an OMS solution for e-commerce in Switzerland must begin with this decision regarding responsibility. Technical compatibility comes next, along with an analysis of versions, modules, and interfaces.

For a specific marketplace flow, the Shopify–Galaxus–WMS integration guide presents a complementary case.

 


Scenario B : change of Swiss logistics provider


A European distributor is keeping its ERP and e-commerce site but is replacing its Swiss 3PL. The company makes the business decisions and approves the scope. The integrator maps the interfaces, transforms the data, and organizes the tests. The former 3PL provides export data, inventory, and open order statuses. The new 3PL prepares the environment, imports product listings, and executes the agreed-upon scenarios.

 

The project follows this order :

  1. audit of contracts, data, flows and responsibilities ;
  2. export and mapping of items, orders and stocks ;
  3. inventory physical and discrepancy resolution ;
  4. tests parallel without double physical execution ;
  5. switch to acceptance criteria ;
  6. activation of the fallback plan if necessary ;
  7. monitoring of orders, inventory, tracking, and returns.

 

Emaloja is proficient in WordPress with WooCommerce, Magento, Shopify, and Odoo as part of its expertise CMS. The feasibility of a project, however, depends on the architecture, versions, and available interfaces. Research on the services of order management system integration must therefore be translated into verifiable requirements rather than a simple list of software.

Commissioning checklist and choice of an integration partner

Go-live checklist


Before allowing commissioning, check the following points :

  • validated data sets ;
  • approved and versioned mappings ;
  • tested idempotency keys ;
  • access and authentication verified ;
  • active alerts ;
  • assigned exception queue ;
  • successful end-to-end tests ;
  • repeated fallback procedure ;
  • reconciled inventory ;
  • reachable decision-makers.

 

Each item must produce evidence, such as a test result, a named validation, or a log entry.

 


Questions to ask a technical and logistics partner


Ask how the interfaces are documented and what testing environment is available. Check the recovery mechanisms, the event logs, and the management of duplicate messages. Clarify the shared stock rules, returns, and written responsibilities.

For a Switzerland–EU flow, ask who provides, validates, and transmits cross-border data. Also clarify the handover between the warehouse, the carrier, and the business systems.

Emaloja can act as a partner linking sales channels, enterprise systems, and logistics operations. Its proven services include, in particular, ERP integration, maintenance, and security for e-commerce sites. For physical fulfillment, Emaloja draws on the supply chain expertise of its parent company, STAR Logistique.

Next steps to secure your architecture

Start by establishing the data ownership matrix. Then map the events, fields, acknowledgments, and conflict rules. Test the exceptions, reconcile the stock, and document the cutover with a fallback plan. Finally, designate the responsible parties authorized to accept, interrupt, or resume the flows.

The E-commerce–WMS Guide provides an in-depth look at the operational connection between the website and the warehouse. The B2B Guide to Selecting a Fulfillment Provider helps evaluate the technical capabilities of a 3PL.


Operational continuity relies on data for which the owner, update rules, controls, and exception handlers are explicitly defined.

eCommerce Integration in Switzerland: ERP, OMS, WMS & 3PL
Lazhar Cader November 16, 2026
Share this post
Archive