Prerequisites: frame the network before launching the flows
Organizing reliable B2B deliveries from several european suppliers to multiple swiss retailers requires a unique and testable flow. Switzerland imported products worth 190.7 billion CHF from the EU in 2025 according to the Federal Customs Office. This flow must coordinate data, customs, inventory, order preparation, and national transport.
Let's take a fictional scenario that will serve as a guiding thread. A european distributor supplies 12 swiss stores from several suppliers located in the European Union. The goods enter Switzerland, pass through a warehouse or a transit dock, then are prepared and delivered according to the constraints of each store. In Switzerland, 63% of goods transport is done by road in 2024 according to the FSO.
Before the launch, gather the following prerequisites:
- a pilot team and a designated owner for each process;
- the initial list of suppliers, pickup points and stores;
- access to product data, forecasts, and orders;
- the contractual rules applicable to transport and merchandise ;
- the contacts responsible for customs formalities ;
- a stock management system or an accepted exchange format ;
- a pilot schedule with its decision gates.
Synchronize the master data and the transactional data with each physical movement. A receipt, a transfer, a preparation or a delivery must have a corresponding IT or documentary event (see also the customs declarations with Passar starting in 2026). This requirement ensures that the stocks, the orders and the destinations describe the same operational flow. For information, the average distance of domestic transport is 40 km by road compared to 105 km by rail according to the OFS.
▣ Phase
◇ Validation
▤ Deliverable
▣ Preparation
◇ Validate the scope, the data and the responsibilities
▤ Flow map, SKU reference, destination sheets and approved roles matrix
▣ Controlled pilot
◇ Confirm that the complete flow can be executed and verified
▤ Test dossier with results, control evidence and documented incidents
▣ Commissioning followed by the extension
◇ Authorize the operation, then each additional wave
▤ Stabilized procedures, active dashboard and formal decision for extension
The expected outcome is an approved starting scope, with explicit responsibilities and evidence required at each gate.
Step 1: map suppliers, flows, and Swiss destinations
Create a unique map linking each supplier from the European Union to its Swiss destination. Indicate the pickup point, the proposed border crossing, the warehouse or transit dock, the store, the final address, and the contact responsible for receiving.
For each of the 12 fictitious stores, create a destination sheet including:
- the address and, if necessary, the language region;
- the hours and the receiving slot;
- the access restrictions for vehicles;
- the unloading method, with ramp or tailgate;
- the operational contact;
- the requested proof of delivery;
- the already known restrictions.
Represent the physical flow and the flow of information side by side. The sequence covers collection at the supplier, import, reception, inspection, storage or transit, preparation by store, the national route, and final reception. For each movement, record the data sent, the receiving system, and the expected proof.
This map determines the data to be gathered in step 2. It also allows for assigning customs responsibilities in step 3 and for verifying the feasibility of routes in step 7. To delve deeper into this method, consult the B2B wholesale and retail distribution logistics.
The result is an approved representation of each route, its data exchanges, and its receiving constraints.
Step 2: gather the product, volume, and order data
Establish a common reference for each inventory management unit, or SKU. Record the designation, reference, tariff code to be validated, country of origin when required, unit of sale, weight, dimensions, and packaging format. Add the lot, date, handling conditions, and documentary value when these details apply.
Complete this reference with flow data:
- expected quantities by supplier;
- collection frequency;
- number and type of pallets or packages;
- orders assigned to each store;
- seasonality and urgent orders;
- minimum preparation;
- replenishment forecasts.
Document the grouping and separation rules. Specify whether pallets must remain homogeneous, if mixed pallets are accepted, if splitting is allowed, and which labels must identify the destination. Also list the documents to be attached.
In the fictional scenario, the same reference may come from multiple suppliers before being distributed among different stores. Therefore, use a persistent matching key between the supplier order, receipt, available stock, and store order.
This data will guide the choice between a buffer stock, a pre-assigned cross-docking, and a cross-docking with pallet splitting. It also forms the basis for inventory management and distribution services intended for manufacturers when management is entrusted to a provider.
Step 3: assign the import, customs, and contractual responsibilities.
Identify in writing the importer, the declarant or customs representative, the owner of the stock, and the liable party for duties and taxes. Also designate the holder of the documents and the person responsible for each dispute or documentary discrepancy.
Switzerland is not part of the customs union of the European Union. Goods imported from the EU require a customs declaration. The duties, applicable origin, and additional requirements depend in particular on the product and its tariff number, as explained in this Swiss customs guide [1].
Depending on the sales model, also check the fiscal situation. A foreign company subject to Swiss VAT must register within 30 days of the start of its liability and designate a fiscal representative established in Switzerland (Federal Tax Administration) [2]. The import VAT deduction requires in particular a tax decision established in the name and address of the liable importer, who must be able to economically dispose of the goods (Swiss SME Portal) [3].
Define the roles with a RACI matrix: "R" performs the activity, "A" is accountable, "C" is consulted, and "I" is informed. The model below should be adapted to the selected contracts.
▣ Activity
◇ Distributor
▤ Customs
▥ Warehouse
⇄ Transport
▣ Basic data
◇ A/R
▤ C
▥ C
⇄ I
▣ Invoice and documents
◇ A/R
▤ C
▥ I
⇄ I
▣ Declaration
◇ A
▤ R
▥ I
⇄ C
▣ Reception
◇ I
▤ I
▥ A/R
⇄ C
▣ Stocking
◇ A
▤ I
▥ R
⇄ I
▣ Preparation
◇ A
▤ I
▥ R
⇄ I
▣ Transport
◇ A
▤ I
▥ C
⇄ R
▣ Proof of delivery
◇ A
▤ I
▥ I
⇄ R
▣ Incident handling
◇ A
▤ C
▥ R
⇄ R
Formalize the Incoterms, the documents, the authorization to declare, the transmission deadlines, and the escalation in case of blockage. This framework must be validated before the release of the first arrival described in step 4. Teams that need to deepen the classification or declarations can consult the Swiss customs brokerage services.
Step 4: prepare the first arrival and the import file
Prepare a receipt notice before the departure of the goods. The file must contain the shipment number, the supplier, the references, the quantities, and the logistical units. Add the commercial or pro forma invoice according to the flow, the transport documents, the recipient, the importer, and the receipt instructions.
Check the consistency between 4 elements: the documents, the SKU data, the physical labels, and the allocation planned for the 12 dummy stores. A reference or quantity present in a file, but absent from the documents or the loading, must trigger a verification.
Then apply this sequence:
- Transmit the notice to the concerned parties.
- Review the customs file.
- Obtain the authorization or declaration instructions.
- Register the arrival on site.
- Check the units at the dock.
- Record the discrepancies and their evidence.
- Release the compliant units for storage or transit.
Isolate any inconsistency in value, description, quantity, origin, or recipient before preparation. Assign its treatment to the owner defined in the RACI matrix.
STAR Logistique can be evaluated as an operational partner, as its international transport services include customs clearance processing. This capability must be included in the established contractual responsibilities.
Only units with defined documentation status and physical control proceed to the next step.
Step 5: define the receipt, inventory control, and preparation model
Establish a receipt procedure covering counting, the apparent condition, and the identification of pallets or packages. Place in quarantine any non-compliant unit. Record discrepancies before validating the stock placement.
Then choose the operational model suitable for the flow:
- Inventory-driven buffer stock : units are stored and then allocated according to confirmed orders.
- Pre-assigned cross-docking : units already have a store destination and move quickly from receipt to shipping.
- Cross-docking with splitting : an incoming pallet is divided into units destined for multiple stores.
For pre-assigned cross-docking, require the supplier to affix the final recipient's identification before shipping. For splitting, document the breakdown, the creation of new labels, and the control prior to departure.
Also define the frequency of counts, the handling of batches, the blocking rules, and the reconciliation between receipt and theoretical stock. No preparation should begin without validation of the available status.
A warehouse management system, or WMS, can track inventory in real-time, process orders, and maintain their traceability. The e-logistics system of STAR Logistique covers these functions among other operations. The chosen model sets the labeling and replenishment rules for the following steps.
Step 6: integrate the requirements specific to each retailer
Create a reusable onboarding checklist for each retailer. It should contain:
- the identifier, address, and contact of the store;
- the hours and the reserved time slot;
- the type of vehicle accepted;
- the presence of a ramp or the need for a liftgate;
- the allowed pallet format;
- the communicated height or weight limits;
- the requested labels and barcodes;
- the expected delivery note;
- the refusal and return rules;
- the format of the proof of delivery.
Separate the common requirements for the entire network from local exceptions. The 12 fictitious stores may apply different time slots, pallet formats, or documents. Therefore, keep a controlled version of each sheet and record its approval date.
To prepare a store order, first allocate the available stock. Then execute the picking, check the completeness, carry out the planned packaging or repackaging, and then affix the destination label. Finally, issue the document requested by the retailer.
If these tasks are outsourced, assess the functional coverage of the provider. The integrated system of STAR Logistique notably supports procurement, storage, picking, cross-docking, packaging, returns, and customs clearance.
Do not integrate any store into the pilot before the joint validation of its destination sheet and checklist.
Step 7: plan the replenishment and national routes
Transform the needs of the stores into a transport plan. Indicate the delivery days, time slots, routes, volumes, the shipping format, and the solution planned in case of impediment. As a reminder, Swiss heavy vehicles traveled 27% of their kilometers without load in 2024 according to the OFS, highlighting the importance of optimizing and/or pooling replenishments.
Determine the replenishment cadence based on demand, confirmed stock, and the store's receiving capacity. Also integrate the possibilities for consolidation and preparation constraints. The cadence must evolve when these data change. Note that, the ban on heavy vehicle traffic between 10 PM and 5 AM, as well as Sunday.
Consolidate the flows from multiple suppliers when the receipts are reliable and correctly identified. Separate the units if the store rules require it. This decision must remain visible in the WMS, the loading plan, and the delivery documents.
In the fictional scenario, distribute the 12 stores into testable routes. Check the order of stops according to appointments, access restrictions, the expected unloading time, and the vehicle capacity. Plan an escalation contact for each stop. With more than 20% of congestion more in 2025 (which is 68,040 hours of congestion on the Swiss national roads) according to OFROU, it is advisable to allow for a safety margin.
STAR Logistique serves Switzerland daily from international destinations and vice versa. This capacity is a point to check in the flow plan if this partner is considered.
Do not launch the pilot until routes, appointments, contacts, and delivery proof instructions are confirmed.
Step 8: test the complete flow before commissioning
Build a pilot plan covering a representative sample of suppliers, SKUs, pallet formats, stores, and time slots. Keep a limited scope to identify defects before expansion.
Test successively the supplier notice, the data transmission, and the customs file. Continue with the receipt, the physical and IT reconciliation, the stocking or transit, the preparation by store, the loading, the delivery, and the retrieval of the delivery proof.
Use observable acceptance criteria: consistency of data, presence of documents, identification of units, stock update, order compliance, and adherence to the agreed time slot. Each incident must also leave a usable trace.
▣ Test
▤ Data / Docs
◉ Proof
✓ Validation
▣ Imported Receipt
▤ Notice, bill, transport document, declaration, and SKU data
◉ Dock control and document status
✓ Available documents, identified units, and updated stock
▣ Multi-SKU Preparation
▤ Store order, available stock, and picking rules
◉ Completeness check and destination label
✓ Order compliant with store instructions
▣ Delivery with time slot
▤ Appointment, route, contact, and delivery note
◉ Timestamp and proof of delivery
✓ Time slot respected according to the agreement and proof retrieved
▣ Fictitious stock discrepancy
▤ Receipt, WMS movements and order
◉ Blocking, reconciliation, and recorded decision
✓ Isolated discrepancy, parties informed, and allocation decided
▣ Fictitious delivery refusal
▤ Store instructions, delivered units, and reason for refusal
◉ Proof of attempt, reservations, or available photos
✓ Documented incident and goods placed under defined status
In the fictitious gap test, the warehouse blocks the unit and compares the receipt to the system stock. The distributor then decides on the allocation or replenishment. The store receives the information provided by the business rules.
The pilot must validate the interfaces, the responsibilities and the control evidence, beyond just the movement of goods. The next step deliberately replays the incidents to test the operational continuity.
Step 9: handle the breaks, refusals, damages, and returns
Apply a common procedure to all incidents. Secure the units and the evidence, then record the event. Designate the owner of the decision, inform the parties, choose the corrective action and update the stocks as well as the documents before the closure.
In case of refusal, the carrier must notify the sender and either temporarily store the good themselves or deposit it with a third party (source: article 444 CO). In Switzerland, the law allows a maximum of 8 days to report an unseen damage (source: article 452 CO).
Always distinguish 3 levels: the factual observation, the business decision, and the logistical execution. This separation prevents a carrier, a store, or a warehouse from making a decision outside of its mandate.
In the fictitious scenario, a retailer refuses a delivery. The carrier records the reason, the date, the affected units, and the available reserves. They keep the proof of attempt and the authorized photos. The distributor chooses a redelivery, a return, or a new appointment. After the physical return, the warehouse adjusts the statuses and the stock.
⚠ Incident
▤ Info
◇ Decision Maker
⇄ Correction / Resumption
⚠ Break or stock discrepancy
▤ SKU, quantity, receipt, movements and affected orders
◇ Distributor
⇄ Block allocation, reconcile data then restock or reassign
⚠ Delivery refusal
▤ Reason, date, units, reserves and proof of attempt
◇ Distributor
⇄ Decide on redelivery, return or a new appointment
⚠ Damage
▤ Condition, quantity, packaging, photos and inspection stage
◇ Distributor according to contractual responsibilities
⇄ Isolate, inspect if planned, replace or return
⚠ Preparation error
▤ Order, expected units, shipped units and control performed
◇ Warehouse with distributor validation
⇄ Correct the order and update the stock
⚠ Unit not identified
▤ Label, batch, origin, location and associated documents
◇ Distributor
⇄ Place in quarantine, identify then release or return
⚠ Return
▤ Reason, authorization, condition, quantity and initial reference
◇ Distributor
⇄ Receive, check and decide on restocking or planned processing
Contractually define roles and internal escalation timelines.The e-logistics offer of STAR Logistique includes return management, which may be relevant in evaluating a partner.
Use pilot incidents to correct store records, transport instructions, and stock rules.
Step 10: manage the service level and expand the network
Build a short dashboard. Measure results by supplier, warehouse, route, and store when the volume allows for a relevant reading. This segmentation prevents an overall average from masking a local issue.
◉ KPI
∑ Calculation
▤ Source
◇ Responsible / Tracking
◉ Accuracy of stocks
∑ Physical stock compliant with the system stock reported to the controlled perimeter
▤ Counts and WMS
◇ Warehouse ; weekly review, analyze discrepancies and correct movements
◉ Completeness of orders
∑ Complete orders delivered reported to controlled orders
▤ WMS, preparation control and proof of delivery
◇ Distributor ; weekly review, examine stockouts and picking errors
◉ Timeliness of deliveries
∑ Deliveries within the agreed window reported to measured deliveries
▤ Transport plan and delivery timestamp
◇ Carrier ; weekly review, review routes, appointments, and capacities
◉ Incident resolution time
∑ Time between documented opening and validated closure
▤ Incident register
◇ Process owner; weekly review, examine open records and recurring causes
Also define the action triggered when a drift occurs, without waiting for the extension review.
Allow a new wave only if the base data is reliable, operational customs responsibilities, and the inventory is validated. Retailer sheets, routes, and incident processing must also have passed the pilot.
Add stores or regions in waves. Reassess the storage and preparation capacity before each extension. Relaunch a pilot when the product, order format, or receiving conditions change.
STAR Logistique customers can directly access their stocks via the WMS to consult, manage, and restock them. This level of visibility is a criterion to examine, without being a guarantee of performance.
At each review, make an explicit decision: stabilize, correct, or extend.
Tips and best practices for a controlled launch
Apply a few constant rules during the pilot and operation:
- Maintain a single SKU reference for suppliers, the warehouse, and store orders.
- Keep an approved sheet by destination.
- Assign each decision to an identifiable owner.
- Give an explicit status to blocked or quarantined stocks.
- Control the versions of store-specific instructions.
- Regularly review incidents and their causes.
- Link each IT update to a physical or documentary proof.
Also respect the order of dependencies. Validate the data for the destination before scheduling a route. Confirm the preparation before promising a time slot. Analyze the results of the pilot before expanding the network.
Treat the WMS and the enterprise resource planning software, or ERP, as control tools. Inventory should not change without receipt, movement, preparation, authorized correction, or corresponding inventory. An order should not advance in status without a verifiable event.
Some integrated logistics services can group these operations under a common governance. Similarly, a model of outsourced logistics for European distributors (3PL) can entrust their execution to a third-party logistics provider. In both cases, the distributor retains control over the rules, data, and business decisions.
Common mistakes to avoid during deployment
- Launching with incomplete SKUs prevents the reconciliation between documents, inventory, and orders. Validate the mandatory fields before the first collection.
- Confusing the owner of the goods and importer creates customs and tax ambiguities. Formalize each role separately in contracts and the RACI matrix.
- Receiving without a control rule allows non-compliant quantities or units into the available inventory. Define the counting, identification, and quarantine.
- Assuming that stores have the same constraints causes refusals or delivery returns. Use a specific form for each destination.
- Schedule without a confirmed slot weakens the delivery order. Record the appointment and its contact before the loading.
- Treat a refusal as a simple delay masks the actual status of the goods. Open an incident and wait for the distributor's decision.
- Choose cross-docking without reliable pre-assignment prevents proper orientation of the units. Return to the model defined in step 5.
- Plan a breakout without splitting capability exposes the network to labeling errors. Validate the rules, space, and control before the pilot.
Expected results after commissioning
At the end of the launch, you must have an approved flow map and actionable product data. A matrix assigns responsibilities, while procedures frame receiving, inventory, and preparation. Each retailer has a validated sheet.
The operational file also includes a pilot plan with its evidence, a common incident handling procedure, and a dashboard assigned to specific owners. These elements form the basis of a warehousing logistics in Switzerland for merchants and distributors structured around actual flows and destination requirements.
The method covers 3 situations: creating a Swiss network, adding stores to an existing setup, or improving recurring replenishments. Each situation may require a new pilot if the products, data, or receiving constraints change.
The expected result is a manageable and improvable process. It does not guarantee the delivery of each order, nor an automatic compliance, nor a commercial result. Use the checklist, the RACI matrix, and the acceptance criteria as an internal launch document or as a basis for discussion with your operational partners.