Ask Lana
Help Center
How can we help? 👋

Pricing Adjustment Event

The Pricing Adjustment Events feature lets planners adjust prices in scenarios and see their impact instantly.

The Pricing Adjustment Events feature allows planners to modify prices in scenarios and immediately see their financial impact. These adjustments provide accurate revenue calculations, support customer-specific negotiations, and ensure KPIs reflect the true financial impact of pricing changes.

There are three types of price adjustments, depending on which level of the commercial model you want to impact:

1. Listed Price Event

  • Scope:
    • Acts as the catalog price and is used to calculate secondary demand and sales values across all customers, if and only if those customers do not have a specific Secondary Customer Price set for them.
    • Setting at the product level (no customer distinction)
  • Used in:
    • Secondary Demand Value
    • Secondary Gross Sales Value
    • and, consequently, Secondary Trade Expenses and Secondary Net Sales Value.
  • Purpose: Represent the "catalog price" of a product in the market before discounts.
  • When to use: Apply when changing the general product price across all markets (e.g., new list price announcement, general price increase).

2. Secondary Customer Price Event

  • Scope:
    • Defines customer-specific prices that override the listed price when available, ensuring accurate secondary sales per customer.
    • Setting at Product x Secondary Customer level
  • Used in:
    • Secondary Demand Value
    • Secondary Gross Sales Value
    • and, consequently, Secondary Trade Expenses and Secondary Net Sales Value.
  • Purpose: Capture customer-specific price agreements that differ from the listed price.
  • When to use: Apply when you need exact pricing per customer, instead of broad discounts or list-based assumptions.

3. Primary Customer Price Event

  • Scope:
    • Represents the negotiated selling price to distributors and is used for primary demand and sales values.
    • Setting at the product x primary customer level
  • Used in:
    • Primary Demand Value
    • Primary Gross Sales Value
    • and, consequently, Primary Trade Expenses, Primary Net Sales Value and all the P&L down to the EBIT
  • Purpose: Reflect the negotiated price at which distributors purchase products before discounts.
  • When to use: Apply when simulating changes in primary sales revenue and distributor agreements scenarios.

Fallback & Adjustment Logic

In SIMCEL, both Product Value Master data (uploaded via ETL) and Pricing Adjustment Events can influence the final price used in scenarios. In the case of Secondary Demand/Sales Value, there could be 2 sources in the Product Value Master (PVM):

  • SP_PVM: Secondary Customer Price defined in Product Value Master (per ProductID, CustomerRef).
  • LP_PVM: Listed Price defined in Product Value Master (per ProductID).

And there could be 2 sources in the Pricing Event:

  • SP_Event: Secondary Customer Price Event (per ProductID, CustomerRef)
  • LP_Event: Listed Price Event (per ProductID).
 

The system applies the following rules to determine which Input to use in the PVM and how events are applied when considering a set of Product and Customer

Input Available \ Event Assigned
LP_Event
SP_Event
SP_Event + LP_Event
LP_PVM
Use LP_PVM as baseline → apply LP_Event adjustment
Use LP_PVM as baseline → apply SP_Event adjustment (acts as customer-specific override)
Ignore LP_Event → Use SP_PVM as baseline → apply SP_Event adjustment
SP_PVM + LP_PVM
Ignore LP_Event → still use SP_PVM (customer-specific price takes priority)
Use SP_PVM as baseline → apply SP_Event adjustment
Ignore LP_Event → Use SP_PVM as baseline → apply SP_Event adjustment

How to Create a Pricing Adjustment Event

Step 1 — Create a New Pricing Adjustment Event

  • Navigate to the Event Management Page
  • Click New Event and select Pricing Adjustment.
  • Fill in the basic details:
    • Event Name (e.g., Secondary Price – Product X)
    • Version Name (optional, to track iterations)
    • Period (select start and end months of the event)
    • Notion image

Step 2 — Select Price Type

  • Choose which price level the event applies to:
    • Listed Price – Product level (same for all customers).
    • Distributor Price – Product × Primary Customer level.
    • Secondary Customer Price – Product × Secondary Customer level (customer-specific price).
    • Notion image

Step 3 — Define Impacted Segments

  • Select the Products the event should affect.
  • Depending on the event type, you can further filter by:
    • Secondary Customer (for Secondary Customer Price events)
    • Primary Customer (for Primary Customer Price events)
    • Locations (if geography is relevant)
  • You can add multiple segments by clicking “Add Another Segment Affected by the Event”.
Notion image

Step 4 — Add Adjustments

For each selected segment, you can define one or more adjustments:

  1. Set Price – Replace the baseline with a fixed value (e.g., 120,000 VND).
  1. Absolute Adjustment – Increase or decrease by a fixed amount (e.g., +20,000 VND).
  1. Percentage Adjustment – Increase or decrease by a percentage (e.g., –30%).
 

You can add multiple adjustments with different validity periods.

Notion image
 

Adjustments are always applied in the following order:

Set PriceAbsolute AdjustmentsPercentage Adjustments

🔢 Example – Applying Adjustments

Baseline (Listed Price): 100,000 VND

  1. Set Price90,000 VND
  1. Absolute Adjustment (+5,000)95,000 VND
  1. Percentage Adjustment (+10%)104,500 VND

⇒ Final Price = 104,500 VND


Step 5 — Finalize the Event

  • Add a Description (optional, for notes or context).
  • Click Submit to save the event.
Did this answer your question?
😞
😐
🤩