Utterbond integration

Updated 19 August 2026

Utterbond runs native Shopify subscriptions on its own billing cycle. Your customer picks a first delivery date with Flare. Left alone, the two drift apart: a renewal is charged too late to make the delivery day, or so early that it sits waiting. This integration locks Utterbond's next charge date to the delivery schedule.

Available on the Precise plan and above.

Connect it

1. In Utterbond, go to Settings → Manage API tokens → Generate New Token. Give the token these permissions: Shop (Read Only), Subscription Contract (Read & Write), and Orders (Read & Write).
2. In Flare, open Integrations & partners → Utterbond, paste the token, and click Connect Utterbond.
3. Flare checks the token with Utterbond before it saves it. If the token or its permissions are wrong, the message appears on the token field. Once it saves, the page shows Active.

There is nothing to paste on the Utterbond side. Flare reads and writes subscriptions through Utterbond's API, so it needs no webhook.

Settings

Days before ship date (processing time): how many days before the ship date Utterbond creates the recurring order. 0 (default) charges on the ship date. Set 2 if you need two days between the charge and dispatch.

This setting moves the charge date, not the delivery date your customer sees. Their delivery day stays exactly as they chose it.

The processing-time card appears only after you connect. Change the value, then click Save.

How it behaves

• A customer subscribes and picks a first delivery date. Flare reads the ship date off the order, adds the subscription's billing interval, subtracts your processing days, and writes the result to Utterbond as the next charge date. Utterbond shows it as Next billing date.
• Only a subscription's first order sets the date. Recurring charges never recalculate it, so later changes made in Utterbond stand.
• Flare never sets a charge date that is today or in the past. If the calculation lands there, it leaves the subscription alone.
• Renewal orders get their own Flare dates when automatic dates for recurring orders is on. They are then tagged, held, released, and on the calendar like any other order.

When Utterbond has not caught up yet

Utterbond takes orders in from Shopify on its own schedule. A brand-new subscription order can be missing from Utterbond's API, or present but not yet linked to its subscription, at the moment Flare first looks. Flare does not treat that as a failure.

• If Shopify says the order carries a subscription, Flare looks again a few seconds later.
• If the subscription is still not linked, Flare keeps the job and retries every five minutes, up to six times, for about half an hour.
• Every retry re-reads the live order, so a late ship date attribute and a late subscription link are both picked up.
• Nothing is dropped quietly. If all retries are used up, Flare records the order and leaves the charge date as Utterbond set it. Send us the order number and we will look, see contact support.

Plan requirement

The Precise requirement is applied on the Integrations & partners page, which is where you connect Utterbond. Below Precise, the Utterbond card offers Upgrade to Precise instead of Connect.

Order processing does not check your plan. If you drop below Precise with Utterbond already connected, charge dates keep syncing until you remove the token.

Removing it

Open Integrations & partners → Utterbond, click Remove connection, and confirm. Flare deletes the token and the processing-time setting, and the sync stops. Existing subscriptions keep the charge dates they already have, so delivery dates and billing cycles then run independently again.