Skip to content

PATTERN Cited by 1 source

Phased SKU rollout for a new channel

Intent

When introducing a new sales channel (in-store → site → mobile → agentic), don't flip the switch on your entire catalog at once. Launch with a narrow, carefully-chosen SKU set, instrument the channel's conversion behaviour on that set, then expand the catalog exposure in measured increments.

Canonicalised in the 2026-03-12 Stripe retrospective: "Don't flip the switch on your entire catalog. One approach we've seen work is to start with a focused set of SKUs you believe will convert, so you can measure performance and watch how the channel actually behaves."

The starter-SKU selection rule

Stripe's explicit recommendation for the opening cohort: straightforward products that ship directly to the buyer's home — nothing that requires installation or complex fulfilment coordination. The rationale is that the frontend UX on new agentic surfaces is still evolving, so any SKU whose fulfilment shape exceeds basic ship-to-home carries compounding risk:

  • Installation-required SKUs need the agent to negotiate scheduling, which the UX doesn't yet support.
  • Complex-fulfilment SKUs (split shipment, inventory across locations, pickup) stress the checkout state machine and return flows before the agent UX is ready.
  • Low-friction ship-to-home SKUs converge on browser-e-commerce semantics, so they port cleanly to agentic rails.

Worked example (URBN)

URBN — parent of Anthropologie, Free People, Urban Outfitters — sells everything from plants to custom furniture. Its opening agentic-commerce deployment concentrated on dresses and denim — the lowest-friction subset of its catalog that (a) ships direct to home, (b) has size/colour variants well-modelled in its existing catalog, (c) converts reliably on existing digital channels, (d) is a high-margin bread-and-butter category the retailer has strong inventory signal on.

The rollout shape is measurement-first: watch how the channel behaves on the narrow SKU set, then decide whether to expand to adjacent categories.

Generalisation beyond commerce

The pattern shape — "start narrow, measure, expand" — is not commerce-specific. The analogous engineering patterns are the canary, staged rollout, and cohort-percentage shapes already catalogued on this wiki (patterns/staged-rollout, patterns/cohort-percentage-rollout). What distinguishes this commerce-specific variant is that the axis of narrowness is the product catalog, not the user base — the seller is learning about the channel's conversion shape rather than about a feature's stability.

Long-term expansion trajectory

Per Stripe's disclosure, the expected trajectory is:

  1. Narrow SKU set; direct-ship; known variants.
  2. Measure channel conversion and cart-abandonment shape.
  3. Expand to adjacent categories as the frontend UX matures.
  4. Over time, "agents will enable new buying experiences beyond single-item, single-business carts" — multi-vendor baskets, bundled goods, subscription flows all become tractable as the ecosystem matures.

Seen in

Last updated · 476 distilled / 1,218 read