> Every checkout fires a sequence. Grant access, sync to your CRM, recover failed payments — without a third tool.

Source: https://plandalf.com/for-operations

For operations

# Wire purchase events into the rest of the business

Every [checkout](https://plandalf.com/products/checkouts) fires a [sequence](https://plandalf.com/sequences). Grant access, sync to your [CRM](https://plandalf.com/platforms/crm), recover failed payments — without a third tool.

[Start free](https://admin.plandalf.dev/register)[See the docs](https://plandalf.com/docs)

[![The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.](https://plandalf.com/images/stacks/api-first/numi-offer-editor.png)](https://plandalf.com/products/checkouts)

Operations need the [offer](https://plandalf.com/products/checkouts), [checkout](https://plandalf.com/products/checkouts), product, [price](https://plandalf.com/features/prices), invoice, and [automation](https://plandalf.com/features/automation) handoff visible before traffic goes live.

## What operations use Plandalf for

[

Sequences on checkout events

](https://plandalf.com/sequences)[

Failed payment recovery

](https://plandalf.com/platforms/payment)[

CRM sync

](https://plandalf.com/platforms/crm)

See more specific patterns in the [use-case library](https://plandalf.com/use-cases).

## Where operations touch the product

This page should work like a practical implementation map for operations: [Offers](https://plandalf.com/products/checkouts), [checkout](https://plandalf.com/products/checkouts), [payment](https://plandalf.com/platforms/payment), [integrations](https://plandalf.com/integrations), [invoices](https://plandalf.com/features/invoices), [API](https://plandalf.com/docs/api/reference) work, [webhooks](https://plandalf.com/docs/api/webhooks), and post-purchase [automation](https://plandalf.com/features/automation) all one click away.

[

![The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.](https://plandalf.com/images/stacks/api-first/numi-offer-editor.png)


](https://plandalf.com/products/checkouts)

### [Build the buying surface first](https://plandalf.com/products/checkouts)

Operations need the [offer](https://plandalf.com/products/checkouts), [checkout](https://plandalf.com/products/checkouts), product, [price](https://plandalf.com/features/prices), invoice, and [automation](https://plandalf.com/features/automation) handoff visible before traffic goes live.

[Offers](https://plandalf.com/products/checkouts)[Products](https://plandalf.com/features/products)[Prices](https://plandalf.com/features/prices)[Invoices](https://plandalf.com/features/invoices)

[

![The Numi integrations settings page showing Stripe, PayPal, TaxJar, and Avalara connection options.](https://plandalf.com/images/stacks/api-first/numi-payment-processors.png)


](https://plandalf.com/integrations)

### [Keep payment and integrations inspectable](https://plandalf.com/integrations)

Operations can connect [Stripe](https://plandalf.com/platforms/stripe), [PayPal](https://plandalf.com/platforms/paypal), [CRM](https://plandalf.com/platforms/crm), email, [tax](https://plandalf.com/features/tax), [API](https://plandalf.com/docs/api/reference), and workflow tools without hiding the [payment](https://plandalf.com/platforms/payment) path from operators.

[Integrations](https://plandalf.com/integrations)[Payment platforms](https://plandalf.com/platforms/payment)[Stripe](https://plandalf.com/platforms/stripe)[PayPal](https://plandalf.com/platforms/paypal)

[

![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)

### [Route the purchase event after checkout](https://plandalf.com/products/automations)

After purchase, Operations can use [Automations](https://plandalf.com/products/automations), [webhooks](https://plandalf.com/docs/api/webhooks), and [sequences](https://plandalf.com/sequences) to grant access, update [CRM](https://plandalf.com/platforms/crm), send fulfilment work, or alert the team.

[Automations](https://plandalf.com/products/automations)[Webhooks](https://plandalf.com/docs/api/webhooks)[Sequences](https://plandalf.com/sequences)[Checkout fulfilment](https://plandalf.com/sequences/checkout-completed-fulfillment)

## Implementation paths to keep open

Use these resources when operations need to move from an idea into a working [offer](https://plandalf.com/products/checkouts), deadline, integration, [payment](https://plandalf.com/platforms/payment) flow, or [automation](https://plandalf.com/features/automation) path.

[**Offers**_Hosted checkout_, _products_, _prices_, _coupons_, _order bumps_, _upsells_, _invoices_, and purchase context.](https://plandalf.com/products/checkouts)[**Promos**_Launch windows_, deadline funnels, expiring _coupons_, and promo state tied to _checkout_.](https://plandalf.com/products/promos)[**Integrations**_Payment_ processors, site builders, _CRM_, email, _tax_, _API_, and _automation_ paths.](https://plandalf.com/integrations)[**API-first stack**_SDK_ _checkout_, _API_ keys, _payment_ processors, _invoices_, and _webhooks_ together.](https://plandalf.com/stacks/api-first)[**Automations**Audience-specific path for operations planning this workflow.](https://plandalf.com/products/automations)[**Webhooks**Audience-specific path for operations planning this workflow.](https://plandalf.com/docs/api/webhooks)[**CRM platforms**Audience-specific path for operations planning this workflow.](https://plandalf.com/platforms/crm)