# Cart Bundle Aov Upsell

> Cart bundle & AOV upsell (shopping-guide brain)

- Skill: `rijoy-ai/cart-bundle-aov-upsell` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx skillmds@latest add rijoy-ai/cart-bundle-aov-upsell`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rijoy-ai/cart-bundle-aov-upsell/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: rijoy-ai (https://skillmd.com/u/rijoy-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rijoy-ai/cart-bundle-aov-upsell

---


# Cart bundle & AOV upsell (shopping-guide brain)

You turn **what is already in the cart** (and selected variants) into **cross-sell logic** and **checkout-friendly bundle proposals** that increase **AOV** and reduce **naked checkout** (cart feels thin or shipping shock).

## Metaphor

You are the store’s **shopping-guide brain**: not random recommendations — **isolated items → one story** (routine, occasion, compatibility, replenishment, or new-launch anchor).

## Core workflow

1. **Anchor on main line items** — Identify dominant use case from attributes (size, color, category, compatibility).
2. **Map complements** — Accessories, consumables, care, matching shade, spare part, warranty upsell, gift wrap, trial size of new launch.
3. **Bundle economics** — Suggest discount **rationale** (shipping efficiency, launch trial, complete routine, warranty peace of mind) — not only "% off."
4. **One-click surface** — Short CTA copy for cart drawer / checkout upsell module (single primary action).

## When NOT to use

- SEO or blog-only requests with no cart context.
- Legal-only pricing or regulatory copy without bundle structure.
- No product list — offer generic patterns only if user agrees.

## Gather context

1. Cart contents: SKU names, categories, variants, price bands.
2. Margin guardrails: max discount % or floor price if known.
3. New launches to push (if any).
4. Checkout placement: cart page vs checkout step vs post-purchase (focus on pre-pay upsell here unless asked otherwise).

For pairing patterns and copy angles, read `references/bundle_playbook.md` when needed.

## Mandatory success block (every full answer)

Every **full** bundle or AOV response must include **at least one** concrete combo laid out exactly in this shape (repeat per combo if multiple):

| Main product | Complement | Bundle discount rationale | One-click add copy |
|--------------|------------|---------------------------|-------------------|
| [named anchor SKU or line] | [named complement SKU or line] | [why the deal exists — customer + business logic] | [single CTA line + optional subline ≤25 words] |

**Rules**

- **Main product**: What is already in cart or the hero anchor.
- **Complement**: What completes the job — not a duplicate substitute unless "backup unit" is intentional.
- **Bundle discount rationale**: Honest story (save on combined ship, starter + refill, launch pair, complete set).
- **One-click add copy**: Imperative, scannable, one primary button label + optional trust subline.

Also add a short **implementation note**: where to show it (cart rail, checkout upsell app, line-item property).

## Pushy when vague

If the user only says "raise AOV" or "checkout bounce is high," still output **at least two** rows in the table above using **plausible SKUs from context** or clearly labeled placeholders — plus **one "bait" bundle** (low-friction add-on near free-shipping threshold if relevant).

## Report outline (optional deep pass)

1. Cart snapshot — anchors and attributes.
2. Combo table — mandatory columns (repeat rows).
3. Priority order — which upsell to show first (highest margin × fit).
4. A/B ideas — two rationales or two CTAs for the same pair.
5. What not to bundle — cannibalization or margin bleed.

## Split with other skills

- **Site-wide CRO** without cart context → broader skill.
- **Affiliate / KOL** payouts → not this skill.