Plandalf

Builder resource

The Membership Site

WordPress + Stripe subscriptions + HubSpot for CRM. Built for renewals.

Convert one-time buyers into renewed members and keep the CRM in sync.

WordPress runs the member-only content, Plandalf handles the upgrade and renewal offers, Stripe runs the subscriptions, Mailchimp keeps the list warm, and HubSpot is the single member record the team works in.

Built for: Community operators, association sites, paid membership orgs

This page is the builder map: patterns, responsibilities, recipes, and product decisions for adding Plandalf to this commerce stack.
The Numi product price row configured as a subscription price.
Subscription prices keep renewal and lifecycle context attached to the product record.
The Numi offer editor settings tab showing customer and checkout settings.
Customer identify makes the buyer durable across checkout, invoices, events, and follow-up.

Architecture

Treat Plandalf Offers as the commerce layer between the sales page, the buying moment, and the payment processor. Your stack owns the audience and fulfilment experience. Plandalf owns offer configuration, checkout state, pricing rules, buyer identity, invoices, and the events that drive follow-up.

Site WordPress Buyer clicks the CTA on your page. Checkout Plandalf Buyer opens the embedded checkout/modal. Payment Stripe Buyer submits payment in Plandalf. CRM HubSpot Plandalf records a completed checkout. Automation HubSpot The previous stack step completes. Email Mailchimp The previous stack step completes.
Stage System Handoff
Site WordPress Plandalf opens from that page with the selected offer context.
Checkout Plandalf Plandalf validates the offer, applies pricing logic, and emits checkout events.
Payment Stripe Plandalf sends the payment request to Stripe, then records the completed purchase event.
CRM HubSpot Plandalf Automation creates or updates the contact in HubSpot.
Automation HubSpot Plandalf Automation sends the event payload to HubSpot.
Email Mailchimp Plandalf Automation sends the event and customer fields to Mailchimp.

How This Stack Makes The Sale Work

The Membership Site is useful when each tool has a clear job: the audience surface creates intent, Plandalf turns that intent into a configured offer, Stripe collects payment, and the follow-up tools receive the purchase context they need.

Choose The Pattern

Start by deciding which business moment you are building. The stack changes depending on whether checkout starts from a sales page, a launch campaign, an offer page, a checkout template, or an existing product catalog.

Build The Offer Layer

The offer is the commercial object your product points at. It should describe what the buyer can purchase, how checkout appears, which price rules apply, what invoice gets recorded, and what automation happens after purchase.

The Numi offer editor with layout, product, theme, automation, invoice, and settings controls.
The offer editor is where the checkout surface, products, automation, invoices, and display mode come together.

Wire The Buying Moment

The stack should decide when the buyer is ready. Plandalf should decide what the checkout means. Keep the page, campaign, or offer focused on the buying moment, then let the offer carry the checkout mode, product, price, invoice, and automation context.

On the offer pageUse for hosted checkout pages, launch pages, pricing pages, and checkout templates.
Inside the campaignUse for coupons, deadline funnels, order bumps, upsells, save offers, and lifecycle sequences.
After purchaseUse when fulfilment, invoices, receipts, CRM updates, tax context, or email follow-up need the same purchase event.
The Numi product price row configured as a subscription price.
Subscription prices keep renewal and lifecycle context attached to the product record.

Plan The Data Contract

The useful part of a commerce stack is not the button. It is the agreement between the offer, Plandalf, the payment processor, and follow-up tools about which object owns each piece of commerce state.

Object Primary owner How Plandalf uses it
Customer Your app Receives identity and buyer fields so checkout and follow-up stay attached to the right person.
Offer Plandalf Packages products, prices, checkout mode, invoices, coupons, bumps, upsells, and confirmation state.
Product and price Shared Use stable keys so app entitlements, invoices, and automation events point at the same commercial object.
Payment Stripe Plandalf keeps checkout and invoice context while the processor handles the charge.
Purchase event Plandalf Starts fulfilment, CRM updates, lifecycle sequences, receipts, and internal notifications.

Product Surfaces This Stack Depends On

These screenshots come from the product surfaces behind The Membership Site. They show the Plandalf records and controls a builder should configure before sending buyers from WordPress into checkout.

The Numi product price row configured as a subscription price.
Subscription prices keep renewal and lifecycle context attached to the product record.
The Numi offer editor settings tab showing customer and checkout settings.
Customer identify makes the buyer durable across checkout, invoices, events, and follow-up.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.
Automation is configured beside the offer, so purchase-triggered workflows stay attached to the buying surface.
The Numi automation integrations screen showing connected workflow destinations.
Automation integrations make the post-purchase handoff visible instead of hiding it inside campaign code.
The Numi offer editor with layout, product, theme, automation, invoice, and settings controls.
The offer editor is where the checkout surface, products, automation, invoices, and display mode come together.
The Numi sales flow builder showing checkout pages and flow structure.
Sales flows keep the buying path visible before traffic moves from the campaign into checkout.
The Numi offer settings payment controls showing checkout payment configuration.
Payment options belong beside the offer, so the seller can review checkout methods before launch.
The Numi offer invoices records view showing customer invoice rows and payment status.
Invoice records preserve the buyer, line item, payment state, and support context after purchase.
The Numi integrations settings page showing Stripe, PayPal, Stripe test mode, TaxJar, and Avalara connection options.
Payment processors and tax services are configured in the app before checkout traffic reaches production.
The Numi offer invoices page showing invoice status, customer, amount, and line item information.
Invoices preserve the commercial record after checkout, including line items and status.
Subscription prices Products and pricing Continuity Developer/API Gates Checkout Customer identify Data Team members Team Automation Automation Notifications Notifications Invoice logo Invoices

Build Recipes

Use these like product-specific implementation notes: choose the selling moment, configure the Plandalf surface, then link into the exact features, integrations, sequences, and docs needed to ship it.

The Numi product price row configured as a package price.
Package prices help bundles and cohorts stay attached to the same offer record.

Sell a cohort, workshop, or course without rebuilding checkout

Outcome: The course platform can keep the learning experience while Plandalf owns the offer, package price, checkout, invoice, and purchase event.

  1. Create the course, workshop, or cohort as a Plandalf product with a package price.
  2. Use the course page, lesson preview, or launch email as the demand surface and point the CTA at the offer.
  3. Keep coupons, order bumps, and upsells inside the offer so the course platform does not become the pricing system.
  4. Use the completed purchase event to grant access, send receipts, and start onboarding.
Package pricesCheckout templatesOrder bumpsUpsellsAutomations
The Numi promo overview showing active deadline campaigns and campaign state.
Deadline campaigns keep launch windows, flash sales, expiring coupons, and promo status visible before checkout.

Add a deadline-backed enrollment window

Outcome: Launch copy, coupon rules, checkout totals, and follow-up sequences all agree when enrollment opens or closes.

  1. Create the offer and price before announcing the launch window.
  2. Attach a deadline campaign or expiring coupon to the offer instead of making urgency live only in page copy.
  3. Send reminder traffic back to the same offer from email, the course page, and social links.
  4. After the deadline, route buyers and non-buyers into different follow-up sequences.
TimersDeadline campaignsCouponsCoupon deadline funnelSequences
The Numi offer invoices records view showing customer invoice rows and payment status.
Invoice records preserve the buyer, line item, payment state, and support context after purchase.

Preserve course buyer records after payment

Outcome: Support can see the buyer, line item, payment state, invoice, coupon, and fulfilment context after the course sale.

  1. Confirm invoice settings before launch so business buyers can get the receipt they need.
  2. Use purchase automations to grant course access only after checkout completes.
  3. Send invoice email and onboarding separately so the buyer receives both the receipt and the next step.
  4. Keep the purchase event available for LMS, CRM, email, and support integrations.
InvoicesEmailing invoicesPurchase automationsCourse creator stackKajabi comparison

Compare The Pattern

A commerce stack is different from a processor-only checkout, a marketplace storefront, or a standalone funnel tool. Use these linked comparisons when a builder is deciding whether Plandalf Offers should sit between the sales surface, payment processor, and follow-up tools.

ThriveCart comparison ThriveCart alternatives ClickFunnels comparison ClickFunnels alternatives Kajabi comparison Kajabi alternatives PayPal comparison PayPal alternatives Zapier comparison Zapier alternatives

Linked Implementation Map

Use this map when The Membership Site turns from an idea into implementation work. Every linked feature, integration, docs page, workflow, comparison, template, 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.

Integrations

The tools that own the audience, payment, delivery, tax, CRM, or follow-up path.

Docs handoff

Move from stack planning into exact setup, SDK, API, and webhook 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. Products Attach products and prices to offers so checkout sessions, invoices, and integrations carry clean catalog context. Pricing models Model one-time prices, subscriptions, tiered pricing, volume pricing, trials, discounts, and promo-driven price changes. Hosted checkout Plandalf's hosted checkout — managed URL, theme-able down to fonts and layout, with test and preview sessions. Save offers Present a discount, plan switch, pause, or deadline-bound offer when a subscriber starts a cancellation path. Stripe Connect Stripe as the payment account behind Plandalf offers, then test checkout, products, prices, and payout behavior before going live. Developer API reference Reference the main SDK methods, HTML attributes, FlowHandle events, and protected API authentication model. Webhooks Start Plandalf automations from generated catch URLs or send outbound HTTP requests from automation actions. SDK checkout API Understand the public checkout endpoints the Plandalf SDK calls for offer loading, session creation, session lookup, mutations, and discounts. Install the SDK Load the Plandalf browser SDK on any site, app, page builder, or framework route. React SDK Use PlandalfProvider and React hooks to present offers, identify customers, check gates, and render checkout experiences. Live events Use FlowHandle events and DOM events to observe checkout starts, purchases, completions, and cancellations. Identify customers Attach Plandalf checkout sessions to logged-in users with email identity or signed JWT identity. Configure the SDK Configure frame style, test mode, size, promos, identity, session continuity, metadata, properties, and close behavior.

Recipes and sequences

Use these when the sale needs fulfilment, lifecycle, webhook, or automation depth.

Comparisons

Decision pages for buyers choosing between Plandalf and narrower checkout, funnel, storefront, or automation tools.

Plandalf vs Stripe Checkout Use this when you need Stripe payments plus offer configuration, invoices, post-purchase automation, and seller-operated checkout changes. 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. 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. Plandalf vs Shopify Use this when the business is selling software, access, templates, subscriptions, or services and does not need a full storefront catalog. ThriveCart comparison Compare Plandalf with ThriveCart when this stack overlaps with a processor, funnel, storefront, course, or automation tool. ThriveCart alternatives Use the ThriveCart alternatives page when the buyer is evaluating replacement options. ClickFunnels comparison Compare Plandalf with ClickFunnels when this stack overlaps with a processor, funnel, storefront, course, or automation tool. ClickFunnels alternatives Use the ClickFunnels alternatives page when the buyer is evaluating replacement options. Kajabi comparison Compare Plandalf with Kajabi when this stack overlaps with a processor, funnel, storefront, course, or automation tool. Kajabi alternatives Use the Kajabi alternatives page when the buyer is evaluating replacement options. PayPal comparison Compare Plandalf with PayPal when this stack overlaps with a processor, funnel, storefront, course, or automation tool. PayPal alternatives Use the PayPal alternatives page when the buyer is evaluating replacement options. Zapier comparison Compare Plandalf with Zapier when this stack overlaps with a processor, funnel, storefront, course, or automation tool. Zapier alternatives Use the Zapier alternatives page when the buyer is evaluating replacement options.

Templates and tools

Adjacent pages that help turn the stack into an implementation plan.

Operational Recipes

These are the practical recipes a builder usually needs after the checkout opens. They stay product-level: Offers, Automations, integrations, invoices, sequences, and payment events explain the workflow before any tool-specific setup.

Builder Checklist

Before shipping the integration, verify these decisions. If one is unclear, the checkout may open, but the business workflow after purchase will still be brittle.

01Offer selectedEvery buying moment points to a clear offer, not an improvised payment link.
02Identity mappedYour product can reconcile the buyer, customer, workspace, account, or entitlement after purchase.
03Event path chosenFulfilment starts from a purchase event or sequence, not from a front-end success screen alone.
04Records preservedInvoices, line items, payment state, and customer fields are available for support and reporting.

Next Steps

Automation sequences

Price plan changed lifecycle Route product, price, plan, and subscription changes into lifecycle messaging and internal records. Invoice issued record sync Send invoice, customer, and payment records to email, CRM, and operations systems after checkout or renewal.

Templates

Webflow + Stripe Checkout A ready-to-clone Plandalf checkout template designed for Webflow sites paying via Stripe.

Use cases

Writers & creators Drop a buy button inside the post. Sell the upgrade in the same scroll. Career coaches & advisors Sell sessions, packages, and cohort programs on a checkout that matches your coaching practice. Event organizers Ticket tiers, early-bird timers, group rates — without renting a ticketing platform that owns your audience. Studios, coaches, trainers Sell memberships, class packs, and drops without renting another membership app every month. Boutique hotels, restaurants, venues Take the booking the moment the guest decides. Deposits, add-ons, and gift cards on one checkout.

Features and docs

Offers product Checkout pages, embedded offers, products, prices, coupons, bumps, upsells, and invoices. Automations product Purchase-triggered workflows for CRM, email, fulfilment, records, and handoff. Sequences Events that fire after checkout, payment, subscription, and lifecycle changes. Payment integrations Stripe, PayPal, payment options, invoices, and payment event routing. Offers docs How Offers packages products, prices, checkout layouts, and conversion elements. Hosted checkout docs Hosted and embedded checkout setup, test sessions, and preview sessions. Stripe docs How Stripe connects and what events Plandalf listens for. Webhook docs Checkout, payment, and subscription events for custom automations. Subscription prices Products and pricing Continuity Developer/API Gates Checkout Customer identify Data

Feature detail