Index

• Shipping Rules UI Lesson 1: File management
• Shipping Rules UI Lesson 2: Creating Select Rules
• Shipping Rules UI Lesson 3: Creating Service Levels
  - What are Service Levels?
  - Creating a Service Level
  - Allocation types
• Shipping Rules UI Lesson 4: Setting up prices
• Shipping Rules UI Lesson 5: Use cases

 
What are Service Levels?

Service Levels are groups of services or products that you define and name. The products in a Service Level all have some common characteristics. Service Levels can be based on the speed of the delivery method like Express, Standard, and Next Day Delivery, but they can also be used for many other scenarios like Receiver Country, Goods type, etc.

For example, if you create a Service Level for each country you are shipping to, you can define all valid carrier products and conditions within each Service Level. Your warehouse staff then only needs to select a Service Level corresponding to the Receiver country, and the correct products and services will then automatically be selected. 

Basically, Service Levels are useful if you have multiple products that can be used for the same destination.

Important note: Service Levels are only applied if your entry product is included in one of your Service Levels. Service level name must be a minimum of 3 characters.
 

Creating a Service Level

A Service Level is created inside a Shipping Rules file, so you must start by creating a new file or editing an existing file. For a tutorial on how to create a new file, click here. 

1. Go to Drafts, click the wrench icon next to the file you want to work with, and choose Edit. 
   
   
2. Go to the Service Levels tab.
   
   
3. Click the New button and enter a name for the new Service Level.
   
   
   
   
4. Select the products that you want in your Service Level and click Create.  
   
   
5. Click the arrow to the left of the name to start defining conditions.
   
   
6. Select a group from the Group drop-down list. When you select a group, a new drop-down list will appear. Select a Field from this list.
   
   
7. Fill in the additional fields/drop-down lists that appear after the field selection. These fields or drop-down lists vary according to the group and the field that you selected.
   
   
8. You can add more Conditions by clicking the plus sign. This will create an additional Conditions line.
   
   
9. In the Allocation section, you have the option to set up allocation rules (see the explanation for each type below). These can be used to select a single carrier product if there are more valid alternatives when all other rules/conditions have been met.
   
   
10. When done with all settings, click the Save button located in the Service Levels section.

Note: If you have multiple carrier products and more than one proves to be valid when Shipping Rules are running, it will always choose the first valid product from the top of the list. You can change the order of your products by clicking the icon and dragging and dropping the product to a new position.

Allocation types 

These are the types of allocation rules that can be defined under Service Levels:

Preselected - If the selected product is valid then it will always be used.

Order - If more valid products are found, then the first product found in the products list of the Service Level will be used.

Lowest Price - Price is the amount calculated by Price Calculation. With this allocation type, the product with the lowest price will be used.

Highest Rank - Will look at the value you entered in the Rank field and select the product with the highest rank.

User selected - This will show a list of valid products in the user interface (Production in nShift On-premises or New in Ticket) to choose from.

Min count for product - the first X number of shipments per day will use this product. If you set the value to 100, then the specified product will be used 100 times before other products may be selected.

Distribution - Use a mix of listed products for a specific scope and distribute shipments with the same submit date (independent of being manifested or in outbox) according to a specified share. The share does not have to add up to 100. The distribution rule removes any product that is not valid and then calculates the share for each remaining product and selects the one that has the biggest difference between the intended share and the actual share. The scope can be "Installation", "location" or "Actor" when applied to an On-premises solution but only "Actor" can be selected for hosted solutions.

Fastest - Select the product with the earliest delivery. Configuration for ETA must be set up. Products without an ETA configuration will be excluded by this rule.