SCC Inventory vs Marketplace Listings.
At a glance
A cross-channel table that lines up your Salesforce Commerce Cloud (SFCC, formerly Demandware) inventory and availability against your live marketplace listings, pulled from a connected marketplace such as Amazon. It catches the dangerous mismatch: SKUs that are out of stock or zero available-to-sell on SFCC but still active, advertised, and sellable on a marketplace. Those are oversell-and-cancel events waiting to happen, the kind that drain marketplace seller metrics and trigger penalties. Because it spans two connectors, this card only populates when both your SFCC connector and a marketplace connector are live.
| What it counts | A SKU-level comparison. From SFCC: inventory record / available-to-sell and online status per SKU. From the marketplace connector: listing status and availability per matched SKU. The card flags SKUs that are unavailable on SFCC but still active/sellable on the marketplace (and can surface the reverse too). |
| Why it matters | If SFCC is your source of truth for stock but a marketplace listing is still live, customers can buy what you cannot ship. That means cancellations, refunds, and damaged marketplace seller standing (late-shipment and defect metrics, suppression, or account risk). It is also lost spend: ads and placement pushing a SKU you cannot fulfil. |
| Reading the value | Each row is a SKU with a mismatch. The headline is the count of SKUs out of stock on SFCC but active elsewhere. Read by exposure: a fast-moving SKU still live on a marketplace while dark on SFCC is an urgent oversell risk; a slow SKU is a tidy-up. |
| The match | SKUs are matched across systems on a shared identifier (SKU / seller SKU / mapped product code). Where mappings are missing or inconsistent, a SKU can appear mismatched simply because the two catalogues are not linked, see the reconcile section. |
| Direction of the flag | Primary flag: OOS on SFCC, active on marketplace (oversell risk). The reverse (in stock on SFCC, not listed on the marketplace) is a missed-sales signal and may surface depending on configuration. |
| Connectors feeding it | SFCC (inventory / availability) plus a marketplace connector, for example Amazon. Both must be connected. |
| Unit | number (count of mismatched SKUs) |
| Time window | RT / 24H (live availability snapshot, reconciled against recent marketplace listing state) |
| Alert trigger | >10 SKUs OOS on SCC but active elsewhere |
| Sentiment key | scc_xc_inventory_vs_marketplace_listings |
| Roles | owner, operations, marketing |
Calculation
Calculated automatically from your Salesforce Commerce Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A retailer runs an SFCC B2C realm as its source of truth for stock and also sells on Amazon via a connected marketplace connector. SFCC inventory is shared across its DTC sites. A snapshot on 12 Jun 26:| SKU | SFCC available-to-sell | SFCC online | Marketplace listing | Flag |
|---|---|---|---|---|
HERO-TEE-BLK-M | 0 | true | Active, in Buy Box | Oversell risk (high velocity) |
HERO-TEE-BLK-L | 0 | true | Active | Oversell risk |
SEASON-COAT-RED | 0 | false | Active | Oversell risk (offline on SFCC, live on marketplace) |
CLEARANCE-MUG | 0 | true | Active | Oversell risk (low velocity) |
STAPLE-SOCK-WHT | 240 | true | Inactive / not listed | Missed sales (reverse flag) |
| Flagged total (this card) | 12 OOS-on-SFCC-but-active, above the >10 alert |
- The hero tee is the row that hurts.
HERO-TEE-BLK-Mis zero on SFCC but holding the Buy Box on the marketplace. Every sale there is an order you cannot fulfil, a cancellation, and a hit to your seller defect rate. Sorted by velocity, this is the first SKU to pull or restock. The card’s value is catching it before the cancellations pile up. - One row is offline on SFCC but live on the marketplace.
SEASON-COAT-REDis marked online = false on SFCC (deliberately retired) yet still active on Amazon. That is a listing that should have been ended when the product was pulled. The mismatch is not a stock feed problem, it is a channel-sync gap, and it points at a different fix (end the listing) than a restock. - The reverse flag is money left on the table.
STAPLE-SOCK-WHThas 240 units on SFCC but is not listed on the marketplace. That is sellable inventory with no marketplace exposure, a missed-sales row rather than an oversell risk. Depending on configuration it surfaces here as the secondary direction; treat it as an opportunity, not an incident. - The same OOS SKUs may have just come from a burst. If Stock-Out Burst fired earlier, the SFCC side of these mismatches may be feed-driven zeros rather than true sell-outs, in which case the right move is to fix the feed and let the marketplace listing stand, not to end it. Always check why the SFCC SKU is at zero before acting on the marketplace.
Sibling cards merchants should reference together
| Card | Why pair it with SCC Inventory vs Marketplace Listings |
|---|---|
| Out-of-Stock Products | The SFCC side of the comparison. This card tells you which OOS SKUs are still live on a marketplace; Out-of-Stock Products is the full standing list to draw from. |
| Stock-Out Burst | Tells you whether the SFCC zeros are a recent feed event. If a burst just fired, the mismatch may be artificial, fix the feed before ending marketplace listings. |
| Top-Velocity SKUs vs Ad Spend | The other cross-channel inventory/marketing card. A fast SKU dark on SFCC but live (and possibly ad-backed) elsewhere is the worst-case oversell. |
| Revenue at Risk (live) | Sizes the exposure from oversell-and-cancel risk and from missed marketplace sales into a single revenue figure. |
| Low-Stock Products | Early warning: SKUs trending low on SFCC are the next to mismatch against a still-live marketplace listing. |
| Offline Products (online=false) | The deliberate-retirement side. SKUs taken offline on SFCC but still live on a marketplace are the channel-sync gaps this card flags. |
Reconciling against Salesforce Commerce Cloud
This is a cross-channel card. It compares SFCC inventory and availability with marketplace listing state, so reconciliation means verifying each side separately and then confirming the SKU mapping that joins them. Verifying the SFCC side (inventory / availability), in Business Manager:- Available-to-sell: Merchant Tools, Products and Catalogs, Inventory, open the relevant inventory list and confirm the flagged SKUs read zero available-to-sell. Remember the list is often shared across sites.
- Online status: Merchant Tools, Products and Catalogs, Products, check the
onlineflag for any SKU flagged as offline-on-SFCC-but-live-elsewhere. - Inventory feed health: Administration, Operations, Jobs (import history) to confirm a recent inventory feed did not wipe quantities, which would make the SFCC side a false zero.
- In Amazon Seller Central (or whichever marketplace connector is linked), open the listing for a sampled flagged SKU and confirm it is active, sellable, and whether it holds the Buy Box.
- Check the marketplace’s own quantity, some sellers hold separate marketplace stock pools, in which case “OOS on SFCC” does not automatically mean “cannot fulfil the marketplace order”.
| Reason | Direction of divergence |
|---|---|
| SKU mapping gaps. If the SFCC SKU and the marketplace seller SKU are not mapped, a SKU can look mismatched when the two records are simply unlinked. | False flags in either direction |
| Separate stock pools. Some sellers allocate dedicated marketplace inventory; an SFCC zero then does not mean the marketplace order is unfulfillable. | Over-counts oversell risk |
| Feed-driven SFCC zeros. If a stock feed wiped quantities, the SFCC side is a false zero; the marketplace listing is correctly live. | Over-counts oversell risk |
| Refresh cadence. SFCC availability is near-real-time; marketplace listing state syncs on its own cadence, so a just-ended listing may briefly still show active. | ±small at the edges |
| Channel-sync gap (offline SFCC). A SKU deliberately taken offline on SFCC but never ended on the marketplace is a genuine flag, not noise. | Correctly flagged |