Marketplace offer — our local mirror of a listing

An offer is a local copy of one listing on one marketplace. It is not a product—it mirrors what the buyer sees on the other side.

One product can have many offers: on different channels, in different countries, and with different fulfillment models.

Step by step

Check whether a product has a mirror on a channel

1. Open a product from the Products list and go to the Offers tab—the number of offers appears beside its name.
2. An empty tab means the product has no listing mirror. This is not an error; it simply is not listed anywhere, or the offer has not been downloaded yet.
3. The table has Marketplace, Status, Offer ID, MP price, WMS price, Δ Price, MP stock, WMS stock, Δ Stock, Last sync, and Actions columns.
4. Status shows a system description: Active, Inactive, Ended, Blocked, or Draft. The third is stored in the system without Polish diacritics. Note: in the full offers list (Integrations → Marketplace Offers), the same column shows the raw code: ACTIVE, INACTIVE, ENDED, BLOCKED, DRAFT.
5. A tile above the table summarizes stock agreement: OK if stock on all offers matches the warehouse, or Discrepancy (stored without Polish diacritics), under Stock synchronization.

Check the same thing from the channel side

1. Open Integrations → Marketplace Offers, on the List tab.
2. Search by EAN, SKU, or title—the field hint says Search by EAN, SKU, title….
3. No result for an EAN you know is on the channel means the mirror has never been downloaded. Download it: Tools → Download all offers (Listings screen — four tabs).
4. A found offer whose row has no product is unlinked. Neither stock nor price passes through it.

Decide whether an empty tab is a problem

1. Check which group the channel belongs to (Connected marketplaces and what each one cannot do).
2. Code-based channels—AboutYou, Ceneo, Shoper, Temu, Tradebyte—send stock by EAN or SKU (AboutYou by SKU) and do not need a linked offer to send stock. An empty offers list is normal for Ceneo, Shoper, Temu, and Tradebyte. AboutYou's offer list should be populated because price changes use it; an empty list means offer downloads are disabled.
3. On other channels, a product without a linked offer is silently skipped during stock updates, with no queue entry.

What an offer stores

An external ID, EAN, SKU, title, status, country and subdomain, fulfillment model (for example, seller-fulfilled versus marketplace-warehouse fulfillment), and—in separate tables—price and stock with their change history.

Offer statuses

By default, stock is sent only to active offers. It is sent to inactive offers if you enable Send stock to inactive offers or Automatically resume inactive offers in the integration settings. Offers with Ended, Blocked, or Draft status are always skipped. The system status is used—for example, an offer Zalando calls blocked or suspended is Inactive here.

For Trendyol and InPost Buy, after every complete offer download the system marks an offer Inactive if the marketplace no longer returns it—and stops sending stock to it. It does this only when the download has completed across the entire catalog without an error; an interrupted download changes nothing. Products Trendyol is still reviewing or has rejected are also Inactive.

Resuming inactive offers

Some marketplaces (for example, Zalando) disable an offer after it receives stock 0 and reactivate it only when stock greater than zero arrives. If that stock update never arrives, the offer remains inactive even though the goods are in the warehouse.

Resumption is available only for integrations with marketplaces that work this way—currently Zalando. Other channels have neither the setting nor a section with a button.

• Automatic—in the integration's Advanced step, enable Automatically resume inactive offers. Once a day, the system finds offers that are inactive with marketplace stock 0 but have stock available for sale in our system, then queues a regular stock update for them. It considers only offers whose marketplace status code is on the Resume offers with these marketplace status codes list—by default ZANOS_01 (no stock) for Zalando. It skips a product whose update is currently running or that had any queue entry in the last 23 hours. If an offer remains inactive after three such daily attempts within a week (button clicks do not count), the system stops trying—the marketplace apparently does not resume an offer based on stock alone.
• Manual—the Resume inactive offers section in the same step shows how many products are waiting. Resume inactive offers now queues the update immediately (with 2FA confirmation). It bypasses the daily limit and attempt limit, but requires stock synchronization to be enabled, a warehouse mapped for stock synchronization, and one of these settings: Automatically resume inactive offers or Send stock to inactive offers.

Offers that are inactive for a reason other than no stock are not resumed: paused by you (Zalando PAUSE_06), blocked by the marketplace (ZABLO_…, for example, old season or missing data), under review (ACSBL_…, JETBL_…), or missing a price (ZANOP_01). Sending stock alone will not resume them. Change the code list in integration settings; an empty list stops resumption entirely—the section will show a message instead of considering all inactive offers.

Offers fulfilled from a marketplace warehouse (Zalando ZFS) are not resumed. Nor is an inactive offer when the same product already has an active offer on the same channel—the stock goes to the active one instead. An offer is also skipped if stock for its country would be zero anyway—for example, if the product is marked unavailable there or stock is below the minimum, unless the product is excluded from that rule.

Two settings beside the code list narrow resumption further:

• Resume offers with this fulfillment type—by default, only our warehouse (partner fulfillment), because that is the stock you control. The second option, unknown fulfillment, includes older offers downloaded before Zalando began splitting them by country; some are actually ZFS, so choose this knowingly. ZFS offers cannot be selected at all.
• Resume offers in these countries—empty means all countries. Selecting countries limits resumption to those markets; an offer without an assigned country is included only when the list is empty.

An empty fulfillment-type list, just like an empty status-code list, stops resumption and shows a message instead of including everything.

Important: both settings determine which offer triggers resumption, not which offer receives the update. The queue holds one entry per product and channel. So when a product enters resumption through its German offer fulfilled from our warehouse, the same stock update also goes to its other Zalando offers—including its French offer and its sibling ZFS offer. This is how every stock update works, not just resumption.

Disabling both settings (Automatically resume inactive offers and Send stock to inactive offers) removes pending resumption updates from the queue—they could not reach inactive offers anyway.

Offers newly linked to a product during an offer download or automatic linking immediately receive a stock update, without waiting for a warehouse stock change, as long as the offer can receive stock (active, or inactive only if one of the settings above is enabled) and the integration has a warehouse mapped for stock synchronization. Manually linking one offer does not do this; use the resume button or wait for the next stock change.

Pitfall: an ended or blocked offer sharing a key with a live offer can block the live offer in the queue until its entry is permanently rejected or cleared. Symptom: stock for one specific product stubbornly does not update while everything else works.

Offer without a product

An offer does not have to be linked to a product. An offer downloaded from a marketplace remains unlinked until someone matches it.

This has a specific consequence: neither stock nor price passes through an unlinked offer. Matching is described in Linking a listing to a product — without it, nothing gets sent.

Fulfillment model

Some channels distinguish seller-warehouse fulfillment from marketplace-warehouse fulfillment. These are two separate offers for the same product, and they may have different stock—an offer fulfilled by the marketplace should not receive your stock.

You can also manually choose which warehouse to use when calculating stock for a specific offer.

“Not synchronized” marker

Offers migrated from older versions may be marked as not synchronized—these are placeholder records without marketplace confirmation. Refresh them before relying on them (Offer actions — download, quick sync, refresh).