Sales channels: types, connecting to a platform and mapping listings

What it is for

A sales channel is a place where orders come from: an online shop, a marketplace, a till or your own system. Every order in Zaksio belongs to one channel. A channel has its own stock pools (how much stock it sees), its own listings (items on the platform linked to a product from the catalogue) and, if the platform allows it, a connection through which Zaksio fetches orders and sends stock levels.

• "Manual": you enter orders yourself or upload them from a CSV file.
• "API": an integration point for your own shop or system.
• "POS till": sales in a physical shop.
• Platforms: Allegro, WooCommerce, Shopify, PrestaShop, Amazon.pl, Erli, Empik Place, Zalando, Temu, AliExpress, Google and Facebook have connectors on the server (the scope of each is described in the list below). Vinted has a file connector: ready-made CSV templates instead of synchronisation.

Where to find it in the app

Menu "Sales and logistics", item "Sales channels". The page has the tabs "Channels", "Allocation rules" and "Listings" (unassigned listings from all channels). You add a new channel in the "Channels" tab, in the "Add sales channel" window. When you open a channel, you will see the tabs "Settings", "Stock pools", "Listings", "Connection" and "Synchronisation". Channel types that are platforms require the "Sales channels" module. Changes require write permission for channels; the salesperson role can only view channels.

Step by step: connecting to a platform

1. Add a channel of the right type and open its "Connection" tab.
2. The form is built from the platform description, so fields differ between platforms (e.g. "Client ID" for Allegro, "Shop address" for WooCommerce). Next to it you will find short instructions on obtaining the keys and a link to the platform documentation. Details are in separate articles for each platform.
3. Enter the keys and click "Save credentials". The keys are encrypted and never return to the browser: you only see which fields are set. When changing them, enter only the field you want to change; empty fields stay unchanged.
4. Click "Check connection". Zaksio sends one request to the platform and shows "Connected as ..." or the reason for the refusal. In Allegro, you must authorise the account first.
5. Configure the stock pools and map the listings (below), read the article about the first synchronisation and only then click "Start".

Saving new keys deletes the existing authorisation and turns synchronisation off until the connection is successfully checked again.

Synchronisation: Start and Stop

Synchronisation does not start by itself after you save the keys. "Start" works only after a successful "Check connection", and "Stop" pauses fetching and sending. The "Synchronisation" tab shows stock and price jobs, a "Retry" button for failed ones, and "Run synchronisation" and "Full reconciliation" for manual forcing. The "Integration health" card collects the channel's latest errors. The channel run covers: orders, listings, stock levels, tracking numbers, returns. The channel's first "Start" does not turn sending on right away: it creates a change plan for you to review and approve (see the article about the first synchronisation).

Listing mapping

A listing is a channel item (e.g. an auction or a product in a shop). For an order to be fulfilled and stock to be sent, the listing must point to an item from the catalogue. Zaksio matches listings automatically by SKU and EAN. If a listing's SKU and EAN point to two different items, it does not choose for you: the listing gets a conflict status and waits for your decision in the "Listings" tab. You assign the rest manually with the "Assign item" button. An order with an unknown listing appears in the list as "Unassigned".

Connector scope

• Allegro: with OAuth; orders, listings, stock levels, prices (optional), parcel number. A return reported on Allegro notifies the team.
• WooCommerce and Shopify: orders, listings, stock levels, prices (optional), parcels.
• PrestaShop: orders, listings, stock levels, parcels; no prices.
• Amazon.pl (SP-API): orders shipped by the seller, listings, stock levels, prices (optional), parcels. Requires Amazon to approve the roles (see the Amazon.pl article).
• Erli: orders, listings, stock levels, prices, parcels. No approval needed on the platform side (see the Erli article).
• Empik Place: orders after acceptance in the Empik panel, listings, stock levels, parcels; no prices. Requires an agreement with Empik Place (see the Empik Place article).
• Zalando: orders, stock levels and prices by EAN, parcels; no list of listings. Only for partners with a contract and access to zDirect (see the article about Zalando).
• Temu: orders, listings, stock levels, parcels; no prices. Requires an approved application and a DPA agreement (see the article about Temu).
• AliExpress: orders, listings, stock levels, prices (optional), parcels, with OAuth. Requires an approved Self Developer app (see the AliExpress article).
• Google (Merchant Center): only listings, availability and prices, no orders. No partner approval needed (see the Google article).
• Facebook and Instagram (Meta catalogue): only listings, stock levels and prices of existing products, no orders (see the Facebook article).
• Vinted: import from a CSV file only, using ready-made templates, without synchronisation (see the article about CSV import).
• Manual / CSV import: orders and listings from a file, without synchronisation.
• Customer API: an integration point for your system, Zaksio does not fetch anything from it.