checkout
Templates
Start with a real checkout system, not an empty page.
Plandalf templates package the page, offer, products, prices, payment handoff, invoices, and post-purchase automation into a builder path an operator can inspect.
The same offer record can carry the checkout template, product, price, payment options, invoice, and automation context.
Template catalog
Clone the path, then wire the business logic.
The useful part of a checkout template is not the visual shell alone. It is the relationship between the page, the Plandalf Offer, Stripe, integrations, and the work that happens after purchase.
Builder paths
Choose what the template needs to do.
A useful template should point to the implementation path around it: the site integration, checkout surface, product and price model, deadline or coupon logic, and the automation that runs after the purchase event.
Turn the template into a promotion
Use this path when the checkout template needs a launch window, expiring coupon, email countdown GIF, deadline campaign, price change, or save-offer sequence.
Automate the handoff after checkout
Use this path when a template should grant access, send receipts, sync the CRM, notify the team, create invoice records, or fan purchase events into webhooks and SDK apps.
Product surfaces
The app screens behind the template catalog.
These are real Plandalf product surfaces, not generic mockups. They show where templates connect to offers, products, checkout, and automation.
Builder references
Every template should create its next step.
Use these links when moving from a template preview into the offer record, the checkout docs, platform integration, or comparison research.