Custom pages in Throttle Builder: create, duplicate, rename
Create content and landing pages in Throttle Builder, duplicate them, choose an address and rename a page without breaking links, and delete a page safely.
Playbooks that walk one job end to end — what you do, in what order, and what to watch out for. Looking up how a single feature behaves instead? That's Docs.
Create content and landing pages in Throttle Builder, duplicate them, choose an address and rename a page without breaking links, and delete a page safely.
The fulfiller's playbook: finding what still needs to go out, shipping in parts, adding tracking, delivering digital goods, and when to hold an order.
Giving a buyer their money back the right way: refunds, cancellations, returns that refund themselves, exchanges, comps, and what the buyer is told.
The two delivery modes of Throttle Builder, in plain words: when a change shows, what each costs on your host, how releases work and how to roll back.
Launching a discount code without surprises: creating it in the right environment, setting limits, testing it before you announce it, and pausing it.
The operator's loop: what arrives in your queue, what needs a decision, and how to close out an order without leaving money or goods in limbo.
How your Throttle Builder pages appear in search and when shared: titles, descriptions, share images, hiding a page, the sitemap and what your developer does.
Install Throttle Builder, connect your store, create and publish pages, and optionally let an AI agent build them for you, safely, from your own account.
The finance month-end routine in Throttle: closing against production, exporting orders, recording offline payments, aging receivables, and timezone traps.
The finance playbook for selling on Net-N: deciding who gets credit, setting terms that stick, chasing what's late, and reconciling what arrives.
The finance playbook for contested money: how card chargebacks arrive, where disputes show up, flagging an invoice dispute, and what pauses dunning.
The admin playbook for who can do what: inviting people with the least access they need, environment limits, minting and rotating API keys, and audits.
The admin playbook: workspaces and applications, environments, connecting a processor, inviting your team, and the four checks that gate going live.
Putting subscription billing behind a multi-tenant app: the decisions that are hard to reverse, the integration in order, and the cutover.
How a Throttle checkout splits between your storefront and ours: cart state on your server, payment capture in a hardened embed, webhooks as the record.
Every box to tick before billing real customers — build, test matrix, and cutover — with the assertion that proves each one actually works.
What actually moves when you migrate to Throttle, what stays where it is, and how to run the whole thing in parallel before you touch DNS.