Sell on Swiss Marketplaces (Galaxus, Manor) with Automatic Inventory Synchronization

What are the steps to become a seller on Galaxus from France?

The process involves selection, preparation, and technical integration. It’s not just a matter of creating an account.

Becoming a Merchant on Galaxus

The Galaxus process involves several steps: verifying that your product offerings meet the marketplace’s expectations, preparing your application, expressing your interest via the registration form, preparing for technical integration, and then scheduling catalog and order testing.

The Galaxus merchant program targets professional retailers with an established IT infrastructure, such as an online store or an ERP system.

Implementing technical integration via an interface is a basic requirement: manual data entry is not an option. Galaxus selects merchants and asks them to express their interest by filling out a registration form.

The program charges no base fees or initial fees, only variable commissions on products sold.​

The merchant registration form requires a set of information to be prepared in advance:

• Company contact information and address
• Commercial registry number
• Contact person and direct phone number
• Website and e-commerce platform
• Middleware or feed engine used
• Choice between full or partial automation
• Availability of EAN/GTIN codes
• Number of products and percentage in stock
• Product categories
• Images on a white background, resolution, and number of SKUs

The “Become a Merchant” page on Galaxus distinguishes between two levels of automation [1] [2].​

Partial automation requires, at a minimum, a daily export of product data in CSV format, uploaded via an FTP server.

Your product assortments, prices, and inventory statuses are thus updated, but you view and process orders manually in the Partner Portal.

Full automation also allows for the direct import of orders into your system and the automatic transmission of order statuses.

Selling on Manor and Shipping to Switzerland

What are the requirements for selling on Manor and shipping to customers in Switzerland?

To sell on Manor, you must first have your application approved, as the marketplace selects its partners based on the relevance of their product selection, their experience, and their reliability. Additionally, based on our most recent discussions, Manor does not accept merchants with fewer than 1,000 SKUs.

The merchant must then prepare a catalog tailored to the Swiss market, including EAN or GTIN codes, complete product listings in French and German, prices in Swiss francs, and customer service in both languages.

The merchant must also be able to provide Manor—via Mirakl or a connector—with up-to-date data on products, prices, orders, and, most importantly, available inventory.

Logistically, products are sold by Manor but stored and shipped directly by the partner, who must generally ensure delivery within 3 to 5 days, provide package tracking, and handle returns for 30 days.

A seller based abroad must also handle customs clearance, import duties, and VAT processing to ensure that Swiss customers do not incur any unexpected costs upon delivery.

The exact tax terms must be confirmed with Manor based on the contractual model and the seller’s country of establishment.

Registration and technical connection alone are not enough. The master catalog must be usable by the website, the connector, the marketplaces, and the warehouse.

An inconsistent catalog leads to product rejections, mapping errors, and, ultimately, overselling.

Prepare and verify this data before the very first export:

• Unique SKU per product reference
• EAN/GTIN
• Titles and descriptions
• Images that meet each channel’s requirements (white background for Galaxus)
• Product categories
• Price and availability
• Weight or dimensions if required for shipping
• Shipping and return policies
• Order statuses

Several of these elements correspond to the information requested in the Galaxus registration form: EAN/GTIN, categories, availability, and image specifications [3].​

The SKU must be identical or unambiguously mapped across the source catalog, the connector, the WMS, and each marketplace.

Treat this as a design rule to be validated, not as a universal automatic capability. A misaligned SKU breaks the link between an order and its stock reservation.

Next, distinguish between two flow directions. To the marketplaces, you publish the product assortment, product content, prices, and available stock. In return, you receive orders, cancellations, return requests, and status changes.

Emaloja offers automated data feed connectors to Digitec, Galaxus, and Manor. Before your very first export, remove duplicates, verify product identifiers, and select the source catalog that will serve as the reference.

The target architecture connects multiple systems through a clear data flow: e-commerce site and marketplaces → connector or API → WMS → order fulfillment, carrier, tracking, and returns. Return data is then fed back to the sales channels to update statuses and inventory.

An API (Application Programming Interface)is an interface that allows software systems to automatically exchange data. Middleware is the layer that translates, maps, and transmits data between these systems —for example, between a marketplace and a WMS.

Emaloja offers integration via API for automation or via FTP for operations that require direct control.

Emaloja relies in particular on CommerceHub, Iziflux, Lengow, and Sellermania as specialized integration tools. The WMS is connected to the marketplace for order management, returns processing, and inventory tracking.

No third-party tools are required. The choice depends on the targeted channels, the CMS or ERP in use, the order volume, the quality of the product catalog, and the desired level of automation.

The table below outlines the responsibilities of each component, along with the triggers and frequencies selected for the proposed implementation.

How does the WMS become the single source of truth for available inventory across multiple channels?

By centralizing physical movements and reservations, and then publishing a calculated inventory count to each channel. This prevents the website and marketplaces from relying on conflicting inventory counts.

First, distinguish between four concepts:

• Physical inventory: the quantity actually present in the warehouse.
• Reserved inventory: the quantity allocated to orders that have not yet been shipped.
• Available-to-sell inventory: physical inventory minus reserved inventory.
• Published inventory: the quantity communicated to each channel, after a safety buffer is applied.

Making the WMS the Operational Inventory Reference

As soon as an order is confirmed on an e-commerce site or marketplace, it is immediately processed in Emaloja’s WMS. The WMS then automatically updates inventory in real time on the online store.

Emaloja thus ensures inventory synchronization between the warehouse and the sales channels.

Making the WMS the operational reference means that each channel reads inventory derived from the warehouse—never the other way around. Other systems display information; they do not make decisions.

Reserve, Decrement, and Republish Available Inventory

The operational sequence follows a consistent order without imposing a universal architecture: order receipt, order ID verification, inventory reservation, calculation of available inventory, publication to channels, preparation, shipping, and status updates.

How can overselling be prevented when an order arrives simultaneously on the website and a marketplace?

A synchronization architecture can treat inventory as an event log rather than a simple modifiable counter [4]​

Available inventory then becomes a calculated projection: the sum of restocks, returns, releases, and adjustments, minus the sum of reservations. This approach tracks every movement, which an overwritten counter cannot do.

The principle of idempotence complements this model: an order received twice should trigger only a single reservation. The solution is to use the marketplace order ID as a check key, so that a webhook delivered twice does not create a duplicate reservation.

Allocate a safety stock and manage conflicts

Safety stock protects against synchronization latency between the warehouse and the channels. The source recommends publishing available stock with a buffer of 5% or 5 units, whichever is greater [5]. This buffer absorbs the brief delay during which a channel has not yet received the latest update.

The buffer, synchronization delays, and alert thresholds should be adjusted based on your sales volume, order frequency, and the actual capabilities of your systems. A high-turnover catalog requires a different buffer than one with low order frequency.

Which statuses should be synchronized between the marketplace, website, WMS, and carrier? Those that describe the entire lifecycle of an order, from placement to a potential refund.

Inbound Order Flow

The inbound flow begins upon receipt of the order. With full automation, Galaxus allows orders to be imported directly into the merchant’s system and order completion statuses to be transmitted via an XML file [6]​

​ Emaloja’s WMS is connected to marketplaces for order processing, inventory tracking, and returns management.

A brief example illustrates the dual workflow. A Galaxus order and a website order arrive almost simultaneously for the same SKU. The WMS reserves inventory for the first confirmed order, recalculates available stock, and republishes it.

If inventory becomes insufficient for the second order, the safety buffer and reservation rule prevent the acceptance of an uncovered quantity or trigger the defined exception handling.​

Statuses to Send Back to Sales Channels

Map statuses according to each channel’s capabilities:

• Order received
• Accepted or pending review
• Stock reserved
• Being prepared
• Shipped
• Delivered, when reported by the carrier
• Canceled
• Return requested
• Return received
• Refunded
• Processing error

Verify the labels and statuses actually available in each marketplace’s specifications and in the connector settings. Do not invent statuses specific to Galaxus or Manor.

Cancellations, Returns, and Synchronization Errors

Process a cancellation in two scenarios. Before order fulfillment, the reservation must be released to make the inventory available. After shipment, the process depends on the return and refund workflow you have defined.

Error management follows a specific process: alert, identification of the order and SKU, verification of the reservation, controlled correction, resubmission of the status, and then tracking of the incident.

Conclude with a concrete action: create a status mapping matrix, jointly validated by the e-commerce, warehouse, and customer service teams.

How do you manage orders, cancellations, returns, VAT, customs, and shipments between France, Switzerland, and the EU? By clearly separating the data flow from the physical logistics. The integration transmits an order, but fulfillment also requires receipt, storage, preparation, labeling, transportation, tracking, and returns processing.

Emaloja has facilities in Switzerland and neighboring France. The offering includes cross-border services: customs clearance, tax representation, and business registration. It also incorporates warehouse management, order fulfillment, and delivery in Switzerland, France, and Europe.

This guide does not provide VAT thresholds, rates, customs formalities, or guaranteed delivery times. These parameters depend on your specific situation and must be confirmed with a qualified representative.

Before publishing your product lineup, establish a decision matrix:

• Location for storing goods
• Destination countries served
• Responsibility for customs clearance
• Delivery status to be reported to each channel
• Selected return process

The previous sections form a reusable operational workflow for a project manager.

1. Define the channels, catalog, and responsibilities

Select the channels to launch, the initial catalog, the relevant warehouses, the countries served, and the business owners for each data flow. Without a designated owner for each data flow, incidents remain unassigned.

2. Validate Vendor Onboarding and Technical Prerequisites

Gather the Galaxus merchant file, Manor settings, API credentials or files, delivery rules, and the returns process. Confirm the target level of automation for each channel.

3. Connect and map the systems

Map SKUs, EAN/GTINs, categories, prices, available inventory, order statuses, shipping methods, and tracking IDs. Verify that each SKU points to the same reference across all systems.

4. Test inventory and order flows

Run test scenarios before any launch: single order, simultaneous orders across two channels, out-of-stock situations, cancellation before fulfillment, cancellation after shipment, returns, and duplicate order notifications. Each scenario must result in the expected status and consistent inventory reservation.

5. Launch with Enhanced Monitoring

Closely monitor initial synchronizations, mapping errors, reserved inventory, and discrepancies between projected inventory and actual warehouse inventory. Enhanced monitoring during the first few days minimizes the impact of incorrect settings.

6. Measure and Correct Discrepancies

Track the reservation conflict rate, synchronization latency, blocked reservations, and the discrepancy between projected inventory and warehouse counts. Feedpilot recommends, as architectural benchmarks, a 99th percentile synchronization latency of less than 90 seconds and a reservation conflict rate of less than 0.3% [7]. Use these benchmarks to guide your corrective actions.

This checklist summarizes the checks already explained, grouped by category.

Sales Preparation:

☐ Validated seller account or profile

☐ Selected and tested Galaxus automation level (partial or full)

☐ France-Switzerland shipping plan confirmed

Catalog Data:

☐ Catalog mapped

☐ SKUs and EAN/GTINs verified

☐ Stock “source of truth” confirmed

Integration and Warehouse:

☐ Reservation rules tested

☐ Safety stock defined

☐ Statuses mapped in a shared matrix

Shipping, Compliance, and Returns:

☐ Carriers and tracking configured

☐ Compliance responsibilities confirmed

☐ Return process defined

Monitoring:

☐ Designated escalation contact

☐ Monitoring dashboard activated

Selling on Galaxus and Manor hinges on four decisions: Meeting each channel’s seller requirements; preparing a reliable and properly mapped catalog; connecting the channels to the WMS as the single source of truth; and securing inventory reservations with a buffer and an idempotence key.

Emaloja combines marketplace integration, inventory synchronization, order processing, and logistics operations across Switzerland, France, and Europe. ​

This combination addresses a specific need: How can you sell on Galaxus from France with automated inventory and order management?

Before sales begin, align your sales channels, data flows, and warehouse operations. This alignment reduces the risk of overselling and clarifies each team’s responsibilities.