For the complete documentation index, see llms.txt. This page is also available as Markdown.

Changelog

New updates and improvements

More starting points in the welcome popup

The What do you want to do first? popup you see after installing now has two more options: referral codes and scheduled credit (birthdays, anniversaries, monthly loyalty drops). Pick either one to get a shortcut to set it up, plus a link to the docs.

Closing the popup or choosing Skip without picking anything now just closes it. Before, it showed an empty You're all set screen.

Referral codes, customer-tag rewards, and "once per customer"

Referral codes are here. Create a code for each influencer or partner under Referral codes, add the Referral Code block to your checkout, and reward everyone who uses one with store credit. It works for guest checkouts too: the code is saved on the order and the customer is tagged once the order is placed, so an abandoned checkout earns nothing.

  • Your own success message. Each code has a message shoppers see when it's accepted. It defaults to Code Successfully Applied and can be edited at any time.

  • Live estimate at checkout. The Automatic Store Credit checkout block refreshes as soon as a code is applied or removed, so shoppers see the credit their code earns before they pay.

  • One-click reward rules. Create reward rule sets up an order-value rule for a single code, or for every code at once. There's also a new Referral Reward template.

Two new options on order-value automations, useful well beyond referrals:

  • Customers with specific tags. A new eligibility option that rewards customers carrying any of the tags you list, matched exactly or by how the tag starts. Tags are read the moment the order is paid, so a tag added seconds before checkout still counts.

  • Uses per customer: Once per customer. Rewards only a customer's first qualifying order from the rule. A redelivered order can never pay the same customer twice.

See Referral codes and Order-value automations for setup and details.

Show earned store credit in your order confirmation email

Order-value automations can now attach the store credit a customer earns to their order, so you can show it in your own order confirmation email.

Turn on Show earned credit in order confirmation email on the Automatic Store Credit checkout block (Settings → Checkout → Customize → Automatic Store Credit block), then add {{ metafields.stork.credit_earned.value | money }} to your order confirmation email template in Settings → Notifications.

This isn't available for point-of-sale orders or accelerated checkout (Apple Pay, Google Pay, Shop Pay) — those customers still get Shopify's standard store credit notification, just not inside your customized email. See Cart & checkout widgets for setup and details.

Threshold automations: reliable customer recording

Activating a threshold rule records where every existing customer sits before it starts rewarding. That step could get stuck — a rule would stay on "Existing customers are still being recorded" indefinitely, and toggling it off and on didn't help. This is fixed, and the whole step is now visible:

  • The activation dialog tells you how many customers it will record before you commit.

  • Small stores finish recording during activation and show a short summary. Larger stores continue in the background, and the run now shows live progress — "recorded 800 of 3,200" — instead of sitting silent until it's done.

  • Deactivating and reactivating reliably restarts recording. Deactivating now clears the recorded baseline; reactivating re-records everyone, keeping the position of any customer already recorded. Past rewards are never reversed and no threshold is ever paid twice.

  • New: Settings → Retry seeding. If recording ever gets stuck, run it again from here — it records whoever is still missing and reports the result. No store credit is issued.

  • Recording runs are now labelled Seed or Re-seed in run history so you can tell a fresh recording from a restart.

Threshold automations: safer crediting and a clearer reward cap

Correctness and clarity work on threshold automations:

  • A threshold is now paid once, guaranteed. Stork Credit keeps its own ledger of every threshold it has rewarded a customer. If a run is interrupted after crediting but before it finishes, the next run recognises the reward as already issued and does not repeat it — overlapping or retried runs can no longer double-pay.

  • A manual "Run now" can no longer collide with a scheduled run. Each rule now runs one pass at a time.

  • "Wait before issuing credit" (holds) is now reliable. Held rewards are recorded before a customer's progress moves, are re-checked against the ledger when they are released, and are cancelled cleanly if the customer no longer exists — rather than retrying forever.

  • "Stop after" fills in automatically at 100 rewards' worth of spend and follows the threshold amount as you change it. You can lower it, but it can no longer be left blank or set above the 100-level ceiling — so the most a rule can ever issue a customer is always visible.

  • A transient error reading a customer's progress no longer over-credits them. Blank progress is re-checked before any credit is issued.

  • A failed activation backfill now retries within minutes instead of waiting for the next scheduled run.

Threshold automation guardrails

Several changes to make threshold automations harder to misconfigure:

  • Rewards ceiling is now shown. The form spells out the lifetime-spend amount at which a rule stops rewarding — including when Stop after is left blank, where a rule still tops out at 100 × its threshold amount (a $500 threshold rewards up to $50,000 spent; a $5 threshold up to $500).

  • Threshold amount and Stop after are locked while a rule is active. Customer progress is measured against them, so they can only be changed while the rule is deactivated — followed by a re-baseline.

  • Re-baseline threshold progress — a new action on the Settings page that re-records every eligible customer at their current lifetime spend without issuing credit. Use it after changing the threshold amount or cap, or if progress looks wrong.

  • Activating and deactivating a threshold rule now asks for confirmation, explaining that activation records everyone's starting point and deactivation keeps their progress.

  • Run history shows skip and failure reasons on the row — for example No thresholds crossed — without opening each run.

Show threshold progress at checkout

Threshold automations now have a checkout block, alongside the theme widget added a couple of days ago. Add Threshold Store Credit to your checkout in Settings → Checkout → Customize, and customers see how close they are to their next reward — "you're $80 away from earning $10 in store credit" — right before they pay, with an optional progress bar.

If completing the current order will cross that threshold, the block highlights it so the customer knows this purchase unlocks their reward.

This is a live estimate, the same way the existing order-value checkout widget is — see Cart & checkout widgets for how that compares to what's actually issued.

Show threshold progress on your storefront

Threshold automations now come with a widget you can add to your theme, so customers can see how close they are to their next reward instead of finding out only when the credit arrives.

Open your threshold rule and use Add a widget to your site in the right-hand column. You get a one-line "spend $80 more to earn your next $10" version and a version with a progress bar — both already filled in with your own threshold, reward and maximum, ready to paste into your theme.

Choosing a plan no longer shows an error page

Selecting a plan could end on a "Something went wrong" page instead of taking you to Shopify's approval screen. This happened whenever Shopify declined to start the subscription — a store that can only take test charges, a card or currency Shopify wouldn't accept, an existing charge it wouldn't replace, or a plan that had been changed since the page loaded.

The reason was never shown, so there was nothing to act on. Now the Plans page stays put and tells you what Shopify said, so you can fix it or contact us with something specific. Cancelling your old charge when you move to Free also no longer blocks the switch.

A rebuilt home page, a clearer Plans page, and a plan choice up front

New installs now start on the Plans page. Pick a plan before the rest of the app opens — it's step 1 of a two-step setup, and Continue on Free is a real option that keeps you on Free for as long as you like. If you already have Stork Credit installed, nothing changes: your plan is your plan, and the app opens on your home page as before.

The Plans page has been rebuilt. One Monthly / Annual switch now changes every paid plan at once and shows what annual billing saves you, each plan says plainly what it doesn't include as well as what it does, and where a plan offers a free trial the button says how long it runs and the date you'd first be charged.

The home page has been rebuilt around your plan.

  • Plan & usage (previously Plan & limits) now has a progress bar on every metered limit, and sits at the top of the page on the Free plan where your limits matter most — on a paid plan it moves to the bottom.

  • A scrolling New automation row puts every template one click away, with a badge on rule types your plan would need an upgrade for.

  • A Pro tools row shows everything the app can do beyond a basic order-value rule — reminders, external triggers, reports, exports, Flow, the checkout block and bulk import — each saying what your plan includes.

  • Your automations summarises credit issued, runs, and average credit per run over the last 30 days, above your most recently edited rules.

Shopify Flow now shows an allowance. The Flow action works on every plan, including Free, and each plan includes up to $1,000 of store credit issued through Flow per billing period. Your usage is on the home page as Flow credit issued. The allowance isn't applied automatically — going over it doesn't stop your workflows or change your bill.

Reports, credit export and external triggers are now paid features. On the Free plan these open the Plans page instead. Nothing is deleted: your reports, your trigger endpoint and its secret are all kept, and work again as soon as you upgrade.

Fixed: if Shopify declined a subscription request — which happens on development stores, and can happen when an existing charge is in a state Shopify won't replace — the Plans page showed a generic error screen. It now stays on the page and tells you what Shopify said.

Fixed: an error on any page outside the main app used to render a blank "Application Error" screen with no detail. It now shows what went wrong.

Spend Threshold is live, and Scheduled and Reports move to paid plans

Spend Threshold automations are no longer marked Coming soon — they're available now on the Grow and Pro plans. Reward loyalty as it builds by issuing credit each time a customer's lifetime spend passes another threshold.

Alongside the release, three features are now part of the paid plans:

  • Scheduled and Spend Threshold automations — on the Free plan they appear in the Add automation picker with an Upgrade to activate button. Order value automations are unchanged and still work on every plan.

  • Reports and exports — the Reports page keeps your history on Free, with Upgrade in place of the generate actions.

The Plan & limits card on your home page now shows a Reports and exports tile so you can see at a glance what your plan includes.

Rules and reports you created on a paid plan are never deleted if you move down to Free — they're just paused until you upgrade again.

Hold threshold credit until refunds have settled

Threshold automations can now wait before issuing credit, so an order that gets refunded never pays out a reward.

Turn on Wait before issuing credit on a threshold rule and choose how long to hold — in hours or days, up to 180 days. Two weeks covers most return windows.

  • When the wait is over, the customer's lifetime spend is checked again. If a refund has taken them back below the threshold, the credit is not issued and their progress is rewound so they can earn it again later.

  • A customer who passed two thresholds at once and was refunded past only one of them is paid for the one they kept.

  • Their progress moves forward as soon as they pass a threshold, so nobody is rewarded twice for the same milestone while credit is waiting — and customers who keep buying during the wait still earn their next reward normally.

  • Run history shows rewards being held, then later released, reduced, or cancelled after a refund.

Store credit expiry is still counted from the day credit is issued, so a hold never eats into a customer's expiry window.

Read the docs

Threshold automations — reward lifetime spend

Issue store credit every time a customer's lifetime spend passes another threshold — for example $10 for every $500 they spend, again at $1,000, $1,500, and so on.

  • Each threshold is rewarded exactly once, so a customer is never credited twice for the same milestone.

  • A customer who passes several thresholds in one order is rewarded for all of them — a first order of $1,200 earns $20.

  • Optionally cap the program so no further credit is issued above a chosen lifetime spend.

  • Narrow the rule to a Shopify segment or customer query to exclude wholesale or staff accounts.

When you activate a rule, existing customers are recorded at their current spend and are not given credit for thresholds they passed before the rule existed.

Read the docs

Full list of September 2026 Product Updates

We've shipped a heap of new features to Stork Credit to help merchants get ready for Black Friday, so here's a run through of our features:

  • Bulk Store Credit Import: Import store credit data directly from a CSV file.

  • Automated Store Credit Templates: Basic templates to offer cashback, spend incentives, and rewards.

  • Scheduled Automations: Query customer data to automatically send credit based on specific dates or triggers (such as customer anniversaries, birthdays, or Shopify segments like win-back and abandoned cart flows) with custom expiry dates and promotion priority settings - **NEW**.

  • Webhook URL Integration: Send store credit via third-party platforms (such as Klaviyo for reviews or help desk software) using a custom webhook URL - **NEW**.

  • Shopify Flow Triggers: Trigger store credit issuance based on events in Shopify (e.g., when a customer signs up for marketing).

  • Store Credit Export Function: Export store credit balances and lists directly out of Shopify into a CSV file - **NEW**.

  • Customizable Email Expiry Reminders: Built-in rich email editor to send scheduled, branded reminder emails to customers before their store credit expires - **NEW**.

Reports: export customers' store credit balances

Shopify's customer export leaves store credit out. The new Reports section fixes that with the Customers' Store Credit report — a CSV of every customer holding credit and their current balance, one row per currency.

How it works

  • Cover all customers with store credit, or narrow the list with a customer query (the same segment language scheduled automations use) — with a Check query button to preview the match count.

  • The finished CSV is emailed to you as an attachment and stays downloadable from the Reports page for 72 hours.

  • Watch progress in the new Report history list; stop a running report or delete old ones from there.

Available on every plan with no usage limit. Read more in Customers' Store Credit report.

Scheduled Store Credit

Store credit no longer has to wait for an order. Scheduled automations issue credit to a group of customers at a point in time — once on a set date, or on a repeating cycle.

This is the automation type for birthday and anniversary rewards, monthly loyalty drops, win-back campaigns, and one-off credit for a segment.

Available to all stores. Create one from Add automation → Scheduled.

Pick who gets credited

Choose the audience when you build the rule, and it is resolved fresh on every run — a repeating campaign automatically picks up customers who joined since last time.

  • A Shopify customer segment

  • A hand-picked list of customers

  • All customers

  • A customer query, written in Shopify's segment query language and evaluated at run time

Date-driven rewards with customer queries

Customer queries are what make anniversary rewards possible. A query like anniversary(date: 'metafields.facts.birth_date') = today resolves to whoever has a birthday today, every day the rule runs.

The form validates your query and tells you how many customers currently match before you save.

Schedule it once, or on a cycle

  • Set a start date, time, and timezone — the timezone travels with the rule, so a 09:00 run stays at 09:00 across daylight saving changes.

  • Turn on repeat to run every n days, weeks, months, or years.

  • One-shot rules deactivate themselves after running, freeing a slot against your plan's active-automation limit.

Stop rewarding the same customer every day

A daily anniversary rule would otherwise match the same customer tomorrow, and every day after. After issuing fixes that by updating the metafield that made them eligible — either clearing it, or rolling the date forward by an interval such as 12 months.

Only customers who were successfully credited are updated, so a failed credit never silently consumes its anniversary date.

Also in this release
  • Priority ordering — when several scheduled rules come due together, lower priority numbers run first. Built for tiered loyalty programs that run one rule per tier over the same customers.

  • Per-rule expiry — scheduled credit can never expire, expire after a set period, or expire on a fixed date. Relative expiry is calculated per run, so each occurrence of a repeating rule gets its own countdown.

  • Optional notifications — Shopify's store credit email is sent by default and can be turned off per rule for silent top-ups.

  • Run history — every execution records how many customers were resolved, credited, and failed, with per-customer failures in the run log.

  • Safety ceiling — a run credits at most 10,000 customers. Above that the run stops without crediting anyone, rather than silently rewarding a subset.