How to Apply Advanced Conditions in a Charge Profile

Modified on Thu, 12 Jun at 7:07 PM

How Advanced Conditions Work

Each condition is made up of three parts:

  1. Load Parameter – The specific attribute of the load to evaluate.

  2. Condition Type – The logic used to match values. Options:

    • Any in – Rule applies if any of the selected values match.

    • Not in – Rule applies if none of the selected values match.

  3. Values – The values to compare against. These vary depending on the load parameter.

When creating multiple rules, and a load must match all rules (logical AND) for the Charge Profile to apply.


Available Load Parameters and Definitions

Below is a list of the 33 available Load Parameters, along with a brief description of each:


Load ParameterDefinition
Load TypeType of load selected.
CustomerThe customer associated with the load.
PortPickup location for the load.
ConsigneeDelivery location of the load.
Chassis Pick UpChassis pick-up location in routing.
Container ReturnContainer return location.
Chassis TermChassis termination location.
Container TypeType of container used.
Container SizeSize of the container.
Container OwnerOwner of the container.
Chassis TypeType of chassis used.
Chassis SizeSize of the chassis.
Chassis OwnerOwner of the chassis.
TerminalTerminal to which the load belongs.
Commodity ProfileCommodity type in the container.
Commodities - WeightWeight of the commodity (uses different condition logic).
HotIndicates if the load is marked as "hot".
HazmatIndicates if the load is hazardous.
ReeferIndicates if the load is refrigerated.
LiquorIndicates if the load contains alcohol.
City-StateCombination of city and state for the delivery location.
StateState of the delivery location.
Delivery DayDay of the delivery (from time-in).
Delivery Time (24 Hours)Hour of the delivery (24-hour format).
City GroupsGroups of cities the delivery location may belong to.
OverweightIndicates if the load is marked as overweight.
Drop LocationDrop container or lift-off event location.
DroppedRefers to container drop timing.
GensetIndicates if the load requires a genset.
CSRCSR (Customer Service Rep) assigned to the load.
StopoffType of stopoff selected in routing.
Delivery CountryCountry of the delivery location.
Postal/Zip Code GroupGroup the postal or ZIP code belongs to.

Best Practices

  • Use specific parameters when targeting particular load types or customers.

  • Combine multiple rules to create fine-grained conditions.

  • Always validate the condition logic aligns with pricing or operational goals.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article