First channel synchronisation: what will happen to stock levels on the platform

What it is for

Turning synchronisation on for the first time is the moment when Zaksio may change a great many stock levels on your platform at once. That is why the first "Start" sends nothing: the channel switches to preview mode (dry-run) and prepares a change plan. This article describes the plan, its contents and what happens after approval.

Where to find it in the app

Sales and logistics, "Sales channels", the chosen channel. The "Connection" tab (check), "Stock pools" (how much stock the channel sees), "Listings" (mapping) and "Synchronisation" (the "Run synchronisation" button, the "First synchronisation plan" screen, the job queue). "Stop synchronisation" and "Run synchronisation" turn the channel's entire synchronisation off and on.

Step by step: before "Start"

1. Save the keys and click "Check connection". Without a successful check, synchronisation cannot be turned on, just as with a paused or disabled channel.
2. In the "Listings" tab, map listings to items. Zaksio assigns listings with a matching SKU or EAN by itself; you must resolve conflicts manually. We send stock levels only for listings that point to an item.
3. Check the stock levels of these items. Every item with no stock in the warehouse will be set to 0 on the platform.
4. In the "Stock pools" tab, set how much stock the channel should see (modes "Everything", "Percentage of stock", "Fixed number") and the buffer subtracted from the calculated quantity. Without any pool, the channel sees all available stock.
5. Export the stock levels from the platform panel if you want something to go back to.
6. Click "Run synchronisation". Zaksio will fetch orders from the last few days, plus listings with stock levels and prices, from the platform, calculate the differences and show the "First synchronisation plan" screen.
7. Review the plan, tick the operations, enter the confirmation and click "Approve and run" (described below).

First synchronisation plan

The plan is created in preview mode: Zaksio only reads data from the platform and compares it with the warehouse. Nothing changes on the platform, and no orders or listings are created in Zaksio. The summary shows the numbers, with details in groups below.

• Orders to import: from the last 7 days (you can change the window in the synchronisation settings or in the plan, from 0 to 90 days). We skip orders that are already in Zaksio.
• Listings: new channel listings and a split into mapped, unmapped and in conflict (the same as with SKU and EAN mapping).
• Stock levels to send: the listing, its stock level on the platform and the target stock level from Zaksio. This is an overwriting operation, ticked by default.
• Prices to send: disabled and unticked by default. Ticking prices also enables continuous sending of prices for the channel.
• Unmapped listings with stock on the platform: zeroing is off and unticked by default. Tick it only if you deliberately want to zero such listings.
• A connector that does not read listings from the platform is marked "import only" in the plan: the plan then covers orders, and stock level differences cannot be calculated.

To approve the plan, type the sentence "I understand that stock levels on the platform will be overwritten" and click "Approve and run". The plan is valid for 24 hours: after that it expires and you need to run the synchronisation again to generate a new one. Changing the channel keys also invalidates the plan, because it may be a different platform account.

What happens after approval

• Listings from the platform go into the channel, and the ticked stock levels and prices go into the send queue. Unticked stock levels are held back: Zaksio does not send them for those listings until you release them.
• Ticked zeroing of unmapped listings is carried out immediately, and the result for each listing is recorded in the plan.
• Orders: the first import covers the last 7 days (the "Import orders back" setting). Unticking the orders group in the plan skips the history import. The import is idempotent, so the same order will not be created twice.
• Prices: not sent to the platform by default. They are enabled by ticking prices in the plan or by the "Send prices to the platform" setting.
• Stock levels: besides the first reconciliation, they repeat every 6 hours and after a full fetch of listings. A stock mismatch on the platform side is therefore corrected periodically, not in real time.
• Subsequent runs after stopping synchronisation do not require a new plan.

How to turn it off

Click "Stop synchronisation" in the channel. This pauses fetching and sending, but does not undo anything: stock levels already sent stay on the platform. You can also stop synchronisation by setting the channel to "Paused" or "Disabled". The platform administrator can disable synchronisation globally or for an organisation.

Errors and dead jobs

• A stock or price job with a permanent error has the status "Failed" and requires a manual "Retry" in the "Synchronisation" tab. Temporary errors are retried automatically with an increasing interval from 30 seconds to an hour; after 5 attempts the job also becomes "Failed" and the team receives an alert.
• An order that could not be imported is retried up to 5 times, then moves to failed with an alert. Synchronisation carries on and no order is lost.
• "Reconnection required": the platform rejected the keys or token (after one refresh attempt). Channel synchronisation is paused and the team receives an alert. Enter the keys again, and in Allegro authorise the account anew.
• Circuit: after 5 consecutive runs with a connection error the circuit opens, and further attempts are spaced out (up to an hour) and generate an alert. A "too many requests" (429) response from the platform pauses the channel for the time it specifies, without counting errors.