Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.retailgrid.io/llms.txt

Use this file to discover all available pages before exploring further.

Pricing Strategy is an analytics agent that reads your Account and the products in a grid, queries your real transactional data over a chosen historical timeframe, and generates a pricing-strategy presentation as a Gamma deck. The output is an editable, shareable narrative - portfolio overview, category roles, pricing pressure, and proposed moves - grounded in your actual data, not a templated demo.

When to use Pricing Strategy

Reach for Pricing Strategy when you need a stakeholder-facing narrative on top of your portfolio:
  • Quarterly business reviews and board decks.
  • Opening conversations with retailers - explain where the pricing levers are before you propose specific changes.
  • Cross-functional alignment - give Merchandising, Finance, and Leadership a shared picture of how the portfolio is priced today.
  • Pre-sales storytelling - turn raw data into a recognisable strategy frame in minutes.
If you instead want concrete per-SKU prices to apply, use Rules Based Pricing (rule-driven) or Price Optimization (AI-suggested).

Run Pricing Strategy

In any grid:
  1. Click Agents in the top toolbar.
  2. Switch to the Analytics Agents tab in the All Agents modal.
  3. Select Pricing Strategy.
  4. Pick a Timeframe (see the ladder below).
  5. Click Run.
The agent runs in the background. Watch progress in the Runs section in the left sidebar; the active-runs badge on the Runs icon will tick up while it’s working.

Choose a timeframe

Pricing Strategy supports seven timeframes. Pick the one that matches the audience and the question you’re answering:
TimeframeGood for
Last 7 daysReacting to a recent promo or competitor move.
Last 30 daysMonthly category review.
Last 90 daysQuarter-in-progress check, supplier conversations.
Quarter-to-date (QTD)Mid-quarter steering.
Year-to-date (YTD)Mid-year and full-year executive reviews.
Trailing 12 months (T12M)Annual planning, removes seasonality artifacts at the boundaries.
CustomPick exact start and end dates - useful for promo windows or pre/post comparisons.
The agent only sees transactions inside the selected window. Pick a window with enough volume to support the analysis - very short windows on small product sets produce thin decks.

What the agent reads

No manual configuration is required beyond picking a timeframe. Pricing Strategy automatically pulls:
  • Company name - from your Account / Organization. Appears on the deck cover and throughout the narrative. Set it before running if your Organization is freshly provisioned.
  • Products and attributes - the grid you ran the agent from (categories, prices, costs, custom attributes).
  • Transactional data - real sales over the chosen timeframe, queried directly from the analytics warehouse. No placeholder numbers; if a category has no transactions in the window, it shows as zero rather than a synthesized value.

Output

When the run completes, a Download button appears on the run progress card so you can open the deck in Gamma directly. The same link is also available from the Runs detail view. The deck is a complete strategy narrative covering:
  • Portfolio overview (catalog size, revenue, average price, margin band).
  • Category roles (Traffic Builders, Profit Drivers, Niche, Promo - inferred from price elasticity proxies and contribution).
  • Pricing pressure (where competitor or margin signals suggest the most movement is needed).
  • Proposed strategic moves with expected directional impact.
The Gamma deck is editable - you can rewrite copy, swap visuals, and reorder slides before sharing. Edits stay in Gamma; re-running Pricing Strategy generates a new deck rather than overwriting the previous one.

Common pitfalls

  • Empty timeframe - if there are no transactions in the chosen window, the deck is sparse. Pick a wider window or confirm your transactional data has loaded.
  • Account name unset - the deck cover and narrative will reference a default placeholder. Set the company name on the Organization page first.
  • Very small product set - the category-role analysis needs enough SKUs per category to be meaningful. Decks generated against fewer than ~20 products tend to read more like a per-SKU summary than a strategy.