> ## 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.

# Run Price Optimization

> Set an optimization goal, check the parameters and guardrails, and run Price Optimization on your grid.

**Price Optimization** proposes a price per SKU from your sales history, your costs and competitor prices. It changes no live price: every proposal goes to review in [part three](https://docs.retailgrid.io/get-started/review-and-approve-prices.md).

## Open the agent

In the grid, click **Agents** in the top toolbar and pick **Price Optimization**, or use the pinned **Price Optimization** button if your grid has one.

The dialog opens with four tabs on the left, **General**, **Parameters**, **Rules** and **Automation**, and the **Config by AI** panel on the right. Fill them in any order.

![The Price Optimization dialog open on the General tab, showing the optimization goal options](https://mintcdn.com/retailgrid/7_pkwVphWfw5qaz_/images/get-started/price-optimization-settings.png?fit=max\&auto=format\&n=7_pkwVphWfw5qaz_\&q=85\&s=a2b32142fc1e877248715c4e16f39630)

## Set the goal

On **General**, choose what the run optimizes for:

* **Maximize Profit** - prioritize margin and bottom-line return.
* **Maximize Revenue** - drive top-line growth and sales volume.
* **GMROI** - maximize profit while respecting stock: no price rise on overstock, no cut when stock runs low. See [GMROI optimization](https://docs.retailgrid.io/agents/gmroi-optimization.md).

For a first run, **Maximize Profit** on a small scope gives the result that is easiest to read.

## Check the parameters

On **Parameters**, confirm:

* **Inputs** - which column holds **Price** and which holds **Cost**. The run needs both.
* **Scope** - the **Full grid**, or a **Sample** of rows to sanity-check the setup first.
* **Expected Impact Timeframe** - how far ahead the optimizer projects the impact it scores.
* **Confidence tiers** - which elasticity-confidence tiers the run may act on, so thin SKUs can be held back.
* **Preserve manually updated prices** - leave prices you set by hand untouched.

Account-level model settings such as clustering, recommendation corridors and seasonality are not per run. They live in **Settings → Modelling**. See [Modelling](https://docs.retailgrid.io/settings/modelling.md).

## Check the guardrails

The **Rules** tab holds the rules applied after the model proposes a price: margin floors, index corridors, rounding and price endings, maximum change per cycle. The badge on the tab counts the rules in play, and rule validation must pass before a run can start. See the [Pricing rules guide](https://docs.retailgrid.io/agents/pricing-rules-guide.md).

> [!TIP]
>
> Not sure which settings you need? Describe the outcome in **Config by AI** in plain language, for example "maximize profit on KVI products without taking margin below 20% or moving any price more than 10%", then review what it fills in. It is a starting point, not a final answer.

## Run it

Click **Run**. The job appears on the [Runs](https://docs.retailgrid.io/runs/overview.md) page, and when it finishes the proposed prices are written into the grid.

> [!NOTE]
>
> A run never changes a live price. It writes proposals that wait for your approval.

## Next

See what it proposed, and why: [Review and approve prices](https://docs.retailgrid.io/get-started/review-and-approve-prices.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.