The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before WordPress and Customer.io receive events.
Integration pair
WordPress + Customer.io
Use WordPress and Customer.io together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use WordPress as their website layer and Customer.io as their email layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See WordPress and Customer.io docs for connection details.
Product surfaces behind this integration
This legacy integration URL now points builders toward the same product reality as the canonical app-pair guide: Offers, payment options, invoices, integrations, Automations, API docs, and webhooks.
Purchase automation carries the details
Automations and webhooks let WordPress and Customer.io receive buyer, product, payment, invoice, coupon, and deadline context.
Integration settings remain visible
Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the WordPress and Customer.io path live.
Use the richer guide from here
Keep moving from this page into canonical integration docs, platform pages, stack guides, and sequence recipes so every WordPress or Customer.io mention has a useful next step.
Open canonical app-pair guide Use the richer WordPress and Customer.io implementation guide. WordPress platform page Roles, capabilities, and setup notes for WordPress. Customer.io platform page Roles, capabilities, and setup notes for Customer.io. API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.