Intern
What you actually do
Day one: write the truth about shipping (what you can actually say). Write when use is plausible. Ban day-0 review. Map the second purchase. Do not clone a 'best of Klaviyo' flow that lies about delivery.
Library / DTC brands / Post-purchase system
Home décor has long consideration. Flows have to respect that without going quiet.
Read it once, then stop negotiating with it. Post-purchase system for home décor brands is a wiring job: truth → use → second order → review. 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.
Home décor brands do not have a Post-purchase system problem because they lack Shopify + Klaviyo. They have it because the order confirmation is the whole relationship.
Wire these objects first: Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them.
Then these edges, in order: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status · Delivered (or time proxy) → use/care; review ask only after use is plausible · Second-purchase → attach/replenish path with exclusions for what they already own · Refunded → exit post-purchase; do not ask for a review on a returned order
Done looks like a test you can repeat: Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule.
Start here: Cart timing matches AOV. Proof before coupon. Browse does not clone cart.
Home décor brands already have Shopify + Klaviyo. The leak is not a missing feature. The order confirmation is the whole relationship. 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: Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them. Then connect these edges, in order: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status · Delivered (or time proxy) → use/care; review ask only after use is plausible · Second-purchase → attach/replenish path with exclusions for what they already own · Refunded → exit post-purchase; do not ask for a review on a returned order. If you skip an edge, the next one is decoration. If you add a Shopify + Klaviyo feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule. How you know it worked on the board: Second purchase is the conversion (buyer → customer). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Cart timing matches AOV. Proof before coupon. Browse does not clone cart. An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: write the truth about shipping (what you can actually say). Write when use is plausible. Ban day-0 review. Map the second purchase. Do not clone a 'best of Klaviyo' flow that lies about delivery.
Operator
You already feel the order confirmation is the whole relationship. Home décor has long consideration. Flows have to respect that without going quiet. Protect one sequence for 90 days. The four moves are truth → use → second order → review. The edges are Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status then Delivered (or time proxy) → use/care; review ask only after use is plausible. Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait.
CEO
This is a money leak, not a preference about tools. The order confirmation is the whole relationship. Until second purchase is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status.
Before
Tuesday. Someone among home décor brands. Home décor has long consideration. Flows have to respect that without going quiet. Shopify + 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. Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait. Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in home décor brands already paid for Shopify + Klaviyo. Home décor has long consideration. Flows have to respect that without going quiet. 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. Truth, then use, then second purchase, then review — in that order. Prove write-in: Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule. This week is one move: Cart timing matches AOV. Proof before coupon. Browse does not clone cart. If that feels too small, that is the point. Operators fail by starting at move four.
The leak
The order confirmation is the whole relationship. Review ask on day zero. Upsell before the box arrives. Shipping lies. The second purchase is left to a newsletter.
The system
Truth, then use, then second purchase, then review — in that order. Post-purchase exists to make a customer, not to harvest a star while the truck is still moving.
If shipping emails lie, retention work starts underwater. Tell the truth about the window. Then teach use — especially when the product has a protocol, a fit issue, or a replenishment clock. The second purchase is the conversion that turns a buyer into a customer.
Reviews after they have used it. Asking on day zero trains people to ignore you and gives you reviews from people who have not opened the box. Attach-rate and replenishment are flow jobs, not a Thursday campaign.
Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait.
The order confirmation is the whole relationship when post-purchase is not a flow. Shipping truth must match operations — if you cannot say the date, do not invent one. Use and care exist so the product works. Second purchase path is obvious and timed after delivery, not in the confirmation. Reviews are earned after use, not begged on day 0. Refunds exit the flow. That is the object graph: order, fulfillment state, profile properties, exclusions.
Wire fulfillment events if Shopify provides them; otherwise time delays that match your real SLA, labeled as estimates. Cross-sell exclusions: they should not be pitched the unit they own. Subscribers (if any) get a different post-purchase than one-time. Campaigns during this window should not scream acquire coupons at people who just paid full price.
Two databases: Shopify notification emails and Klaviyo post-purchase both firing, plus a review tool that also emails on day 0. Pick one owner per job. The intern places an order and lists every email from every system that day. Duplicates are bugs. Kill until one voice owns shipping, one owns care, one owns review.
Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them.
Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status
Delivered (or time proxy) → use/care; review ask only after use is plausible
Second-purchase → attach/replenish path with exclusions for what they already own
Refunded → exit post-purchase; do not ask for a review on a returned order
Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule.
Day one: write the truth about shipping (what you can actually say). Write when use is plausible. Ban day-0 review. Map the second purchase. Do not clone a 'best of Klaviyo' flow that lies about delivery.
Shipping window in the emails. No theatre.
Care, fit, protocol — timed after they have the thing.
Obvious next SKU or replenishment clock.
After use. Earned. Not begged at checkout panic.
On one line, for home décor brands: The order confirmation is the whole relationship. 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.
Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Shipping window in the emails. No theatre. Then wire: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status
Why: Home décor brands cannot skip this edge. The order confirmation is the whole relationship when post-purchase is not a flow. If it is not true, Shopify + Klaviyo is already a second database.
Done when: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status is true on a test.
Care, fit, protocol — timed after they have the thing. Then wire: Delivered (or time proxy) → use/care; review ask only after use is plausible
Why: Home décor brands skip this and the leak returns as a private language. Wire fulfillment events if Shopify provides them; otherwise time delays that match your real SLA, labeled as estimates. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Delivered (or time proxy) → use/care; review ask only after use is plausible is true on a test.
Obvious next SKU or replenishment clock. Then wire: Second-purchase → attach/replenish path with exclusions for what they already own
Why: Home décor brands feel this as the order confirmation is the whole relationship. Two databases: Shopify notification emails and Klaviyo post-purchase both firing, plus a review tool that also emails on day 0.
Done when: Second-purchase → attach/replenish path with exclusions for what they already own is true on a test.
Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Second purchase (Buyer → customer), then shipping truth (Lies kill the next order). 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.
Cart timing matches AOV. Proof before coupon. Browse does not clone cart.
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.
Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them.
If objects aren't named, software invents a second database.
Home décor has long consideration. Flows have to respect that without going quiet.
Shipping window in the emails. No theatre. Then wire: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status
Home décor brands cannot skip this edge. The order confirmation is the whole relationship when post-purchase is not a flow. If it is not true, Shopify + Klaviyo is already a second database.
On Shopify + Klaviyo, this means the data model matches how home décor brands actually work — not the snapshot demo. Edge: Delivered (or time proxy) → use/care; review ask only after use is plausible
Care, fit, protocol — timed after they have the thing. Then wire: Delivered (or time proxy) → use/care; review ask only after use is plausible
Home décor brands skip this and the leak returns as a private language. Wire fulfillment events if Shopify provides them; otherwise time delays that match your real SLA, labeled as estimates. Spec tags, fields, and states have to be the same objects the next workflow will read.
Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait.
Obvious next SKU or replenishment clock. Then wire: Second-purchase → attach/replenish path with exclusions for what they already own
Home décor brands feel this as the order confirmation is the whole relationship. Two databases: Shopify notification emails and Klaviyo post-purchase both firing, plus a review tool that also emails on day 0.
cart timing matches AOV. Proof before coupon. Browse does not clone cart.
Because the login already exists. The order confirmation is the whole relationship. Review ask on day zero. A new feature on a missing spec is a second database. Finish this edge first: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status.
Day one: write the truth about shipping (what you can actually say). Write when use is plausible. Ban day-0 review. Map the second purchase. Do not clone a 'best of Klaviyo' flow that lies about delivery. 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. Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule. 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. Review timing (Not day zero) 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. Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait. Watch second purchase 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. Cart timing matches AOV. Proof before coupon. Browse does not clone cart. That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Shopify + Klaviyo is “set up”.
Do this
Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status
Skip this
Calling it done because a screenshot looks busy.
Do this
Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule.
Skip this
Leaving “Review” to chance.
Do this
After use. Earned. Not begged at checkout panic.
The usual miss
Calling Shopify + Klaviyo “set up” because someone logged in and imported a snapshot.
Do this instead
Shipping window in the emails. No theatre. Then prove write-in: Place a $1 order.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status 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
Second purchase: The conversion. Buyer → customer. 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.
Second purchase
The conversion
Buyer → customer
Shipping truth
Required
Lies kill the next order
Review timing
After use
Not day zero
This week
cart timing matches AOV. Proof before coupon. Browse does not clone cart.
US operators · Monday reviews, US-friendly hours. The spine is the same — the clock is not.
Shipping truth is in the emails
Use and care exist
Second purchase path is obvious
Reviews are earned, not begged on day 0
Want the longer lesson, not the page for this niche? Post-purchase has an order of operations ↗
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.
Home décor brands do not have a Post-purchase system problem because they lack Shopify + Klaviyo. They have it because the order confirmation is the whole relationship. Wire these objects first: Placed Order flow, shipping-truth emails, use-and-care, second-purchase path, review ask (not day 0), profile, Shopify fulfillment events if you have them. Then these edges, in order: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status · Delivered (or time proxy) → use/care; review ask only after use is plausible · Second-purchase → attach/replenish path with exclusions for what they already own · Refunded → exit post-purchase; do not ask for a review on a returned order Done looks like a test you can repeat: Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule. Start here: Cart timing matches AOV. Proof before coupon. Browse does not clone cart.
The order confirmation is the whole relationship. Review ask on day zero. Upsell before the box arrives. Shipping lies. The second purchase is left to a newsletter. Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait.
Before: Tuesday. Someone among home décor brands. Home décor has long consideration. Flows have to respect that without going quiet. Shopify + 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. Discount-first abandon on a high-consideration cart trains the wrong buyer and trains the right one to wait. Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status The next move is written. That is the difference between a login and a system.
Leaving objects unnamed because Shopify + Klaviyo is “set up”. Building a workflow or flow before a writer lands on one contact. Do the four moves instead: truth → use → second order → review.
Second purchase: The conversion — Buyer → customer. Then shipping truth (Lies kill the next order). If those are folklore, do not add another Shopify + Klaviyo workflow.
cart timing matches AOV. Proof before coupon. Browse does not clone cart.
Because the login already exists. The order confirmation is the whole relationship. Review ask on day zero. A new feature on a missing spec is a second database. Finish this edge first: Placed Order → confirmation/shipping truth from the flow, aligned with Shopify status.
Day one: write the truth about shipping (what you can actually say). Write when use is plausible. Ban day-0 review. Map the second purchase. Do not clone a 'best of Klaviyo' flow that lies about delivery. 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. Place a $1 order. Watch the sequence against the fake shipping you can trigger (or time delays). Confirm you do not ask for a review on day 0. Confirm a refunded test exits. Second-purchase email must not recommend the same SKU they just bought if that is your rule. 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.
Posts go live. Search still does not know you.
Read ↗GSC and GA4 sit in silos. Nobody sequences the work.
Read ↗Roadmaps are annual. Execution is weekly panic.
Read ↗You have access. You do not have a Monday ritual.
Read ↗You write better emails into a worse inbox.
Read ↗Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.