Product
Automations The work that happens after a customer buys.Metadata
Metadata in Plandalf: where it fits across products, integrations, docs, workflows, and related capabilities.
Build from this feature.
Metadata should not dead-end as an article. Use these product screenshots and references to connect the feature to Offers, Timers, Automations, integrations, docs, workflows, stacks, and comparisons.
Docs
Affiliate attribution Capture partner, referral, and campaign references with URL parameters, SDK metadata, and checkout events.Docs
Catalog API Read catalog products, product plans, and related product metadata from the protected Plandalf API.Docs
API playground pages Build Mintlify-style API reference pages in Plandalf with endpoint metadata, request fields, response fields, examples, multiple responses, SDK samples, schema notes, visibility, and troubleshooting.Docs
Badge Use badges for compact status labels, version markers, and small inline metadata in Plandalf docs.Sequence
Checkout started to abandonment recovery Recover a checkout that opened but did not complete by sending the buyer and offer context to the email or automation tool.Sequence
Purchase event webhook fanout Fan a single purchase event out to custom APIs, SDK-built apps, email systems, analytics, and fulfillment services.Stack
The Affiliate Tax Launch Connect affiliate sales, payment options, live tax calculation, and post-purchase reconciliation.Stack
The API-First Product Split transactional email from lifecycle email so each tool does what it's good at.Stack
The Developer Webhook Stack Give developers a concrete stack for API-led checkout, entitlements, fulfillment, analytics, and custom automations.Where this feature lives
Each product route explains the feature in the context of a real checkout, deadline, or automation workflow.
The work that happens after a customer buys.
Automations turns the completed purchase into the downstream handoff: affiliate attribution, fulfilment, alerts, webhooks, and tool updates can all start from the same buyer and offer context.
Docs, workflows, and implementation links
Capture partner, referral, and campaign references with URL parameters, SDK metadata, and checkout events.
Catalog APIRead catalog products, product plans, and related product metadata from the protected Plandalf API.
API playground pagesBuild Mintlify-style API reference pages in Plandalf with endpoint metadata, request fields, response fields, examples, multiple responses, SDK samples, schema notes, visibility, and troubleshooting.
BadgeUse badges for compact status labels, version markers, and small inline metadata in Plandalf docs.
Code formattingUse Mintlify-style code fence metadata for titled snippets, line numbers, wrapping, highlighted lines, focused lines, diffs, and expandable examples.
Configure the SDKConfigure frame style, test mode, size, promos, identity, session continuity, metadata, properties, and close behavior.
Checkout started to abandonment recoveryRecover a checkout that opened but did not complete by sending the buyer and offer context to the email or automation tool.
Purchase event webhook fanoutFan a single purchase event out to custom APIs, SDK-built apps, email systems, analytics, and fulfillment services.
Builder resources that use Metadata
Use these linked resources when you want to move from the feature itself into a stack, calculator, integration, docs, workflow, or comparison decision.
Connect affiliate sales, payment options, live tax calculation, and post-purchase reconciliation.
The API-First ProductSplit transactional email from lifecycle email so each tool does what it's good at.
The Developer Webhook StackGive developers a concrete stack for API-led checkout, entitlements, fulfillment, analytics, and custom automations.
The Invoice Records Ops StackKeep invoices, receipts, customer identity, team notifications, and CRM records in sync after purchase.