Which Authorization Restriction Should I Use?

A Customer Authorization carrier restriction defines which carriers are allowed to load for a specific customer, while a Carrier Authorization customer restriction defines which customers a specific carrier is allowed to load for at a specific terminal. 

Option 1: Control which Carriers can load for a Customer

Use Carrier Restriction on a Customer Authorization

Choose this when: 

• A customer requires only specific approved carriers 

• You want to block all other carriers from loading for that customer 

• You want to control who can use that customer’s LCNs 

Result: 

• Only the selected carriers can load for that customer 
• All other carriers are denied for that customer

Option 2: Control which customers a carrier can load for at a terminal

Use Customer Restriction on a Carrier Authorization 

Choose this when: 

• A carrier should only load for certain customers at a specific location 

• A carrier is approved at a terminal but not for every customer 

• You want to limit a carrier’s access at a specific location 

Result: 

• The carrier can only load for the selected customers at that terminal 

• Loads for other customers are denied 

Option 3: Do I need both? 

You would use both restrictions together when you need two different layers of control that answer two different business questions. Use both restrictions together if you want: 

• A customer to allow only certain carriers, and 

• A carrier to be limited to certain customers 

Each restriction works independently and applies only where it is set. 

Scenarios

Scenario using Option 1: Carrier Restriction using a Customer Authorization

Situation: Control which Carriers can load for a Customer

• Customer B ⛽ wants to use only Carrier Z 🚚

• Carrier Z 🚚 is allowed to load for many customers 

How you configure it

• Set a Carrier Restriction on Customer B’s ⛽ Customer Authorization 

• Do not set a Customer Restriction on Carrier Z 🚚

Result at the terminal

• Carrier Z can load for Customer B ✅ 

• Carrier Z can still load for all other customers ✅ 
• Non-Carrier Z carriers cannot load for Customer B ✅ 

Only one restriction is needed here. 

Scenario for Option 2: Customer Restriction using a Carrier Authorization

Situation: Control which customers a carrier can load for at a terminal

• Carrier Z 🚚 is only allowed to load Customer B ⛽
• Customer B ⛽ can have any carrier load for them 

How you configure it

• Set a Customer Restriction on Carrier Z’s 🚚 Carrier Authorizations at the terminals where you only want them to load for Customer B
• Do not set a Carrier Restriction on Customer B

Result at the terminal

• Carrier Z can only load for Customer B ✅ 
• Carrier Z cannot load for any other customers ✅ 
• All carriers can load for Customer B ✅ 

Only one restriction is needed here. 

Scenario for Option 3: Mutual Carrier and Customer Restrictions

Situation: Using both restriction types together

• Customer A ⛽ requires that only Carrier X 🚚 and Carrier Y 🚚 can load for them 

• Carrier X 🚚 is approved to load at the terminal, but should only ever load for Customer A ⛽

• Carrier Y 🚚 can load for all customers 

How you configure it 

1. On Customer A’s ⛽ Customer Authorization, select:  
   1. Carrier X 🚚
   2. Carrier Y 🚚
2. On Carrier X's 🚚 Carrier Authorization at the terminal(s), select:
   1. Customer A ⛽
3. On Carrier Y's 🚚 Carrier Authorization at the terminal(s), do not set any restrictions

Result at the terminal 

• Carrier X can load for Customer A ✅ 

• Carrier X cannot load for any other customers ✅ 

• Carrier Y can load for Customer A ✅ 

• Carrier Y can still load for all other customers ✅ 

• All other carriers cannot load for Customer A ✅ 

Both restrictions are doing different jobs, and together they create a tight, intentional control model.