Disabled Products, Ecwid

Disabled Products: count of products set to disabled and hidden from the storefront. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Ecommerce Platform

Count of products set to disabled (hidden from the storefront).

At a glance

Live count of products marked disabled in the Ecwid catalogue, meaning they are hidden from the storefront and cannot be bought. On Ecwid, disabling is the normal way a merchant takes a product out of sale without deleting it: seasonal items, sold-out one-offs, drafts in progress, or lines being reworked. The card is informational. Its value is catalogue hygiene, a quiet trend up may mean products are silently dropping out of the shop, and a sudden jump may mean a bulk edit or sync went wrong.

What it counts	COUNT(products WHERE enabled = false) across the whole catalogue, evaluated in real time. A disabled product does not render on the storefront widget.
API endpoint	GET /v3/{store-id}/products (paged, max 100 per call, OAuth2 with read_catalog scope). The engine reads each product’s enabled flag. Webhook updates fire on product.updated.
What “disabled” means	The product exists in the catalogue but is hidden from buyers. It keeps its data, images, and history; re-enabling restores it instantly. This is different from deleting, which removes the product entirely.
What it excludes	Deleted products (gone from the catalogue), and products that are enabled but out of stock (those are visible but unbuyable, tracked by Out-of-Stock Products).
Disabled vs out of stock	Distinct states. Disabled = hidden by merchant choice. Out of stock = visible but at zero quantity. A product can be both.
Why merchants disable	Seasonal pause, sold-out limited editions kept for later, draft products not ready to publish, lines under photo or copy rework, or items withdrawn pending a supplier fix.
Currency	number. A count of products, not a money figure.
Time window	RT (real time). The card reflects the current catalogue state.
Alert trigger	None - informational. The card surfaces the count for hygiene review; it does not fire a threshold alert.
Roles	owner, operations.

Calculation

Calculated automatically from your Ecwid 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 small US apparel reseller running an Ecwid widget on their Wix site, catalogue review on 21 Apr 26.

The reseller carries a mix of evergreen basics and seasonal drops. They disable seasonal lines between seasons rather than deleting them, so artwork and pricing are preserved for the next run.

Snapshot	21 Apr 26	21 Mar 26	Change
Total Products	142	138	+4
Disabled Products (this card)	31	18	+13
Enabled and live	111	120	-9

Disabled Products:   31
Total Products:      142
Share disabled:      31 / 142 = 21.8%
Read: roughly one in five products is hidden from buyers

What it means for this reseller. Disabled count jumped from 18 to 31, and live products fell by nine even though the catalogue grew by four. Some of that is expected: a spring line was rotated out as the season turned. But a 13-product rise is large enough to warrant a look, because two failure modes hide inside it.

The first is silent drop-off. If a few of those newly disabled products were not deliberately paused but were disabled by an editing slip or a bulk-action that overshot, they are now invisible to buyers and earning nothing. For a small store, three or four accidentally hidden best-sellers is a real revenue leak that no error message will announce.

The second is staleness. A growing disabled pile that never shrinks suggests the catalogue is accumulating dead weight: half-finished drafts, abandoned experiments, seasonal lines that will never return. None of that hurts the storefront directly, but it clutters the admin and makes the true live catalogue size harder to reason about. The hygiene action is to review the disabled list in the Ecwid Control Panel, re-enable anything hidden by mistake, and delete anything genuinely retired. Cross-check Total Products so the live versus total split stays honest.

Sibling cards merchants should reference together

Card	Why it matters next to disabled products	What the combination tells you
Total Products	The catalogue total.	Disabled / total gives the share of the catalogue hidden from buyers.
Out-of-Stock Products	The other unbuyable state.	Disabled = hidden by choice; out of stock = visible but empty. Together they show all unbuyable SKUs.
Low Stock Products	The restock watchlist.	A product disabled because it sold out should reconcile with the low-stock and OOS lists.
Products on Unlimited Stock (No Tracking)	Catalogue hygiene.	Both cards review catalogue configuration health rather than sales.
Top Products by Revenue	Revenue exposure.	If a top earner appears disabled, that is a revenue leak to fix immediately.
Total Revenue	The stakes.	Accidentally disabling a strong seller dents revenue with no error message; watch both.
Inventory Sync Drift Across Storefronts	Sync integrity.	A sync fault can disable products unintentionally; a drift signal next to a disabled spike points to the cause.

Reconciling against Ecwid

Where to look in Ecwid’s own dashboard:

Ecwid Control Panel (my.ecwid.com) -> Catalog -> Products -> filter Visibility = “Disabled” The filtered count is the apples-to-apples comparison against this card.

To audit quickly, sort the disabled list by last-updated to see which products were hidden most recently, which surfaces accidental disables fast.

Why our number may differ:

Reason	Direction	Why
Category vs product visibility	Either	A product can be hidden because its category is disabled rather than the product itself; we count the product enabled flag, so category-level hiding may not match a visual scan of the storefront.
Draft products	Either	Newly created, never-published products may default to disabled; whether you think of those as “products” affects the count you expect.
Variations	Ours product-level	We count at the product level, not the variation level; a product with some disabled variations still counts as one enabled product.
Sync lag	Marginal	Webhook-driven; a just-toggled product may take a polling cycle to reflect.
Bulk-edit timing	Either	A bulk enable/disable in progress can briefly show a count between the old and new state.

Internal identity:

ecwid_disabled_products = COUNT(products WHERE enabled = false) across the catalogue.

Known limitations / merchant FAQs

What is the difference between disabled and out of stock? Disabled means you have hidden the product from the storefront on purpose; buyers cannot see it. Out of stock means the product is visible but has zero quantity. A product can be both. Out-of-stock SKUs are tracked separately by Out-of-Stock Products.

Is a high disabled count bad? Not by itself. Many healthy stores keep a large disabled archive of seasonal or retired lines. The card is informational. The thing to watch is an unexplained jump, which can mean an editing slip hid live products, or steady accumulation that suggests dead weight worth cleaning up.

Why is there no alert? Because disabling is a normal merchant action with no single “wrong” level. A fixed threshold would fire constantly for stores that legitimately keep big archives. The card is for periodic hygiene review, not real-time alarm.

Could a sync error disable my products? Yes. A faulty inventory or catalogue sync, especially across multiple storefront surfaces, can flip products to disabled unintentionally. If you see a disabled jump you did not make, check Inventory Sync Drift Across Storefronts and your recent sync activity.

I disabled a product but the storefront still shows it. Why? Usually caching on the host site. The Ecwid widget and the page it is embedded in can cache for a short period; a hard refresh or waiting for the cache to expire resolves it. If it persists, confirm the product is truly disabled and not just out of stock.

Does a disabled product keep its data and URL? Yes. Disabling preserves the product’s images, description, pricing, and history; re-enabling restores it exactly. Deleting is the destructive action that removes the product entirely. Prefer disabling when you might bring a line back.

Will disabling a product affect my past orders or revenue figures? No. Past orders that included the product are unaffected and still count toward revenue cards. Disabling only changes future visibility on the storefront.

How fresh is this count? It is real time, refreshed each polling cycle and on the product.updated webhook. A just-disabled product appears in the next dashboard render.

Should I delete disabled products instead? Only if you are sure the line is permanently retired. Disabling is reversible and safe; deleting is not. For seasonal or might-return items, disabling is the right tool and a large disabled archive is perfectly healthy.

---

Tracked live in Vortex IQ Nerve Centre

Disabled Products is one of hundreds of KPI pulses Vortex IQ tracks across Ecwid 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.