In October 2026, a multichannel sale can change the availability of a product across multiple systems. An order placed in Switzerland must reach the warehouse, reduce the publishable stock, and update the other channels. If this chain breaks, the merchant risks selling a unit that no longer exists. A reliable synchronization thus connects the commercial data to the logistical execution, from the order to the return.
Why a stock discrepancy becomes a business risk
65% of respondents consider stock accuracy to be an important or critical priority. However, less than 22% exceed 80% compliance on each of the fundamental indicators according to a study by IHL.
Imagine there is only one unit left in the warehouse. A customer buys it on a marketplace, while the e-commerce store continues to show it as available. A second order arrives before the stock update. The team must then cancel a sale, offer another solution, or wait for a restock.
This discrepancy arises when the listing, the physical stock, and the order rely on different data. It can cause cancellations, delays, and a loss of ranking on the marketplace, as explained by the page dedicated to marketplaces by Emaloja.
The risk increases with each added channel. A merchant from Switzerland can sell on their own site, on multiple marketplaces, and from stocks located in Switzerland or in the European Union. A manual correction in each interface does not guarantee either consistency or the order of events.
The operational question becomes simple: how to manage the same availability between the store, the marketplaces, and the warehouse, while maintaining consistent orders and statuses?
Define the stock synchronization and order management
A WMS (Warehouse Management System) is warehouse management software that controls stock and order flows. An OMS (Order Management System) is an order management system. Emaloja integrates stock software, OMS, and automation technologies into its e-logistics processes.
A marketplace integration connects the catalog, the stock levels, the orders, and the shipments. It connects one or more marketplaces to the e-commerce site and the WMS. This architecture concerns active sellers in Switzerland as well as cross-border operations.
A unique operational source for stock
Stock synchronization calculates the available quantity, and then publishes it to the connected channels. The calculation can take into account the physical stock, already reserved units, authorized locations, and any safety stock. Read the stock synchronization of Microsoft with Shopify.
The stock synchronization on marketplaces for e-commerce must rely on an authoritative system. In a flow driven by the warehouse, the WMS records physical movements and reservations. Other systems then consume the calculated availability instead of maintaining their own quantities.
2 complementary, but distinct flows
Order management covers capture, validation, preparation, shipping, tracking, cancellations, and returns. The integration of order management on marketplaces for e-merchants organizes the flow of this information between channels, the OMS and the WMS.
The 2 flows interact when an order reserves a unit. However, they maintain different responsibilities: the stock flow answers the question "how much can we still sell?", while the order flow indicates "what needs to be processed and in what condition?".
Reliability therefore relies on a unique operational reference, rather than on manual changes in each dashboard.
How a sale updates all connected channels
From the purchase click to the stock reservation
The flow begins when a customer confirms an order on a connected channel. The integration retrieves the order reference, the products, and the quantities. It then checks the order status and availability before transmitting the relevant data to the WMS.
The operation of stock synchronization describes an automatic transmission of the order to the WMS. It reserves or reduces the quantity in the warehouse record. The revised availability then goes back to the store and the connected marketplaces.
The term "real-time" here refers to a chain triggered by received events: sale, reservation, physical movement, or status change. It does not, by itself, guarantee universal latency. The observed delay also depends on the channel, its interface, and error handling. Shopify recommends, for example, to plan for the processing of webhooks arriving with a 24-hour delay (error handling).
From preparation to tracking and returns
After validation, the WMS receives the references and quantities necessary for preparation. The warehouse performs picking and packing, then the shipping status and tracking are sent back to the relevant systems.
A cancellation or return follows a defined rule. The system records the event, determines if the item can become available again, and adjusts the publishable stock when the conditions are met. Emaloja connects its WMS to the marketplaces to manage orders, returns, and the tracking of stock. Its Marketplace Pack provides real-time tracking of stock and orders through a dedicated WMS.
🔄 Step
📥 Event
🖥️ System
✅ Update
🔄 Order
📥 Reference, products and quantities ordered
🖥️ Marketplace and integration
✅ Order transmission
🔄 Validation
📥 Order status and availability
🖥️ OMS or integration flow
✅ Order validated for processing
🔄 Stock adjustment
📥 Reservation or quantity reduction
🖥️ WMS
✅ Warehouse stock adjusted
🔄 Publication to channels
📥 Revised availability
🖥️ WMS and integration
✅ New quantity sent to channels
🔄 Preparation
📥 References and quantities to pick
🖥️ WMS
✅ Picking and packing recorded
🔄 Shipping/ return
📥 Status, tracking, cancellation or return reason
🖥️ WMS, OMS and integration
✅ Status updated and stock rule applied
Before activation, document which system decides the available quantity and which receives each order status.
Technical rules that prevent availability discrepancies
Product references, reservations and safety stock
An integration cannot correct ambiguous references. Each variant must match the correct product in the site, the marketplace, the OMS and the WMS. Internal SKUs and EAN or GTIN must therefore be associated without confusion.
The availability rule must also specify when a unit becomes reserved. Depending on the chosen process, the reservation may occur at validation or during transmission to the WMS. This decision must remain consistent throughout the chain. Note that Shopify has announced a change in its inventory statuses: the quantities associated with certain provisional orders, transfers, and shipments change from reserved to committed.
A safety stock can absorb the gap between a warehouse modification and its publication on a channel. Its level depends on the items, movements, and business constraints. No single threshold fits all flows. Microsoft recommends a scheduled synchronization every 15 to 30 minutes with Shopify for example.
Before activation, check the following items:
- SKU, EAN or GTIN matching and variants
- Source of truth for available stock
- Reservation and release rules
- Safety stock by channel or location
- Triggered by event or defined frequency
- Logging, error handling, and reconciliation of statuses
Exceptions, duplicates, and status control
A marketplace can transmit the same event multiple times (see how Shopify detects duplicates). The integration must then check the order ID before creating a reservation. This idempotence rule prevents a repeated delivery from producing 2 movements. It must be validated during project design, as its activation cannot be assumed.
Order, shipping, cancellation, and return statuses must also have the same meaning in the marketplace, OMS, and WMS. The order flow documented by Emaloja covers the capture, validation, the synchronization of stock, preparation, shipping, and recording of returns or cancellations.
Define a procedure for unknown references, rejected quantities, and events that occurred in the wrong order. The log must allow for identifying the order, the channel, the received state, and the action executed.
Before launch, test at minimum the case of the last unit, a cancellation after reservation, and a return that may put the item back in stock.
What Switzerland adds to the flows between warehouse, marketplace, and customer
Operations between Switzerland, France, and the European Union do not stop at the publication of a quantity. Integration must link the stock to its location, to logistics execution, to the delivery promise, and to the return circuit.
Emaloja directly connects the WMS to the channels for companies selling in Switzerland, France, and the European Union. The device includes automated flow tools and a cross-border logistics. Emaloja also has warehouses in Switzerland and France as part of its marketplace offering.
The location of the stock influences the processing of the order. 2 identical units placed on each side of the border do not necessarily follow the same path. The system must send the order to the chosen location, then publish availability consistent with this decision.
Customs clearance must enter the process when it applies. It is then necessary to plan the required data, the role of each participant, and the handling of a cross-border return, without confusing technical integration with legal or tax advice.
Associate each published stock with its logistical location, the applicable delivery rule, and the planned return path.
Frequently Asked Questions
Emaloja can connect an e-commerce site, marketplaces, an OMS, and a WMS to circulate stocks, orders, and statuses. The connections depend on the channel and can use an automated connector, an API, or a suitable import flow for the project.
Run a test order, then timestamp its receipt, its reservation in the WMS, and the update of each channel. Also check the error logs and trigger a voluntary failure to verify the alert, the recovery, and the reconciliation of the data.
Key points for a reliable multichannel launch
A reliable launch depends on three conditions: a reference stock managed by the WMS, consistent order flows, and tested exception rules. These foundations reduce manual decisions and make each event traceable.
Emaloja offers automated connectors to Digitec, Galaxus, and Manor. Depending on the need, the integration can go through an API or a manual import.
Before any online launch, have your sources mapped of stock, your channels, your order statuses, and your return flows. This mapping allows you to define the responsibilities of each system before the first real movements.