Changes and alerts — outbound queue and stock discrepancies

The last two tabs on the offers screen help you monitor what does not match between us and the marketplace.

Step by step

Change offer prices

1. On the List tab, select the offer rows whose prices you want to change.
2. Click Actions and, in Scheduled changes, choose Change prices.
3. In Price type, choose Regular price or Promotional price.
4. Under Price source, choose From WMS to take the price from the database separately for each offer, or Manual to enter it yourself.
5. If you chose Manual, select one of the options under Change mode—Fixed price, Percentage change, or Amount change—and enter a value.
6. Under Application mode, leave Preview changes selected if you want to review the result first.
7. Click Preview changes, review the columns, and confirm with Confirm and apply. If you choose Apply without preview, finish with Apply changes.
8. Open the Changes tab and check that the items have the Queued status.

Changes are not sent immediately; they enter a queue processed in the background.

Find out why a price did not arrive

1. Open the Changes tab.
2. Narrow the list with the Change type filter or a status filter to find Failed items.
3. Click an item to open Change details.
4. Scroll to Event log. It records what happened to the item and the marketplace's response.
5. If the cause was temporary, use Retry failed. If the change is no longer current, use Cancel change; for the entire set, use Cancel all.

Close a stock discrepancy alert

1. Open the Alerts tab.
2. Compare WMS stock and Marketplace stock; the difference appears in the Discrepancy column.
3. Identify the cause from the three cases described below.
4. If our stock should be sent to the marketplace, use Sync to marketplace—this is the same route as Send stock in the offer list (Offer actions — download, quick sync, refresh).
5. When the issue is understood, close the item with Resolve. Mark an alert you will handle later with Acknowledge; set an irrelevant alert aside with Ignore.

Remember what Resolve does: “Resolving does not change stock levels anywhere—it only closes the alert.” Closing an alert does not fix the discrepancy.

Changes

A queue of modifications being sent to the marketplace—primarily price changes. Each item has a status, from draft to completed, and an immutable event log recording what happened, when, and with what result.

The event log is the right place to answer “why did the price not arrive?” The answer is recorded there along with the marketplace's response.

Changes can be scheduled for later. A mechanism processes scheduled items periodically and cleans up expired ones.

Channels that do not support changes

Not every connector has an outbound changes layer. For a manual channel and some newer connectors, the changes queue will not work—the item simply has no way to be sent.

An inactive connection stops the queue

Disabling a connection stops processing all its price and attribute changes (Switches that stop an entire channel).

Stock discrepancy alerts

These detect cases where our stock and the marketplace stock differ. Alerts range in severity from low to critical.

Three possible causes of a discrepancy

This is not an action sequence; it is a list of cases. Identify which one applies:

• The stock update did not arrive—check the queue and exclusions (Synchronization is not working — checklist).
• The offer is not linked to a product (Linking a listing to a product — without it, nothing gets sent).
• Someone changed the stock manually on the other side, in the marketplace control panel.

An alert without a linked offer cannot be sent. In that case, the Sync to marketplace button returns “This alert has no linked marketplace offer”.

Review alerts regularly: a stock discrepancy can result in selling goods you do not have or failing to sell goods you do have. Both cases cost money.

See the wider picture

These tabs cover individual offers. To see the full synchronization pipelines, open the console (Synchronization console — where to see what is happening).