Canada Post's XML doesn't let you specify units, just amounts. So this module explicitly converts the product weights to kg (which is what the Canada Post server expects), regardless of what your store units are. If you've set the product weight units and entered the product weight in those units on the product edit page, the conversion to kilograms is done automatically in the code. But this is why I really need you to do what I asked and print out *exactly* what is being sent to the Canada Post server, because the quote returned depends only on the numbers you send it.
The issue with dimensions ... this module uses a package size of 1x1x1 cm. Shipping rates (for *all* carriers, not just Canada Post) are based entirely on weight *except* in cases where the package is exceptionally light for its size - then the rate is based on the *expected* weight, known as "dimensional rate". If your package is not exceptionally light for its size, then choosing a small package size like this is the correct strategy, and indeed this is exactly what the carriers do on their own web sites when you get a "quick quote" (i.e., when you just type in origin, destination, and weight). The only time this is a problem is when a dimensional rate should be charged.
None of Ubercart's shipping modules handles dimensional weights, because the packaging problem is intractable without many constraints. For example, what size package would you have Ubercart assume if you had two 80cm x 40cm x 10cm products in an order? Would it be 80x80x10, or 80x40x20, or 160x40x10 ? Do you really have boxes that fit exactly two of these items with no room to spare, or do you have to use a larger box? How about 3 of these items? How about two of these items plus some number of smaller 10cm x 10cm x 10cm items? Without knowing exactly what your available box sizes are, and without a packing algorithm that boxes up items exactly as a human would (i.e., not necessarily the most efficient way in the smallest possible box for that order, but with cushioning material and extra padding material for items that aren't already individually boxed and without the extra padding for items that ship in a manufacturer's packaging, etc.) there is no way to accurately determine the true dimensions of the shipping box. I suppose a packaging module could be written to make a fair guess, but it would have to have a lot of configuration parameters. Regardless, that's outside the scope of a shipping module like this.
Depends on what you're shipping, of course, but I think a common reason people need to deal with dimensional rates is when they have large, light items that ship alone. For those, it's easy to just enter a dimensional weight rather than the real weight on the product page. Other common situations might be just as easy to deal with.


