Skip to main content
Card class: HeroCategory: Ecommerce Platform
Count of enabled storefront surfaces. Top of the multi-channel health stack.

At a glance

Count of enabled storefront surfaces the store is currently selling through - the embed widget on the merchant’s existing site, the Ecwid Instant Site, Facebook Shop, Instagram Shopping, Square POS, marketplaces, and any other surface the merchant has switched on. Ecwid’s whole pitch is “one catalogue, many surfaces”, so this is the top of the multi-channel health stack. It tells the owner at a glance how many places the store can take an order right now.
What it countsThe number of distinct storefront surfaces currently enabled and capable of taking an order. Each surface (embed, Instant Site, Facebook Shop, Instagram Shopping, Square POS, marketplace connection) is counted once if it is active.
API endpointSurface configuration read from GET /v3/{store-id}/profile and the sales-channel settings (OAuth2 with read_store_profile scope). Surface-level enablement flags are derived from the store profile and channel objects.
What “active” meansEnabled in the Ecwid Control Panel AND wired to the catalogue. A surface that is configured but switched off (or disconnected) is not counted.
Embed widgetCounted as one surface regardless of how many host pages it appears on. A widget on five WordPress pages is still one embed surface.
Instant SiteThe Ecwid-hosted standalone site. Counted separately from the embed surface even though it shares the same catalogue.
Social surfacesFacebook Shop and Instagram Shopping are counted separately when each is connected and live.
POSEcwid POS (Square POS, or the Ecwid mobile app till) counts as a surface when the merchant is actively using it.
CurrencyNot applicable. This is a count, not a money value.
Time windowRT (real-time snapshot of the current configuration).
Alert triggerNone - informational. The card is a configuration health readout, not a threshold alarm.
Rolesowner, marketing.

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 UK candle and home-fragrance maker running Ecwid, snapshot taken 21 Apr 26. The merchant started on Ecwid because the widget dropped straight into their existing Squarespace-style WordPress site. Over two years they have switched on more surfaces as the business grew.
SurfaceStatusNotes
Embed widget (WordPress)ActiveThe original surface; still the largest by revenue.
Instant SiteActiveStood up for a Christmas market QR code last winter.
Facebook ShopActiveConnected, catalogue synced.
Instagram ShoppingActiveTagged posts drive a small but steady trickle.
Square POSInactiveConfigured for craft fairs but switched off out of season.
Active Storefront Surfaces = 4
(embed + Instant Site + Facebook + Instagram)
Square POS configured but not counted (off-season, disabled)
What it means for this maker. Four active surfaces is healthy for a small Ecwid merchant. The card reframes a question owners rarely ask themselves: “how many ways can someone actually buy from me right now?” Each surface is a path to an order, and each one can break independently. A merchant who thinks they sell on four channels but whose Instagram connection silently dropped last week is, in reality, selling on three. This card is the first place that mismatch surfaces. The number on its own is just context. Its value is as the headline of the multi-channel stack: it tells the owner how many surfaces to expect revenue from, which then makes Revenue by Storefront Surface and Channel-Specific Order Drop legible. If this card says four but only two surfaces show revenue this month, the other two are either dormant or broken, and that is the real story. The Square POS line is the teaching case. It is configured but off, so it is not counted. When the maker does their next craft fair and switches POS back on, this card ticks to five, and the owner gets a clean signal that the till surface is live again.

Sibling cards merchants should reference together

CardWhy it matters next to Active Storefront SurfacesWhat the combination tells you
Revenue by Storefront SurfaceThe money behind the count.Four surfaces active but revenue from one = the others are dormant or mis-promoted.
Channel-Specific Order DropSurface-level outage detector.Surface count steady but one channel’s orders fall off = silent break on a still-enabled surface.
Inventory Sync Drift Across StorefrontsCross-surface integrity.More surfaces = more places stock counts can diverge; watch drift as you add surfaces.
Storefronts on Deprecated ThemeSurface quality, not just quantity.A counted surface on an old theme is active but degraded; quantity hides a quality gap.
Total RevenueThe aggregate the surfaces feed.Adding a surface should lift total revenue; if it does not, the surface is not pulling weight.
Total OrdersVolume across all surfaces.Surfaces up + orders flat = new surfaces are cannibalising, not expanding, demand.
Conversion RatePer-surface funnel health.A new surface that drags overall CR down may have a broken or clumsy checkout.
Orders by CountryGeographic reach by surface.Social surfaces often pull a different country mix than the embed; reach widens as surfaces grow.

Reconciling against Ecwid

Where to look in Ecwid’s own dashboard:
Ecwid Control Panel (my.ecwid.com) -> Sell Anywhere (Channels) Each surface (Instant Site, Facebook, Instagram, Point of Sale, marketplaces) shows a connection toggle and status. Count the toggles that read “Connected” or “Enabled”.
The embed widget itself is managed under Website -> Embed your store; if you have placed the embed code on a live host page, that counts as the embed surface. Why our number may differ from Ecwid’s Control Panel:
ReasonDirectionWhy
Configured-but-off surfacesTheirs higherEcwid lists a surface even when toggled off; we only count surfaces that can currently take an order.
Embed placementEitherEcwid shows the embed code as available; we count the embed surface as active based on the store profile flag. A configured embed never placed on a live page may still read as available in Ecwid.
Disconnected social channelsTheirs higherA Facebook or Instagram connection that has lapsed (token expired) may still appear listed in Ecwid until you reconnect; we count it inactive.
Sync lagMarginalSurface enablement is read on the polling cycle; a surface switched on in the last few minutes may not be reflected yet.
Internal identity: ecwid_active_storefront_surfaces = COUNT(surfaces WHERE enabled = true AND order_capable = true)

Known limitations / merchant FAQs

What counts as a “surface” exactly? Any distinct place a customer can complete a purchase from your catalogue: the embed widget, the Instant Site, Facebook Shop, Instagram Shopping, Square POS, and any marketplace connection you have switched on. Each is counted once when active. My widget is on five different pages of my site. Is that five surfaces? No. The embed widget is one surface no matter how many host pages carry the embed code. Surfaces are about distinct selling channels, not page placements. Why is my Instant Site counted separately from my embed? Because they are two different surfaces sharing one catalogue. The embed lives inside your existing website; the Instant Site is a standalone Ecwid-hosted page with its own URL. Either can break or be disabled without affecting the other, so each is counted on its own. I switched off my POS for the off-season. Why did my count drop? That is correct behaviour. The card counts surfaces that can take an order right now. A disabled POS cannot, so it is not counted until you switch it back on for your next fair or pop-up. My Instagram still shows in Ecwid but the count went down. What happened? The most common cause is a lapsed connection (an expired Facebook/Instagram token). Ecwid may still list the channel, but if it can no longer take orders we count it inactive. Reconnect the channel in the Control Panel and the count will recover on the next cycle. Is a higher count always better? Not on its own. More surfaces mean more reach but also more to maintain, more places stock can drift, and more checkouts to keep current. Read this card alongside Revenue by Storefront Surface: a surface that takes no orders is overhead, not growth. Does the count include marketplaces like Amazon or eBay? Yes if you have connected them through Ecwid’s marketplace channels and they are live. A configured-but-paused marketplace listing is not counted until it is actively listing your catalogue. Why is there no alert on this card? It is a configuration health readout, not a performance threshold. A change in surface count is meaningful context, but whether it is good or bad depends entirely on intent (you may have deliberately turned a surface off). The cards that do alert - Channel-Specific Order Drop and Inventory Sync Drift Across Storefronts - sit directly beneath this one and watch the surfaces this card counts. How quickly does the count update when I add a surface? On the next polling cycle, typically within a few minutes of enabling the surface in your Control Panel.

Tracked live in Vortex IQ Nerve Centre

Active Storefront Surfaces 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.