> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Guest vs Registered Order Split, Ecwid > Guest vs Registered Order Split: the share of orders from guests versus account holders. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > The share of orders placed by guests versus registered account holders. ## At a glance > A donut split of orders over the rolling 30 days into guest checkout versus registered-account checkout. Ecwid permits guest checkout by default, which removes friction but also removes the email reach you would otherwise get for re-engagement. A high guest share means lower contactability: you are converting buyers but not capturing a relationship with them. | | | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | `COUNT(orders placed as guest)` versus `COUNT(orders placed by a registered customer)` over the rolling 30D window, expressed as a two-segment share. | | **API endpoint** | `GET /v3/{store-id}/orders` (paged, max 100 per call, OAuth2 with `read_orders` scope); each order indicates whether it was tied to a registered customer or placed as a guest. Webhook updates fire on `order.created`. | | **What "guest" includes** | Any order completed without the buyer being signed in to a store account. Ecwid allows guest checkout out of the box, so this is common for first-time buyers. | | **What "registered" includes** | Any order where the buyer was signed in to, or created, a store account at checkout. | | **What it excludes** | Cancelled-before-payment orders; staff test orders flagged as such. | | **Currency** | Not applicable; this is an order-count share. | | **Time window** | `30D vsP` (rolling 30D vs prior 30D). | | **Alert trigger** | None - informational. | | **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 coffee roaster running an Ecwid widget on a Webflow site, rolling 30D ending 18 May 26.** The roaster sells whole-bean and ground coffee plus a few brewing accessories. Guest checkout is on because the merchant wanted the fastest possible path to a first order. | Segment | Orders (this 30D) | Share | Prior 30D share | | ---------- | ----------------- | ----- | --------------- | | Guest | 168 | 62% | 58% | | Registered | 102 | 38% | 42% | | Total | 270 | 100% | 100% | ```text theme={null} Guest share: 168 / 270 = 62% Registered share: 102 / 270 = 38% Guest share moved +4pp vs prior 30D ``` **What it means for this roaster.** Nearly two-thirds of orders came from guests, and the guest share is creeping up. That is good for top-of-funnel conversion (no signup wall) but it means 168 of the last 270 buyers are harder to reach by email for a "reorder your beans" nudge, the single most natural repeat trigger for a consumable like coffee. For a consumable product the guest share is the metric that quietly caps lifetime value. Coffee is bought again roughly every three to four weeks; if you cannot email the buyer, you are relying on them to remember you. A creeping guest share is therefore an early warning that your repeat engine is being starved of contactable customers. The action is not to force account creation, which would dent conversion. Instead, capture email at guest checkout for transactional and consented marketing use, and add a "create an account to track your order and reorder faster" prompt on the confirmation page. Pair this card with [Repeat Customer Rate](/nerve-centre/kpi-cards/ecwid/repeat-customer-rate); if repeat rate is soft while guest share is high, the two are almost certainly linked. ## Sibling cards merchants should reference together | Card | Why it matters next to the guest/registered split | What the combination tells you | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- | ----------------------------------------------------------------------------------- | | [Total Customers](/nerve-centre/kpi-cards/ecwid/total-customers) | Your contactable base. | High guest share explains a customer count that lags order count. | | [New Customers](/nerve-centre/kpi-cards/ecwid/new-customers) | Account inflow. | Falling new customers + rising guest share = remarketing reach shrinking. | | [Repeat Customer Rate](/nerve-centre/kpi-cards/ecwid/repeat-customer-rate) | The cost of low reach. | High guest share usually drags repeat rate down for consumables. | | [Repeat Purchase Rate](/nerve-centre/kpi-cards/ecwid/repeat-purchase-rate) | Order-level loyalty. | Confirms whether the unreachable guests come back anyway. | | [Total Orders](/nerve-centre/kpi-cards/ecwid/total-orders) | The denominator. | Order growth driven entirely by guests is fragile growth. | | [High-Value Customers Unengaged on Email](/nerve-centre/kpi-cards/ecwid/high-value-customers-unengaged-on-email) | Who to recover. | Pinpoints valuable registered buyers you are still failing to reach. | | [Conversion Rate](/nerve-centre/kpi-cards/ecwid/conversion-rate) | The trade-off. | Guest checkout lifts conversion; this card shows the reachability you trade for it. | ## Reconciling against Ecwid **Where to look in Ecwid's own dashboard:** > **Ecwid Control Panel (`my.ecwid.com`) -> My Sales -> Orders** > Filter the order list and inspect whether each order is tied to a registered customer; guest orders show no linked account. For a quick sanity check, sample a page of recent orders and compare the guest-to-registered ratio against the card. **Why our number may differ from Ecwid's Control Panel:** | Reason | Direction | Why | | ------------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **Account created at checkout** | Either | If a buyer creates an account during a guest-style checkout, Ecwid may classify the order as registered; we follow the order's final account linkage. | | **Time zone** | Boundary days | Ecwid uses store-local; we use UTC. The boundary effect on a 30D window is small. | | **Cancelled orders** | Theirs higher | Some Ecwid views include cancelled orders in the split; we exclude them. | | **Sync lag** | Marginal | Webhook-driven; the most recent orders may not be in for a few minutes. | | **Merged customer records** | Marginal | If a guest order is later linked to a merged account, our classification may shift on re-sync. | **Internal identity:** `guest_share = COUNT(guest orders) / COUNT(all paid orders)` over the same window; `registered_share = 1 - guest_share`. ## Known limitations / merchant FAQs **Is a high guest share bad?** Not on its own. Guest checkout lifts conversion by removing friction, which is good. It becomes a problem only if you sell repeatable products and need email reach for reorders. For one-off purchases, a high guest share is perfectly healthy. **Why does Ecwid default to allowing guest checkout?** Because forcing account creation is a well-known conversion killer for small stores. Ecwid's audience is SMB and hobby merchants where every point of friction costs orders, so guest checkout is on by default. **How do I lower the guest share without hurting conversion?** Use a soft post-purchase prompt rather than a hard checkout gate. Offer account creation on the order-confirmation page ("save your details to reorder faster"). You keep the frictionless first order and recover some of the relationship afterwards. **Can I capture a guest's email even if they do not create an account?** Yes. Guest checkout still requires an email for the order confirmation. With the buyer's consent you can use that email for marketing. Capturing consent at checkout is the cheapest way to keep guests reachable. **Why did my guest share jump this month?** Common causes: a paid-traffic campaign sending cold first-time buyers, a viral social post, or a promo that drew bargain hunters who do not want an account. A spike of new, low-intent buyers usually shows up as a guest-share jump. **Does an order from a returning guest (same email, no account) count as registered?** No. If there is no store account, it is a guest order regardless of how many times that email has bought. Only a signed-in or newly created account makes an order registered. **Why does my Ecwid Control Panel show a slightly different ratio?** Usually classification of accounts created during checkout, or time zone and cancelled-order handling. Sample a page of orders over the same window and compare; small differences are expected. **Does this card tell me revenue by segment?** No. This is an order-count split, not a revenue split. Guests and registered customers can have different average order values, so the revenue split may differ from the order split. Pair with [Average Order Value](/nerve-centre/kpi-cards/ecwid/average-order-value) for the value angle. *** ### Tracked live in Vortex IQ Nerve Centre *Guest vs Registered Order Split* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.