The offer record connects the stack
Use Offers to define the product, price, checkout mode, invoice, and automation context before Avalara and Custom API receive events.
Integration pair
Avalara + Custom API
Use Avalara and Custom API together with Plandalf as the layer that ties checkout, payments, invoices, integrations, and lifecycle automation together.
Common setup
Most teams use Avalara as their tax layer and Custom API as their sdk layer, with Plandalf in the middle handling the checkout, Offers, invoices, integrations, and the events that fire after a purchase.
See Avalara and Custom API 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.
Integration settings remain visible
Confirm Stripe, PayPal, TaxJar, Avalara, and test-mode routing before sending the Avalara and Custom API 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 Avalara or Custom API mention has a useful next step.
Open canonical app-pair guide Use the richer Avalara and Custom API implementation guide. Avalara platform page Roles, capabilities, and setup notes for Avalara. Custom API platform page Roles, capabilities, and setup notes for Custom API. API-first stack SDK checkout, API keys, webhooks, payment processors, and invoices.