Recharge integration

Updated 23 July 2026

Subscription customers pick a first delivery date with Flare; Recharge bills on its own cycle. Without alignment those drift apart — renewals get created too late to make the delivery day, or so early they sit around. This integration keeps Recharge's next-charge dates locked to the delivery schedule.

Available on the Precise plan and above.

Connect it

1. In Recharge, create an API token: Tools & apps → API tokens → Create new, with permissions Read customers and Write subscriptions.
2. In Flare, open Integrations → Recharge, paste the token, and click Connect Recharge.
3. Done — Flare registers its Recharge webhook automatically; there's nothing to paste on the Recharge side.

Settings

• Days before ship date (processing time) — how many days before the ship date Recharge should create/charge the renewal. 0 (default) charges on the ship date; set 2 if you need two days between charge and dispatch.
• Assign dates to recurring subscription orders (on by default) — Flare calculates proper ship/delivery dates for every renewal order, so they're tagged, held, and on the calendar like everything else. Turn off if you only want the billing alignment. Pair with automatic dates for recurring orders to give renewals their own weekday/blocked-date rules.

How it behaves

• When a subscription is created at checkout, Flare reads the chosen first delivery, works back to the ship date, and sets Recharge's next charge date so the following cycle lines up (charge = ship date + interval − processing days).
• Customer reschedules a delivery? The subscription's next charge follows.
• Safety nets: Flare never sets a charge date in the past, and it only adjusts subscriptions created through checkout — mid-cycle manual edits in Recharge aren't overwritten.

Removing it

Integrations → Recharge → Remove connection — Flare cleans up its webhook in Recharge and stops syncing. Billing cycles and delivery dates then run independently again.