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 counts | The 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 endpoint | Surface 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” means | Enabled in the Ecwid Control Panel AND wired to the catalogue. A surface that is configured but switched off (or disconnected) is not counted. |
| Embed widget | Counted as one surface regardless of how many host pages it appears on. A widget on five WordPress pages is still one embed surface. |
| Instant Site | The Ecwid-hosted standalone site. Counted separately from the embed surface even though it shares the same catalogue. |
| Social surfaces | Facebook Shop and Instagram Shopping are counted separately when each is connected and live. |
| POS | Ecwid POS (Square POS, or the Ecwid mobile app till) counts as a surface when the merchant is actively using it. |
| Currency | Not applicable. This is a count, not a money value. |
| Time window | RT (real-time snapshot of the current configuration). |
| Alert trigger | None - informational. The card is a configuration health readout, not a threshold alarm. |
| Roles | owner, 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.| Surface | Status | Notes |
|---|---|---|
| Embed widget (WordPress) | Active | The original surface; still the largest by revenue. |
| Instant Site | Active | Stood up for a Christmas market QR code last winter. |
| Facebook Shop | Active | Connected, catalogue synced. |
| Instagram Shopping | Active | Tagged posts drive a small but steady trickle. |
| Square POS | Inactive | Configured for craft fairs but switched off out of season. |
Sibling cards merchants should reference together
| Card | Why it matters next to Active Storefront Surfaces | What the combination tells you |
|---|---|---|
| Revenue by Storefront Surface | The money behind the count. | Four surfaces active but revenue from one = the others are dormant or mis-promoted. |
| Channel-Specific Order Drop | Surface-level outage detector. | Surface count steady but one channel’s orders fall off = silent break on a still-enabled surface. |
| Inventory Sync Drift Across Storefronts | Cross-surface integrity. | More surfaces = more places stock counts can diverge; watch drift as you add surfaces. |
| Storefronts on Deprecated Theme | Surface quality, not just quantity. | A counted surface on an old theme is active but degraded; quantity hides a quality gap. |
| Total Revenue | The aggregate the surfaces feed. | Adding a surface should lift total revenue; if it does not, the surface is not pulling weight. |
| Total Orders | Volume across all surfaces. | Surfaces up + orders flat = new surfaces are cannibalising, not expanding, demand. |
| Conversion Rate | Per-surface funnel health. | A new surface that drags overall CR down may have a broken or clumsy checkout. |
| Orders by Country | Geographic 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:
| Reason | Direction | Why |
|---|---|---|
| Configured-but-off surfaces | Theirs higher | Ecwid lists a surface even when toggled off; we only count surfaces that can currently take an order. |
| Embed placement | Either | Ecwid 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 channels | Theirs higher | A Facebook or Instagram connection that has lapsed (token expired) may still appear listed in Ecwid until you reconnect; we count it inactive. |
| Sync lag | Marginal | Surface enablement is read on the polling cycle; a surface switched on in the last few minutes may not be reflected yet. |
ecwid_active_storefront_surfaces = COUNT(surfaces WHERE enabled = true AND order_capable = true)