Checkouts feature
The whole sale,
one flow
Build the checkout as a run of screens: choose, fill in, pay, upsell, confirm. Send each buyer down the path that fits their answers.
No credit card required. No coding required.
- EntryPick your ticketStandard · VIP
- PageAttendee details
- PaymentPaymentAdd-on: workshop recordings
- UpsellVIP dinner
- EndingSee you there
How it works
Every screen knows what came before
One checkout, many screens. The buyer moves through them and the cart comes along.
- Entry screen
They pick what they want
Plans, tickets or bundles, chosen on the first screen.
- Content screen
You ask what you need
Details, questions or a tax ID, only when they apply.
- Confirmation
They land where you send them
Your confirmation screen, or your own thank-you page.
Set it up
Lay out the screens, then route them
Screens and routes live in the checkout editor’s Layout tab. Nothing to wire up elsewhere.
- 1
Add the products
In the Products tab, add the products and prices this checkout sells. Mark each one required or optional.
- 2
Add screens in order
In the Layout tab, add Entry, Content, Payment, Upsell and Confirmation screens and drag them into order.
- 3
Set the routes
Open a screen’s logic and add conditional branches: when conditions match, then go to another screen.
- 4
Publish and share
Set the status to Published in Settings, then copy the link or embed code from Share.
- Read the multi-page flow docs →
Add Screen
Choose the type of screen to add to your flow
Routing
Branch on what the buyer actually did
Each screen has a default next screen and any number of rules ahead of it.
The option they picked
Send annual buyers one way and monthly buyers another, from the same checkout.
What is in the cart
Skip the bump screen for buyers who already added it, or show a bundle to those who did not.
What they bought before
Route returning customers past the screens they have already seen.
A discount code
Show a different screen when a code is applied.
The order total
Ask for a company and tax ID only on orders above an amount you choose.
A saved card on file
Go straight to a one-click screen when the buyer already has a payment method saved.
Integrations
Keep your site. Upgrade how it sells.
Plus a fully documented REST API and webhook layer for whatever’s not in the list.
Questions
Common questions about sales flows
The short answers. The docs have the long ones.
Can a checkout have more than one page?
Yes. Add Entry, Content, Payment, Upsell and Confirmation screens to one checkout and set the order they run in.
Can buyers take different paths?
Yes. Each screen can branch on the option chosen, the cart, past purchases, a discount code, the order total or a saved card. A default route catches everyone else.
Can I keep my own landing page?
Yes. The flow opens from a hosted link, as a popup from a button on your page, or embedded inline.
How do I test it before going live?
Use the test mode link from Share. It runs the whole flow against your Stripe test account.
The team
Built by a team obsessed with conversion.
15+ years testing every pricing model under the sun. Every part of Plandalf comes from a real checkout problem we’ve had to solve ourselves.
No credit card required. Nothing to migrate.