Blog

Most common carriers don't handle packages that weigh more than 150lbs.  Or, if they do, they have special freight rates.  Usually, you get the best rate by negotiating with an LTL trucking service.  Unfortunately, most don't have an API that can be called from an eCommerce system, and if they do, nopCommerce does not have any out-of-the-box.   (Also, Freight Rates can be a little tricky, because they sometimes require a Freight Class, but we won't go into that here)

In a previous blog, I showed how Shipping Director can deal with Freight scenarios by using your own rate lookup tables .  Here's another way that has a carrier's freight rates entered using the Shipping.ByWeight plugin, and then use Shipping Director to handle using Fedex plugin if weight is <= 150 lbs, or use ByWeight plugin to get freight rate if weight is > 150 lbs

Type	Name	Expression	Rate Expression	Surcharge Expression
Decimal	Freight Fuel Surcharge %	30.7
OptionExit	FedEx	[$TotalWeight] <= 150	Shipping.Fedex
String	State	ShippingAddress.StateProvince.Abbreviation
ErrorExit	No Freight State	"AK,HI,ID,MT,NM,ND,SD,TX,WY".Contains([State])
Option	Freight	true	Shipping.ByWeight	[$Rate] * ([Freight Fuel Surcharge %] / 100.0)

The freight rates don't change that often, but Fuel Surcharge % does, so it can be easily adjusted.
Also, you can prevent customers from shipping freight to the states that your carrier does not handle - Use the Decription Expression to show them a friendly message.

Be sure your expression is of the correct type whether assigned to a variable, or used in one of the Expression fields of a record.  Here are the types for the various Expression Fields:

Record/ExpressionName	Data Type	Description
Option and OptionExit
Expression	Boolean	When evaluates to true, the Option is presented to customer
Rate Expression	Decimal	The calculated Rate + Surcharge appears to customer as the rate
Surcharge Expression	Decimal
Name Expression	String	If present, will override the record Name displayed to customer
Description Expression	String	If present, the description appears under the Name/Rate line
Error and ErrorExit
Expression	Boolean	When evaluates to true, the Error message is presented to customer
Description Expression	String	Required.  The description appears under the Name/Rate line
Packing		See the Packing blogs
Expression	Boolean	When evaluates to true, the packing is performed
Packing Method	literal	E.g. Packing.FirstFitSingleBox  .
Requires Own Package Expression	Boolean	Evaluated for each item
Sender Expression	Boolean	Evaluated for each item
Exclude Item Expression	Boolean	Evaluated for each item
Reference		See the Reference Type blog
Expression	literal	A reference is a type of variable that is really just a shortcut.
Notes
Booleans	You can use literals 'true' and 'false'.   (lowercase, no quotes)
Strings	Be sure to put literals in double quotes. To put a double quote in your literal, use two double quotes. If using String.Format(), beware of localization.
Decimals, Doubles, Singles	Literals must include a decimal point "." regardless of localization If using e.g. Decimal.Parse(), beware of localization.
DateTimes	Construct literals using DateTime() - e.g. DateTime(2010,8,9).  If using DateTime.Parse(dateString), beware of localization parsing.
Rate and Surcharge Expression	Numeric only.  Do not include any leading currency symbol.

Here's a list of all built-in variables.  Note that they all start with a "$".  As with user defined variables, the must be enclosed in brackets when used - e.g. [$TotalWeight].

     

Shopping Cart Properties - Set by system at start of rate calculation
$TotalWeight Decimal   uses ShippingService.GetShoppingCartTotalWeight()

$SubTotalWithoutDiscounts Decimal    (uses orderTotalCalcService.GetShoppingCartSubTotal() )

$SubTotalWithDiscounts Decimal

$SubTotalWithoutDiscountsInclTax Decimal

$SubTotalWithDiscountsInclTax Decimal

$ProductTotalWithoutDiscounts Decimal    (uses PriceCalculationService.GetSubTotal() )
$ProductTotalWithDiscounts Decimal

$IsFreeShipping Decimal   uses OrderTotalCalcService.IsFreeShipping()

Shipping Director Record - Set by system for each row (used in debugging and error messages)
$Id Integer   SD record's Id field
$Order Integer   SD record's Order Field
$Name String   SD records's Name field
$Expression String   Set before each expression evaluated (Expression, RateExpression, SurchargeExpression, etc.)

Option Processing - Set by system when the record type is Option, OptionExit, OptionReplace (OptionReplace available only in SD ver 1.05 and above)
$Name String 
$Description String
$Rate Decimal (e.g. surcharge expression can use $Rate)
The Option record's Expressions can reference $Name & $Description & $Rate variables.  Thus, you can adjust the data returned by external shipping rate methods.  (Reminder – an external shipping rate method is called in the Option’s Rate Expression – e.g. Shipping.Fedex).
External shipping rate methods can return multiple options/rates.  If the $Name of an external shipping rate option is set to "", then that option is removed.
Example: To show an option name of just "Ground" and "Priority" rather than "FedEx Ground" and "FedEx Priority", use [$Name].Replace("FedEx ", "") in the NameExpression to remove the word "FedEx " from the option name.

 

Shipping Option Request properties (These are passed to other shipping rate calculation methods to override the other methods' configuration page.  Not supported by all shipping rate methods.)
$ZipPostalCodeFrom String
$StateProvinceFrom String
$CountryFromTwoLetterIsoCode String

Set by system after other shipping rate calculation method is called
$ShippingOptionsCount Integer

SD sets this after using an external shipping plugin (or SQL) with the total # of shipping rate options it returned.  It's not typically used, but if you are doing something where you think no options will match, then you should check it and say something like "call for rate".

Packaging
$Sender string ""   Set by system when a package is rated manually (not external shipper rate).  Can then be used in Option's Rate, Surchage, Name, Description expressions
$PackageCount Integer 0   Set by system after packaging.  Although defaults to 0, if no Packaging is done, the system actually creates 1 package with all shopping cart items just before rate calculation.

Packaging using PackingFirstFitSingleBox
$PackageBoxWeight Decimal
$PackageBoxMaxWeight Decimal
$PackageBoxHeight Decimal
$PackageBoxLength Decimal
$PackageBoxWidth Decimal
$PackageItemAddWeight Decimal
$PackageItemAddDimension Decimal
$PackageShrinkPercent Integer 0 - Used by PackingFirstFitSingleBox - If $PackageShrinkPercent > 0, and the volume actually packed is less than this % of the given box volume, then this will shrink the final box to its actual packed content volume, rather than the given box volume.  ("less than this %" => The idea is if the box is "almost full", then use the box dimensions)

Packaging's SenderExpression can evaluate to a string that can contain Ship From Location information.  The string is of the form:
"State=...; ZipCode=...; Country=...;"
This allows different Ship From address for each Sender (see Shipping Option Request properties above):

$PackageBox variable (shorthand for setting many package attributes in one line)
 e.g. $PackageBox   "MaxWeight:40,Height:15,Width:15,Length:15"
 Here's how each shorthand attribute corresponds to the built in variable:
    MaxWeight    => $PackageBoxMaxWeight
    Height       => $PackageBoxHeight
    Width        => $PackageBoxWidth
    Length       => $PackageBoxLength
    Weight       => $PackageBoxWeight
    AddWeight    => $PackageItemAddWeight
    AddDimension => $PackageItemAddDimension
    ShrinkPercent=> $PackageShrinkPercent

Rate Request Type - When Packaging, can be set by user to indicate the way that rate requests are made to other rate calculation methods when Packaging
$ShippingRateRequest String
    "OneRequestForAllPackages"
    "OneRequestPerPackage"
    "OneRequestPerSender"

E.g. "OneRequestPerPackage" => Get FedEx rates separately for each package

if $ShippingRateRequest is not set by user, then the system will default depending on if the Packing SenderExpression used:
    if no SenderExpression then "OneRequestForAllPackages" else  "OneRequestPerSender"

Debugging

$Debug boolean false   When true, detailed messages are written to the system log.

(Note:   Because log messages are not HTML formatted, they can be hard to read in the browser.  So, when viewing a System Log record, click View to see the log detail page.  Then, right click the page and "View Source".  Scroll down (a bit more than half way) until you see the plain text messages.)

Flow Control  (SD ver 1.05 and up)
$Goto Integer 0 Set to a Order/Line number. Can be conditional and dynamic. Set to 0 to skip.  E.g. Use ternary if/then/else operator $Goto condition ? 100 : 0 ==> "If condition then Goto 100 (else goto next line)"

Special Functions
Special functions must be assigned to a String variable and must be the first word in the variable’s Expression field.  The expression cannot be complex: E.g. it can be like GetLocaleString("...") or GetLocaleString([someotherstringvar]), but cannot include any operators.

GetLocaleString(<string>)   get a language specific message.
GetSetting(<string>)        get a setting

In this scenario, our requirement is to prevent shipping certain products to countries outside of the European Union (EU 27).  Similar to the last blog, you should set up an unpublished category for the restricted products.  Then, in SD, we check if both the shipping address is outside the permitted countries and the cart contains restricted products.  If this condition occurs, the ErrorExit line will cause the message "Sorry, we can't ship restricted products outside the EU" to appear to the customer, and prevent them from checking out. (The double quotes are required because Description Expression is an expression) 

Order	Type	Name	Expression	Description Expression
30	String	EU_27	"AT,BE,BG,CY,CZ,DK,EE,FI,FR,DE,GR,HU,IE,IT,LV,LT, LU,MT,NL,PL,PT,RO,SK,SI,ES,SE,GB,"
40	Boolean	IsRestrictedCountry	![EU_27].Contains(ShippingAddress.Country.TwoLetterIsoCode)
50	ErrorExit	Restricted Products	[IsRestrictedCountry] and Items.Any(Product.HasCategory("Restricted Shipping"))	"Sorry, we can't ship restricted products outside the EU"
60	Option

  Order Line 60 would be whatever Option(s) you would want to offer.

(The above blog was updated 9/8/2013.  Older versions of Shipping Director did not have HasCategory() function, and used a more complex expression to get the Category:

Order	Type	Name	Expression	Description Expression
10	Reference	categories	ProductVariant.Product.ProductCategories
20	Reference	categoriesAny_Restricted	[@categories].Any(Category.Name = "Restricted Shipping")
30	String	EU_27	"AT,BE,BG,CY,CZ,DK,EE,FI,FR,DE,GR,HU,IE,IT,LV,LT, LU,MT,NL,PL,PT,RO,SK,SI,ES,SE,GB,"
40	Boolean	IsRestrictedCountry	![EU_27].Contains(ShippingAddress.Country.TwoLetterIsoCode)
50	ErrorExit	Restricted Products	[IsRestrictedCountry] and Items.Any([@categoriesAny_Restricted])	"Sorry, we can't ship restricted products outside the EU"
60	Option

In this scenario, our requirement is to offer Standard Shipping and Next Day Shipping methods with fixed amount for each: £3 for Standard and £10 for Next Day).  However, only certain products can be sent on Next Day delivery.  We need the checkout process to exclude Next Day if not applicable.   Additionally, if the cart has a mix of products, some that allow Next Day and some that don't, we want to charge BOTH the Standard and Next Day delivery charge combined on the order (£3 + £10 = £13).

So, we always want to offer Standard shipping at £3, and then additionally offer Next Day if the cart has any Next Day eligible products – but if the cart has a mix, then since we need to ship out two deliveries, we want to charge for both.  Here are the possible cases:

No Next Day eligible products:

Standard              £3

All Next Day eligible products:

Standard              £3

Next Day             £10

Some Next Day eligible products, and some not:

Standard              £3

Next Day             £13

And here’s one way to do it in Shipping Director:

Create a (non-published) Category called “Can Ship Next Day”, and put all eligible products in that category.   (Remember, products can be in more than one category).  Then, just configure Shipping Director! 

Order	Type	Name	Expression	Rate Expression
10	Reference	canShipNextDay	Product.HasCategory("Can Ship Next Day")
30	Option	Standard	true	3
40	OptionExit	Next Day	Items.All([@canShipNextDay])	10
50	OptionExit	Next Day	Items.Any([@canShipNextDay])	13

 

(The above blog was updated 9/8/2013.  Older versions of Shipping Director did not have HasCategory() function, and used a more complex expression to get the Category: 

Order	Type	Name	Expression	Rate Expression
10	Reference	categories	ProductVariant.Product.ProductCategories
20	Reference	categoriesAny_CanShipNextDay	[@categories].Any(Category.Name = "Can Ship Next Day")
30	Option	Standard	true	3
40	OptionExit	Next Day	Items.All([@categoriesAny_CanShipNextDay])	10
50	OptionExit	Next Day	Items.Any([@categoriesAny_CanShipNextDay])	13

First, I recommend checking if a Country/State/Zip has been provided, because the “Estimate Shipping” will work even if they are not selected, and depending on rate calculation method (shipping plugin), you could get funny results, or an error. (Only US and Canada have states.)   For this, we use the ErrorExit record Type.  This will Exit if the Expression (condition) evaluates to true, and the customer will see the message calculated in the Description Expression.  Note, that this is a String Expression, so be sure to include quotes for a literal value.

Order	10
Type	ErrorExit
Name	Missing Country State Zip
Expression	ShippingAddress.Country = null or ShippingAddress.ZipPostalCode = null or ("US,CA".Contains(ShippingAddress.Country.TwoLetterIsoCode) and ShippingAddress.StateProvince = null)
Description Expression	"Please Enter Country, State, and Postal Code"

Then, let’s say we want to prevent shipping if the State is Alaska or Hawaii.  We would use the ErrorExit type here too:

Order	20
Type	ErrorExit
Name	No Shipping to Alaska and Hawaii
Expression	"AK,HI".Contains(ShippingAddress.StateProvince.Abbreviation)
Description Expression	"Sorry, we can’t ship to Alaska or Hawaii"

The condition Expression could have also been written as

Expression

ShippingAddress.StateProvince.Abbreviation = "HI" or ShippingAddress.StateProvince.Abbreviation = "AK"

But when using an “or”, be sure to use parenthesis if you have a more complex expression that includes “and”s too.

Alternately, you may just want to exclude just Ground shipping to Alaska and Hawaii.  For example, you want to use the Shipping.ByWeight rate calculation method, but don’t want to offer Ground to Alaska or Hawaii.  Then the above would instead be entered with an Option type:

Order	20
Type	Option
Name	Ship By Weight but no Ground for AK and HI
Expression	true
Rate Expression	Shipping.ByWeight
Name Expression	"AK,HI".Contains(ShippingAddress.StateProvince.Abbreviation) and [$Name].Contains("Ground") ? "" : [$Name]

For the Option type, the Expression field is a condition.  If it evaluates to true, then the option record is processed, otherwise it's skipped.  The Rate Expression can either be a decimal expression calculating the actual rate you want to charge, or the name of a shipping plugin.  The Name Expression calculates the shipping option Name shown to the customer.  However, if the Name Expression evaluates to blank (""), then Shipping Director will exclude the Option.  The [$Name] is a built-in variable that contains the Name of the shipping option as returned by the other rate caclulation plugin.  So, here we are saying "if the state is Alaska or Hawaii, then exlude the named option, else show the named option".  The If-Then-Else is achieved using the " ? : " ternary operator -  condition ? if-true : if-false.

Here's a simple but useful shipping scenario:

First Item shipping would be £3.50
Each additional Item adds £1.00

So, for example, 3 items would be £3.50 + £1 + £1 = £5.50

This is easily handled by Shipping Director with a single Option type record:

Type:	Option
Name:	Shipping Rate
Expression:	true
Rate Expression:	3.50 + ((Items.Sum(Quantity)-1) * 1.00)

You can even decide to charge different rates for different countries or postal codes.  For example, shipping to the Highlands and the islands should be

First Item shipping would be £5.50
Each additional Item adds £1.50

For that, we would just add an OptionExit type record ordered before the previous one.  

Type:	OptionExit
Name:	Shipping Rate
Expression:	",AB,BT,DD,HS,IM,IV,KA,PA,PH,TR,ZE,".Contains( Zip.Substring(0,2) )
Rate Expression:	5.50 + ((Items.Sum(Quantity)-1) * 1.50)

OptionExit will exit with the calculated rate when the "Expression" condition is true.  Whereas "Option" with true expression will return the caclulated rate, and continue looking for more Options.

(Note, the above postal codes are just examples.  Determining all the actual codes for the Highlands & islands is more complex)

And finally, a little about the "Name:" field.  This is the option's name displayed to the customer.  In the examples above both Option records used the same Name "Shipping Rate".  But, the Highlands Option could have used "Shipping to Highlands and Islands".   Or, you can also include a "Name Expression".  If none is present, then the "Name" is displayed to the customer.  The Name Expression allows you to caclulate the option's name displayed to the customer.  For examples, see the other blogs like this one where the weight is included in the option name, and see this blog about using localized resources

UPDATE:

The postal code expression above was updated;  in older versions the "Zip" part was written as

  ShippingAddress.ZipPostalCode.Substring(0,2)

Additionally, in any version, you should probably have a prior rule to check that a Zip/Postal code was entered, otherwise an error will result - e.g.

ErrorExit   String.IsNullOrWhitespace(Zip)         "Please enter a zip/postal code"

(Updated 11/29/2013 for Shipping Director versions for nopCommerce 3.x) 

For external shipping rate methods (carrier plugins like FedEx, USPS, etc.), which can return many options, it may be desirable to conditionally eliminate some options.

In this example, we only offer USPS Media Mail if all items in the cart are books:

Order	Type	Name	Expression	Rate Expression	Name Expression
10	Boolean	CategoriesAllBooks	Items.All(Product.HasCategory("Books"))
100	Option	USPS	true	Shipping.USPS	[$Name].Contains("Media Mail") and ![CategoriesAllBooks] ? "" : [$Name]

Of course you're not limited to checking Categories.  For example, you could also eliminate an option based on there being any item in the cart with the Product Name Length greater than X.  E.g.

Items.Any(ProductVariant.Product.Name.Length > 12)

_________________________________________________________________________________________________  

Here's the old version for nopC 2.x having Product Variants, and prior to SD having HasCategory() function:

Order	Type	Name	Expression	Rate Expression	Name Expression
10	Reference	categories	ProductVariant.Product.ProductCategories
20	Boolean	categoriesAllBooks	Items.All([@categories].Any(Category.Name = "Books"))
100	Option	USPS	true	Shipping.USPS	[$Name].Contains("Media Mail") and ![categoriesAllBooks] ? "" : [$Name]

As previously mentioned, I'll be posting some more simple shipping examples...

Only allow shipping if the destination country is Mexico:

Create this record with a low "Order" (e.g. 10) , so that it gets evaluated before any shipping Options.