---
name: "skill-lifecycle"
type: skill
description: Reach's procedure for the automated flows that turn a first buyer into a repeat one — the standard flow set (welcome, browse, cart and checkout abandonment, post-purchase from confirmed to review ask, replenishment and cross-sell, win-back, VIP thank-you, back-in-stock, anniversary where data exists), each with trigger, timing, message intent and KPI, mapped to the Shopify surface that runs it (Flow, Email, Inbox, customer segments, or a named app), with the human-action boundary stated. Segmentation basics and measurement through skill-campaign-report, email revenue share as the headline. Use when a retail venture has customers to retain, a lifecycle gap is found, or playbook-store-launch reaches the flows step. Retail on Shopify is the drafted mode; app activation and reader nurture reuse the loop with their own surfaces. Drafts and stages; the operator activates. Promoted from placeholder under APP-1080 / APP-1087; first full draft 2026-09-04.
license: CC BY-NC-SA 4.0
---

# lifecycle

Reach's retention skill. Repeat rate is step 8 of the `convention-retail` touchpoint chain — the step everything else exists for — and email revenue share is the owned channel's measure; this skill builds the automated flows that move both, on Shopify's native tooling first (Shopify Flow, Shopify Email, Shopify Inbox), routing to Klaviyo only when a venture outgrows them. It reads `convention-retail` for the chain and KPI vocabulary, `convention-shopify` for the store, the queries and the human-action boundary, and the venture's `convention-brand` voice reference for every word; it restates none of them. Copy is drafted through `skill-content-studio`, visuals through Pixel, setup staged through `skill-channel-ops`, measurement through `skill-campaign-report`. Promoted from placeholder under APP-1087; first full draft 2026-09-04.

## Trigger

- A retail venture has customers to retain, or a lifecycle gap is found: no post-purchase sequence, an abandonment flow missing, a review ask that never fires.
- `playbook-store-launch` reaches the flows step (Keroma first, the BARA relaunch second).
- `skill-campaign-report` reads repeat rate or email revenue share below target, or a flow's revenue against baseline has fallen.
- A new segment or product line needs a flow the standard set does not cover.

Run by Reach for the vertical's operator. The retail mode below is the drafted one; for the apps (activation) and Mr Pritchard (reader nurture) the same loop runs with the domain's own surfaces and KPI tree.

## Behaviour

Five steps.

### Step 1 — Read the picture

Read the KPI baseline through `convention-shopify`'s queries — repeat-customer rate, orders and AOV, channel mix for the email share — and the customer data the store holds (consent state, order history, days since last order). Read the venture's voice reference (`bara.voice-reference`; Keroma's once its brand instance exists, and until then say the voice is unset rather than inventing one) and its discount posture from `skill-retail-strategy`. Read the arrival narrative from `skill-packaging-unboxing` where one exists, so the post-purchase flow mirrors the parcel. Mark each input known or assumed; a store with no orders has almost everything assumed.

### Step 2 — Map the flows against the standard set

Audit the store against the standard flow set below: which exist, which fire, which are missing. The gap list, in order of the KPI each moves, is the brief.

### Step 3 — Design each flow

For every flow in scope, specify trigger, timing, message intent, the KPI it moves, the Shopify surface that runs it and the segment it needs. Sequence steps within a flow with an exit condition (a purchase ends an abandonment flow; a reply ends a win-back). Working rule: no customer receives more than two automated messages in a week across all flows; a flow that would breach that yields to the one closer to a purchase.

### Step 4 — Draft, stage, hand over

Brief copy per message to `skill-content-studio` against the voice reference, one message and one action each; brief visuals to Pixel. Build the segments through `skill-channel-ops` on the Shopify connector. The flows themselves are a different case, and this is the step where that matters: the Shopify surfaces most of this set runs on — Shopify Email, Shopify Flow, and the native popup and signup form the welcome flow is fed by — are Admin-only, with no Admin API and so no connector tool that can stage them at all (`convention-shopify`, *The connector-vs-theme split*, the third surface). So a run does not attempt a connector stage for those and does not report one: it produces the packed artefact — per message, the audience, the timing, the copy, the exit condition and any discount, ready to be entered — and names the Admin route that will enter it, with the audience, the timing and any discount shown for the operator. The operator activates. Where a flow needs a third-party app (reviews, back-in-stock, SMS), name the app and what it needs installed as a config action for the operator; never assume it is there.

**Which flows this bites, and what the ticket state is (APP-1641).** Every row of the standard flow set whose *Runs on* column names Shopify Email, Shopify Flow or Shopify's native abandoned-checkout recovery is in this class, as is the email-capture popup or signup form that feeds the welcome flow. The segments are not: Shopify customer segments are connector-reachable and are built, not packed. A ticket in this class is **not Blocked** — nothing upstream will ever clear it, so a run that parks it there is waiting on nothing (`convention-shopify`, *Human-action boundary*). It is a packed artefact plus a named Admin route — the browser-driven route in the Owner's own signed-in Admin session, under that convention's three conditions, or the operator by hand — recorded on the ticket as the action taken. The surface list and those conditions live in `convention-shopify` and are not copied here, so there is one place to correct if Shopify ever ships an API for them. (Worked case: MBN-254, 2026-09-22 — a `skill-dispatch-run` leg on this skill followed the unqualified Step 4 line onto the connector, re-derived the absence from the connector's tool list and Shopify's docs, and went Blocked rather than fabricate a live flow. MBN-293 — welcome, abandoned checkout, post-purchase, review ask and win-back, all stated as built on Shopify Email and Shopify Flow — is the next ticket in the same shape. *Recorded as reported, not observed: this is APP-1641's account and is not verifiable from a read-only refine pass without Shopify Admin access.*)

### Step 5 — Measure and iterate

Each flow reports revenue and conversion against its baseline through `skill-campaign-report` — flow revenue, open and click as leading indicators, the KPI it was designed to move as the verdict — and email revenue share as the headline for the set. One change per flow per read, so the effect is attributable. A flow that moves nothing over a full read window is paused, not padded.

## The standard flow set

| Flow | Trigger and timing | Message intent | KPI | Runs on |
| -- | -- | -- | -- | -- |
| **Welcome** | Sign-up without purchase; send at once, then two more over ten days. | Who the brand is, the maker story, one path into the range. A first-purchase incentive only where the discount posture allows one. | Sign-up to first order | Shopify Email, segment: subscribed, no orders |
| **Browse abandonment** | Product viewed, no cart, identified customer; one message after 24 hours. | The product seen, its detail and scale, no pressure. | Session to order | Shopify Flow trigger plus Shopify Email; needs an app on some plans |
| **Cart abandonment** | Cart created, no checkout; 1 hour, then 24 hours. | The cart, delivery terms, the returns route; no discount by default. | Cart to checkout | Shopify Email abandoned-cart automation |
| **Checkout abandonment** | Checkout started, not completed; 1 hour, then 24 hours. | The one thing that stops the purchase — cost, delivery, doubt — answered. | Checkout to order | Shopify's native abandoned-checkout recovery |
| **Post-purchase** | Order placed; confirmed → shipped → delivered → care and use (delivered plus 3 days) → review ask (delivered plus 10 days, or plus 14 for ceramics in use). | Keep the promise in the brand voice; the care card's content again; the review ask as an invitation with a route. Mirrors the `skill-packaging-unboxing` narrative. | Review rate, repeat rate | Shopify order notifications (voice-edited), Shopify Flow for the delivered timings, Shopify Email; a reviews app for the ask |
| **Replenishment and cross-sell** | Days since order equal to the product's re-order interval, or a goes-with line exists. | The pair to what they bought; the refill where the line is consumable. | Repeat rate, AOV | Shopify Flow, segment: product-affinity |
| **Win-back** | Lapsed: no order for a stated window (working rule: 120 days for homeware, 90 for apparel). Two messages, three weeks apart. | What is new since they last bought; a reason to return that is not a discount. | Lapsed to repeat | Shopify Email, segment: lapsed |
| **VIP and repeat thank-you** | Second order, and each order above the high-AOV threshold. | A thank-you in the voice, early access to a drop where the calendar has one. | Repeat rate, LTV | Shopify Flow tag plus Shopify Email, segment: repeat, high-AOV |
| **Back in stock** | A sold-out line restocked; customer opted in on the product page. | The line is back; the drop window if dated. | Restock sell-through | A back-in-stock app; Shopify Inbox for direct asks |
| **Anniversary** | Birthday or first-order anniversary, where the data exists and was given for the purpose. | A small on-voice note; never a discount by default. | Repeat rate | Shopify Email, segment by date field |

Timings are working rules per venture; the operator can strike any of them.

## Segments

Built as Shopify customer segments, named plainly: **first-time** (one order), **repeat** (two or more), **high-AOV** (above the live AOV by a stated margin), **lapsed** (days since last order past the window above), **product-affinity** (bought from a named collection), **subscribed, no orders**. Segments are the flow audiences; a flow with no segment is sent to nobody.

## Human-action boundary

Per `convention-shopify`: sending to a full list, activating a flow that spends margin (any incentive), and installing or paying for an app are the operator's. This skill drafts, builds segments, stages flows paused, and hands over with everything prepared. Consent is read from the store; a contact who has not consented to marketing receives transactional messages only.

## Reads and feeds

Reads: `convention-retail`, `convention-shopify`, the venture's `convention-brand` voice reference, `skill-retail-strategy` (discount posture, calendar), `skill-packaging-unboxing` (the arrival narrative), live customer and order data. Feeds: `skill-content-studio` (copy briefs), Pixel (visual briefs), `skill-channel-ops` (setup), `skill-campaign-report` (measurement), `skill-newsletter-strategy` (the editorial channel the flows hand a customer to once they are engaged).

## Guardrails

- Respect consent and frequency; retention that becomes fatigue is a failure. The weekly cap holds across all flows.
- Every flow earns its place against a KPI in `convention-retail` vocabulary, reported against baseline.
- Discounts follow the venture's discount posture; manufactured urgency is off-voice for BARA and the default exclusion here.
- Copy, visuals and setup are deferred to their skills; this skill designs and sequences.
- Stages, never activates; never sends to a full list; never installs an app.
- Never invents a voice; an unset voice is stated as unset.
- Propose-only.

## Setup

Run on demand by Reach from an operator brief, a `playbook-store-launch` step or a `skill-campaign-report` finding; revisited each retail-calendar window. Connectors: Shopify (through `skill-channel-ops` for writes, read-only here) and Linear. On finish, run skill-ops-retro capture on this run's friction: **search the Pulse queue first and add the evidence to a same-root note if one exists, otherwise file a new FRICTION note** for the drain pass to assess, in capture step 3's literal shape — team Apps, project os.Claude, `FRICTION:` title, labels `task` + `work:configuration` + `PUL-5E`, Backlog, unassigned — filing the friction, never the run report.

Owned by Reach (R3-ACH).
