A B2B order can be correct in the ERP and yet fail at the warehouse if the stock, batch, or shipping status arrives too late in the WMS. In Switzerland, this risk increases when goods move between Switzerland, France, and the European Union. Microsoft has an excellent article on the "Warehouse management mode only with external ERP systems."
This guide provides a method for evaluating a fulfillment provider based on technical and operational evidence. It is aimed at e-commerce, supply chain, operations, and information systems managers who distribute pharmaceutical products or industrial parts.
Why B2B fulfillment in Switzerland requires a technical assessment
E-commerce fulfillment covers the physical handling of goods, from their receipt to their shipping and returns. In B2B, this scope also includes bulk orders, technical references, complex logistics units, and traceability requirements (e-commerce fulfillment guide in Switzerland).
A desynchronization can affect several elements at the same time: the stock available in the ERP, the physical stock, reservations, customer orders, and transport documents. A reference announced as available can then be blocked, assigned to another order, or stored under an incompatible quality status. Read the SAP article to better understand the Integration into a warehouse management system (WMS).
Switzerland is not part of the European Union. The goods that cross this border are therefore treated as imports or exports. The process may include customs clearance, Swiss VAT, and applicable duties depending on the product and the flow.
Technology must count as much as storage, the transportation, and the price in the decision. A commercial presentation does not prove either the quality of an interface, nor the retention of a lot number, nor the ability to resume a message after a failure.
The question "What are the best e-commerce fulfillment providers in Switzerland?" does not therefore call for a universal ranking. A comparison updated in September 2026 covers Emaloja, 7Days, e-LOGIK Switzerland and Logistikkönner, without establishing a definitive ranking. The choice depends on the sales channels, the products, the destinations, and the entrusted operations.
Before comparing quotes, map the systems, the physical flows, the data exchanges, and the traceability requirements that will need to be demonstrated.
Define the operational scope before comparing providers
An ERP is the enterprise resource management system. It centralizes commercial data, orders, items, and certain stock movements. Read the article What is an ERP ? of Oracle for detailed information. A WMS, or warehouse management system, manages stocks, locations, and preparation operations.
The scope must specify which system has authority for each data point. It should also indicate where the responsibility of the provider begins and ends. Read our Guide to integrating ecommerce and warehouse management (WMS) in Switzerland.
Map the B2B flows, sales channels, and exceptions
Start by representing the journey of an order, from the sales channel to the potential return. The mapping should cover the e-commerce stores, marketplaces, B2B portals, intranet stores, and orders entered directly into the ERP.
Then document the following elements:
- affected customers and customer groups;
- sales units, packages, pallets, and other logistical units;
- available, reserved, blocked, or controlled stocks;
- warehouses and shipping sites;
- carriers and services used;
- destinations in Switzerland and the European Union;
- return processes and manual exceptions.
Add scenarios that do not follow the standard path. A late cancellation, a partial order, an invalid address, a missing stock, or a customs rejection must produce a comprehensible status in the appropriate system.
For industrial parts, describe the references, the variants, and the kits. Also specify the allowed substitutions, the orders by package or pallet, and the rules applicable to returns.
Distinguish the requirements for pharmaceutical products and industrial parts.
Pharmaceutical products require a precise definition of batches, relevant dates, and exit rules. The specifications must also cover quality holds, recalls, documentary evidence, and the required storage conditions.
Distinguish products outside the cold chain from products that require a cold chain. For the latter, validate on a case-by-case basis the temperature range, qualifications, equipment, monitoring, and available evidence. Announced capacity is not sufficient to establish regulatory compliance.
Industrial parts require a different granularity. The WMS may need to retain a manufacturer reference, a variant, a serial number, the composition of a kit, or the link between a returned part and a replacement part.
To obtain comparable proposals, provide each candidate with the same set of data:
- product typology and storage constraints;
- ordering channels and systems used;
- catalog structure, variants, and logistics units;
- forecast volumes and expected variations;
- destinations, carriers, and relevant Incoterms;
- return, hold, and exception scenarios.
Evaluate the ERP-WMS integration and API interfaces.
An API is an interface that allows multiple systems to automatically exchange data. Its presence does not guarantee either the completeness of flows, their frequency, or their ability to handle an error.
The objective is to verify the complete cycle. An order created in the ERP must arrive in the WMS with the correct lines, reservations, and instructions. After preparation, the WMS must return the shipment, the tracking number, and any discrepancies.
Check what it really means to have a native integration
Ask if the integration relies on a standard connector, a custom development, or a file exchange. For each mode, obtain the functional scope, maintenance responsibilities, known limitations, and costs associated with a modification.
A native integration is verified with technical documentation, a list of supported objects, and tests. It must specify the flows covered among the following items:
- products, variants, and logistics units;
- available, reserved, and blocked stocks;
- orders, modifications, and cancellations;
- shipments and tracking numbers;
- returns and inventory adjustments;
- exception statuses.
The evaluation of a provider of WMS integration solutions for ecommerce in Switzerland must also cover authentication, unique identifiers, and the testing environment. For a ERP-WMS integration for pharmaceutical distribution in Switzerland, add batches, dates, and quality statuses. An ERP and WMS integration for online spare parts sales in Switzerland must retain the required variants, kits, and serial numbers.
Emaloja registers the integration of WMS, OMS, TMS, and ERP in its approach to an integrated supply chain and monitored in real time. This orientation does not prove the existence of a native API for a particular ERP. Request written validation for the software and version used.
Emaloja also offers a interface between the marketplaces and its WMS. This device illustrates the integration of sales channels, but a marketplace, an ERP, and a native API remain distinct components.
Test the flows, the events, and the incident recovery
A stock consultation in a dashboard does not constitute a complete operational flow. The test should start from the creation of the order and end after the status update in the ERP.
Control the synchronization frequency as well as the events or webhooks. A webhook transmits an event to another system as soon as a specified action occurs, such as a shipment or a rejection. Read What is a webhook? Concept and complete guide from MailChimp.
Then provoke errors: unknown item, duplicate, missing field, expired authentication, or temporary unavailability. The provider must demonstrate logging, alerting, correction, and the replayability of the message. Replayability allows reprocessing an exchange without creating a second order or a duplicate movement.
⚙️ Technical criterion
❓ Question to the provider
📋 Expected proof
⚠️ Potential risk
⚙️ Catalog
❓What products, variants, kits, and logistics units does the interface accept?
📋 Documentation of objects, field matrix, and test import
⚠️ References rejected or incomplete article structure
⚙️ Stock
❓What stock statuses are exchanged and how often?
📋 Demonstration of available, reserved, and blocked stocks
⚠️ Sale of unavailable stock or inconsistent reservation
⚙️ Order
❓How are creations, modifications, cancellations, and duplicates handled?
📋 Test scenarios and unique identifiers
⚠️ Incorrect preparation or duplicate order
⚙️ Shipping
❓What statuses, packages, and tracking numbers return to the ERP?
📋 Shipping test and event log
⚠️ Client not informed or billing triggered at the wrong time
⚙️ Return
❓How does the return affect stock and the order status?
📋 Return of test with restocking decision
⚠️ Stock reintegrated without control or delayed credit
⚙️ Exception
❓How is an error detected, affected, and replayed?
📋 Error message, alert, and documented recovery
⚠️ Order blocked without visibility
⚙️ Supervision
❓Who monitors the interfaces and keeps the logs?
📋 Supervision table, escalation procedure, and history
⚠️ Incident discovered late or incomplete diagnosis
Include in the contract the flows, the mandatory fields, the expected events, the responsibilities, and the correction deadlines. Add the acceptance criteria that condition the production deployment.
Control the traceability by batch, by serial number, and by date
Traceability must become a set of requirements for verifiable data. The file must specify the batch, the serial number when necessary, the relevant date, the quality status, the location, the customer order, the shipment, and the return.
An end-to-end test must cover the receipt of 2 batches of the same reference. It continues with the reservation, preparation, the shipment, the return, an inventory correction, and the extraction of the history. At each step, record the identifier, the status, the location, the user or the system that initiated the movement, and the available timestamp.
Traceability adapted to pharmaceutical products
Ask how the WMS receives the batch number and retains it during each movement. Then check how it applies the defined exit rule and prevents the preparation of blocked stock.
Date-based rules must use the appropriate field. The candidate must demonstrate the stock selection in a controlled scenario, then provide the necessary data for a recall.
Emaloja indicates that its WMS supports a secure storage at controlled temperature. This capability does not by itself demonstrate batch management, the application of FEFO, the maintenance of a cold chain, or compliance with a pharmaceutical standard. Each of these points requires separate documents and tests.
Traceability adapted to industrial spare parts
For an industrial part, the commercial reference may be insufficient. The process sometimes needs to retain a variant, a serial number, and the exact composition of a kit.
Also test the replacement of a component. The history must link the initial order, the returned part, any diagnosis, and the new part shipped. This relationship facilitates defect analysis and limits warranty errors.
🔍 Control
💊 Pharmaceutical
⚙️ Industrial parts
📋 Proof requested
🔍 Identifier
💊 Batch, reference and relevant date
⚙️ Reference, variant, serial number or kit depending on the product
📋 Receiving and reading identifiers in the WMS
🔍 Exit
rule
💊 Rule defined by batch, date, and authorized status
⚙️ Stock priority, compatibility, and authorized substitution
📋 Preparation of two units subject to different rules
🔍 Quality
status
💊 Available, blocked, under control or other defined status
⚙️ Available, damaged, incomplete or under control
📋 Blocking a unit and attempting to reserve
🔍 History
💊 Movements of the batch between receiving, location, and customer
⚙️ Movements of the reference, serial number or component
📋 Export of the complete history
🔍 Return
💊 Retention of the batch and quality decision before reintegration
⚙️ Identification of the returned part and link to the replacement
📋 Return test with stock control and decision
🔍 Reminder
💊 Identification of relevant stocks and clients
⚙️ Identification of orders containing the part or component
📋 Reverse search from the identifier to the shipments
The capabilities missing from the documentation must remain open in the evaluation grid. The candidate must confirm them through a demonstration or a contractual commitment.
Evaluate the execution of the warehouse, transport, and Switzerland-EU flows
The quality of an interface does not compensate for a poorly defined physical process. Evaluate each step from the arrival of goods up to the proof of delivery, then assign responsibility for exceptions. Read our blog on the logistics of cross-border ecommerce: France-Switzerland guide.
Receiving, preparing, packing, and returns
Receiving must cover the reconciliation with the expected notice, counting, control, and handling of discrepancies. Check how the provider records a damaged package, an incorrect quantity, or an unexpected batch.
For B2B preparation, review the rules regarding complete packages, pallets, multi-reference orders, and attached documents. Packaging and labeling must consider the carrier, the destination, and the requirements of the professional client.
The return process must identify the product, the original order, and the reason for the return. It must also separate the physical inspection, the decision to restock, and the update of systems.
Ask the provider about the cross-docking if certain products must leave as soon as they arrive. Emaloja offers this process to ship goods directly upon arrival, without storage. Ask how the WMS then links the receipt to the outgoing order.
Customs, implementation and continuity of flows
Evaluate the Switzerland-France-EU perimeter flow by flow. The presence of warehouses in Switzerland and France can bring stock closer to certain destinations, but it does not automatically define the applicable customs, tax or contractual regime.
Emaloja offers cross-border services that include customs clearance, tax representation and commercial domiciliation. Confirm their applicability based on the products, destinations, official importer and selected Incoterms.
Continuity also depends on carriers, drop-off points and the handling of missing documents. Ask who intervenes when a shipment is stuck, who corrects the data and how the ERP receives the new status.
Route optimization and sustainable practices can be included in purchasing criteria. Emaloja emphasizes route optimization to reduce the carbon footprint. The evaluation should then focus on the methods used and the available data, without assuming a quantified impact.
Request a simulation of a cross-border B2B order. The scenario should include a customs exception, its correction, delivery and a return to the country of origin or the designated site.
Build a grid for selection and a comparable call for tenders
Rank the criteria according to the company's priorities, without imposing a generic weighting. A pharmaceutical activity may place traceability and quality status at the top level. A parts distributor may prioritize references, kits, serial numbers, and urgent orders.
Use qualitative levels such as "essential", " important" and "desirable". Add a validation status: demonstrated, documented, contractual or unconfirmed. This method distinguishes a declared functionality from an observed capability.
Send candidates the same data dictionary, the same forecast volumes, and the same scenarios. Request the following documents:
- flow and responsibility diagram;
- interface documentation and field matrix;
- incident and escalation procedure;
- operational report template;
- return procedure;
- example of traceability history;
- detailed pricing conditions.
The recipe must cover the initial stock, the order, cancellation, breakage, shipping, return, and inventory discrepancy. Add the export of the lot history when the product requires it.
A quote depends on the volumes, operations, and regions covered. Request a breakdown between reception, storage, preparation, consumables, transport, returns, integration, and exceptional services.
🎯 Domain
🔍 Criteria
📋 Proof required
📝 Decision or reservation
🎯 Integration
🔍 Items covered, frequency, errors, maintenance and security
📋 Documentation, complete test and responsibility matrix
📝 Flows accepted, required adaptations or dependencies
🎯 Traceability
🔍 Lots, series, dates, statuses and history export
📋 Acceptance scenario and extraction file
📝 Requirements demonstrated or unconfirmed points
🎯 Warehouse
🔍 Reception, storage, B2B preparation and exceptional capacity
📋 Visit, procedures and test order
📝 Processes validated or controls to add
🎯 Transport
🔍 Services, tracking, proof of delivery and incident management
📋 Simulation, tracking example and escalation procedure
📝 Coverage retained and exclusions
🎯 Cross-border
flows
🔍 Customs, taxation, Incoterms and responsibilities
📋 Flow diagram and documentary example
📝 Countries covered and necessary validations
🎯 Returns
🔍 Identification, inspection, decision and stock update
📋 Test return and operational procedure
📝 Agreed timelines and responsibilities
🎯 Support
🔍 Schedules, channels, priorities and escalation
📋 Incident procedure and report template
📝 Accepted support level or reservation
🎯 Commercial
terms
🔍 Cost structure, revision, minimums and reversibility
📋 Detailed offer and contract draft
📝 Costs retained, assumptions and clauses to negotiate
Keep the discrepancies and reserves in the final grid. An unproven response should not receive the same status as a scenario successfully executed.
Position Emaloja in a Swiss B2B fulfillment project
This summary presents the documented scope of Emaloja. It does not constitute a ranking against other Swiss providers.
Emaloja is the digital agency of the RDV SA group, STAR Logistique, a transport and logistics company based in Geneva for 38 years. Emaloja offers a turnkey integrated solution for e-commerce and e-logistics projects in Switzerland, in France and in the European Union.
When an order is validated on a site e-commerce or a marketplace, it is immediately processed in Emaloja's WMS. The experience presented by Emaloja is also based on over 38 years of expertise through STAR Logistique.
The scope covers the creation of e-commerce sites, the integration of marketplaces, intranet shops, the storage, the preparation of orders and national or international shipping. The model aims for centralized and consistent management, from receipt to shipping.
These elements do not prove a native API integration with any given ERP. They also do not establish a specific rule for batch management or pharmaceutical compliance. These capabilities must be subject to a demonstration, documentation, and contractual validation.
To evaluate Emaloja on your own project, request a demonstration based on your ERP-WMS flow, a batch or serial number scenario, and your actual destinations.
Frequently asked questions about choosing a B2B fulfillment provider in Switzerland
Request indicators related to the accuracy of inventory, correct preparation, orders shipped as committed, processed returns, and unresolved incidents. Each indicator must specify its formula, data source, reporting frequency, and the allowed exclusions.
Add indicators specific to your business, such as batch discrepancies, serial number errors, or orders blocked for a customs reason.
The contract must clearly assign ownership of the data to the relevant company and frame its processing by the provider. It must also define access rights, export formats, the duration of data retention, and deletion after the end of the service.
Also check the rights applicable to technical logs, data generated by the WMS, and backup copies.
Plan a procedure that sets responsibilities, the alert channels, and the authorized manual operations. It must define how to record urgent orders, protect inventory, and reconcile the movements after recovery.
Test this procedure during the acceptance with a simulated unavailability. The test must also verify the order of resumption of the messages and the detection of duplicates.
The contract must specify the notice period, assistance with the transfer, export formats, and the schedule for returning the inventory. Include open orders, ongoing returns, histories, traceability data, and the destruction of remaining copies.
Also define the exit costs, responsibilities during the final inventory, and the handling of specific interface developments.
Provide a scenario with your references, your statuses, and your exceptions rather than a general list of functions. Ask the candidate to execute the order, shipping, return, and data extraction in front of representatives from operations and information systems.
Prepare an acceptance document tailored to your products and your flows. You can then request a demonstration and a quote from Emaloja based on this real data.
In summary: choose based on technical and operational evidence.
The choice of a B2B fulfillment provider in Switzerland must be based on six priorities:
- clear scope of systems, products, channels, and destinations;
- proof of the complete cycle between the ERP and the WMS ;
- traceability adapted to batches, dates, or serial numbers ;
- recipe including errors, returns, and recovery on incident ;
- validated cross-border capacity for each flow Switzerland-EU ;
- responsibilities, costs, and conditions of reversibility transparent.
The right provider must be able to demonstrate the complete path, from creation in the ERP to return and operational history. Prepare your scenario notebook, then request a demonstration or a quote based on your actual B2B flows.