Skip to content

Offer page ​

The Offer page shows everything Stock Sync knows about one offer: what its status means and what to do, the path its stock takes from the PIM to the marketplace, its details, and its history of steps and marketplace calls. Use it when a stock number looks wrong and you want to know why.

You see the same content in two places:

  • Beside the list — click a row on Offers (or an account's Offers tab) and the offer opens in a side panel. J and K move to the next and previous offer; Esc closes it.
  • On its own page — Open full page in the side panel or in a row's ⋯ menu. The page's address is the offer's own: copy it to send a colleague straight to the offer.

The page at a glance ​

The Offer page of offer 310458 of Fashion Days RO: the teal FR badge, TOMMY HILFIGER Slim fit organic cotton polo, MW0MW17770-DW5 · M, Offer 310458 on Fashion Days RO; Resync and Copy id; a green box In sync, The marketplace shows the number Stock Sync wants, What to do: Nothing; the stock path 7 › Eligible › 7 › 7 › 7; the Details; and the History on the right

From top to bottom:

  • The account's badge, then the product: its brand, its name, and its SKU · size. An offer whose product PIM has not named yet shows Offer and its id; a not linked offer says No PIM product.
  • Offer 310458 on Fashion Days RO — the marketplace's offer id and the account, a link to the account.
  • The actions: Resync (operators; see Resync), Retry for a failed offer (operators), Open in PIM (the linked product in PIM, in a new tab; only when the product has a page in PIM, so the pictures here show none) and Copy id (copies the offer id).
  • What this means — the status in a sentence, with what to do.
  • Stock path — the five steps from the PIM to the marketplace, the step that is off coloured.
  • Details — every figure, with links to PIM and the marketplace.
  • History — what happened to the offer and every call to the marketplace, newest first. On the page it is a column on the right; in the side panel it comes last.

The trail at the top of the screen reads Offers › [product]: click Offers to go back to the list. The browser's Back button returns to the list with your view and filters.

What this means ​

The coloured box under the actions says what the offer's status means and what to do, in the same words as the status's tooltip and Every status explained:

  • The status, for example Rejected, and its meaning: The marketplace refused the number for a business reason: a campaign lock, offer not found, or a validation error.
  • What to do: for example Read the problem. Campaign locks retry by themselves every 6 hours; otherwise fix the cause, then Resync.
  • For an ABOUT YOU offer that is Sent, awaiting confirmation: Sent 12 at 30/09/2026, 10:51, waiting for the marketplace to confirm.
  • What the marketplace says, when it matters: Ended on the marketplace — no stock sent, a validation reason such as Blocked — no stock sent, or Switched off on the marketplace.
  • The last problem in the marketplace's words, in a grey box, with the next attempt while Stock Sync retries by itself.

The box is green for an offer in sync, amber while waiting, red when it needs a person, grey when there is nothing to do.

The stock path ​

Five boxes, left to right, follow one stock number from the PIM to the marketplace. The box where things go wrong is coloured: amber while waiting or when the marketplace shows something else, red when stuck or orphaned. Hover over a box for what it is.

StepBig numberUnder it
PIM stockWhat PIM says can be sold (available)N on hand, for reference only
RulesEligible, Not eligible or OrphanedThe lead time and the account's limit, for example lead time 5 days, limit 2 days, or no lead-time limit
Stock to publishThe number Stock Sync wants the marketplace to showthe target
SentThe last number the marketplace acceptedHow long ago; or N waiting to send, N awaiting confirmation, nothing is sent (withheld by the marketplace), or never
Marketplace showsWhat the marketplace reported at its last daily offer importat the last offer import, or differs from the target

A not linked offer has no path: the box says Not linked to a PIM product: Stock Sync never sends stock for this offer. and what to do if it should sync.

How the numbers fit together ​

Read the path from left to right. For offer 310458:

  1. PIM stock 7 (9 on hand).
  2. Rules: Eligible, so Stock to publish is 7.
  3. Sent 7, 2 minutes ago.
  4. Marketplace shows 7. Everything agrees, so the offer is In sync and no box is coloured.

When the numbers do not agree, the box where they part tells you where to look:

What you seeWhat it means
PIM stock looks wrongThe problem is in the PIM or the warehouse, not in Stock Sync. Tell the product data team.
Rules amber, Stock to publish 0The lead-time limit made it 0 (Not eligible). A cap of 65,535 also applies.
Rules red: OrphanedThe PIM product was removed; Stock Sync sends 0.
Sent amber or redThe new number is not on the marketplace yet: it is Waiting to send, Sent, awaiting confirmation, Rejected or Failed. Read the last problem in What this means.
Marketplace shows amber, differs from the targetSomeone or something changed the stock on the marketplace after Stock Sync sent it, or the new number went out after the last import. The next offer import notices a difference and Stock Sync sends its own number again by itself; Resync does it now.

How the quantity is calculated has every rule. Find out why a stock number is wrong walks you through it step by step.

Details ​

RowWhat it showsExample (offer 310458)
AccountThe account, a link to itFashion Days RO
MarketplaceThe marketplace the account talks toFashion Days Romania
Marketplace stateOn sale, Switched off (Switched off on the marketplace) or Ended (Ended on the marketplace — no further stock is sent). Hover for what it means.On sale
Marketplace validationThe marketplace's validation reason, or Nothing reported. A reason that stops stock adds — no stock is sent until it is fixed; the next daily offer import after the fix sends it again.Nothing reported
PIM productPIM product id · SKU · size, then Open in PIM (the product in PIM, new tab) when linked, and Open in the marketplace (for example Open in ABOUT YOU: the product in ABOUT YOU's Seller Center, searched by its SKU).310458 · MW0MW17770-DW5 · M
BarcodesThe EAN barcode(s) of the linked PIM product8712423341784
PIM stockx available / y on hand7 available / 9 on hand
Lead timeDays the product takes to deliver, from the PIM; unknown when the PIM has none1 day
EligibleYes, or No with the lead time and the limitYes
Stock to publishThe number Stock Sync wants the marketplace to show7
PublishedThe last quantity sent, last synced how long ago, and the exact time7 · last synced 2 minutes ago (…)
Marketplace showsWhat the marketplace reported at the last offer import (at least once a day)7
Last problemThe last error in the marketplace's words, or ——
Last changeWhen anything about the offer last changed1 minute ago

History ​

The history lists the offer's recent past, newest first: the last 50 steps and the last 20 marketplace calls. Steps are kept for 90 days and calls for 30 days. It follows live updates: a new step appears the moment it happens. There are two kinds of entry.

Stock sync entries are steps in the offer's life:

EntryMeans
Linked to PIM productThe offer was matched to its PIM product
Orphaned (product removed from PIM)The PIM product disappeared; the offer is now sent 0
Stock to publish changedA new quantity was worked out: the PIM stock changed, the account's settings changed, or the product left the PIM
Queued to be sent againSomeone pressed Resync, Resync stock or Retry failed. The stock is sent again even when the number has not changed
Marketplace showed a different number, queued to be sent againThe offer import found another number on the marketplace than the one sent, for example after an order. Stock Sync sends its own
Offer can receive stock again, queued to be sentThe marketplace had ended or refused the offer and no longer does. The stock it missed meanwhile is sent
Sent, awaiting confirmationThe quantity was sent to ABOUT YOU, which has not said yet whether it applied it
PublishedThe marketplace accepted the quantity
Rejected by the marketplaceThe marketplace refused the quantity
Failed after retriesSending gave up after every retry

Click Details under an entry to see its data, for example the new stock to publish and why it was queued:

The history of offer 310458 with Details opened under Stock to publish changed, showing cause catalog, desiredQuantity 7 and publishedQuantity 9

In DetailsMeans
desiredQuantityThe stock to publish: the number to send
publishedQuantityThe number the marketplace had, as far as Stock Sync knows: the last one it sent, or the one the offer import found there
submittedQuantityOnly on an ABOUT YOU offer that was Sent, awaiting confirmation: the number on its way, which this one replaces
causeWhy it was queued: catalog (Stock to publish changed), resync (Queued to be sent again), drift (Marketplace showed a different number) or release (Offer can receive stock again)
channelAccountId, externalOfferIdThe account and the offer id

The same number in desiredQuantity and publishedQuantity is normal for a resync, which sends the number again on purpose. Older lines, recorded before Stock Sync kept the cause, have none.

Marketplace entries are calls Stock Sync made to the marketplace, for example called offer/save · HTTP 200 · 184 ms: Stock Sync called the marketplace's offer/save service, the marketplace answered with code 200 (it received the call), and the answer took 184 milliseconds. Request and response shows exactly what was sent and what came back.

Call lineMeans
HTTP 200The marketplace answered. Look inside: it can still refuse the quantity.
HTTP 429The marketplace was busy. Stock Sync waits and retries by itself.
HTTP 401, HTTP 403The marketplace refused the credentials (401) or does not allow this user, or our server, to use its API (403). The whole account is suspended.
HTTP 503, HTTP 500The marketplace had a problem. Stock Sync waits and retries by itself.
no answerThe marketplace did not answer in time. Stock Sync waits and retries by itself.

Retries wait longer each time, from 30 seconds up to 30 minutes. After about an hour of failures the offer becomes Failed. Sending stock to the marketplace has the timetable. User names, passwords and tokens are never shown in these details.

Resync ​

Resync sends this offer's stock to the marketplace again, even if the number did not change. Hover over it to read exactly that before you click. It acts at once, with no confirmation:

Offer 310458 right after Resync: a green message at the bottom right says the offer is queued to be sent again

The message reads "Offer 310458 is queued to be sent again." The history shows Queued to be sent again straight away. On an account that is Sending, a marketplace call and a Published entry follow within moments; otherwise the offer waits as Waiting to send.

When Resync cannot help, it is greyed out and the reason is written under it: Resync is not available — Not linked to a PIM product: Stock Sync never sends its stock. The reasons:

ReasonWhy
Not linked to a PIM product: Stock Sync never sends its stock.There is nothing to send
Its PIM product was removed: Stock Sync already sends 0 for it.An orphaned offer is already sent 0
The offer has ended on the marketplace: no further stock is sent.An ended offer never gets stock again
[reason] on the marketplace. Stock is sent again from the first daily offer import after it is fixed.The marketplace withholds the offer (for example Blocked); a resync would be refused
Stock Sync has not worked out a stock to publish for it yet.Wait for the next recalculation

A Failed offer also has Retry, which does the same as Resync, worded for what you are doing: Send this failed offer again. Use it once the marketplace works again.

Examples ​

An offer sent to ABOUT YOU ​

ABOUT YOU accepts a stock update first and confirms it a moment later. In between the offer is Sent, awaiting confirmation (amber), What this means says Sent 12 at 30/09/2026, 10:51, waiting for the marketplace to confirm, and the Sent step reads 12 awaiting confirmation. When ABOUT YOU confirms, the offer turns In sync and Published becomes 12. If it refuses, the offer is Rejected with ABOUT YOU's reason. If nothing has been answered after 30 minutes, it is Waiting to send again and the stock is sent again. Sending stock to the marketplace tells the whole story.

An ABOUT YOU offer's id is its SKU. Marketplace validation can read Rejected in review or Needs correction: both only inform, the stock is still sent, so it is right when the product goes on sale again.

A rejected offer ​

Offer 305660 of Fashion Days RO, TOMMY HILFIGER Essential crew neck jumper, rejected: a red box with the meaning, what to do and the marketplace's reason, Stock value 250 is above the maximum of 200 allowed for this offer; the stock path 250 › Eligible › 250 › Sent 180 in red › Marketplace shows 180 in amber; the history with a call answered HTTP 200 and Rejected by the marketplace

The PIM has 250 available, so Stock Sync wants to publish 250. The marketplace allows at most 200 on this offer, so it refused: the Sent step is red and still shows 180, and Marketplace shows 180. The call in the history answered HTTP 200, but inside it says "isError": true with the same message. Stock Sync does not retry this rejection by itself, because sending the same number would get the same answer. Someone must change the limit on the marketplace, or accept it; then Resync sends the number again.

Another common rejection is a campaign that locks the stock of an offer ("The offer is in an active campaign…"). That one Stock Sync retries by itself, every 6 hours for up to 14 days, because the lock ends with the campaign. Messages and what they mean explains the usual marketplace texts.

A failed offer ​

Offer 298117 of Fashion Days RO, NIKE Air Max SC trainers, failed: Resync, Retry and Copy id; a red box saying sending kept failing and Stock Sync gave up after 8 attempts, with the last problem eMAG offer/save request failed: Headers Timeout Error; the stock path 11 › Eligible › 11 › Sent 9 three hours ago in red › Marketplace shows 9 in amber; the history with Failed after retries, a call with no answer after 30000 ms and an earlier one answered HTTP 503

Stock Sync wants 11, the marketplace still shows 9, the last successful send was 9 three hours ago. The history shows the attempts: first HTTP 503 (the marketplace was unavailable), then no answer after 30,000 ms. The marketplace had an outage. When it is back, click Retry here, or Retry failed on Offers to retry every failed offer at once.

An offer that is not eligible ​

Offer 312870 of Fashion Days RO, TOMMY JEANS Essential hooded sweatshirt: In sync, with the line Not eligible — publishes 0; the stock path 6 › Not eligible in amber (lead time 5 days, limit 2 days) › 0 › 0 › 0; in the Details, Eligible reads No — 5 days > 2 days

The PIM has 6 pieces, but they take 5 days to reach the customer. The account only sells products that arrive within 2 days, so the Rules step is amber, Not eligible, and Stock Sync publishes 0 on purpose; the offer is In sync with 0. This is not an error. To sell it, either the product's lead time changes in the PIM, or an operator raises the account's lead-time limit in its Stock rules.

Good to know

  • A viewer sees the same page and panel without Resync and Retry.
  • Everything on the page follows live updates: when the offer is sent or its stock changes, the status, the path and the history change by themselves.
  • The old addresses of an offer (from bookmarks or e-mails) still open it.

Channel Hub Stock Sync — user guide for operators and viewers