Real‑Time eCommerce & WMS Integration for Swiss Spare Parts

In October 2026, parts distributors often have to manage extensive catalogs across multiple sales channels (Read the study on the Trends in omnichannel commerce in 2026 from the University of St. Gallen).

Bolomey Repuestos, a leading French distributor of automotive parts in Chile, has, for example, accelerated order preparation, reduced customer wait times, and implemented next-day delivery thanks to SAP and WMS technologies. Read the case study " Bolomey streamlines order preparation and next-day delivery thanks to SAP Business One ".

Emaloja is particularly suitable for companies facing this depth of catalog and the resulting logistical operations.

A part may appear in stock while already being reserved, immobilized, or allocated to another order (see the WM interface with SAP's IM stock management). Therefore, the physical quantity is not sufficient. The distributor must define the actually sellable stock, and then apply this definition to each channel.

An inaccurate data can lead to an unfulfilled order, a backorder, or a reassignment from another site. The team must then contact the customer again and correct the statuses in several systems.

The approach of the Integration of e-commerce and warehouse for the distribution of spare parts in Switzerland addresses this risk through a centralized and coherent management. It links catalog data to stock, preparation, shipping, and return operations.

Read how Swisslog automates the management of confections for Mondelēz for a larger-scale integration example.

A WMS (Warehouse Management System) is software that controls warehouse operations, from receiving to shipping. It tracks stock movements, organizes locations, and guides order preparation, as explained by this WMS definition [1].

E-commerce and WMS integration connects business activity to logistics activity. It creates a common flow for orders, stocks, preparation, shipping, tracking, and returns.

This scope must be distinguished from that of an ERP, a Order Management System (OMS), or a Transportation Management System (TMS). Their presence and role must be validated during the scoping.

The role of the WMS in the order chain

In the Emaloja model, the WMS receives information from sales channels and transmits it to warehouse operations. It thus allows for the automation of flows between order validation and its logistical processing.

The WMS also provides the necessary statuses for operational tracking. Teams can know if an order has been received, prepared or shipped, subject to the mapping defined for the project.

The WMS Emaloja supports real-time tracking of inventory and orders. For spare parts, this capability must rely on specific references and documented availability rules.

Read our Guide to ecommerce integration and warehouse management (WMS) in Switzerland for more information.

A common stock source for sales channels

The project must designate the system that holds the reference stock. This source determines the quantity published on the store, the marketplaces, and any potential private sales spaces.

The sellable quantity may depend on physical stock, reservations, and blocking rules. An item under control, assigned to an order or awaiting a decision after a return should not be treated as available without an explicit rule.

The integration aims to maintain consistent values between the channels. It does not exempt from anticipating cases of discrepancy, delay in transmission, or unknown reference.

A reliable integration starts with a mapping of the data. Each field must have an owner, a source system, a direction of synchronization, and an update rule.

Product data and cataloging rules to frame

The basic data to map includes:

• the part reference ;
• the commercial designation ;
• the variant ;
• the location in the warehouse ;
• the data necessary for publication on the channels ;
• the rules for creation, modification, and deactivation.

Some data specific to spare parts require a technical validation. This concerns compatibility with a vehicle or an equipment, reference equivalences, serial numbers, batches, and substitution rules.

The framing must also verify the handling of backorders and preorders. These functions should not be considered as available until their written confirmation.

Emaloja manages the locations of products in its WMS, the real-time stock tracking, and the organization of preparation and shipping. Its operation as a logistics center connected to sites and marketplaces helps to link the catalog information to physical operations.

Stock, order, shipping, and return data

The operational data to be synchronized covers availability, reserved stock, order, preparation status, and the tracking number. The model must also include the return reason and the restocking status.

Emaloja continuously tracks stock and allows adjustments to stock levels. The rules that trigger these adjustments must, however, correspond to the distributor's operations.

Returns belong to the same data model as the outgoing orders. Without this link, a returned item may remain out of sellable stock or return before the control decision.

Designate the system that holds the reference stock before developing the interfaces. Then document each field, its format, its source, its destination and its correction rule.

The flow must connect the commercial action to the physical operations. Each step produces a status that can be used to inform the sales channel, the warehouse or customer service.

From order validation to preparation

As soon as an order is validated on an e-commerce site or a marketplace, it is immediately processed in Emaloja's WMS. The system also updates in real time the stocks of the online store.

A typical flow includes the following steps:

1.      The e-commerce site or marketplace validates the order.

2.      The WMS receives the order and verifies the transmitted references.

3.      The necessary stock is allocated according to the project rules.

4.      The warehouse locates the parts and initiates preparation.

5.      The team prepares the package and produces the shipping elements.

6.      The package is handed over to the carrier and the tracking is updated in the flow.

7.      In the case of a return, the warehouse receives the part and records the processing decision.

The receipt of goods and the supply are coordinated to maintain availability. The triggering and priority rules remain to be defined according to the parts, suppliers, and relevant sites.

Emaloja also offers the cross-docking. This method ships a product after its arrival, without going through a traditional storage phase. Its use must be validated according to the necessary controls and the physical flow of the parts.

From shipping to return processing

After preparation, integration must associate the order with the package and the tracking number. Emaloja provides detailed tracking of shipments, without any assumption of update frequency or specific service level.

The return follows a distinct process :

• receipt of the returned part ;
• reconciliation with the initial order ;
• control according to the distributor's rules ;
• decision to restock or specific processing ;
• update of status and stock, if the part becomes sellable again.

The inspection criteria must be written before the launch. They may depend on the condition of the item, its packaging, its identification, or the stated reason, if the distributor retains these criteria.

The choice of channel influences the data to be exchanged and the necessary controls. The project must confirm each compatibility instead of deducing that a tool can be connected.

Stores, marketplaces and connectors

The documented options include the e-commerce site, the private store, and the intranet intended for a defined group of buyers. The channels supported by Emaloja also include marketplaces such as Digitec, Galaxus, Manor, and Galeries Lafayette.

A marketplace integration can establish a interface between the marketplace and the WMS. This interface serves to integrate the items and to track orders and inventory in real time.

The mentioned connection tools are Lengow, Iziflux, CommerceHub, Sellermania, and Mirakl Connect. Their compatibility with an account, a catalog, or a specific flow must be confirmed before the project.

API, files and synchronization rules

An API allows systems to automatically exchange data. It is suitable when the project requires frequent updates and reduces manual interventions, subject to the functions exposed by each system.

CSV or Excel imports give the team direct control over the transmitted files. They require a procedure to prepare, validate, load and correct the data.

The framing must answer the following questions:

• Which e-commerce system needs to be connected?
• Which marketplaces are involved?
• Is there already an ERP or WMS?
• Is a documented API available?
• What is the structure of each feed?
• What authentication is required?
• What update frequency is expected?
• Does an EDI protocol fall within the scope?

The integration method depends on the volume of updates, the degree of automation sought, and the team's ability to manage the imports. No ERP, EDI protocol, or additional connector should be announced as compatible without confirmation.

Emaloja has warehouses in Switzerland and France. The choice of the preparation site must take into account the destination, the physical presence of the part, and the cross-border flow applicable.

Storage, preparation, and shipping from the right site

The WMS coordinates the flow of goods between the warehouses to direct orders to an appropriate shipping location. The project must define the criteria for this direction without presuming a site or a timeline.

Inaccurate availability may prevent the intended site from preparing the part. The team may then need to reassign the order, create a backorder, or inform the customer that it cannot fulfill it according to the initial flow.

The choice of site must include:

• the mobilizable stock;
• the delivery destination;
• the applicable formalities;
• the selected carrier;
• the handling planned in case of return.

Emaloja emphasizes sustainable practices and route optimization. This direction may be included in the flow selection criteria, without constituting a guarantee of measured environmental results.

Customs, tracking and returns in cross-border flows

Emaloja's cross-border services include customs clearance, tax representation, and commercial domiciliation. The management of international deliveries and VAT issues must be integrated into the framework of flows between Switzerland, France, and the European Union.

Before launch, designate who prepares the customs documents, who validates the value and classification of goods, and who generates the labels. Also assign the reception of carrier events and the handling of international returns.

Responsibilities should not remain implicit. An operational matrix must specify the actor responsible for each decision and the system in which they record the evidence.

When a stock or order synchronization fails, the processing depends on the process defined in the project. No alert, reminder, or automatic recovery mechanism should be assumed without documentation.

Rules to define before production deployment

Business rules must cover situations specific to spare parts:

• reservation and release of stock;
• cancellation before or after preparation;
• processing of a backorder;
• substitution of a reference;
• priority of an urgent order;
• published availability threshold;
• quarantine of a disputed order;
• escalation to a designated person.

The Emaloja process aims to maintain consistent stock levels between the store, marketplaces, and the warehouse. This consistency depends on the quality of data, interfaces, and correction rules.

Anomaly handling procedure

An anomaly log must at minimum track:

• the order transmission status;
• the timestamp of the last synchronization;
• unknown references;
• stock discrepancies;
• duplicate orders;
• label generation failures;
• the absence of carrier event ;
• returns without order reference.

For each anomaly, document the owner, the level of priority, the data to verify, and the authorized action. Also specify if the channel should be blocked, corrected, or simply monitored.

Before going live, require a test scenario for each exception. The result must show the initial status, the injected error, the action taken, and the expected final state.

The cost and timeline depend on the technical and operational scope. No pricing, deployment timeline, synchronization timeline, order volume, or service level can be set without project data.

Information to gather before framing

Group the information into operational blocks:

• Sales channels: stores, private spaces, marketplaces, and covered countries.
• Catalog: number of references, variants, attributes, compatibilities, and data quality.
• Stocks and warehouses: sites, reference stock, reservations, and availability rules.
• Orders: statuses, cancellations, urgencies, backorders, and substitutions.
• Transport and returns: carriers, transmitted events, and return circuits.
• Compliance and reporting: flow Switzerland-France-European Union, VAT, customs, and required reports.

Emaloja services can cover the chain from import to storage, then to packaging, shipping, and returns. The scoping must determine the elements retained and the responsibilities kept by the distributor or other providers.

Questions to ask about the scope, timeline, and budget

The scoping request must explicitly answer these questions:

• Which sites, marketplaces, ERP, WMS, API or EDI exchanges are involved?
• Which system holds the reference stock?
• What frequency of synchronization is expected?
• What rules apply to errors?
• What are the order cut-off times?
• What carrier events are transmitted?
• How are returns received, checked, and closed?
• What reports need to be produced?

Add the number of channels, the number of references, the structure of variants, and the state of the data. Also describe the flows between Switzerland, France, and the European Union, the carriers, and the reporting needs.

These elements help define the development, testing, data recovery, and operational organization. The budget and the schedule can then be assessed based on this scope.

The indicators serve to verify the actual functioning of the integration. They must rely on identified data and stable formulas.

Stock, order, and delivery indicators

KPIs can be defined as such, without imposing a numerical objective:

• Stock accuracy: match between controlled stock and reference stock.
• Availability gap: orders or references showing a difference between displayed quantity and available quantity, reported to the observed scope.
• Transmission time: time between validation on the channel and receipt by the WMS.
• Share of exception orders: orders in anomaly reported to received orders.
• Preparation time: time between receipt in the WMS and completion of preparation.
• Tracking coverage: shipments with expected events reported to tracked shipments.
• Return rate: returns received reported to shipped orders or lines.
• Restocking time: time between receipt of return and stock decision.

For spare parts, add the backorder rate, the emergency processing time, and the frequency of unavailable references. The quality of compatibility data can also be tracked if this information exists.

Evidence to request for assessing service quality

Real-time order and inventory tracking is a documented capability of the WMS Emaloja. Its operation within the defined scope must be verified before and after the launch.

Request textual evidence or anonymized tables:

• a complete example of order flow;
• a synchronization log;
• a reconciliation between published stock and reference stock;
• a shipping event associated with an order;
• a return sample and its final decision;
• a dashboard with the sources used.

No available data allows for announcing stock accuracy, processing speed, tracking coverage, or a measured service level. These indicators should therefore be treated as criteria for management to be constructed and verified.

An e-commerce and WMS integration for spare parts relies on a few documented decisions:

• designating the system that holds the reference inventory;
• mapping product, order, shipping, and return data;
• defining how to handle each error and exception;
• organizing workflows between Switzerland, France, and the European Union;
• measuring performance using KPIs and verifiable evidence.

The Emaloja WMS links inventory management to order fulfillment, shipping, and real-time tracking. The exact scope of each workflow depends on the selected channels, data, and operations.

Prepare your scoping checklist, then contact Emaloja to assess your parts workflows, sales channels, and cross-border requirements.