Sequence playbook

Affiliate sale tax reconciliation

Attach affiliate attribution, tax calculation, payment context, and reporting records to the same completed checkout event.

Triggers

checkout.completed
affiliate.attributed
tax.calculated

Actions

sync_affiliate_sale Sync Affiliate Sale
write_tax_record Write Tax Record
notify_finance Notify Finance

Implementation

How this sequence should be wired.

A named sequence is useful only when the trigger, commercial context, and downstream handoff are all explicit across checkout, integrations, webhooks, and fulfillment.

Trigger

Choose the event that starts the work.

checkout.completed, affiliate.attributed, tax.calculated should fire from a real Plandalf checkout, payment, invoice, subscription, deadline, or affiliate event, not from a front-end success page alone.

Automations Sequences Webhooks

Context

Carry the commercial state with the event.

The sequence should know the offer, product, price, buyer, payment state, coupon, invoice, and integration context before it touches another tool.

Offers Products Prices Invoices

Handoff

Route each action to the right product or platform.

sync_affiliate_sale, write_tax_record, notify_finance should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.

Integrations Purchase automations Tolt TaxJar Avalara

Product surfaces

Where the operator checks the work.

These are real Plandalf app surfaces tied to the products, features, integrations, invoices, payment settings, API docs, and sequences this playbook depends on.

The Numi tax settings screen showing tax configuration. — Tax settings keep checkout totals and finance records tied to the same purchase context.

The Numi Stripe payment methods settings page showing card, wallet, bank transfer, and buy now pay later options. — Payment options shape the checkout event before the sequence sends it downstream.

The Numi integrations settings page showing Stripe, PayPal, TaxJar, and Avalara connection options. — Payment processors stay visible in the app before checkout traffic reaches production.

The Numi sequences screen showing automated workflow configuration. — Sequences turn checkout, payment, invoice, subscription, and deadline events into follow-up work.

The Numi offer editor automation tab showing sequence controls beside the checkout canvas. — Purchase automations start from the offer, product, buyer, payment, and invoice context Plandalf already knows.

The Numi automation integrations screen showing connected tools. — Integrations decide where the event lands after Plandalf records the checkout state.

Reference links

Everything this playbook touches.

Use these links when a builder needs to move from the sequence concept into the exact product, feature, integration, platform, workflow, stack, or documentation page.

Product

Offers

The checkout surface where your customers actually decide.

Product

Automations

The work that happens after a customer buys.

Feature

Affiliate integration

Affiliates

Feature

Tax

Taxes