Location & Accessorial Override Rules

Location & Accessorial Override Rules allow administrators to dynamically adjust item pricing or cost based on job location or accessorial conditions. These rules ensure accurate billing for specialized scenarios, enforce compliance, and prevent revenue leakage.

Location & Accessorial Override Rules are evaluated alongside other Advanced Pricing Module rules. When multiple rules apply, the most restrictive compliance action takes precedence.

When to Use Location & Accessorial Override Rules

Use these rules when pricing, cost, or compliance requirements depend on job location attributes or accessorial conditions, such as remote sites, hazardous handling, or restricted environments.

If one rule recommends an item while another prohibits it, the prohibited action will take precedence to ensure compliance.

Key Differences

Table 1. Location & Accessorial Rule Capability Comparison
Feature Advanced Pricing Module FX CPQ (Legacy)

Enforcement

Back Office and Mobile

Back Office only

Actions Supported

Required, Recommended, Prohibited, Override

Required (via rule), Override (price/cost)

Conditions

Job/ticket-level + field conditions (e.g., location, accessorial type, site restrictions)

Quote-level only

Compliance

Blocks prohibited items and prevents ticket completion if conditions are violated.

No support for prohibited actions

Setup Tool

Admin Tool – Conditional Pricing

CPQ Rule Engine

Highlights

Advanced Pricing Module FX CPQ (Legacy)
  • Rules apply across Back Office and Mobile workflows.

  • Compliance actions include:

    • Prohibit Item (blocks item addition)

    • Add Required Item

    • Recommend Item

    • Override Price/Cost

  • Supports location-based and accessorial triggers for dynamic compliance.

  • Requires Mobile sync profile configuration to dispatch price books and staged data.

  • Rules apply only during quote creation in Back Office.

  • Focused on applicability and pricing overrides.

  • No support for prohibited or recommended actions.

  • Conditions limited to quote-level attributes (e.g., account, segment, geography).

Common Use Cases

  • Apply remote site surcharges based on job location

  • Increase handling cost for hazardous material accessorial

  • Enforce mandatory safety items when restricted site flags are present

  • Prevent use of non‑compliant SKUs in regulated environments

Step-by-Step Setup Guide

Complete these steps in order.

1. Confirm Prerequisites

Licenses

  • FieldFX Base Managed Package

  • FieldFX E‑Ticketing

  • Advanced Pricing Module (purchased separately)

Installed Components

  • Latest FieldFX Managed Package

  • FieldFX Mobile app with connected app configuration

User Permissions

System

API Enabled, Customize Application, View Setup and Configuration

Object Access

FX5__Price_Book__c, FX5__Price_Book_Item__c, FX5__Field_Rule__c, FX5__Field_Action__c, FX5__Staged_Data__c

Apex Class Access

all FX5 pricing and sync classes

Visualforce Page Access

all FX5 admin pages

Admin Tool Permission Sets

  • AdminTool_Conditional_Pricing

  • AdminTool_Price_Book_Rules

  • AdminTool_Sync_Profile_Wizard

Process
  1. Ensure there is an active Advanced Pricing Module license.

  2. You have correctly configured Price Books and items in Back Office.

  3. Sync Profile configuration for Mobile enforcement:

    • Job and Price Book Dispatch enabled

    • Staged data permissions validated for Mobile users

  4. FieldFX Managed Package and Mobile app installed and updated.

2. Navigate to Conditional Pricing

  1. Navigate to FieldFX Admin ToolsConditional Pricing.

  2. Click New Rule.

  3. Define rule conditions:

    • Example: Job Location = "Remote Site"

    • Example: Accessorial Type = "Hazmat Handling"

  4. Continue with 3. Define Rule Actions.

3. Define Rule Actions

  1. Under Actions, select:

    • Override Price/Cost.

      Override values apply only when rule conditions are met and do not permanently modify the base price book.

  2. Enter override details:

    • Specify target fields (Price or Cost).

    • Input override values or formulas (e.g., Price = 200, Cost = 150).

  3. Optionally combine with other actions (e.g., Recommend Item).

  4. Save and activate the rule.

  5. Continue with 4. Configure Sync Profiles.

4. Configure Sync Profiles

  1. In the Sync Profile Manager, configure sync profiles to dispatch updated price books and rules to Mobile.

  2. Validate that staged data permissions are correct for field users.

  3. Continue with 5. Test the Rule.

If sync profiles do not include Job and Price Book dispatch, Mobile users will not receive enforcement or override behavior.

5. Test the Rule

Test in Back Office and Mobile:

  • Create a sample job or ticket that meets the defined conditions.

  • Verify that the overridden price or cost appears correctly.

  • Confirm that compliance actions (if any) behave as expected.

Best Practices

  • Use clear naming conventions for rules to simplify maintenance

  • Always define effective dates to prevent unintended overrides

  • Test in a sandbox environment before deploying to production

  • Document logic for audit and training purposes