ERP and WMS Integration for Swiss Watchmakers

An ERP (Enterprise Resource Planning software) generally manages the data financials, purchasing, production, orders, and stock value. A WMS (Warehouse Management System) organizes the physical operations, including receiving, stocking, transfers, picking, packing, and shipping. Read how a WMS works.

The 2 systems have different responsibilities. Their integration allows the WMS to execute physical operations while transmitting to the ERP the movements necessary for financial and commercial management. A manufacturer can therefore connect a WMS to its existing ERP without automatically engaging its replacement.

Operational gains can be measured. After the deployment of a mobile solution directly integrated with SAP WM, Watches of Switzerland reduced picking errors by 92%, increased stock accuracy by 28%, and accelerated picking by 25%, according to the case study of Watches of Switzerland [1].

Watchmaking adds several constraints to this integration:

• the individual traceability of watches and movements;
• the numerous variants of dials, cases, bracelets, and components;
• the management of precious metals;
• the proof of origin and Swiss added value ;
• the operations entrusted to subcontractors;
• the availability of spare parts for a long duration.

These requirements imply unit management, rather than simple quantity management. Each event must link a physical object to a reference, a serial number, a location, a document, and a status. The data must also cover authenticity, warranty, and installed components, as described in this ERP presentation for watchmaking and precision industry [2].

The operational objective is therefore to maintain a unique and usable data point for each unit and each movement. The synchronization of quantities becomes a consequence of this traceability, rather than its sole purpose.

The target architecture must assign a clear responsibility to each system. It must also define how events flow, how errors are detected, and how a transaction can be replayed without producing duplicates.

Roles of the ERP, WMS and integration layers

The ERP remains the reference system for financial data and stock value. The WMS holds the operational detail necessary to know where a watch is, which operator handled it, and what logistical task remains to be executed.

A production tool, often called MES for Manufacturing Execution System, can complement this architecture. It collects manufacturing declarations, component consumption, and control results before transmitting the end of production. Read What is a Manufacturing Execution System (MES)? by Visiativ.

The integration layer connects these systems. It transforms a receipt, a transfer, or an adjustment into native ERP objects and maintains an audit trail. It must produce clean and idempotent transactions. An idempotent operation does not create any duplicates when an incident forces the system to replay it.

The depth of an integration is therefore not only measured by the existence of a programming interface, or API. It also depends on the quality of transformations, idempotence, and visibility on queues, delays, and errors.

References, identifiers, and data ownership rules

Before any development, define the master identifiers that the systems must share:

• the item reference and its variant;
• the watch's serial number;
• the movement's serial number;
• the batch, when applicable;
• the location;
• the quality status;
• the manufacturing order;
• the sales order;
• the return;
• the carrier and the shipping reference.

Each piece of data should have only one master system. For example, the ERP can control the item reference and the order, while the WMS controls the operational location. Other systems receive the relevant data without being free to modify it.

This rule reduces conflicts. It also allows for deciding which value prevails when a sales channel, the WMS, and the ERP temporarily present different information.

Event flows and exception management

The target flow can be described as follows:

1. Manufacturing Order : the ERP creates the order and transmits the necessary data to production.
2. Unit Assignment : the MES or ERP associates the serial numbers with the watch and its movement.
3. End of Production : the production system confirms the quantity, the units and their quality status.
4. WMS Reception : the WMS checks the expected identifiers and assigns a location.
5. Reservation : a validated order blocks the available unit.
6. Picking and Packing : the WMS verifies the match between the order, the reference, and the serial number.
7. Shipping : handing over to the carrier triggers commercial and financial updates.
8. Potential Return : the WMS places the unit in a distinct status until inspection.

The integration layer must handle ownership conflicts, rejected transactions, queue delays, and restarts. Each event retains an identifier, a timestamp, its origin, its result, and the reason for any potential rejection. These elements allow the IT team to correct the error without inventing a manual movement that is difficult to auditing.

A serial number tracking system captures, stores, searches, and retrieves the unique identifiers of units purchased, manufactured, transferred, sold, or serviced. This definition covers the physical and documentary lifecycle of the watch.

In watchmaking, traceability also connects the finished product to its movement, its components, its customer, and its service history and eliminates the risk of counterfeiting. It supports the warranty, proof of authenticity, the fight against counterfeiting, and the analysis of a defect.

The unit register of each watch and each movement

Each watch can have its own serial number (see the example of Oris), while its movement carries another identifier. The unit register must maintain the relationship between the two, including when a movement is replaced during a repair.

An actionable unit record contains, in particular:

• the reference and the variant ;
• the watch's serial number;
• the movement's serial number;
• the installed serialized components ;
• the quality status and the logistics status ;
• the current location ;
• the production, sales, and transport documents ;
• the history of interventions.

The canonical register, that is to say the official version, must reside in the chosen master system. Mobile applications and interfaces submit transactions without creating their own concurrent versions of the history.

The capture points to secure

Traceability must cover events that change the state, location, or responsibility of a unit:

• manufacturing and assignment of the serial number ;
• receipt ;
• stocking ;
• transfer ;
• picking ;
• packaging ;
• shipping ;
• return ;
• service or repair.

Each event associates the serial number with a location, a document, and the user or system responsible. This structure facilitates the search for a watch and the explanation of its journey.

Upon receipt, the WMS reads the serial number, compares it to the expected order line, and checks its format. It then looks for a potential duplicate before any writing in the master data. These checks are part of the practices described for managing serial numbers [3].

Upstream, aval and after-sales traceability

Upstream traceability links the finished watch to supplier batches, components, and production operations. See the tracking example of warranty, digital passport, and lost or stolen watch from Vacheron Constantin. It helps identify the units affected by a defective component or a problem detected at a subcontractor.

Downstream traceability links the serial number to the recipient, the order, and the shipment. It allows for the containment of a recall and the retrieval of proof of delivery.

After-sales extends this record. Each diagnosis, repair, component replacement, and final check enriches the history of the watch. A removed part should not disappear from the audit trail, even if it is no longer part of the active configuration.

To audit a serialized event, check at a minimum :

• the serial number ;
• the reference and the variant ;
• the date and time ;
• the departure and arrival location ;
• the associated document ;
• the status before and after the operation ;
• the user or the responsible system ;
• the reason for a correction.

The stock published on an e-commerce site must not mechanically correspond to everything in the warehouse. The calculation must exclude reserved watches, blocked by quality, in transit or under review after a return. 

Real-time synchronization broadcasts confirmed events as soon as they change availability. Forecasting remains a distinct layer. It helps anticipate needs, but it never replaces a validated transactional movement.

Events that modify the available stock

Systems must immediately broadcast the following events :

• validated receipt ;
• production completed ;
• transfer between locations or sites ;
• order reservation ;
• picking ;
• shipping ;
• cancellation ;
• return.

Each event indicates the concerned unit, the quantity, the status and the original document. A reservation reduces the available stock for sale without immediately modifying the physical stock. Shipping then removes the unit from the held stock.

Real-time stock visualization and trend analysis help anticipate order volumes, reduce stockouts and better allocate resources. The functions of stock optimization through artificial intelligence can support this analysis, as long as confirmed transactions are kept as operational truth.

The stock statuses to share between systems

A clock model can distinguish :

• physical stock : units present in a controlled location ;
• reserved stock : units allocated to an order ;
• stock available for sale : units publishable after deducting reservations and blocks ;
• quality control stock : units present but not marketable ;
• in transit stock : units moved between two sites or entrusted to a carrier ;
• returned stock : units received after delivery and awaiting decision.

This model must be adapted to the processes of the manufacture. The availability calculation must be identical in the ERP, the WMS and the sales channels, even if each system displays a different level of detail.

Emaloja's advanced WMS provides a real-time visibility on stocks and orders. This visibility can feed the e-commerce activities when the availability rules and data responsibilities have been defined.

The consistency checks and reconciliation

Each message must carry an event identifier and a timestamp. The receiving system sends an acknowledgment, while the integration layer retains the processing result.

Rejected transactions must join a visible queue, with an actionable reason. The responsible team can then correct the data or replay the event. The idempotence mechanism prevents this replay from creating a second receipt, reservation, or shipment.

A periodic reconciliation compares :

• physical units and recorded units ;
• ERP and WMS statuses ;
• reservations and active orders ;
• sent and received events ;
• serial numbers and their locations ;
• adjustments and their supporting documents.

These controls detect a drift before it reaches the customer or accounting.

The ERP-WMS integration organizes the handoffs between production, quality, warehouse, and transport. A watchmaking WMS can also integrate with the ERP and production machines to exchange data and improve visibility across the supply chain, as illustrated by this WMS for the watchmaking sector [4].

From the manufacturing order to stock entry

Let’s take the hypothetical case of a watch produced in Switzerland. The ERP creates a manufacturing order with the reference, variant, and expected components. The production system assigns the serial numbers of the watch and the movement.

At the end of manufacturing, the operator declares the unit finished. Quality can then release it, block it, or request a rework. Only a released unit joins the available stock.

The WMS then receives the watch, validates its identity and assigns a location. The stock confirmation returns to the ERP with the serial number, status, and movement reference.

From order to secure shipping

A validated order reserves an available unit. The WMS generates a picking task that requires reading the reference and the serial number.

The packaging associates the unit with the package and the shipping document. Handover to the carrier provides the necessary proof for the status change. Emaloja coordinates operations from order validation to delivery, with shipment tracking, packaging, and labeling in its e-commerce logistics.

For high-value items, plan for the following checks:

• matching between the reference and the serial number;
• scan at each sensitive transfer;
• restriction of adjustment rights;
• mandatory justification of discrepancies;
• immediate consultation of unit history;
• proof of handover to the carrier.

Returns, checks, and availability reinstatement

A return should not be directly reintegrated into the sellable stock. The WMS receives the unit in a distinct status and verifies the serial number, condition, accessories, and associated documents.

The check then determines the processing: restocking, repair, quality blocking, return to supplier, or other authorized decision. A watch reinstated for availability must retain its return history.

Before any interface development, map each event, its owner, its master system, and the starting and ending statuses.

A reliable integration relies on clean data, trained operators, and tested exception procedures. A gradual migration limits operational exposure and provides observable results before expanding the scope.

Framing and data quality.

Start by auditing the item repositories, the variants, the locations, the statuses, and the existing serial numbers. Look for duplicates, missing fields, and differences in coding between systems.

Then define the data responsibilities. For each object, specify the master system, the consuming systems, the modification points, and the handling planned in case of conflict.

Select the priority flows based on their operational risk. Receiving, stocking, reserving, and shipping often constitute a coherent scope for tracking a unit from end to end.

Pilot on a serialized scope.

Choose a family of watches or serialized parts with a manageable volume. The pilot must cover normal operations and the errors that require intervention.

Test at a minimum:

• a duplicated serial number;
• an item placed in the wrong location;
• an interrupted shipment;
• a cancellation after reservation;
• a return with a non-compliant status;
• a temporary interface failure;
• the replay of an event that has already been processed.
• 
  

The pilot also checks the readability of the screens, the quality of the scans, and the operators' ability to understand a rejection.

Testing, deployment, and continuous improvement

The testing validates the functional rules, security, the recovery after an incident, and the audit trail. It must also confirm that the ERP, WMS, and e-commerce transactions remain consistent after each scenario.

The deployment requires enhanced monitoring of the queues and exceptions. Teams must know the responsibilities and correction procedures before the actual flow opens.

Follow indicators that describe reliability:

• scan error rates;
• inventory discrepancies;
• failed events;
• exception processing time;
• unit traceability accuracy;
• preparation time.

The case Watches of Switzerland provides an example of a measurable scope. Mobile transactions directly fed SAP in real-time for receiving, physical inventory, stock consultation, and picking. Each manufacturer must set its own objectives according to its flows and risks.

Emaloja acts as a partner for e-commerce logistics and Fulfillment. Its role complements the manufacturer's ERP, without replacing it.

Emaloja covers supply chain management, from import to returns, including storage, packaging, and shipping. This coverage is presented on the dedicated page for Emaloja.

Its WMS consolidates order, inventory, and returns management into a single digital interface. This organization is suitable for flows from multiple channels, including the marketplaces in Switzerland.

Emaloja also handles storage, order processing, and inventory management in warehouses located in Switzerland, France, and Europe. Emaloja's storage logistics can thus support an organization that distributes its inventory across multiple markets.

For sales between Switzerland and the European Union, the operations must integrate transportation, storage, and customs formalities. The cross-border services of Emaloja also include customs clearance and tax representation.

The implementation depends on the ERP, data model, and available interfaces. Technical validation is still necessary before confirming the integration scope with a specific watchmaking ERP. This approach addresses the need expressed by the search for Integration between the ERP and warehouse management systems for Swiss luxury and watchmaking brands, with particular attention to serialized units.

To build an integration suitable for watches and high-value parts, keep the following decisions in mind:

• assign a master system to each data;
• link watches, movements, and components to serialized identifiers;
• broadcast confirmed events in real time;
• separate the physical stock, reserved, available, blocked, in transit and returned ;
• anticipate rejections, returns and reconciliation from the design stage ;
• start with a pilot and measure errors, the variances and processing times.

Research such as How to synchronize the ERP and the warehouse stocks for watch manufacturers? or The best inventory management integration solution for spare parts distributors refer to the same principle: each movement must remain traceable between the financial system and the physical operation. This logic also applies to ERP integration for inventory management and traceability in the pharmaceutical sector in Switzerland, even if the sectoral rules and the data to be controlled differ.

For a brand looking for a logistics service provider for luxury ecommerce in Switzerland, the decision must focus on the quality of flows, stock visibility and exception handling. Evaluate with Emaloja your exchanges between the ERP, production, the warehouse and sales channels to define a verifiable integration scope.