Recharge or native Shopify subscriptions run. Klaviyo still treats subscribers like one-time buyers. They get 15% off what they already pay monthly. Skips look like churn. Dunning is a failed-payment email from the app nobody reads.
Read it once, then stop negotiating with it. Subscriptions and Recharge for DTC brands is a wiring job: events → split → coupons → dunning. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
DTC brands do not have a Subscriptions and Recharge problem because they lack Recharge + Klaviyo. They have it because subscribers get acquire coupons. One-time buyers get nothing that matches a clock.
Wire these objects first: Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock.
Then these edges, in order: Active subscriber → property/state; acquire coupons never apply · Failed renewal → dunning with a human save after N; access/shipment rules written · Skip/pause → a state, not a lost customer and not a win-back coupon · Cancelled → win-back-for-subs or churn flow, distinct from one-time lapse
Done looks like a test you can repeat: Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock.
Start here: Subscriber vs one-time is a hard split
DTC brands already have Recharge + Klaviyo. The leak is not a missing feature. Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock. Then connect these edges, in order: Active subscriber → property/state; acquire coupons never apply · Failed renewal → dunning with a human save after N; access/shipment rules written · Skip/pause → a state, not a lost customer and not a win-back coupon · Cancelled → win-back-for-subs or churn flow, distinct from one-time lapse. If you skip an edge, the next one is decoration. If you add a Recharge + Klaviyo feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock. How you know it worked on the board: Subscriber flag is true (used in every campaign filter). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Subscriber vs one-time is a hard split An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: subscribers get acquire coupons, one-time buyers get nothing that matches a clock — split the objects. Subscriber vs one-time is hard. Dunning has a human save. Skip/pause is a state. Do not send 15% off to paying subscribers.
Operator
You already feel subscribers get acquire coupons. one-time buyers get nothing that matches a clock. Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Protect one sequence for 90 days. The four moves are events → split → coupons → dunning. The edges are Active subscriber → property/state; acquire coupons never apply then Failed renewal → dunning with a human save after N; access/shipment rules written. Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy.
CEO
This is a money leak, not a preference about tools. Recharge or native Shopify subscriptions run. Until subscriber flag is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Active subscriber → property/state; acquire coupons never apply.
Before
Tuesday. Someone among DTC brands. Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Recharge + Klaviyo is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy. Active subscriber → property/state; acquire coupons never apply The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in DTC brands already paid for Recharge + Klaviyo. Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Subscriber vs one-time is a hard split. Prove write-in: Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock. This week is one move: Subscriber vs one-time is a hard split If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Recharge or native Shopify subscriptions run. Klaviyo still treats subscribers like one-time buyers. They get 15% off what they already pay monthly. Skips look like churn. Dunning is a failed-payment email from the app nobody reads.
The system
Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy.
Verify the events: subscription created, skipped, paused, cancelled, charge failed. Map each to a profile property. Then exclusions: subscribers out of first-order discounts and out of win-back that assumes they left.
Dunning: email/SMS on fail, a retry window, a human task if they reply 'cancel.' Access or next box follows the rule you wrote — not a surprise on the doorstep.
Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy.
Subscribers get acquire coupons; one-time buyers get nothing that matches a clock — that is two missing wires. Subscriber vs one-time is a hard split. Dunning has a human save path. Skip/pause is a state, not a lost customer, and acquire coupons never hit paying subscribers. Recharge (or equivalent) is the billing truth; Klaviyo must read those properties or it will lie.
Wire subscription events: created, paused, skipped, cancelled, charged, failed. Each updates the profile. Flows: onboarding for new subs (different from one-time post-purchase), dunning, cancellation save, skip reminder. Campaigns exclude active subs from first-order discounts. One-time replenish remains for people not on sub. Do not mash them.
Two databases: Recharge portal emails and Klaviyo both dunning, plus Shopify notifications. Pick owners per job. The intern creates, pauses, and cancels a test sub. They do not plan a 'subscriber VIP brand moment' until exclusions are true. A VIP moment that is a coupon is still an acquire coupon. Paying people notice.
Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock.
Active subscriber → property/state; acquire coupons never apply
Failed renewal → dunning with a human save after N; access/shipment rules written
Skip/pause → a state, not a lost customer and not a win-back coupon
Cancelled → win-back-for-subs or churn flow, distinct from one-time lapse
Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock.
Day one: subscribers get acquire coupons, one-time buyers get nothing that matches a clock — split the objects. Subscriber vs one-time is hard. Dunning has a human save. Skip/pause is a state. Do not send 15% off to paying subscribers.
Created, skipped, paused, cancelled, failed. Mapped.
Subscriber vs one-time. Hard suppressions.
Acquire discounts never hit active subscribers.
Finite path plus a human on reply.
On one line, for DTC brands: Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Created, skipped, paused, cancelled, failed. Mapped. Then wire: Active subscriber → property/state; acquire coupons never apply
Why: DTC brands cannot skip this edge. Subscribers get acquire coupons; one-time buyers get nothing that matches a clock — that is two missing wires. If it is not true, Recharge + Klaviyo is already a second database.
Done when: Active subscriber → property/state; acquire coupons never apply is true on a test.
Subscriber vs one-time. Hard suppressions. Then wire: Failed renewal → dunning with a human save after N; access/shipment rules written
Why: DTC brands skip this and the leak returns as a private language. Wire subscription events: created, paused, skipped, cancelled, charged, failed. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Failed renewal → dunning with a human save after N; access/shipment rules written is true on a test.
Acquire discounts never hit active subscribers. Then wire: Skip/pause → a state, not a lost customer and not a win-back coupon
Why: DTC brands feel this as Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Two databases: Recharge portal emails and Klaviyo both dunning, plus Shopify notifications.
Done when: Skip/pause → a state, not a lost customer and not a win-back coupon is true on a test.
Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Subscriber flag (Used in every campaign filter), then failed charge (Not one app email). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Subscriber vs one-time is a hard split
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock.
If objects aren't named, software invents a second database.
Subscribers get acquire coupons. One-time buyers get nothing that matches a clock.
Created, skipped, paused, cancelled, failed. Mapped. Then wire: Active subscriber → property/state; acquire coupons never apply
DTC brands cannot skip this edge. Subscribers get acquire coupons; one-time buyers get nothing that matches a clock — that is two missing wires. If it is not true, Recharge + Klaviyo is already a second database.
On Recharge + Klaviyo, this means the data model matches how DTC brands actually work — not the snapshot demo. Edge: Failed renewal → dunning with a human save after N; access/shipment rules written
Subscriber vs one-time. Hard suppressions. Then wire: Failed renewal → dunning with a human save after N; access/shipment rules written
DTC brands skip this and the leak returns as a private language. Wire subscription events: created, paused, skipped, cancelled, charged, failed. Spec tags, fields, and states have to be the same objects the next workflow will read.
Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy.
Acquire discounts never hit active subscribers. Then wire: Skip/pause → a state, not a lost customer and not a win-back coupon
DTC brands feel this as Subscribers get acquire coupons. One-time buyers get nothing that matches a clock. Two databases: Recharge portal emails and Klaviyo both dunning, plus Shopify notifications.
Subscriber vs one-time is a hard split
Because the login already exists. Recharge or native Shopify subscriptions run. Klaviyo still treats subscribers like one-time buyers. A new feature on a missing spec is a second database. Finish this edge first: Active subscriber → property/state; acquire coupons never apply.
Day one: subscribers get acquire coupons, one-time buyers get nothing that matches a clock — split the objects. Subscriber vs one-time is hard. Dunning has a human save. Skip/pause is a state. Do not send 15% off to paying subscribers. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Skip ≠ churn (Skip is a state) is how you stop the leak returning dressed as a new feature. If Placed Order is dirty, every metric is theatre. If browse collides with cart, you trained people to ignore you. Discount-first abandon trains the wrong buyer — especially when consideration is long. Score the system. Then ship the two worst gaps. Not another brand story.
More leads into a leak is a more expensive leak. Subscriber vs one-time is a hard split. Acquire coupons never hit paying subscribers. Skip and pause are states. Dunning is a finite path with a human if they reply. Placed Order and subscription events must both be trustworthy. Watch subscriber flag before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Subscriber vs one-time is a hard split That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Recharge + Klaviyo is “set up”.
Do this
Recharge (or Shopify subscriptions) subscriber vs one-time, dunning, skip/pause states, Klaviyo profile properties, acquire-coupon exclusion, billing clock.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Active subscriber → property/state; acquire coupons never apply
Skip this
Calling it done because a screenshot looks busy.
Do this
Create a test subscription. Confirm Klaviyo knows they are a subscriber and a coupon campaign cannot include them. Pause; confirm state. Fail a renewal if you can; confirm dunning. One-time buyers should still get a clock that is not the subscriber clock.
Skip this
Leaving “Dunning” to chance.
Do this
Finite path plus a human on reply.
The usual miss
Calling Recharge + Klaviyo “set up” because someone logged in and imported a snapshot.
Do this instead
Created, skipped, paused, cancelled, failed. Mapped. Then prove write-in: Create a test subscription.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Active subscriber → property/state; acquire coupons never apply first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Subscriber flag: True. Used in every campaign filter. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Subscriber flag
True
Used in every campaign filter
Failed charge
A path
Not one app email
Skip ≠ churn
Yes
Skip is a state
This week
Subscriber vs one-time is a hard split
Subscriber vs one-time is a hard split
Dunning has a human save path
Skip/pause is a state, not a lost customer
Acquire coupons never hit paying subscribers
Want the longer lesson, not the page for this niche? Replenishment is a clock ↗
Working notes
Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Subscriptions and Recharge does not split by niche and city. The wiring is the same: objects, edges, one test conversion. Read a connect map if two tools are already in the stack, or a vertical essay if the language needs to change.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗Revenue per recipient on flows is the number. Open rate is a meeting.
Read ↗If Placed Order is dirty, every flow metric is theatre. Fix the event before the subject line.
Read ↗Returns and second purchase are different states. Mailing a returner like a VIP is how you look careless.
Read ↗Email and WhatsApp stay open. A call is for installing the system.