If one storefront surface stops producing orders while others continue, it points to a surface-specific outage or sync break.
At a glance
Detects when a single storefront surface goes quiet while the rest of the store keeps taking orders. A total-revenue dip is easy to spot; a single-surface outage hides because the other surfaces mask it in the headline number. This card watches each surface’s order volume against its own recent baseline, so a Facebook Shop that has silently stopped converting, or an embed broken by a host-site change, is caught before a week’s revenue from that surface is lost.
| What it counts | Per-surface order volume in the last 24H compared with each surface’s own prior-period baseline. The card reports any surface whose order volume has dropped sharply while sibling surfaces continue normally. |
| API endpoint | GET /v3/{store-id}/orders (paged, OAuth2 with read_orders scope), grouped by originating surface; order.created webhook feeds the live count. Surface list cross-checked against the store profile. |
| Baseline | Each surface is compared against its own recent typical volume, not the store total, so a small surface is judged on its own scale. |
| What triggers it | A surface whose 24H order volume falls more than 50% versus its prior-period baseline while at least one other surface is producing orders normally. |
| Cancelled / pending | Excluded from the count; only orders that reach PAID (or the surface’s normal completion state) are counted toward volume. |
| Currency | Not applicable. This is an order-volume signal, not a money value. |
| Time window | 24H vsP (last 24 hours vs prior comparable period). |
| Alert trigger | Any channel with order-volume drop greater than 50% vsP while sibling surfaces continue. |
| Sentiment | Inverse gauge - a fired alert is bad. A surface going quiet relative to its peers is a problem, not a neutral observation. |
| Roles | owner, operations, engineering. |
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 across four surfaces, 24H ending 21 Apr 26. The maker’s WordPress host pushed a plugin update overnight that broke the page the Ecwid embed sits on. The embed surface went quiet while every other surface kept selling.| Surface | Orders (last 24H) | Baseline (typical 24H) | Change | Status |
|---|---|---|---|---|
| Embed (WordPress) | 1 | 12 | -92% | ALERT |
| Instant Site | 4 | 4 | 0% | normal |
| Instagram Shopping | 3 | 2 | +50% | normal |
| Facebook Shop | 1 | 1 | 0% | normal |
Sibling cards merchants should reference together
| Card | Why it matters next to Channel-Specific Order Drop | What the combination tells you |
|---|---|---|
| Active Storefront Surfaces | The surfaces being watched. | A surface that drops to zero AND falls off the active count = fully disconnected, not just quiet. |
| Revenue by Storefront Surface | The cost of the drop. | The dropped surface’s revenue share tells you how expensive the outage is per hour. |
| Total Orders | The masked aggregate. | Total orders look fine while one surface is down; this card is why the aggregate lies. |
| Ecwid API Failure Rate Spike | Shared-cause check. | A drop plus an API spike points to a platform/connector fault rather than a host-page break. |
| Inventory Sync Drift Across Storefronts | Adjacent surface fault. | A surface showing as out of stock due to sync drift will also stop producing orders. |
| Conversion Rate | Funnel vs traffic. | Drop with traffic still arriving = checkout broke; drop with no traffic = the surface is unreachable. |
| Orders by Status | Where stuck orders pile. | Orders entering but stalling (e.g. awaiting payment) on one surface mimics a drop. |
| Total Revenue | The bottom line at risk. | The drop is the early warning; revenue is what it protects. |
Reconciling against Ecwid
Where to look in Ecwid’s own dashboard:
Ecwid Control Panel (my.ecwid.com) -> My Sales -> Orders, filter by date (last 24H) and segment by source/channel
Compare today’s per-surface order count against a normal day. A surface sitting near zero while others are normal confirms the alert.
To check whether a surface is actually reachable, open it directly: load the host page carrying the embed, open the Instant Site URL, or open the Facebook/Instagram shop, and attempt to add to cart.
Why our number may differ from Ecwid’s Control Panel:
| Reason | Direction | Why |
|---|---|---|
| Attribution of source | Either | A surface drop is only visible if Ecwid recorded the order source; unattributed orders sit in “other / direct” and can blur a single surface’s count. |
| Time zone | Boundary hours | We compare on a UTC 24H window; Ecwid uses the store’s configured time zone, which can shift which orders fall inside “today”. |
| Low-volume noise | False signal risk | A surface that normally does one or two orders a day can read as a large percentage drop on a quiet but normal day; the card weighs sibling activity to reduce this. |
| Pending payment | Either | An order placed but not yet PAID may not count toward completed volume yet, briefly mimicking a drop. |
| Sync lag | Marginal | Webhook-driven; the most recent few minutes may not be counted. |
drop_flag(surface) = (orders_24h(surface) / baseline_24h(surface)) < 0.5 AND any_sibling_normal = true