Price Validation — What Needs Recalculation

Overview

Price Validation helps product and operations teams manage the effect of service price changes. After a cost or sell price is changed in Price Manager, the workspace identifies Price Models and operational itinerary lines that use the service during overlapping travel dates.

Users can see what may be stale, review the expected impact, and choose one, several, or all records for action. Price Validation does not automatically recalculate records.

Scope of this guide: This guide covers service cost and sell price changes. Price season comparison is still in progress and is not included.

Before You Start

Salesforce and Edge must both be configured before affected records appear.

Salesforce Setup

Give each user access to the Price Validation workspace and the Service, Business Unit, Price Model, and itinerary records they need to review.
Add the workspace at the required placement:
- Service — records affected by changes to one service;
- Business Unit — records within one business unit; or
- Global — records across the company.
Choose the placement that matches the user’s responsibility. There is no scope switch inside the workspace.
Confirm users can access both workspace tabs:
- Price Models
- Itinerary lines, covering operational itineraries.

Use the customer’s established Salesforce access model. Your Kaptio implementation team or administrator can confirm the required access and page placement.

Edge Setup

Ask the Kaptio implementation team to enable Price Validation for the customer’s Edge tenant.
Confirm the Salesforce org is connected to the correct Edge tenant and environment.
Test each configured Service, Business Unit, or Global placement with a user who will perform validation.

The Price Validation inbox does not fill until the customer has been enabled in Edge.

How the Workflow Operates

A user changes a service cost or sell price in Price Manager.
Price Validation finds Price Models and itinerary lines that use the service during overlapping travel dates. Identifying candidates typically takes about 15 minutes after the price is saved.
Affected records enter the validation workflow.
The system compares eligible records and shows whether the cost, sell price, or both are outdated. The comparison job runs 1–2 times a day, during low-workload periods.
The user reviews the impact and decides which records to act on.
Selected work runs in the background, and the user receives a completion notice.

Nothing recalculates automatically. The user remains in control of which records are updated.

Demo: Changing a service price

This recording shows the initial event: a price value is changed in Price Manager and saved.

Demo: Checking the results in Edge

This recording shows how to review the resulting records in the Edge component.

Open the Right View

Open Price Validation from the Salesforce placement configured for your role:

Use the Service view when reviewing the effect of a specific service price change.
Use the Business Unit view when managing changes for one operational area.
Use the Global view when managing changes across the company.

Then choose:

Price Models to review calculated group pricing; or
Itinerary lines to review affected operational itinerary services.

The placement controls the scope. Changing tabs changes the type of record shown, not the placement scope.

Review Status and Impact

The workspace moves records through these stages:

Stage	What it means	What to do
Pending	The record has been identified and is waiting for comparison.	Wait for background processing.
Outdated cost	The comparison found a cost impact.	Review the impact and decide whether to confirm.
Outdated sell	The comparison found a sell-price impact.	Review the impact and decide whether to confirm.
Outdated cost and sell	Both cost and sell price are affected.	Review both impacts before taking action.
In progress	Selected work is running in the background.	Wait for the completion notice before starting another action on the same record.
Completed	The selected action finished.	Review the updated record where required.

Use the available impact, departure-date, and booking-count information to judge the business effect before selecting records. Pay particular attention to departures with existing bookings.

Take Bulk Action

Price Models

Open the Price Models tab.
Filter or sort the list to focus on the relevant records.
Review the cost or sell impact, departure dates, and booking counts.
Select one, several, or all appropriate Price Models.
Choose the Confirm action. Price Validation does not recalculate Price Models from this workspace.
Review the selection and start the action.
Wait for the background work and completion notice.

When you confirm a Price Model after comparison, the system applies the result that was already calculated and retained for that comparison. It does not silently run the full pricing engine a second time.

If the Price Model structure was changed as well as the service price, comparison is skipped because the previous and current structures are no longer equivalent. Recalculate that Price Model using the standard Price Model process; this workspace does not offer a Recalculate action.

Operational Itinerary Lines

Open the Itinerary lines tab.
Review travel dates, impact, and booking information for operational itinerary rows.
Select the records that are safe to update.
Start the available bulk repricing action.
Monitor the background work until the completion notice appears.

Do not select every row by default. Use the operational and booking context to decide which records should be updated.

What This Does Not Do

It does not recalculate anything automatically after a service price change.
It does not provide a scope switch inside the workspace; scope comes from the Salesforce page placement.
It does not compare Price season changes. That functionality is still in progress.
Version 1 does not flag inflation-derived future-year prices when a base-year price changes.
It does not compare a Price Model whose structure changed in parallel with the service price. That Price Model requires a full recalculation.

Troubleshooting

No rows appear after a price change

Wait up to 15 minutes, then refresh the workspace. Confirm the price was saved, the service is used within overlapping travel dates, and you opened the correct Service, Business Unit, or Global placement.

If rows still do not appear, ask your administrator or Kaptio implementation team to confirm that Price Validation is enabled for the Edge tenant and that the Salesforce org is connected to the correct tenant and environment.

A record stays Pending

Pending means the record has been found but comparison has not completed. Refresh after the next background processing cycle. If it remains pending beyond the expected operating window, provide the service, Price Model or itinerary reference, and price-change time to your Kaptio support contact.

A Price Model cannot be compared

Check whether its structure was changed after or alongside the service price change. Structurally changed Price Models are intentionally excluded from comparison and require a full recalculation.

An action is blocked

A Price Model cannot start another recalculation while a confirmed result is being pushed into Salesforce. Wait for the in-progress action and completion notice, then refresh the workspace.