Supplements · Repeat and claims
MixedSupplements & wellnessRepeat orders and careful claims for supplement brands
A supplement brand lives on the second and third order, and it can lose everything on one careless claim. Here is how to time refill reminders to the pack, and check every ad, product page and generated creative before it goes live.
Valnora & Elric team5 min read
Supplement economics are simple and unforgiving. The first order often barely pays for the ad that brought it. The brand makes money when a customer finishes a 30-day pack and orders again, and again. At the same time, supplements sit close to health, and one product page that promises to "cure" something can create far more trouble than a month of revenue is worth.
Those two jobs, earning the repeat order and saying only what you can back up, are both about timing and checking. Both suit a workspace where workflows, tables, rules and a policy library live together.
Remind people when they are about to run out
A generic "we miss you" email on day 45 arrives after the customer has already bought something else at the pharmacy. A reminder that lands on day 25 of a 30-day pack, when the bottle is visibly low, is useful.
The setup in Agent Serve is small. A Shopify orders webhook points at the Webhook trigger of a workflow in the workflow builder. The workflow writes each line item to a refills table in Tables with the SKU, servings per pack, suggested daily use and order date, and works out the expected run-out date. A 60-capsule pack at two a day runs out on day 30; a 90-serving powder at one scoop a day on day 90.
A daily Schedule trigger finds customers about five days from run-out who opted in to WhatsApp, and sends an approved template with Send Template: Reorder, Remind me in a week, Stop reminders. Replies arrive through the WhatsApp trigger. "Stop" removes them for good, and the record says so.
What the solution produces
Refill reminder on WhatsApp (illustrative)
MessageHi Meera, your 60-capsule Magnesium Glycinate from Tula Wellness should last about five more days.
Reorder now and it arrives before you run out.
[Reorder] [Remind me in a week] [Stop reminders]
Claims check on a product page draft (illustrative)
Record- Asset
- Shopify product page · Ashwagandha KSM-66, 60 capsules
- Flagged line
- "Clinically proven to cure anxiety and insomnia."
- Why
- Disease and cure wording. Not on the approved-claims list.
- Closest approved claim
- "Supports a sense of calm", substantiation file ASH-03
- Suggested rewrite
- "Formulated with KSM-66 ashwagandha to support a sense of calm."
- Status
- Sent to regulatory reviewer. Not published.
If the customer already reordered, or holds an active subscription in Stripe, the workflow skips them. For brands selling subscriptions through Stripe, the Stripe block reads subscription status; a cancelled subscription can start a gentler follow-up asking whether the product worked for them, routed to a person if the answer is a complaint.
Count what repeat really looks like
The refills table feeds a dashboard with reminder-to-reorder rate by SKU and pack size, days between orders, and opt-outs. A 30-day pack whose customers reorder on day 38 on average is telling you something about dosage habits, and maybe that a 45-day pack would suit them better.
Check claims before anything goes live
The second half is less about growth and more about not causing harm.
Start with what your regulatory team has already decided. Put the approved-claims list in the Knowledge Base: each claim, the exact wording allowed, the products it applies to, and a pointer to the evidence behind it. Then write rules in plain language:
- Flag any wording that suggests the product treats, cures, prevents or diagnoses a disease.
- Flag "clinically proven", "guaranteed" or numbers such as "lose 5 kg" unless that exact claim is on the approved list.
- Flag any claim about a product that the approved list does not tie to that product.
A claims-check workflow runs on every piece of copy before it goes live: ad copy, Shopify product descriptions read with the Shopify block, Instagram captions, and the prompts and on-image text behind creative generated in Chat. Each flagged line comes back with the reason and the closest approved claim. Nothing is published by the check itself; a person publishes after review.
Where the rules come from is not our call
In the US, the FTC’s Health Products Compliance Guidance explains its expectation that health claims are backed by competent and reliable scientific evidence. In India, the Food Safety and Standards (Advertising and Claims) Regulations, 2018 set out how food and supplement claims may be made. Other markets have their own rules.
Agent Serve does not interpret any of them. The rules and the approved list are what your regulatory or legal team writes; the workflow applies them consistently, on every asset, every time. When the check and your reviewer disagree, the reviewer wins and the rule gets updated.
Keeping it honest
Controls and governance
Run logs
Every workflow run records each block’s inputs, outputs and errors, so a reviewer can trace how a result was reached.
Deployed versions
Workflows run from a deployed version, so a change is reviewed before it reaches production runs.
Roles and permission groups
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Audit trail
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
PII detection
A Guardrails block detects personal data and blocks or masks it before text reaches the next step.
More on how Agent Serve handles access, data and audit on the security page.
Run logs record each check, so you can show which version of a product page was reviewed and when. Workflows run from a deployed version, so a change to the claim rules is itself reviewed.
What you need
- Servings per pack and suggested daily use for every SKU
- WhatsApp opt-in recorded at checkout, and an approved reminder template
- An approved-claims list with the substantiation behind each claim, agreed with your regulatory team
- A short list of wording you never use, such as cure, treat, prevent or guaranteed results
- A named reviewer who signs off flagged copy
- Shopify app token to read products and orders
Questions teams ask
Does the claims check tell us what is legal?
No. It compares copy with the claims your regulatory team has approved and flags wording that needs their review. It is not legal or regulatory advice, and a person decides.
Can it check text inside generated images and videos?
It can check the prompt, the caption and any on-image text you write. Treat the final asset as needing a person’s look before publishing, as with any creative.
We sell subscriptions through Stripe. Can we see them?
Yes. The Stripe block reads customers and subscriptions, so the same workflow can skip reminders for active subscribers and follow up on cancelled ones.
Refills on time, claims checked before publishing
Workflow · Refill reminders
- 01Shopify order webhookEach order is written to a refills table with SKU, servings and order date.
- 02Refills tableExpected run-out date per customer and SKU, from servings per day.
- 03Daily scheduleFinds customers about five days from running out who opted in.
- 04WhatsApp reminderTemplate with Reorder and Not now buttons and a cart link.
Workflow · Claims check
- 05Copy to checkAd copy, Shopify product descriptions, captions and text in generated creative.
- 06Approved claimsYour approved-claims list and substantiation notes in the Knowledge Base.
- 07Claim rulesFlag disease, cure, guarantee and unapproved structure-function wording.
- 08Regulatory reviewFlagged copy goes to your regulatory or legal reviewer before publishing.