retailer-jbp-and-line-review
This skill helps CPG and brand teams prepare for retail buyer conversations by building category stories, analyzing promotions with true incrementality…
Identity proven by GitHub's verified organisation badge (writer)
- Agents
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, claude.ai and API
- License
- CC0-1.0 (permissive)
- Pin
- 20837c9pinned Oct 9, 2026
- Context cost
- about 2,500 tokenswhen the skill loads
- GitHub stars
- 8on writer/skills
- Scripts
- None found
What it does
“For CPG and brand key-account teams selling into retailers, distributors and marketplaces. Builds the category story and line-review or new-item pitch, joint business plan (JBP) and trade-term negotiation prep, promotion post-event analysis with true incrementality, trade-spend ROI, price-increase and cost pass-through conversations, and retailer scorecard reviews (OTIF, fill rate, deductions). Use it whenever the user mentions a retailer buyer or category manager, line or category review, JBP, trade terms, slotting, promo calendar, TPR/BOGO results, a price increase to a retailer, facings or shelf space, or OTIF fines, even if they only paste POS or syndicated data. Not for selling software or services (use enterprise-deal-strategy).”
Generated summary from the skill's own text
This skill helps CPG and brand teams prepare for retail buyer conversations by building category stories, analyzing promotions with true incrementality, calculating trade spend ROI, and managing price increases and retailer scorecards. It provides frameworks for line reviews, JBP negotiations, and new-item pitches grounded in the buyer's category metrics, not brand growth alone. All outputs show working math from syndicated or retailer POS data.
When to use it
- Preparing a line review or category story presentation for a retail buyer
- Analyzing promotion results to calculate true ROI and incremental volume
- Negotiating JBP terms, trade allowances or new item placement
- Justifying price increases to retailers with cost breakdown and elasticity data
When not to
- Selling software or enterprise services to retailers
- Situations without retail buyer involvement or category data
Install
These commands install from the publisher's repository and need no account.
skills CLI
npx skills add writer/skills --skill retailer-jbp-and-line-reviewInstalls from the repository's default branch, which may have changed since the commit we checked.
GitHub CLI 2.90 or later
gh skill install writer/skills retailer-jbp-and-line-review@20837c912ac6df73f78119b7075678f122083a34Installs the commit we checked (20837c9).
Copy by hand
Download the folder at 20837c9 and put it in .claude/skills/retailer-jbp-and-line-review for Claude Code and in .agents/skills/retailer-jbp-and-line-review for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.
Copy for your agent
A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.
Prompt
Install the agent skill "retailer-jbp-and-line-review" by Writer. Source, pinned to commit 20837c912ac6df73f78119b7075678f122083a34: https://github.com/writer/skills/tree/20837c912ac6df73f78119b7075678f122083a34/skills/retailer-jbp-and-line-review 1. Download that folder at exactly this commit. Do not use the default branch. 2. Copy every file unchanged, keeping the folder structure, into .claude/skills/retailer-jbp-and-line-review/ for Claude Code and .agents/skills/retailer-jbp-and-line-review/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist. 3. Do not edit the files, and do not run any script in the folder unless I ask you to. 4. When you are done, list the files you copied and where you put them. Listing and checks: https://www.agentnative.dev/skills/writer/retailer-jbp-and-line-review
SKILL.md at the pin
---
name: retailer-jbp-and-line-review
description: For CPG and brand key-account teams selling into retailers, distributors and marketplaces. Builds the category story and line-review or new-item pitch, joint business plan (JBP) and trade-term negotiation prep, promotion post-event analysis with true incrementality, trade-spend ROI, price-increase and cost pass-through conversations, and retailer scorecard reviews (OTIF, fill rate, deductions). Use it whenever the user mentions a retailer buyer or category manager, line or category review, JBP, trade terms, slotting, promo calendar, TPR/BOGO results, a price increase to a retailer, facings or shelf space, or OTIF fines, even if they only paste POS or syndicated data. Not for selling software or services (use enterprise-deal-strategy).
---
# Retailer JBP & Line Review
A retail buyer is measured on **their category**, not your brand: category sales and share against the market, category margin dollars (including trade funds), traffic, turns, in-stock and private-label goals. Brands that win shelf space present a category story in which their plan grows the buyer's numbers. Brands that pitch their own brand growth get treated as a cost line.
**Shared rules for every output:**
- Label every data source. Syndicated data (Circana, NielsenIQ), retailer POS portals and panel data (Numerator) each come with use restrictions. Retailer-provided data is used only as its agreement allows, and never in another retailer's materials.
- No industry benchmarks unless they are in the proof library with a source. Ranges about "typical" promo lift or trade rates are folklore; the user's own history is the benchmark.
- Show your maths. Buyers and category analysts will check it. The formulas are in `references/commercial-math.md`.
- Anything going to the retailer passes through `customer-facing-quality-gate` (and its `customer-facing-quality-gate/references/industry-rules/cpg-product-claims.md` for product claims and commercial terms).
## 1. Category story and line review
**Build the fact base first:**
- Compare category and brand performance against year-ago, plan and the **total market**. If the category grows more slowly at this retailer than in the total market (both figures sourced), the retailer is losing share, and that is the opening.
- Build a **growth bridge**: Sales = traffic × conversion × units per basket × average unit price. Measure basket in units so price isn't counted twice. The drivers multiply, so attribute Δ sales with a log (LMDI) or sequential-substitution method that makes the parts sum exactly to the total. Split price/mix into pure price, tier trade-up or trade-down, size and channel.
**Diagnose the cause:**
| Pattern | Likely cause |
|---|---|
| Traffic down, conversion stable | Relevance or media problem |
| Conversion down | Assortment, price gap or friction |
| Conversion up, basket down | Cherry-picking or out-of-stocks |
| Average price down, units flat | Trade-down, deeper promos, channel mix |
| Average price up, units down | Elasticity threshold crossed |
Separate base volume from promoted volume, and adjust for calendar shifts such as holidays moving between weeks.
**Make the ask with these tools:**
- **Share-to-space:** compare brand share of category sales with share of shelf ("18% of sales on 5% of the section"). Add the growth contribution index: share of category growth ÷ share of category sales.
- **Consumer decision tree:** need state → form → tier → size → variant. Empty cells are white space; validate each with two independent signals. Keep *assortment* gaps (a segment missing) separate from *distribution* gaps (listed but not carried in every store).
**New-item sell-in checklist.** The buyer needs:
- source of volume (incremental vs. cannibalization)
- expected velocity against the category average, with its basis
- marketing and shopper support, with timing
- distribution plan, with confirmed POs kept separate from pending ones
- supply readiness
- item setup **and PDP content live at every channel before ship date** (see `pdp-content`)
- a 13-week read plan with checkpoints
- what the buyer needs to see to keep the item past the next reset
**Defending an at-risk SKU:** argue on transferable demand (how much volume would *not* move to other items), velocity rank within its segment, and its role: traffic driver, trial, or price-tier anchor.
## 2. Promotion post-event analysis
1. **Baseline.** Use one of:
- (A) the average of non-promoted weeks before the event (e.g., 4–8 weeks), adjusted for trend and seasonality. Exclude post-event weeks, which contain the dip, and any weeks with other promotions
- (B) matched control stores or SKUs (preferred)
- (C) a time-series model
Always net out the post-promo dip in the following weeks.
2. **Decompose the lift:** baseline (subsidized), category expansion, switching from competitors, cannibalization of your own items, and pull-forward. Measure pull-forward **once**, preferably as the post-period dip against baseline. Never subtract both a pantry-loading estimate and the dip.
- **Manufacturer:** true incremental = expansion + brand switching.
- **Retailer:** true incremental = category expansion + shoppers switching from other stores. Brand switching within the category isn't incremental to the retailer.
3. **Cost and profit impact.** Use one consistent method; both are given in `references/commercial-math.md`. Always run this check: incremental contribution − promo cost = profit with the promo − profit without it. Report separately the share of funding that subsidized volume which would have sold anyway.
4. **ROI at three levels:**
- gross: incremental revenue ÷ spend
- net: incremental contribution ÷ spend
- true: net, after cannibalization, the dip and execution costs
5. **Compare actual lift with breakeven lift.** A promo that "lifted 80%" can still lose money.
**Rules:**
- Calculate ROI separately for the retailer and the manufacturer.
- Split variable trade (scan, bill-back, TPR) from fixed trade (slotting, lump sums). Fixed trade is excluded from per-event ROI.
- Track promo dependency: the share of volume sold on deal.
- Recommend **reallocation**, not just cuts.
## 3. JBP and trade-term negotiation prep (internal only)
- **Power and alternatives.** Assess:
- brand pull
- this retailer's share of our sales, and our share of their category
- our alternative channels
- the retailer's private-label readiness
- switching costs
Write down the **BATNA for both sides**; the retailer's usually includes its private label and the #2 brand. Estimate the zone of possible agreement.
- **Value levers, ranked by cost to us against value to them.** Lead with low-cost, high-value levers:
- exclusive pack, flavor or size
- early access to innovation
- category insights (within data rights)
- joint forecasting
- display and merchandising support
- payment terms (expensive, because they tie up working capital)
- **Concession discipline:**
- Trade, never give. Every concession is tied to something in return.
- Each concession is smaller than the last.
- Keep one concession in reserve for the close.
- Keep a hard-no list, with the reason for each item.
- **Rehearse three scenarios:**
- best
- base
- worst: a delist threat, answered by proposing a test, a pilot or a timeline
- **Every talking point carries a quantified benefit to the retailer** and a line for "if they push back".
- **Commitments:**
- Get approval at the right authority level before any verbal commitment.
- Exclusives and special terms can trigger most-favored-customer clauses in other retailers' agreements.
## 4. Price increase and cost pass-through
- **Justify cost by component:** commodity, packaging, freight, labor. Give a source for each and a date for each source.
- **Breakeven volume loss** = p ÷ (m + p), where p is the price increase % and m is the contribution margin %.
- **Elasticity:** show a range, not a point estimate. Never extrapolate beyond price points actually observed.
- **Check the retailer's side:**
- Model the retailer's margin. The manufacturer sets list price; **the retailer sets shelf price**.
- Re-check the price gap to private label.
- **Offer alternatives:** partial pass-through; pack-size or price-pack-architecture change (keeping unit price logical across the size ladder); mix.
- **Follow the notice period** in the agreement.
## 5. Scorecard, OTIF and deductions review
- **Define OTIF exactly as this retailer's current supplier guide does.** Programs differ and change, so pull thresholds and fine rates from the current guide, never from memory.
- Track 4-week and 13-week rolling figures. Flag three consecutive periods of decline.
- **Deductions:**
- Classify by type: delivery, quantity, documentation, labeling, packaging, compliance.
- Report as a percentage of net sales.
- Run a Pareto to find the few causes behind most of the value, then 5-whys to the root cause, with an owner per function (demand planning, procurement, 3PL, carrier, EDI, QA).
- **Disputes:** back them with evidence: POD/BOL, EDI timestamps, duplicate-deduction checks, program-guide citations.
- **Corrective action plan:** owner, date, milestones, leading indicators.
## Guardrails (legal; flag, don't decide)
- **Robinson-Patman (US).** Price and promotional-allowance differences between competing retailers need legal review. Allowances must be offered to competitors on proportionally equal terms.
- **Antitrust.** Never request, share or infer competitor pricing or plans. If the user receives such information unasked ("a friend at a competitor told me…"), don't use or forward it. Advise them to tell legal or compliance. Category captains keep firewalls. Suggested retail prices and unilateral pricing policies are fine. Never agree or negotiate a retailer's resale price: that is rule of reason federally, but per se illegal in some states. MAP limits *advertised* price only.
- **Internal stays internal.** Floors, other retailers' terms, and the hard-no list never appear in anything the buyer sees.
## Outputs
- **Line-review / category-story deck outline.** Each slide carries a headline that states the insight, the evidence behind it, and the ask in the buyer's metrics.
- **New-item pitch one-pager.**
- **Promo post-event readout:** verdict first, then breakeven vs. actual, the decomposition, and the reallocation recommendation.
- **Negotiation prep sheet** (internal).
- **Price-increase rationale and buyer talk track.**
- **Scorecard corrective action plan.**
Lead with the answer to the user's question. Put the supporting tables in an appendix.
From writer/skills at 20837c9, shown as plain text under its license: CC0-1.0 (permissive). The license text is in LICENSE.
View SKILL.md on GitHub at 20837c9Files
- SKILL.md11 KB · b1aa20a49414
- references/
- commercial-math.md4.7 KB · 56d586c0abec
2 files, 15 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.
Skill folder on GitHub at 20837c9More from Writer
agent-execution-receipts
This skill inspects signed execution receipts and correlates them with provider audit logs to determine whether an agent action has local evidence, a…
Claude Code, Codex, Cursor +4 · about 290 tokens · pinned 7 days ago
practice-registry
This skill checks Scala, Python, TypeScript, JavaScript, and Rust code against company-specific coding practices before generation, during editing, and before…
Claude Code, Codex, Cursor +4 · about 410 tokens · pinned 7 days ago
account-targeting-and-research
This skill helps sales and marketing teams identify and research enterprise accounts most likely to buy.
Claude Code, Codex, Cursor +4 · about 2.6K tokens · pinned 7 days ago
b2b-content-and-campaigns
This skill helps the agent create enterprise B2B marketing content and campaigns, including case studies, executive thought leadership, email programs, web…
Claude Code, Codex, Cursor +4 · about 1.4K tokens · pinned 7 days ago
business-case-and-proposal
This skill helps agents construct enterprise business cases, ROI and TCO models, executive summaries, proposals, RFP responses, security questionnaires, and…
Claude Code, Codex, Cursor +4 · about 2.3K tokens · pinned 7 days ago
competitive-and-objections
This skill equips agents to build honest competitive battle cards, handle sales objections, and analyze win/loss outcomes.
Claude Code, Codex, Cursor +4 · about 2.5K tokens · pinned 7 days ago
Related in Marketing, sales and product
accelo-automation
This skill enables agents to automate Accelo project management tasks by discovering and executing operations through Composio's Accelo toolkit via Rube MCP.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 7 days ago
acculynx-automation
This skill automates Acculynx operations by discovering and executing available tools through the Rube MCP server.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 7 days ago
active-campaign-automation
This skill automates ActiveCampaign tasks by discovering and executing tools through Rube MCP and Composio's ActiveCampaign toolkit.
by ComposioOfficial publisher
Agents not labelled yet · about 710 tokens · pinned 7 days ago
adrapid-automation
This skill enables agents to automate Adrapid tasks through Composio's toolkit via Rube MCP.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 7 days ago
aeroleads-automation
This skill automates Aeroleads tasks by connecting to the Aeroleads toolkit via Composio's Rube MCP server.
by ComposioOfficial publisher
Agents not labelled yet · about 700 tokens · pinned 7 days ago
affinity-automation
This skill automates Affinity CRM operations by executing tools through Rube MCP and Composio's Affinity toolkit.
by ComposioOfficial publisher
Agents not labelled yet · about 690 tokens · pinned 7 days ago
Open roles at Writer
5 of 15 open roles on the jobs board
- Security engineer, detection and response (UK)
London, UK (Remote)
- Security engineer, application security (UK)
London, United Kingdom (Hybrid)
- Infrastructure engineer
New York City, NY, USA | Seattle, WA, USA | San Francisco, CA, USA | London, UK (Hybrid)
- Staff security engineer, application security
New York City, NY, United States | Seattle, WA, United States | San Francisco, CA, United States (Hybrid)
- AI engineer (UK)
London, UK (Hybrid)