Skip to main content
Metrics type: Key Metrics • Category: Ecommerce Platform
SCC Inventory vs Marketplace Listings.

​
At a glance

A cross-platform 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.

​
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: Things to notice:
  1. The hero tee is the row that hurts. HERO-TEE-BLK-M is 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.
  2. One row is offline on SFCC but live on the marketplace. SEASON-COAT-RED is 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.
  3. The reverse flag is money left on the table. STAPLE-SOCK-WHT has 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.
  4. 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

​
Reconciling against Salesforce Commerce Cloud

This is a cross-platform 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 online flag 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.
Verifying the marketplace side (listing state), in the marketplace:
  • 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”.
Verifying the SKU mapping: The card matches SKUs across systems on a shared identifier. A missing or wrong mapping is the most common false flag. Because no single Business Manager report equals this card, treat the reconcile as “confirm SFCC availability, confirm the marketplace listing, then check the SKU mapping”. If you sell on more than one marketplace, confirm which connector feeds the comparison.

​
Known limitations / merchant FAQs

Which marketplace feeds this card? Whichever marketplace connector you have linked, commonly Amazon. The card compares your SFCC inventory and availability against that marketplace’s live listings. If no marketplace connector is connected, the card cannot populate, because the “active elsewhere” half of the comparison has no source. Connect a marketplace first. A SKU is flagged but we hold separate stock for the marketplace. Is that a false alarm? Possibly. If you run a dedicated marketplace inventory pool, an SFCC zero does not mean you cannot fulfil the marketplace order, and the flag is conservative rather than wrong. Confirm in the marketplace’s own inventory whether stock exists there. The card uses SFCC as the source of truth; if your operating model splits stock by channel, treat these rows as “check”, not “pull”. A SKU shows OOS on SFCC but we know it sold this morning. Why? Check whether a stock feed just wiped quantities. If Stock-Out Burst fired, the SFCC zero may be a feed event, not a true sell-out, in which case the marketplace listing is correctly live and the fix is to repair the feed, not to end the listing. Always confirm why the SFCC side is at zero before touching the marketplace. What does the reverse flag (in stock on SFCC, not listed) mean? It is a missed-sales signal: sellable inventory with no marketplace exposure. Depending on configuration it surfaces here as the secondary direction. Treat it as an opportunity to list, not an incident. It is the inverse risk to oversell: instead of selling what you cannot ship, you are sitting on stock no marketplace shopper can see. Why are some SKUs flagged that are not even the same product? Almost certainly a SKU mapping gap. The card joins SFCC SKUs to marketplace seller SKUs on a shared identifier; if the mapping is missing or inconsistent, unrelated records can appear mismatched. Cleaning up the SKU mapping between SFCC and the marketplace is the highest-leverage fix for this card’s accuracy. How fast does this update? The SFCC availability side is near-real-time; the marketplace listing side syncs on the marketplace connector’s cadence, so the comparison is a live SFCC snapshot reconciled against recent marketplace state (hence the RT / 24H window). A listing you just ended may briefly still show as active until the next marketplace sync. For oversell prevention, treat a fresh flag as actionable rather than waiting for perfect agreement. Can I tune the alert? Yes. The default fires at more than 10 SKUs out of stock on SFCC but active elsewhere; the threshold and the engagement of the reverse flag are configurable per profile in the Alert Rules tab. A high-SKU-count seller may want a higher threshold; a curated catalogue where any oversell risk is serious may want a lower one.

​
Tracked live in Vortex IQ Nerve Centre

SCC Inventory vs Marketplace Listings is one of hundreds of KPI pulses Vortex IQ tracks across Salesforce Commerce Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.