Draft v1, reconstructed from the two walkthroughs + Nova screenshots. A map to correct against staging, not a validated flow. Node border = how sure we are; edge labels = the routing conditions.
Start here — what am I looking at?
The picture: VShred's "SGA" sales funnel — the quiz → checkout → upsells journey a customer travels — drawn as a routing matrix (a table of steps, where each step is a page and something decides the next one).
The finding that started this: VShred's current custom system (their Laravel/Nova admin) already works exactly like this — a funnel made of steps, each step is a page (or A/B variants of a page), and small conditions (where you're from, what's in your cart) pick where you go next.
What we're proposing: rebuild that same model on Shopify — the funnel as editable data (metaobjects) + a small service layer that reads the conditions and serves the right page. Same model, new home — not a reinvention.
How to read it: follow left → right. Boxes = pages (routes). Arrows = the conditions that route the customer. Color = how sure we are: green = seen for real in their admin, amber = page real, rule inferred, gray dashed = still to confirm. Next: walk this against their live staging admin and correct the amber/gray parts.
Hover a step → the boxes it maps to light up. Click Burn Evolved for the data-model detail. Numbers ①–⑥ match steps to boxes.
Left band = Upper Funnel (quiz → segment VSL → checkout). Right band = post-checkout Upsells. The three green edges off us/burn-gt are the only conditions we saw verbatim in Nova — every other edge is a target to confirm.
us/burn-gt) — the one page where we saw the real rules in their admin: bought a subscription → Burn PM · bought bottles → Burn 3-bottle · bought nothing → a 1-bottle downsell. (And anyone not in the US is redirected away before they even see it.)| Mechanism | Their CMS today | Shopify equivalent |
|---|---|---|
| Funnel | Sales Funnel — envelope of pages, chained | funnel metaobject |
| Step | Route (a URI) | funnel_step |
| Variant | Page Version — Control + Weight, sticky | variant set, weighted by service layer |
| Branch | Before/After-Visit Conditions (geo · SKU · purchase · gender) | branch_rules in the service layer |
| Reorder | move an offer's position ("basic mutation") | reorder step refs in admin |
| A/B | add a page version at weight | add a variant to a step |
| Post-checkout | conditions read cart SKUs + purchase state | service layer carries that context (confirm) |
| Measurement | Track API → Snowflake (won't port) | per-step events → analytics (net-new) |
Every box in the funnel is one of these. This is the whole abstraction.
A node is a route, the chips inside it are variants, the arrows out of it are conditions. Nothing else.