The average duration of ERP use in Switzerland is 18 years and Acabus represents 17% of the Swiss ERP market according to It Markt.
How can these figures be explained? Information on stock, batch, or shipment transmitted too late can break the link between the physical item and its order. The WMS, or warehouse management software, executes the physical movements while the ERP retains the commercial and management data.
An ERP integration for tracking batches and serial numbers must therefore define the necessary data and controls, from receipt to return.
Galexis, a subsidiary of Galenica, has achieved an automation rate of over 70%, up to 5 times faster, with about 10,000 references in its logistics center in Lausanne-Écublens after the introduction of a new SAP system in 2025. This transformation has also strengthened the traceability of batches and the control of shipments.
This approach also concerns the flows between Switzerland, France, and the European Union. The WMS of Emaloja allows for inventory management and real-time order tracking.
Batches and serial numbers : two levels of traceability to distinguish
The difference between unit tracking and group tracking determines the expected precision of the integration [1].
Batch tracking
A lot groups together items that share attributes, such as a manufacturing date or a lot number. It allows tracking of due dates, movements, and recalls concerning a group.
This model is suitable when the company needs to isolate a homogeneous set. Each movement must then retain the identifier of the concerned lot.
Note that since July 2026, manufacturers and importers must register certain medical devices in the Swiss database swissdamed. They have until the end of December 2026 to complete this registration.
Tracking by serial number
A serial number identifies a specific item and allows tracking its lifecycle. It is particularly used to locate a unit during a return, quality control, or recall.
The ERP and WMS must preserve this individual identity in each transaction. The technical scope must confirm the formats that both systems accept.
📋 Criterion
📦 Lot
🔢 Serial No.
🔄 ERP–WMS
📋 Tracked unit
📦 Group of items
🔢 Individual item
🔄 Define the unit to isolate
📋 Identification data
📦 Lot, common attributes, potential expiration
🔢 Unique identifier
🔄 Map the fields in both systems
📋 Operational use cases
📦 Expiration, quality, grouped recall
🔢 Lifecycle, return, targeted recall
🔄 Retain the identifier during each movement
📋 Level of required precision
📦 Group
🔢 Unit
🔄 Adapt controls to the reference
Define the traceability rule for each product reference before configuring the flows.
Which data to synchronize between the ERP and the WMS
Mapping, that is, the correspondence between fields, must cover:
- SKU and product description
- Lot, serial number and expiration date
- Quantity, location and stock status
- Order and shipping status
- Tracking number
- Return status and adjustment reason
Assign each data to a reference source: ERP, WMS or third-party system. This responsibility prevents multiple applications from maintaining different versions. Any change in stock, location or status must retain its link to the lot or serial number.
The Emaloja WMS provides visibility and automation to supply chain operations. Before configuration, ensure that product sheets contain the required identifiers, that orders have actionable statuses, and that stocks have defined locations and states.
From the receiving dock to return: the traceability flow to design
The target flow follows this order:
- Receiving goods
- Control and capture of the lot or serial number
- Assignment to a location
- Synchronization of availability
- Allocation to an order
- Picking
- Packaging
- Shipping
- Status update
- Return, then restocking or blocking
Receiving, checking and stocking
Upon receipt, the integration associates the reference, quantity, batch or serial number and location. It adds the expiration date when the product requires it.
The check must reject or report a missing, invalid or already used identifier. Availability only changes after the recording of the expected movement.
Allocation, preparation and shipping
The allocation and picking retain the identifier for traceability. The company can thus link the prepared item to the order, the package, and the shipment.
At shipping, the WMS links the status and tracking number to the order. Emaloja's WMS allows for real-time tracking of orders and inventory.
Recall, return and reconciliation
A recall must allow for finding the orders, shipments and returns related to the searched identifier. For a return, the check decides whether the item joins available stock, blocked stock or quality control.
Illustrative scenario: a serialized reference sold in Switzerland returns to the warehouse. The serial number links the return to the initial shipment, while the return status documents the decision made. The reconciliation then verifies that the ERP and WMS present the same state.
Define the technical scope of the integration
Interfaces, frequency and synchronization rules
Evaluate the API, EDI, and connector according to the systems involved. The choice depends on the available formats, volumes, and operational constraints.
For each exchange, define the triggering event, the frequency, the direction of flow, and the receipt confirmation. Also set the applicable priority when two systems simultaneously modify a data.
Emaloja solutions can link e-commerce to inventory management software and automate the orders, preparation, and shipping. The scope remains to be validated for each ERP and each traceability rule.
Management of discrepancies and auditing trail
Errors must be detectable, logged, and assigned to a responsible party. The audit trail must include:
- Transaction ID and timestamp
- Sender and receiver systems
- User or process that initiated the movement
- Processing status
Before the framing, gather the relevant ERP and WMS, the catalog, batch or series rules, order volumes, warehouses, and channels. Add the exchange formats, existing exceptions, and data owners.
Validate the mapping and exception scenarios on a sample of orders before deployment.
Swiss specifics and flows between Switzerland, France, and the European Union
Swiss operations must integrate multichannel orders, product data useful for customs formalities, and transfers between warehouses or carriers. Customs and language requirements vary by goods, markets, and partners.
Emaloja has warehouses in Switzerland and France. Its WMS is designed for online commerce logistics in Switzerland, France, and Europe. It also supports customs clearance and compliant labeling.
At each handover, the batch or serial number must remain associated with the order, the package, the relevant customs status, and the possible return.
Frequently asked questions about ERP–WMS integration and traceability
Yes, if the scope confirms the presence of the corresponding fields in the ERP, the WMS, and the exchanges. Also test the length, the format, and the accepted characters to avoid the rejection of an identifier.
Visibility depends on automatic updates and an organized handling of exceptions. Emaloja's WMS offers automatic inventory updates, but teams must also monitor suspended or rejected exchanges.
Prepare technical accesses, data formats, statuses used, and histories necessary for validation. Also document the test environments and authorization rules, then request a technical framing of the ERP–WMS flow from Emaloja.
In summary: a traceability designed before being automated.
Choose the level of traceability, designate the owner of each data point, and test the exceptions of the complete flow. You thus achieve centralized and consistent management, from receipt to shipping and then returns, while maintaining a process to handle variances.
Have your ERP–WMS scope analyzed, the data to be synchronized, and the flows between Switzerland, France, and the European Union before deployment.