LET’S BOUNCE INFLATABLES SHIPPING INFORMATION

Last updated on February 25, 2021

IMPORTANT SHIPPING INFORMATION:

At Let’s Bounce Inflatables Ltd. we are using several reputable shipping carriers at discounted rates. We, in turn, pass these shipping discounts on to you. You also have the option of arranging your own shipping. In either case, Let’s Bounce Inflatables Ltd. has no control over the delivery of your shipment and the condition it may arrive in. We are diligent in ensuring your shipment is properly prepared and packaged for safe delivery. The shipping carrier assumes responsibility once they pick-up your shipment.

 

LTL (Less Than Truckload):   

The majority of the products we sell are very large and heavy and a lot of shipping companies like Canada Post do not deal with large Items. We use the services of LTL freight carriers, to handle large shipments. LTL carriers handle deliveries differently than small package shipping companies. Please let us know in advance if any of these options are required. 

  • Residential Delivery
  • Lift Gate Service
  • Inside Delivery
  • Limited Access Delivery
  • Arrival/Delivery Notification

LTL carriers charge extra for the services above. Additional charges will apply if we do not know in advance that the above services are required.

 

COST AND PRICE RANGES TO MAJOR CANADIAN CITIES:

 

Order Price RangesShipping Cost
$0.01 CAD–$495.00 CAD$50.00 CAD
$495.01 CAD–$750.00 CAD$100.00 CAD
$750.01 CAD–$1,200.00 CAD$150.00 CAD
$1,200.01 CAD–$3,000.00 CAD$250.00 CAD
$3,000.01 CAD–and up$0.00 CAD

These shipping costs do not include the above-mentioned LTL carrier charges.

 

UPON RECEIPT OF YOUR ORDER:

Upon receipt, please make sure that you inspect your entire shipment prior to signing for your order. Check for missing items and/or damages. If you find anything, let the delivery person know and take a picture of it, and clearly write it out on the paperwork that the delivery person gives you to sign. Contact us immediately after so that we can help you in getting the issue resolved.