Synchronization console — where to see what is happening

Integrations → Integrations → Synchronization console is the main diagnostic screen for the whole module. The page heading itself says Stock synchronization.

Step by step

Find which channel is lagging

1. Open the console. By default, it shows the 24 hours window.
2. Stay on the Overview stage. The channel table on the right has columns Name, Traffic, In queue, a column named for the current window (for example, 24 hours), Per hour, and Median.
3. A channel with a growing In queue count or an empty time-window column is the one to investigate.
4. Change the window and compare. A problem that looks constant in 1 hour may turn out to be a one-off spike in 7 days.
5. Then open the stage for the relevant pipeline: Offers, Stock and prices, Orders, Shipping, or Settings.

Trace one product across all channels

1. Find the Check one product card.
2. Enter a code in the EAN… field and click Check. Clicking any EAN in the console tables opens the same view.
3. The card expands under Full shipping history, all channels and has three sections:
   • This item now — current status on each channel (Channel, Listed, In queue, Failed, Last sent, Quantity);
   • Queue tables · recent weeks — entries from live queues (When, Channel, Stage, Status, Details);
   • Parquet archive · everything earlier — archived entries.
4. If the product appears in none of these sections, that does not mean something failed along the way; it means nothing entered the pipeline. Go to Synchronization is not working — checklist.

Read an entry’s status

1. The Status column in the main table shows one of four grouped values: Pending, In progress, Done, Failed. You can filter by these too.
2. Row details show more specific statuses: Pending, In progress, Sent, Done, Skipped, Failed, Permanently failed, Cancelled.
3. Permanently failed means retries have ended; the item will not move by itself and needs a decision. Skipped means the channel had nothing to update, not that something broke.

Process items already waiting in the queue

1. The console header has a Process queue now button. When items are waiting, their count appears in parentheses: Process queue now (128).
2. The button processes items already in the queue. It does not add anything to the queue; a product that never entered it will not appear after you click.
3. Clicking too often returns: “Already triggered just now — give it a minute.” If a connection error appears, wait a moment and try again. If the problem repeats, contact NOXTI support.

Open the archive and download data

1. The console has two separate archive-window buttons beside the four live windows: 90 days and All time.
2. Download files from the separate Offer sync archive screen at /integration/offer-sync-history. This screen is not in the menu; open it by its address. A link to it is intentional.
3. Each week has a Download button that saves offer_sync_<week>.parquet. The current, still-open week has a disabled button with the hint Export after archiving.
4. The Search product history card on the same screen searches the archive by EAN, channel, week range, and status, with Search and Clear buttons.

Stages

The console separates data by pipeline: Overview, Offers, Stock and prices, Orders, Shipping, and Settings. Start with the overview; it shows which channel is lagging before you open the details.

Time windows

Choose 1 hour, 24 hours, 7 days, or 30 days. Two archive windows, 90 days and All time, are visually separated. The default is 24 hours.

The window matters for diagnosis: something that looks constant in the hourly view may be a one-off spike in the seven-day view.

Archive

Older queue entries are archived and can be searched and exported. Data from months ago is not lost. The 90 days window reaches back thirteen complete weeks.

Live view

The screen refreshes without reloading the page. The console chooses an interval between 3 and 12 seconds based on server response speed. The header indicator says Live when data is less than 15 seconds old; otherwise it says how many seconds ago it was updated. Archive windows say Archive. Refreshing pauses while the browser tab is in the background.

What to check first

The last row matters: the console shows what entered the pipeline. A product rejected at entry — no linked offer or no warehouse mapping — will not appear here at all because there is nothing to display (Synchronization is not working — checklist).