Overview
Generate Distributor Price lets you turn a demand scenario into a ready-to-use Distributor Price event in a single guided flow. Instead of exporting data and computing prices manually in Excel, you generate the prices from the scenario, review and edit them in SIMCEL Sheets, and create a reusable Pricing Adjustment Event.
The feature computes a volume-weighted average of the Secondary Customer Price per product, grouped by half fiscal year (H1 / H2), then applies that value across every month in the half-year window. The result is one price per product per month, where all months in the same half-year share the same value.
This is a manual, validated step: generating prices does not automatically apply them to any scenario. You always review and confirm first.
Step-by-step
1. Open the scenario menu
On the Demand Planning page, find the scenario you want to use and click its 3-dot menu.
2. Select Generate Distributor Price
Choose Generate Distributor Price from the menu. SIMCEL computes the prices and saves the result as a sheet — wait for the generation to finish.
3. Open Spreadsheets
The generated prices are saved into SIMCEL Sheets. Open Spreadsheets from the Tools section in the left sidebar.
4. Open the sheet list
Click Open (top-right) to see your saved sheets.
5. Choose the generated sheet
Under My Sheets, select the generated sheet — named like Distributor Price – Pricing – V1.
6. Review the prices
The sheet opens in Distributor Price Preview mode, with a banner prompting you to review the prices and then create the event. The layout:
- Rows — one per product in the scenario (product code and name).
- Columns — one per month across the scenario horizon, grouped under H1 / H2 super-headers for each fiscal year (e.g. FY26 H1, FY26 H2).
- Values — within a product, all months under the same half-year header initially show the same computed price.
- A banner at the top summarizes the scenario name, horizon, how many products are complete vs incomplete, and any half-year windows that were skipped or computed from a partial date range.
7. Edit a price (optional)
You can override any cell before creating the event — for example, changing Product ID 1's price for Jan–Mar 2026 from 100,000 to 200,000. Overriding one month does not change the other months in that half-year; each cell is edited on its own.
8. Create the event
Click Create Event (top-right). In the Create Pricing Adjustment Event dialog, set the Event Name, Version Name, and an optional Description, then click Create Event to confirm. The event name defaults to Distributor Price – {Scenario Name}. You can edit the description before confirming. On confirmation, SIMCEL creates a new Pricing Adjustment Event:
- Type: Set Price
- Price Type: Distributor Price
- Scope: product-level, across all customers and channels
- Values: monthly, matching the spreadsheet
- Period: the source scenario's horizon
The event appears in Event Management and can be attached to any scenario like any other Set Price event.
How the price is calculated
For each product and half fiscal year, SIMCEL computes:
Half-Year Price = (sum of Secondary Customer Price × Secondary Demand Volume, across every customer and month in the half-year window) ÷ (sum of Secondary Demand Volume, across the same customers and months)
That half-year price is then assigned to every month inside the window.
Key rules:
- If total demand volume is zero for a product's half-year window, the price is undefined — those months show "—" and are skipped in the generated event.
- If a Secondary Customer Price is missing for a given customer/month, that data point is excluded from the calculation (it does not count as a zero).
- A product is considered "complete" if it has at least one valid half-year price in the scenario horizon.
- Prices are rounded to the workspace's configured precision (4 decimals by default).
Partial half-years: If the scenario horizon doesn't start or end exactly on a half-year boundary, the affected window is computed using only the months actually covered. For example, a scenario starting in November means that fiscal year's H1 covers Nov–Mar instead of Oct–Mar. The top banner lists any partial windows and the month range used.
Edge cases and what to expect
- Scenario not computed — the menu item is disabled until you run the scenario.
- Missing prices for some products — those products show "—" with a warning; the event is still created for the valid products, and skipped ones are noted in the event description.
- Zero demand in a half-year window — that window is skipped and reported in the banner.
- Computation fails or times out — the view shows an error with a Retry button; no event is created.
Good to know
- Re-generating always recomputes from the latest scenario output and creates a new event each time — it never overwrites a previous one. You can generate multiple events from the same scenario (useful for versioning).
- The generated event is a snapshot. If the source scenario changes later, the event does not auto-update; generate again if you need refreshed prices.
- Deleting the source scenario does not delete events generated from it — they're independent once created.
- Each generated event keeps a metadata link back to the scenario it came from, visible in the event's activity log.