> Kajabi delivery with a Plandalf offer, Stripe payment, and lifecycle email. Source: https://plandalf.com/stacks/kajabi-course-launch [Integrations](https://plandalf.com/integrations) The Kajabi Course Launch **Tools in this stack**[Kajabi](https://plandalf.com/platforms/kajabi)[Stripe](https://plandalf.com/platforms/stripe)[Zapier](https://plandalf.com/platforms/zapier)[MailerLite](https://plandalf.com/platforms/mailerlite) Builder resource # The Kajabi Course Launch [Kajabi](https://plandalf.com/platforms/kajabi) delivery with a Plandalf [offer](https://plandalf.com/products/checkouts), [Stripe](https://plandalf.com/platforms/stripe) [payment](https://plandalf.com/products/checkouts/payment-options), and lifecycle email. Sell a [Kajabi](https://plandalf.com/platforms/kajabi) course through a more flexible [offer](https://plandalf.com/products/checkouts) and send each [buyer](https://plandalf.com/docs/sdk/identity) into the right follow-up path. [Kajabi](https://plandalf.com/platforms/kajabi) hosts the course experience, Plandalf handles the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) and [offer](https://plandalf.com/products/checkouts) mechanics, [Stripe](https://plandalf.com/platforms/stripe) processes [payment](https://plandalf.com/products/checkouts/payment-options), and [Zapier](https://plandalf.com/platforms/zapier) routes the [purchase event](https://plandalf.com/docs/api/webhooks) into [Kajabi](https://plandalf.com/platforms/kajabi) access and lifecycle email. **Built for:** Course creators and education businesses already delivering in [Kajabi](https://plandalf.com/platforms/kajabi) This page is the builder map: patterns, responsibilities, recipes, and [product](https://plandalf.com/products/checkouts) decisions for adding Plandalf to this commerce stack. [ ![The Numi offer editor showing hosted checkout mode controls.](https://plandalf.com/images/features/hosted-checkout/offer-editor-hosted-mode-product.png) ](https://plandalf.com/products/checkouts/hosted-checkout) [Hosted checkout](https://plandalf.com/docs/offers/hosted-checkout) lets a sales page hand buyers to a branded [offer page](https://plandalf.com/products/checkouts) when embedding is not the right fit. [ ![The Numi selling blocks panel showing order bump controls.](https://plandalf.com/images/features/order-bumps/order-bumps-selling-blocks-product.png) ](https://plandalf.com/products/checkouts/order-bumps) [Order bumps](https://plandalf.com/products/checkouts/order-bumps) are configured as selling blocks rather than one-off front-end code. ## Architecture Treat [Plandalf Offers](https://plandalf.com/products/checkouts) as the commerce layer between the sales page, the buying moment, and the [payment processor](https://plandalf.com/products/checkouts/payment-options). Your stack owns the audience and fulfilment experience. Plandalf owns [offer configuration](https://plandalf.com/products/checkouts), [checkout state](https://plandalf.com/products/checkouts/hosted-checkout), [pricing rules](https://plandalf.com/products/checkouts/payment-options), [buyer identity](https://plandalf.com/docs/sdk/identity), [invoices](https://plandalf.com/products/checkouts/invoices), and the [events](https://plandalf.com/docs/api/webhooks) that drive follow-up. [Site**Kajabi**_Buyer clicks the CTA on your page._](https://plandalf.com/platforms/kajabi)[Checkout**Plandalf**_Buyer follows the offer link._](https://plandalf.com/products/checkouts)[Payment**Stripe**_Buyer submits payment in Plandalf._](https://plandalf.com/platforms/stripe)[Automation**Zapier**_The same Plandalf purchase event fires._](https://plandalf.com/platforms/zapier)[Email**MailerLite**_The previous stack step completes._](https://plandalf.com/platforms/mailerlite) StageSystemHandoff Site[Kajabi](https://plandalf.com/platforms/kajabi)Plandalf opens from that page with the selected [offer context](https://plandalf.com/products/checkouts). Checkout[Plandalf](https://plandalf.com/products/checkouts)Plandalf validates the [offer](https://plandalf.com/products/checkouts), applies [pricing](https://plandalf.com/products/checkouts/payment-options) logic, and emits [checkout events](https://plandalf.com/docs/api/webhooks). Payment[Stripe](https://plandalf.com/platforms/stripe)Plandalf sends the [payment request](https://plandalf.com/products/checkouts/payment-options) to [Stripe](https://plandalf.com/platforms/stripe), then records the completed [purchase event](https://plandalf.com/docs/api/webhooks). Automation[Zapier](https://plandalf.com/platforms/zapier)Plandalf [Automation](https://plandalf.com/products/automations/purchase-automations) sends the event payload to [Zapier](https://plandalf.com/platforms/zapier). Email[MailerLite](https://plandalf.com/platforms/mailerlite)Plandalf [Automation](https://plandalf.com/products/automations/purchase-automations) sends the event and [customer](https://plandalf.com/docs/sdk/identity) fields to [MailerLite](https://plandalf.com/platforms/mailerlite). ## How This Stack Makes The Sale Work The [Kajabi](https://plandalf.com/platforms/kajabi) Course Launch is useful when each tool has a clear job: the audience surface creates intent, Plandalf turns that intent into a configured [offer](https://plandalf.com/products/checkouts), [Stripe](https://plandalf.com/platforms/stripe) collects [payment](https://plandalf.com/products/checkouts/payment-options), and the follow-up tools receive the purchase context they need. ### Where the [buyer](https://plandalf.com/docs/sdk/identity) starts [Kajabi](https://plandalf.com/platforms/kajabi) owns the attention layer. Keep the editorial page, newsletter block, landing page, or [product](https://plandalf.com/products/checkouts) screen focused on why the [buyer](https://plandalf.com/docs/sdk/identity) should act, then hand the buying decision to [Plandalf Offers](https://plandalf.com/products/checkouts). [Kajabi](https://plandalf.com/platforms/kajabi)[Offers](https://plandalf.com/products/checkouts)[Buy button](https://plandalf.com/products/checkouts/hosted-checkout) ### What the [buyer](https://plandalf.com/docs/sdk/identity) is purchasing Plandalf should own the [offer](https://plandalf.com/products/checkouts), [products](https://plandalf.com/products/checkouts), [prices](https://plandalf.com/products/checkouts/payment-options), [checkout](https://plandalf.com/products/checkouts/hosted-checkout) mode, [coupons](https://plandalf.com/products/checkouts/coupons), [order bumps](https://plandalf.com/products/checkouts/order-bumps), [upsells](https://plandalf.com/products/checkouts/upsells), [invoice](https://plandalf.com/products/checkouts/invoices) settings, and confirmation behavior so [Stripe](https://plandalf.com/platforms/stripe) is not the only durable record. [Products](https://plandalf.com/products/checkouts)[Prices](https://plandalf.com/products/checkouts/payment-options)[Coupons](https://plandalf.com/products/checkouts/coupons)[Invoices](https://plandalf.com/products/checkouts/invoices)[Stripe](https://plandalf.com/platforms/stripe) ### What happens after [payment](https://plandalf.com/products/checkouts/payment-options) The [purchase event](https://plandalf.com/docs/api/webhooks) should drive fulfilment, receipts, lifecycle email, CRM updates, [tax](https://plandalf.com/platforms/tax) context, and reporting. [Zapier](https://plandalf.com/platforms/zapier), [MailerLite](https://plandalf.com/platforms/mailerlite) should receive commerce context instead of a bare form submission. [Automations](https://plandalf.com/products/automations)[Sequences](https://plandalf.com/products/automations)[Zapier](https://plandalf.com/platforms/zapier)[MailerLite](https://plandalf.com/platforms/mailerlite) ## Choose The Pattern Start by deciding which business moment you are building. The stack changes depending on whether [checkout](https://plandalf.com/products/checkouts/hosted-checkout) starts from a sales page, a launch campaign, an [offer page](https://plandalf.com/products/checkouts), a [checkout](https://plandalf.com/products/checkouts/hosted-checkout) [template](https://plandalf.com/templates), or an existing [product](https://plandalf.com/products/checkouts) catalog. ### Sell from Kajabi **Use when:** [Kajabi](https://plandalf.com/platforms/kajabi) already owns the audience, post, landing page, or storefront moment and only needs the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) layer to open at the right time. **Build:** Place the hosted page trigger beside the buying copy, point it at a Plandalf [offer](https://plandalf.com/products/checkouts), and keep [products](https://plandalf.com/products/checkouts), [prices](https://plandalf.com/products/checkouts/payment-options), [coupons](https://plandalf.com/products/checkouts/coupons), [invoices](https://plandalf.com/products/checkouts/invoices), and [automations](https://plandalf.com/products/automations) inside the [offer](https://plandalf.com/products/checkouts) record. [Kajabi](https://plandalf.com/platforms/kajabi)[Offers](https://plandalf.com/products/checkouts)[Hosted checkout](https://plandalf.com/products/checkouts/hosted-checkout)[Checkout templates](https://plandalf.com/templates) ### Package the commercial object **Use when:** The business needs a clean [product](https://plandalf.com/products/checkouts), [price](https://plandalf.com/products/checkouts/payment-options), bundle, cohort, download, membership, or service package before traffic reaches [checkout](https://plandalf.com/products/checkouts/hosted-checkout). **Build:** Create the [product](https://plandalf.com/products/checkouts) and [price](https://plandalf.com/products/checkouts/payment-options), attach conversion controls such as [coupons](https://plandalf.com/products/checkouts/coupons), [order bumps](https://plandalf.com/products/checkouts/order-bumps), and [upsells](https://plandalf.com/products/checkouts/upsells), then make sure the [invoice](https://plandalf.com/products/checkouts/invoices) and fulfilment event carry the same line-item context. [Products](https://plandalf.com/products/checkouts)[Prices](https://plandalf.com/products/checkouts/payment-options)[Coupons](https://plandalf.com/products/checkouts/coupons)[Order bumps](https://plandalf.com/products/checkouts/order-bumps)[Upsells](https://plandalf.com/products/checkouts/upsells) ### Route the work after purchase **Use when:** The [checkout](https://plandalf.com/products/checkouts/hosted-checkout) is only useful if the [buyer](https://plandalf.com/docs/sdk/identity) gets access, receives the right receipt, lands in the correct [sequence](https://plandalf.com/products/automations), and leaves a durable record for support. **Build:** Use [Plandalf Automations](https://plandalf.com/products/automations) and [sequences](https://plandalf.com/products/automations) to send the [purchase event](https://plandalf.com/docs/api/webhooks) into [Zapier](https://plandalf.com/platforms/zapier), [MailerLite](https://plandalf.com/platforms/mailerlite), while [payment](https://plandalf.com/products/checkouts/payment-options) stays with [Stripe](https://plandalf.com/platforms/stripe). [Automations](https://plandalf.com/products/automations)[Sequences](https://plandalf.com/products/automations)[Zapier](https://plandalf.com/platforms/zapier)[MailerLite](https://plandalf.com/platforms/mailerlite)[Invoices](https://plandalf.com/products/checkouts/invoices) ## Build The Offer Layer The [offer](https://plandalf.com/products/checkouts) is the commercial object your [product](https://plandalf.com/products/checkouts) points at. It should describe what the [buyer](https://plandalf.com/docs/sdk/identity) can purchase, how [checkout](https://plandalf.com/products/checkouts/hosted-checkout) appears, which [price](https://plandalf.com/products/checkouts/payment-options) rules apply, what [invoice](https://plandalf.com/products/checkouts/invoices) gets recorded, and what [automation](https://plandalf.com/products/automations/purchase-automations) happens after purchase. - Use a stable [offer](https://plandalf.com/products/checkouts) for each plan, [product](https://plandalf.com/products/checkouts), [template](https://plandalf.com/templates), package, or upgrade path. - Attach [products](https://plandalf.com/products/checkouts) and [prices](https://plandalf.com/products/checkouts/payment-options) before you wire the buying moment into the app. - Set [invoice](https://plandalf.com/products/checkouts/invoices), [automation](https://plandalf.com/products/automations/purchase-automations), [coupon](https://plandalf.com/products/checkouts/coupons), [bump](https://plandalf.com/products/checkouts/order-bumps), [upsell](https://plandalf.com/products/checkouts/upsells), and confirmation behavior where the seller can inspect it. ![The Numi offer editor with layout, product, theme, automation, invoice, and settings controls.](https://plandalf.com/images/stacks/api-first/numi-offer-editor.png) The [offer](https://plandalf.com/products/checkouts) editor is where the [checkout surface](https://plandalf.com/products/checkouts/hosted-checkout), [products](https://plandalf.com/products/checkouts), [automation](https://plandalf.com/products/automations/purchase-automations), [invoices](https://plandalf.com/products/checkouts/invoices), and display mode come together. ## Wire The Buying Moment The stack should decide when the [buyer](https://plandalf.com/docs/sdk/identity) is ready. Plandalf should decide what the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) means. Keep the page, campaign, or [offer](https://plandalf.com/products/checkouts) focused on the buying moment, then let the [offer](https://plandalf.com/products/checkouts) carry the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) mode, [product](https://plandalf.com/products/checkouts), [price](https://plandalf.com/products/checkouts/payment-options), [invoice](https://plandalf.com/products/checkouts/invoices), and [automation](https://plandalf.com/products/automations/purchase-automations) context. **On the offer page**Use for [hosted checkout pages](https://plandalf.com/products/checkouts/hosted-checkout), launch pages, [pricing](https://plandalf.com/products/checkouts/payment-options) pages, and [checkout templates](https://plandalf.com/templates). **Inside the campaign**Use for [coupons](https://plandalf.com/products/checkouts/coupons), deadline funnels, [order bumps](https://plandalf.com/products/checkouts/order-bumps), [upsells](https://plandalf.com/products/checkouts/upsells), [save offers](https://plandalf.com/docs/offers/save-offers), and lifecycle [sequences](https://plandalf.com/products/automations). **After purchase**Use when fulfilment, [invoices](https://plandalf.com/products/checkouts/invoices), receipts, CRM updates, [tax](https://plandalf.com/platforms/tax) context, or email follow-up need the same [purchase event](https://plandalf.com/docs/api/webhooks). [![The Numi offer editor showing hosted checkout mode controls.](https://plandalf.com/images/features/hosted-checkout/offer-editor-hosted-mode-product.png)](https://plandalf.com/products/checkouts/hosted-checkout) [Hosted checkout](https://plandalf.com/docs/offers/hosted-checkout) lets a sales page hand buyers to a branded [offer page](https://plandalf.com/products/checkouts) when embedding is not the right fit. ## Plan The Data Contract The useful part of a commerce stack is not the button. It is the agreement between the [offer](https://plandalf.com/products/checkouts), Plandalf, the [payment processor](https://plandalf.com/products/checkouts/payment-options), and follow-up tools about which object owns each piece of commerce state. ObjectPrimary ownerHow Plandalf uses it [Customer](https://plandalf.com/docs/sdk/identity)Your appReceives identity and [buyer](https://plandalf.com/docs/sdk/identity) fields so [checkout](https://plandalf.com/products/checkouts/hosted-checkout) and follow-up stay attached to the right person. [Offer](https://plandalf.com/products/checkouts)[Plandalf](https://plandalf.com/products/checkouts)Packages [products](https://plandalf.com/products/checkouts), [prices](https://plandalf.com/products/checkouts/payment-options), [checkout](https://plandalf.com/products/checkouts/hosted-checkout) mode, [invoices](https://plandalf.com/products/checkouts/invoices), [coupons](https://plandalf.com/products/checkouts/coupons), [bumps](https://plandalf.com/products/checkouts/order-bumps), [upsells](https://plandalf.com/products/checkouts/upsells), and confirmation state. [Product and price](https://plandalf.com/products/checkouts)SharedUse stable keys so app entitlements, [invoices](https://plandalf.com/products/checkouts/invoices), and [automation](https://plandalf.com/products/automations/purchase-automations) [events](https://plandalf.com/docs/api/webhooks) point at the same commercial object. [Payment](https://plandalf.com/products/checkouts/payment-options)[Stripe](https://plandalf.com/platforms/stripe)Plandalf keeps [checkout](https://plandalf.com/products/checkouts/hosted-checkout) and [invoice](https://plandalf.com/products/checkouts/invoices) context while the processor handles the charge. [Purchase event](https://plandalf.com/docs/api/webhooks)[Plandalf](https://plandalf.com/products/automations)Starts fulfilment, CRM updates, lifecycle [sequences](https://plandalf.com/products/automations), receipts, and internal [notifications](https://plandalf.com/products/automations/purchase-automations). ## Product Surfaces This Stack Depends On These screenshots come from the [product](https://plandalf.com/products/checkouts) surfaces behind The [Kajabi](https://plandalf.com/platforms/kajabi) Course Launch. They show the Plandalf records and controls a builder should configure before sending buyers from [Kajabi](https://plandalf.com/platforms/kajabi) into [checkout](https://plandalf.com/products/checkouts/hosted-checkout). [ ![The Numi offer editor showing hosted checkout mode controls.](https://plandalf.com/images/features/hosted-checkout/offer-editor-hosted-mode-product.png) ](https://plandalf.com/products/checkouts/hosted-checkout) [Hosted checkout](https://plandalf.com/docs/offers/hosted-checkout) lets a sales page hand buyers to a branded [offer page](https://plandalf.com/products/checkouts) when embedding is not the right fit. [ ![The Numi selling blocks panel showing order bump controls.](https://plandalf.com/images/features/order-bumps/order-bumps-selling-blocks-product.png) ](https://plandalf.com/products/checkouts/order-bumps) [Order bumps](https://plandalf.com/products/checkouts/order-bumps) are configured as selling blocks rather than one-off front-end code. [ ![The Numi coupon discount settings panel.](https://plandalf.com/images/features/coupons/coupon-discount-product.png) ](https://plandalf.com/products/checkouts/coupons) [Coupons](https://plandalf.com/products/checkouts/coupons) keep discount behavior inspectable for sellers and reusable across [checkout](https://plandalf.com/products/checkouts/hosted-checkout) flows. [ ![The Numi offer settings payment controls showing checkout payment configuration.](https://plandalf.com/images/features/payment-options/offer-settings-controls-product.png) ](https://plandalf.com/products/checkouts/payment-options) [Payment options](https://plandalf.com/products/checkouts/payment-options) belong beside the [offer](https://plandalf.com/products/checkouts), so the seller can review [checkout](https://plandalf.com/products/checkouts/hosted-checkout) methods before launch. [ ![The Numi offer editor automation tab showing sequence controls beside the checkout canvas.](https://plandalf.com/images/features/automation/offer-editor-automation-tab-product.png) ](https://plandalf.com/products/automations/purchase-automations) [Automation](https://plandalf.com/products/automations/purchase-automations) is configured beside the [offer](https://plandalf.com/products/checkouts), so purchase-triggered [workflows](https://plandalf.com/workflows) stay attached to the buying surface. [ ![The Numi offer editor with layout, product, theme, automation, invoice, and settings controls.](https://plandalf.com/images/stacks/api-first/numi-offer-editor.png) ](https://plandalf.com/products/checkouts) The [offer](https://plandalf.com/products/checkouts) editor is where the [checkout surface](https://plandalf.com/products/checkouts/hosted-checkout), [products](https://plandalf.com/products/checkouts), [automation](https://plandalf.com/products/automations/purchase-automations), [invoices](https://plandalf.com/products/checkouts/invoices), and display mode come together. [ ![The Numi sales flow builder showing checkout pages and flow structure.](https://plandalf.com/images/features/sales-flows/checkout-pages-flow-product.png) ](https://plandalf.com/products/checkouts/sales-flows) Sales flows keep the buying path visible before traffic moves from the campaign into [checkout](https://plandalf.com/products/checkouts/hosted-checkout). [ ![The Numi automation integrations screen showing connected workflow destinations.](https://plandalf.com/images/features/integrations/automation-integrations-product.png) ](https://plandalf.com/integrations) [Automation](https://plandalf.com/products/automations/purchase-automations) [integrations](https://plandalf.com/integrations) make the post-purchase handoff visible instead of hiding it inside campaign code. [ ![The Numi offer invoices records view showing customer invoice rows and payment status.](https://plandalf.com/images/features/invoices/offer-invoices-records-product.png) ](https://plandalf.com/products/checkouts/invoices) [Invoice](https://plandalf.com/products/checkouts/invoices) records preserve the [buyer](https://plandalf.com/docs/sdk/identity), line item, [payment state](https://plandalf.com/products/checkouts/payment-options), and support context after purchase. [ ![The Numi integrations settings page showing Stripe, PayPal, Stripe test mode, TaxJar, and Avalara connection options.](https://plandalf.com/images/stacks/api-first/numi-payment-processors.png) ](https://plandalf.com/integrations) [Payment](https://plandalf.com/products/checkouts/payment-options) processors and [tax](https://plandalf.com/platforms/tax) services are configured in the app before [checkout](https://plandalf.com/products/checkouts/hosted-checkout) traffic reaches production. [**Hosted checkout pages**Checkout](https://plandalf.com/products/checkouts/hosted-checkout)[**Coupons**Coupons](https://plandalf.com/products/checkouts/coupons)[**Coupons for entire checkout**Coupons](https://plandalf.com/products/checkouts/coupons)[**Coupons for specific products**Coupons](https://plandalf.com/products/checkouts/coupons)[**Payment options**Payments](https://plandalf.com/products/checkouts/payment-options)[**Purchase automations**Automation](https://plandalf.com/products/automations/purchase-automations) ## Build Recipes Use these like [product](https://plandalf.com/products/checkouts)\-specific implementation notes: choose the selling moment, configure the Plandalf surface, then link into the exact features, [integrations](https://plandalf.com/integrations), [sequences](https://plandalf.com/products/automations), and docs needed to ship it. ![The Numi product price row configured as a package price.](https://plandalf.com/images/features/prices/package-price-row-product.png) [Package prices](https://plandalf.com/products/checkouts/payment-options) help bundles and cohorts stay attached to the same [offer](https://plandalf.com/products/checkouts) record. ### Sell a cohort, workshop, or course without rebuilding [checkout](https://plandalf.com/products/checkouts/hosted-checkout) **Outcome:** The course platform can keep the learning experience while Plandalf owns the [offer](https://plandalf.com/products/checkouts), package [price](https://plandalf.com/products/checkouts/payment-options), [checkout](https://plandalf.com/products/checkouts/hosted-checkout), [invoice](https://plandalf.com/products/checkouts/invoices), and [purchase event](https://plandalf.com/docs/api/webhooks). 1. Create the course, workshop, or cohort as a Plandalf [product](https://plandalf.com/products/checkouts) with a package [price](https://plandalf.com/products/checkouts/payment-options). 2. Use the course page, lesson preview, or launch email as the demand surface and point the CTA at the [offer](https://plandalf.com/products/checkouts). 3. Keep [coupons](https://plandalf.com/products/checkouts/coupons), [order bumps](https://plandalf.com/products/checkouts/order-bumps), and [upsells](https://plandalf.com/products/checkouts/upsells) inside the [offer](https://plandalf.com/products/checkouts) so the course platform does not become the [pricing](https://plandalf.com/products/checkouts/payment-options) system. 4. Use the completed [purchase event](https://plandalf.com/docs/api/webhooks) to grant access, send receipts, and start onboarding. [Package prices](https://plandalf.com/products/checkouts/payment-options)[Checkout templates](https://plandalf.com/templates)[Order bumps](https://plandalf.com/products/checkouts/order-bumps)[Upsells](https://plandalf.com/products/checkouts/upsells)[Automations](https://plandalf.com/products/automations) ![The Numi promo overview showing active deadline campaigns and campaign state.](https://plandalf.com/images/features/promos/promo-overview-product.png) [Deadline campaigns](https://plandalf.com/products/promos/deadline-campaigns) keep launch windows, flash sales, expiring [coupons](https://plandalf.com/products/checkouts/coupons), and promo status visible before [checkout](https://plandalf.com/products/checkouts/hosted-checkout). ### Add a deadline-backed enrollment window **Outcome:** Launch copy, [coupon](https://plandalf.com/products/checkouts/coupons) rules, [checkout](https://plandalf.com/products/checkouts/hosted-checkout) totals, and follow-up [sequences](https://plandalf.com/products/automations) all agree when enrollment opens or closes. 1. Create the [offer](https://plandalf.com/products/checkouts) and [price](https://plandalf.com/products/checkouts/payment-options) before announcing the launch window. 2. Attach a deadline campaign or expiring [coupon](https://plandalf.com/products/checkouts/coupons) to the [offer](https://plandalf.com/products/checkouts) instead of making urgency live only in page copy. 3. Send reminder traffic back to the same [offer](https://plandalf.com/products/checkouts) from email, the course page, and social links. 4. After the deadline, route buyers and non-buyers into different follow-up [sequences](https://plandalf.com/products/automations). [Promos](https://plandalf.com/products/promos)[Deadline campaigns](https://plandalf.com/products/promos/deadline-campaigns)[Coupons](https://plandalf.com/products/checkouts/coupons)[Coupon deadline funnel](https://plandalf.com/stacks/coupon-deadline-funnel)[Sequences](https://plandalf.com/products/automations) ![The Numi offer invoices records view showing customer invoice rows and payment status.](https://plandalf.com/images/features/invoices/offer-invoices-records-product.png) [Invoice](https://plandalf.com/products/checkouts/invoices) records preserve the [buyer](https://plandalf.com/docs/sdk/identity), line item, [payment state](https://plandalf.com/products/checkouts/payment-options), and support context after purchase. ### Preserve course [buyer](https://plandalf.com/docs/sdk/identity) records after [payment](https://plandalf.com/products/checkouts/payment-options) **Outcome:** Support can see the [buyer](https://plandalf.com/docs/sdk/identity), line item, [payment state](https://plandalf.com/products/checkouts/payment-options), [invoice](https://plandalf.com/products/checkouts/invoices), [coupon](https://plandalf.com/products/checkouts/coupons), and fulfilment context after the course sale. 1. Confirm [invoice](https://plandalf.com/products/checkouts/invoices) settings before launch so business buyers can get the receipt they need. 2. Use [purchase automations](https://plandalf.com/products/automations/purchase-automations) to grant course access only after [checkout](https://plandalf.com/products/checkouts/hosted-checkout) completes. 3. Send [invoice email](https://plandalf.com/products/checkouts/invoices) and onboarding separately so the [buyer](https://plandalf.com/docs/sdk/identity) receives both the receipt and the next step. 4. Keep the [purchase event](https://plandalf.com/docs/api/webhooks) available for LMS, CRM, email, and support [integrations](https://plandalf.com/integrations). [Invoices](https://plandalf.com/products/checkouts/invoices)[Emailing invoices](https://plandalf.com/products/checkouts/invoices)[Purchase automations](https://plandalf.com/products/automations/purchase-automations)[Course creator stack](https://plandalf.com/stacks/course-creator)[Kajabi comparison](https://plandalf.com/comparisons/kajabi-checkout) ## Compare The Pattern A commerce stack is different from a processor-only [checkout](https://plandalf.com/products/checkouts/hosted-checkout), a marketplace storefront, or a standalone funnel tool. Use these linked comparisons when a builder is deciding whether [Plandalf Offers](https://plandalf.com/products/checkouts) should sit between the sales surface, [payment processor](https://plandalf.com/products/checkouts/payment-options), and follow-up tools. ### [Plandalf vs Gumroad](https://plandalf.com/alternatives/gumroad) Compare with [Gumroad](https://plandalf.com/alternatives/gumroad). Use this when your [product](https://plandalf.com/products/checkouts) already has its own app, catalog, [customer identity](https://plandalf.com/docs/sdk/identity), and fulfilment path instead of needing a marketplace-style [checkout](https://plandalf.com/products/checkouts/hosted-checkout) [product](https://plandalf.com/products/checkouts). [Products](https://plandalf.com/products/checkouts)[SDK checkout](https://plandalf.com/docs/api/sdk-checkout)[Webhooks](https://plandalf.com/docs/api/webhooks) ### [Plandalf vs SamCart](https://plandalf.com/comparisons/samcart-alternative) Compare with [SamCart](https://plandalf.com/comparisons/samcart-alternative). Use this when [checkout](https://plandalf.com/products/checkouts/hosted-checkout) needs [offer](https://plandalf.com/products/checkouts) [automation](https://plandalf.com/products/automations/purchase-automations), [product](https://plandalf.com/products/checkouts) context, [invoices](https://plandalf.com/products/checkouts/invoices), and post-purchase [workflows](https://plandalf.com/workflows) rather than a separate funnel tool beside the business. [Order bumps](https://plandalf.com/products/checkouts/order-bumps)[Upsells](https://plandalf.com/products/checkouts/upsells)[Automations](https://plandalf.com/products/automations) [ThriveCart comparison](https://plandalf.com/comparisons/thrivecart-alternative)[ThriveCart alternatives](https://plandalf.com/comparisons/thrivecart-alternative)[ClickFunnels comparison](https://plandalf.com/alternatives/clickfunnels)[ClickFunnels alternatives](https://plandalf.com/alternatives/clickfunnels)[Kajabi comparison](https://plandalf.com/comparisons/kajabi-checkout)[Kajabi alternatives](https://plandalf.com/comparisons/kajabi-checkout) ## Linked Implementation Map Use this map when The [Kajabi](https://plandalf.com/platforms/kajabi) Course Launch turns from an idea into implementation work. Every linked feature, [integration](https://plandalf.com/integrations), docs page, [workflow](https://plandalf.com/workflows), comparison, [template](https://plandalf.com/templates), and tool is a next step a builder or agent can follow from this stack. ### Product surfaces Configure these Plandalf features before sending buyers into the stack. [**Hosted checkout pages**_Checkout_](https://plandalf.com/products/checkouts/hosted-checkout)[**Coupons**_Coupons_](https://plandalf.com/products/checkouts/coupons)[**Coupons for entire checkout**_Coupons_](https://plandalf.com/products/checkouts/coupons)[**Coupons for specific products**_Coupons_](https://plandalf.com/products/checkouts/coupons)[**Payment options**_Payments_](https://plandalf.com/products/checkouts/payment-options)[**Purchase automations**_Automation_](https://plandalf.com/products/automations/purchase-automations) ### Integrations The tools that own the audience, [payment](https://plandalf.com/products/checkouts/payment-options), delivery, [tax](https://plandalf.com/platforms/tax), CRM, or follow-up path. [**Kajabi**Enrol every _buyer_ in the right _Kajabi_ _offer_ the moment a _checkout_ completes.](https://plandalf.com/platforms/kajabi)[**Stripe**Take cards, wallets and subscriptions through your own _Stripe_ account on every Plandalf _checkout_.](https://plandalf.com/platforms/stripe)[**Zapier**Send every Plandalf sale into a Zap, and on to the rest of your stack.](https://plandalf.com/platforms/zapier)[**MailerLite**Connect paid Plandalf purchases to _MailerLite_ subscribers and groups.](https://plandalf.com/platforms/mailerlite) ### Docs handoff Move from stack planning into exact setup, [SDK](https://plandalf.com/docs/sdk), [API](https://plandalf.com/products/automations/webhooks), and [webhook](https://plandalf.com/docs/api/webhooks) reference pages. [**Offers overview**Understand _Plandalf Offers_: _hosted checkout pages_, embedded _checkout_ flows, _products_, _prices_, add-ons, _order bumps_, _upsells_, _save offers_, and purchase context.](https://plandalf.com/docs/offers/overview)[**Products**Attach _products_ and _prices_ to _offers_ so _checkout_ sessions, _invoices_, and _integrations_ carry clean catalog context.](https://plandalf.com/docs/offers/products)[**Pricing models**Model _one-time prices_, subscriptions, tiered _pricing_, volume _pricing_, trials, discounts, and promo-driven _price_ changes.](https://plandalf.com/docs/offers/pricing)[**Hosted checkout**Plandalf's _hosted checkout_ — managed URL, theme-able down to fonts and layout, with test and _preview sessions_.](https://plandalf.com/docs/offers/hosted-checkout)[**Save offers**Present a discount, plan switch, pause, or deadline-bound _offer_ when a subscriber starts a cancellation path.](https://plandalf.com/docs/offers/save-offers)[**Stripe**Connect _Stripe_ as the _payment_ account behind _Plandalf offers_, then test _checkout_, _products_, _prices_, and payout behavior before _going live_.](https://plandalf.com/docs/platforms/stripe)[**Developer API reference**A compact map of _SDK_ methods, public client routes, and security boundaries.](https://plandalf.com/docs/api/reference)[**Webhooks**Start _Plandalf automations_ from generated catch URLs or send outbound HTTP requests from _automation_ actions.](https://plandalf.com/docs/api/webhooks)[**SDK checkout API**Understand _checkout_ internals without confusing _buyer_\-facing routes with _payment_ verification.](https://plandalf.com/docs/api/sdk-checkout)[**Install the SDK**Load the Plandalf browser _SDK_ on any site, app, page builder, or framework route.](https://plandalf.com/docs/sdk/install)[**React SDK**Build a concise upgrade button with the _React_ provider, promise results, and explicit backend props. Add _live events_ only when needed.](https://plandalf.com/docs/sdk/react)[**Live events**Use FlowHandle _events_ and DOM _events_ to observe _checkout_ starts, purchases, completions, and cancellations.](https://plandalf.com/docs/sdk/events)[**Identify customers**_Customer_ JWT claims, signing keys, validation, and browser identity lifecycle.](https://plandalf.com/docs/sdk/identity)[**Configure the SDK**Configure frame style, test mode, size, _promos_, identity, _session continuity_, _metadata_, properties, and close behavior.](https://plandalf.com/docs/sdk/configure) ### Recipes and sequences Use these when the sale needs fulfilment, lifecycle, [webhook](https://plandalf.com/docs/api/webhooks), or [automation](https://plandalf.com/products/automations/purchase-automations) depth. [**Checkout completed → fulfillment**Fire fulfillment actions the moment a Plandalf _checkout_ completes.](https://plandalf.com/products/automations)[**Sell a Webflow product with Stripe Checkout**Wire a Plandalf _hosted checkout_ into a _Webflow_ site, accept _Stripe_ _payments_, and fulfill on completion.](https://plandalf.com/workflows/sell-webflow-product-with-stripe-checkout)[**Stripe to Mailchimp: tag your buyers**Add every Plandalf and _Stripe_ _buyer_ to a _Mailchimp_ audience with a purchase tag, using a Send _Webhook_ action after _checkout_ completes.](https://plandalf.com/workflows/stripe-to-mailchimp-after-checkout) ### Comparisons Decision pages for buyers choosing between Plandalf and narrower [checkout](https://plandalf.com/products/checkouts/hosted-checkout), funnel, storefront, or [automation](https://plandalf.com/products/automations/purchase-automations) tools. [**Plandalf vs Gumroad**Use this when your _product_ already has its own app, catalog, _customer identity_, and fulfilment path instead of needing a marketplace-style _checkout_ _product_.](https://plandalf.com/alternatives/gumroad)[**Plandalf vs SamCart**Use this when _checkout_ needs _offer_ _automation_, _product_ context, _invoices_, and post-purchase _workflows_ rather than a separate funnel tool beside the business.](https://plandalf.com/comparisons/samcart-alternative)[**ThriveCart alternatives**Compare Plandalf with ThriveCart when this stack overlaps with a funnel, course, or _checkout_ tool and the _buyer_ is evaluating replacement options.](https://plandalf.com/comparisons/thrivecart-alternative)[**ClickFunnels alternatives**Compare Plandalf with _ClickFunnels_ when this stack overlaps with a funnel, course, or _checkout_ tool and the _buyer_ is evaluating replacement options.](https://plandalf.com/alternatives/clickfunnels)[**Kajabi alternatives**Compare Plandalf with _Kajabi_ when this stack overlaps with a funnel, course, or _checkout_ tool and the _buyer_ is evaluating replacement options.](https://plandalf.com/comparisons/kajabi-checkout) ### Templates and tools Adjacent pages that help turn the stack into an implementation plan. [**Webflow + Stripe Checkout**A ready-to-clone Plandalf _checkout_ _template_ designed for _Webflow_ sites paying via _Stripe_.](https://plandalf.com/templates/webflow-stripe-checkout)[**Writers & creators**Drop a _buy button_ inside the post. Sell the upgrade in the same scroll.](https://plandalf.com/products/checkouts) ## Operational Recipes These are the practical recipes a builder usually needs after the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) opens. They stay [product](https://plandalf.com/products/checkouts)\-level: [Offers](https://plandalf.com/products/checkouts), [Automations](https://plandalf.com/products/automations), [integrations](https://plandalf.com/integrations), [invoices](https://plandalf.com/products/checkouts/invoices), [sequences](https://plandalf.com/products/automations), and [payment](https://plandalf.com/products/checkouts/payment-options) [events](https://plandalf.com/docs/api/webhooks) explain the [workflow](https://plandalf.com/workflows) before any tool-specific setup. ![The Numi offer editor automation tab showing sequence controls beside the checkout canvas.](https://plandalf.com/images/features/automation/offer-editor-automation-tab-product.png) [Automation](https://plandalf.com/products/automations/purchase-automations) is configured beside the [offer](https://plandalf.com/products/checkouts), so purchase-triggered [workflows](https://plandalf.com/workflows) stay attached to the buying surface. ### Grant access after purchase **Trigger:** [Checkout](https://plandalf.com/products/checkouts/hosted-checkout) completed **Action:** Mark the workspace, account, seat, course, [template](https://plandalf.com/templates), or [API](https://plandalf.com/products/automations/webhooks) plan as active in your [product](https://plandalf.com/products/checkouts) database. [Webhooks](https://plandalf.com/docs/api/webhooks)[SDK events](https://plandalf.com/docs/sdk/events)[Feature gates](https://plandalf.com/products/checkouts) ![The Numi offer invoices page showing invoice status, customer, amount, and line item information.](https://plandalf.com/images/stacks/api-first/numi-offer-invoices.png) [Invoices](https://plandalf.com/products/checkouts/invoices) preserve the commercial record after [checkout](https://plandalf.com/products/checkouts/hosted-checkout), including line items and status. ### Send transactional receipts separately from lifecycle email **Trigger:** [Invoice](https://plandalf.com/products/checkouts/invoices) or purchase recorded **Action:** [MailerLite](https://plandalf.com/platforms/mailerlite) handles receipts, while lifecycle tools handle onboarding and expansion. [Invoices](https://plandalf.com/products/checkouts/invoices)[Emailing invoices](https://plandalf.com/products/checkouts/invoices)[MailerLite](https://plandalf.com/platforms/mailerlite)[Customer.io](https://plandalf.com/platforms/customer-io) ![The Numi sequences screen showing automated workflow configuration.](https://plandalf.com/images/features/automation/sequences-desktop.jpg) [Sequences](https://plandalf.com/products/automations) turn the [purchase event](https://plandalf.com/docs/api/webhooks) into onboarding, fulfilment, alerts, and lifecycle follow-up. ### Start a [customer](https://plandalf.com/docs/sdk/identity) lifecycle [sequence](https://plandalf.com/products/automations) **Trigger:** [Purchase event](https://plandalf.com/docs/api/webhooks) carries [product](https://plandalf.com/products/checkouts), [price](https://plandalf.com/products/checkouts/payment-options), [offer](https://plandalf.com/products/checkouts), [buyer](https://plandalf.com/docs/sdk/identity), and [coupon](https://plandalf.com/products/checkouts/coupons) context **Action:** Send onboarding, activation, renewal, save-[offer](https://plandalf.com/products/checkouts), or expansion messages without treating the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) as a generic form submit. [Sequences](https://plandalf.com/products/automations)[Automations](https://plandalf.com/products/automations)[Coupons](https://plandalf.com/products/checkouts/coupons)[Postmark](https://plandalf.com/platforms/postmark) ![The Numi offer invoices records view showing customer invoice rows and payment status.](https://plandalf.com/images/features/invoices/offer-invoices-records-product.png) [Invoice](https://plandalf.com/products/checkouts/invoices) records preserve the [buyer](https://plandalf.com/docs/sdk/identity), line item, [payment state](https://plandalf.com/products/checkouts/payment-options), and support context after purchase. ### Keep support and finance records useful **Trigger:** [Invoice](https://plandalf.com/products/checkouts/invoices) created or [payment state](https://plandalf.com/products/checkouts/payment-options) changes **Action:** Store [invoice](https://plandalf.com/products/checkouts/invoices) identifiers, line items, [tax](https://plandalf.com/platforms/tax) context, and [customer](https://plandalf.com/docs/sdk/identity) fields so refunds, support questions, and reporting have a durable record. [Custom invoices](https://plandalf.com/products/checkouts/invoices)[PDF invoices](https://plandalf.com/products/checkouts/invoices)[TaxJar](https://plandalf.com/platforms/taxjar)[Avalara](https://plandalf.com/platforms/avalara) ## Builder Checklist Before shipping the [integration](https://plandalf.com/integrations), verify these decisions. If one is unclear, the [checkout](https://plandalf.com/products/checkouts/hosted-checkout) may open, but the business [workflow](https://plandalf.com/workflows) after purchase will still be brittle. `01`**[Offer selected](https://plandalf.com/products/checkouts)**Every buying moment points to a clear [offer](https://plandalf.com/products/checkouts), not an improvised [payment](https://plandalf.com/products/checkouts/payment-options) link. `02`**[Identity mapped](https://plandalf.com/docs/sdk/identity)**Your [product](https://plandalf.com/products/checkouts) can reconcile the [buyer](https://plandalf.com/docs/sdk/identity), [customer](https://plandalf.com/docs/sdk/identity), workspace, account, or entitlement after purchase. `03`**[Event path chosen](https://plandalf.com/docs/api/webhooks)**Fulfilment starts from a [purchase event](https://plandalf.com/docs/api/webhooks) or [sequence](https://plandalf.com/products/automations), not from a front-end success screen alone. `04`**[Records preserved](https://plandalf.com/products/checkouts/invoices)**[Invoices](https://plandalf.com/products/checkouts/invoices), line items, [payment state](https://plandalf.com/products/checkouts/payment-options), and [customer](https://plandalf.com/docs/sdk/identity) fields are available for support and reporting. ## Next Steps ### [Substack Shop](https://plandalf.com/stacks/substack-shop) Sell a [template](https://plandalf.com/templates), report, workshop, membership, or paid download from a Substack post while Plandalf owns the [offer](https://plandalf.com/products/checkouts), [checkout](https://plandalf.com/products/checkouts/hosted-checkout), [invoice](https://plandalf.com/products/checkouts/invoices), and [purchase event](https://plandalf.com/docs/api/webhooks). [Stripe](https://plandalf.com/platforms/stripe)[Hosted checkout pages](https://plandalf.com/products/checkouts/hosted-checkout)[Payment options](https://plandalf.com/products/checkouts/payment-options)[Purchase automations](https://plandalf.com/products/automations/purchase-automations) ### [The Course Creator](https://plandalf.com/stacks/course-creator) Enrol each [buyer](https://plandalf.com/docs/sdk/identity) into the right cohort [sequence](https://plandalf.com/products/automations) the moment they pay. [Stripe](https://plandalf.com/platforms/stripe)[MailerLite](https://plandalf.com/platforms/mailerlite)[order-bumps](https://plandalf.com/products/checkouts/order-bumps)[Coupons for specific products](https://plandalf.com/products/checkouts/coupons)[Purchase automations](https://plandalf.com/products/automations/purchase-automations) ### [The Newsletter Creator](https://plandalf.com/stacks/newsletter-creator) Monetise an existing newsletter audience by selling one-off [products](https://plandalf.com/products/checkouts) from inside the same list tool. [Stripe](https://plandalf.com/platforms/stripe)[Zapier](https://plandalf.com/platforms/zapier)[order-bumps](https://plandalf.com/products/checkouts/order-bumps)[Coupons](https://plandalf.com/products/checkouts/coupons)[Purchase automations](https://plandalf.com/products/automations/purchase-automations) ### [The Drop Shop](https://plandalf.com/stacks/ecom-drop) Run a time-boxed drop with a real countdown, a bundle [upsell](https://plandalf.com/products/checkouts/upsells), and segmented re-engagement. [Stripe](https://plandalf.com/platforms/stripe)[Zapier](https://plandalf.com/platforms/zapier)[order-bumps](https://plandalf.com/products/checkouts/order-bumps)[Coupons](https://plandalf.com/products/checkouts/coupons) ### [The API-First Product](https://plandalf.com/stacks/api-first) Split transactional email from lifecycle email so each tool does what it's good at. [Stripe](https://plandalf.com/platforms/stripe)[Purchase automations](https://plandalf.com/products/automations/purchase-automations)[Payment options](https://plandalf.com/products/checkouts/payment-options) ### [The Affiliate Tax Launch](https://plandalf.com/stacks/affiliate-tax-launch) Connect affiliate sales, [payment options](https://plandalf.com/products/checkouts/payment-options), live [tax](https://plandalf.com/platforms/tax) calculation, and post-purchase reconciliation. [Affiliate integration](https://plandalf.com/products/affiliates)[Tax](https://plandalf.com/platforms/tax)[TaxJar](https://plandalf.com/platforms/taxjar) ### Automation sequences [**Checkout completed → fulfillment**Fire fulfillment actions the moment a Plandalf checkout completes.](https://plandalf.com/products/automations) ### Templates [**Webflow + Stripe Checkout**A ready-to-clone Plandalf checkout template designed for Webflow sites paying via Stripe.](https://plandalf.com/templates/webflow-stripe-checkout) ### Use cases [**Writers & creators**Drop a buy button inside the post. Sell the upgrade in the same scroll.](https://plandalf.com/products/checkouts)[**Career coaches & advisors**Sell sessions, packages, and cohort programs on a checkout that matches your coaching practice.](https://plandalf.com/products/checkouts)[**Studios, coaches, trainers**Sell memberships, class packs, and drops without renting another membership app every month.](https://plandalf.com/products/checkouts)[**Solopreneurs**A practical checkout system for one-person businesses selling digital products, services, subscriptions, and small launches.](https://plandalf.com/products/checkouts)[**Growth & checkout teams**When the checkout is the product. A surface designed to convert, not configure.](https://plandalf.com/products/checkouts) ### Features and docs [**Offers product**Checkout pages, embedded offers, products, prices, coupons, bumps, upsells, and invoices.](https://plandalf.com/products/checkouts)[**Automations product**Purchase-triggered workflows for CRM, email, fulfilment, records, and handoff.](https://plandalf.com/products/automations)[**Sequences**Events that fire after checkout, payment, subscription, and lifecycle changes.](https://plandalf.com/products/automations)[**Payment integrations**Stripe, PayPal, payment options, invoices, and payment event routing.](https://plandalf.com/platforms/payment)[**Offers docs**How Offers packages products, prices, checkout layouts, and conversion elements.](https://plandalf.com/docs/offers/overview)[**Hosted checkout docs**Hosted and embedded checkout setup, test sessions, and preview sessions.](https://plandalf.com/docs/offers/hosted-checkout)[**Stripe docs**How Stripe connects and what events Plandalf listens for.](https://plandalf.com/docs/platforms/stripe)[**Webhook docs**Checkout, payment, and subscription events for custom automations.](https://plandalf.com/docs/api/webhooks)[**Hosted checkout pages**Checkout](https://plandalf.com/products/checkouts/hosted-checkout)[**Coupons**Coupons](https://plandalf.com/products/checkouts/coupons)[**Coupons for entire checkout**Coupons](https://plandalf.com/products/checkouts/coupons)[**Coupons for specific products**Coupons](https://plandalf.com/products/checkouts/coupons)