Advanced Pricing Module Overview
Introduction
The new Advanced Pricing Module (APM) aims to enforce contract logic and improve billing accuracy by using price books, rules, and overrides to minimize manual edits and revenue loss. The main distinction is that Advanced Pricing extends these controls to the newer FieldFX Mobile App (running on iOS, Android, or Windows) and introduces compliance actions—such as required, recommended, or prohibited items—along with field‑condition triggers.
|
A separate license, not included in the base FieldFX license, must be purchased for the use of APM. Contact your account representative for more information. |
|
FX CPQ remains supported for legacy customers, but no new functional parity with APM should be assumed beyond pricing overrides. |
Advantages of APM over FX CPQ
This section provides a comprehensive comparison between the legacy FieldFX CPQ module and the new APM module. It highlights key differences in functionality, architecture, and licensing, as well as the advantages APM offers for modern pricing and compliance needs. Here you can understand why APM is more than a simple rebrand—it is an enhanced solution designed for accuracy, mobility, and operational efficiency.
| Feature | FX CPQ | Advanced Pricing Module (APM) |
|---|---|---|
Scope |
Back Office only |
Back Office and Mobile (iOS, Android, Windows) |
Rule Engine |
|
|
Compliance Actions |
Limited |
Full compliance enforcement at point of service |
Dynamic Triggers |
Not supported |
Supported (field conditions like temperature, pressure, location) |
|
See note below |
No |
Yes – prevents missed billable items in the field |
Licensing |
Architecture |
Legacy CPQ framework |
Licensing |
Included in base FieldFX license |
Separate APM license required |
Operational Accuracy |
Manual edits often needed |
End-to-end consistency from quote to cash |
|
Mobile Enforcement On Mobile, required items are automatically added to tickets and cannot be removed. Prohibited items are blocked at entry. Tickets cannot be completed if compliance rules are violated. |
Features
The Advanced Pricing Module delivers significant improvements over the legacy FX CPQ module, making it a powerful tool for accurate, compliant, and efficient pricing management. Key advantages include:
-
Mobile Integration
APM extends pricing logic and compliance enforcement beyond the Back Office to FieldFX Mobile. This ensures pricing rules get applied at the point of service, reducing missed billable items and improving revenue capture.
-
Expanded Compliance Actions
APM introduces advanced rule actions that go beyond CPQ’s basic applicability:
-
Required Items – Automatically add mandatory items to tickets or quotes.
-
Recommended Items – Suggest optional items for upsell or operational completeness
-
Prohibited Items – Prevents the addition of incompatible or disallowed items
-
Overrides – Dynamically adjust pricing based on conditions.
-
-
Dynamic Field-Condition Triggers
APM supports pricing adjustments based on operational factors such as:
-
Down-hole temperature and pressure bands
-
Corrosive environment or sour gas presence
-
Waste type for disposal fees
-
Location-based surcharges
These triggers enforce contract logic and eliminate unauthorized pricing changes.
-
-
End-to-End Accuracy
By applying consistent pricing rules across Back Office and Mobile workflows, APM minimizes manual edits and ensures accurate quote-to-cash processes.
-
Future-Ready Architecture
Built on the latest FieldFX platform (25R2 and beyond), APM supports evolving industry requirements and new compliance features.
Feature Summary
| CPQ Module | Advanced Pricing Module | |
|---|---|---|
Purpose |
Configure complex contract rules in Back Office quotes (price book rules, applicability, overrides). |
Enforce pricing and compliance across Back Office and Mobile with richer rule actions (auto‑add, recommend, prohibit, override). |
Scope |
Quote creation only; relies on price books and override engine. |
Quote and field ticket entry; applies logic at job, ticket, and ticket item levels. |
Actions Supported |
Rule‑driven applicability and pricing overrides. |
Automatically add required items, recommend items, prevent certain items, and override price/cost. |
Data Inputs |
Price book rules; Back Office configuration. |
Same foundation plus field conditions (e.g., temperature, pressure, waste type, location surcharges). |
User Experience |
Back Office‑centric (Salesforce UI). |
Extends to FieldFX Mobile App workflows for technicians. |
Licensing |
Historically bundled as FX CPQ. |
Sold/licensed as Advanced Pricing Module for cross‑environment enforcement. |
Terminology |
“CPQ” remains in legacy documentation. |
“Advanced Pricing Module” is the go‑forward name in 25R2 and beyond. |
Business Outcomes |
Faster, more accurate quotes; fewer manual price adjustments. |
End‑to‑end quote‑to‑cash accuracy, stronger compliance, reduced revenue leakage. |
Similarities & Overlap |
|
|
Key Differences
Mobile enforcement and field‑condition triggers are exclusive to Advanced Pricing |
Mobile enforcement - Rules now run at the point of field data entry—auto‑adds, recommendations, and prohibitions on ticket lines. |
Field‑condition triggers - Use operational conditions (temperature/pressure bands, corrosive flags, waste handling logic, location surcharges) to select rates or attach items. |
|
Advanced Pricing formalizes compliance actions (required/recommended/prohibited items) beyond pricing overrides. Beyond pricing overrides, admins can require or block items to prevent “rogue pricing.” |
|
Who Should Use APM?
APM is best suited for customers who require:
-
Pricing enforcement at the point of service
-
Contract compliance beyond quote creation
-
Dynamic pricing based on operational conditions
-
Mobile technicians to follow contractual billing rules automatically
|
If your organization requires pricing enforcement on field tickets or condition‑based pricing, FX CPQ alone is insufficient. Advanced Pricing Module is required. |
Customers using FX CPQ for Back Office quoting only may continue to do so, but will not receive Mobile enforcement or compliance actions.
How APM Works
The APM module provides contract administrators with the ability to model contracts with complex rules related to the applicability of certain equipment, services, labor and supplies based on the operational and environmental characteristics of jobs.
Salespeople and field personnel answer questions during quote/ticket creation and a Rule Engine uses these answers to recommend and price the appropriate items to use.
| Scenario 1 | Scenario 2 |
|---|---|
|
|
|
|
The FX CPQ has two major features:
-
Enhanced price book management:
-
Dynamic bundling of price book items
-
Complex modeling
-
Conditional item applicability
-
Discount thresholding
-
Business segment or customer-specific pricing
-
-
Rules-based quoting and ticketing:
-
Salespeople can build rules-based quotes (online or offline) and the Rule Engine adds, recommends, or disallows price book items automatically
-
Field personnel can build rules-based tickets (online or offline) and the Rule Engine adds, recommends, or disallows price book items automatically
-
Key Features
APM has these key features beyond FX CPQ:
Mobile Enforcement (Exclusive to APM) |
APM extends all pricing logic—rules, overrides, and compliance actions—to FieldFX Mobile (iOS, Android, Windows). This means rules run at the point of service, preventing missed billable items and enforcing correct pricing directly on field tickets. |
Expanded Compliance Actions |
APM adds several rule actions that go far beyond CPQ’s basic applicability and pricing overrides:
FX CPQ only supported basic applicability and pricing overrides; it did not support recommended or prohibited actions. |
Dynamic Field‑Condition Triggers (Not Supported in CPQ) |
APM enables rule logic based on real-world operational conditions captured on jobs or tickets, including:
These conditions dynamically adjust rates, add required items, or block prohibited items — a capability CPQ never offered. |
Full Back Office + Mobile Quote-to-Cash Accuracy |
APM applies pricing rules consistently across:
This ensures end-to-end pricing continuity. CPQ applies rules only during quote creation. |
Stronger Compliance Enforcement |
With prohibited items, required items, and ticket-completion enforcement, APM provides:
CPQ had no Mobile compliance and no prohibited-item enforcement. |
More Modern Architecture |
APM is built on the latest FieldFX architecture, designed to support:
|
Advanced Use Cases Not Possible in FX CPQ |
APM supports complex real-world billing logic, such as:
|
CPQ to APM Transition Considerations
While APM builds on CPQ concepts such as price books and rules, it introduces new objects, actions, and Mobile enforcement layers. Existing CPQ configurations do not automatically provide equivalent APM behavior.
Customers should review:
-
Rule action types
-
Mobile sync requirements
-
Licensing differences
Best Practices
When a Rule Triggers
-
The Rule or Rule Action must be
Active. -
Using the Rule Processor, the Rule’s
IsCriteriaDirtyfield must befalse. -
The object record’s
Sync__cfield must be false for Quotes or Tickets.If a Quote or Ticket is already synced (
Sync__c = true), rule changes will not retroactively apply until the record is re‑evaluated or re‑synced. -
The user must have an FX CPQ license assigned and have the required FX CPQ minimum permissions.
-
The rule’s criteria must be valid.
Recommended Reading
For more information, see:
| FieldFX Documentation | PTC ServiceMax Help Center | Salesforce Documentation |
|---|---|---|
Not Applicable |
Not Applicable |

