shop-three-step — Starter templates

PAGES

Six pages, one funnel.

The order is fixed by the contract. Each page declares the slots it renders and the cart actions it may take.

landing preview

information preview

shipping preview

billing preview

upsell preview

receipt preview

plus a presell page and three upsell layouts — nine pages in the family

THE CONTRACT

Templates are runtime contracts. The split below is what keeps an edited template launchable.

THE SDK OWNS

cart stateSelection, totals, and line items live in the SDK — never in your markup.

pricingPackage prices and discounts come from the CampaignSpec at render time.

order submitPayment capture and order creation, including failure retry.

hydrationEvery data-next-* attribute is wired on load. No JS required from you.

analyticsCanonical events, commerce payloads, campaign identity, and provider delivery stay in the SDK runtime.

page routingThe funnel order is fixed by the contract: landing → information → shipping → billing → upsell → receipt.

step progressionInformation → shipping → billing progression and cross-step state — each step validates before advancing.

YOU EDIT

markupSections, layout, and styling — anything that keeps the attributes intact.

copyHeadlines, body, and offer language on every page.

imageryProduct photography, badges, and proof elements.

offerPackages, prices, and the upsell product — declared in the CampaignSpec.

trackingConfigure provider IDs, external scripts, and blocked-event exceptions without replacing SDK-owned payloads.

edits are re-validated on every push — the contract is enforced, not trusted