Aerodrome Documentation

Article content

Shipping exceptions are used to override the base shipping rules set within the partner portal on a per product basis. In Aerodrome, there are two different ways to modify shipping exceptions, and both of the following methods are accessed via the Product Catalog.

The first method is by accessing the Product Details Window and entering Edit Mode. From here you can add an entry to the Shipping Exceptions grid and configure your exception.

The second method is to use a bulk operation from the Product Catalog. From within the product catalog manager:

  1. Select the products you want to add an exception for by checking the checkbox within the far left column in the product grid.
  2. Click the "Bulk Action" button, and select "Add Shipping Exceptions"

You will now see the shipping exception manager window appear. If any of the selected products had shipping exceptions configured, you will see them all appear within this grid. Any exceptions visible within the grid will be applied to each of the selected products.
Note: Products may have conflicting exceptions configured. If this is the case, you can either edit or delete the exceptions directly in the bulk interface.

Shipping Exceptions Manager
Fig. 1

Within the shipping exceptions grid, you will find the following columns:

  • "Fulfillment Node" – Shipping exceptions are configured on a per-fulfillment node basis, meaning the product can have separate shipping rules set for each configured fulfillment node.
  • "Method" – A general shipping method to override. This cannot be used with Service Level.
  • "Level" – The service level to override. If you have configured shipping by level in the Jet partner portal, then you would select the level here instead of using Method
  • "Exception" – The shipping exception type:
    • Exclusive – The product should only be shipped using the shipping method or shipping level specified. There can only be one exclusive shipping method per fulfillment node.
    • Restricted – The product cannot be shipped using the shipping method or shipping level provided.
  • "Charge" – Based on the value of the "Override" column, this amount is:
    • "Additional Charge" – The amount added to the default shipping charge
    • "Override Charge" – The total amount charged for shipping
  • "Override" – Modifies the behavior of "Charge"
    • "Additional Charge" – A charge that is added to the default shipping charge.
    • "Override Charge" – A charge that overrides the default shipping charge.

For any product that always ships freight, please set up a shipping exception by selecting a freight service method or level.
Instead of the "Freight" method, the following service_level values will display different fulfillment expectations to customers at checkout:

  • Scheduled (freight) -- will display freight delivery with 5 to 10 day delivery expectation
  • Scheduled (freight 11 to 20 day) -- will display freight delivery with 11 to 20 day delivery expectation
  • 5 to 10 Day -- will display ground delivery with 5 to 10 Day delivery expectation
  • 11 to 20 Day -- will display ground delivery with 11 to 20 Day delivery expectation

Adding Free Shipping

Adding free shipping isn't very straightforward, and must be configured as a shipping exception on a per-product basis.

  1. Select the fulfillment node the product will ship from. (This will only affect a single node. If the product has inventory in multiple nodes, you would need to set up an exception for each node individually)
  2. Do not set "Method"
  3. Set "Level" to the level you wish to offer for free
  4. Set "Exception" to "exclusive"
  5. Set "Charge" to zero
  6. Set "Override" to "Override Charge"

Some Rules

  • Must set a shipping method OR a shipping level
  • Both override type and charge amount are required when exception is not set to "Restricted"
  • Restricted exceptions must be associated with methods that are enabled by the merchant at the fulfillment node
  • A merchant cannot restrict all methods at a fulfillment node
  • If an Exclusive exception is specified at a node, then no other exception cannot be listed at that same fulfillment node