let's get started!

When using both Engineer Rates and Special Price Profiles within Service Geeni, it’s important to understand how the system determines which rate is applied; this is based on the pricing priority logic.

Service Geeni evaluates pricing using a defined hierarchy. The system will always apply the first valid rate it finds in the following order:

This means that Engineer-level pricing will always take precedence over Cost Code or Customer Special Pricing, unless no valid engineer rate exists.

If an engineer has a configured rate, the system will apply that rate before checking any customer-specific or cost-code special pricing.

As a result, even if a Special Price Profile is set up against a customer, it will not be used if an applicable engineer rate is present.

If the goal is to prioritise Special Price Profiles for certain customers, you have two options:

Remove the engineer’s revenue rate for the relevant cost codes.
This allows the system to fall back to:

Create a dedicated cost code for the special pricing scenario and:

This prevents the engineer rate from overriding the special price.