separate product REAL weight and dimensions, and SHIPPING weight and dimensions: a) make sense? b) how to implement?

My client would like REAL weight and size shown for the customer's interest, AND SHIPPING weight and size (not necessary to show) so that he doesn't under bill for items that will have a significant weight and size added by packaging —for example, fragile items might require an increased weight and size in the actual box and padding.

Is this totally wrongheaded in approach or is there a more elegant solution than two sets of weight and size columns in the database?

If it's a legit consideration for UPS shipping, where and how would I alter the normal requests for this information.

Thanks.

Since they want to show one weight and size, but use a different wight and size for the shipping calculation, you need separate columns for each in the Database, and also in the cart object.

When you create the cart display, choose to show the real weight and size columns in the display.

In the UPS shopping server behavior, you will be able to select the cart columns to use for passing the weight and dimensions for the package.

Thanks so much!

you're welcome.

Again, regarding sending a REAL shipping set of sizes and weight to UPS, I have to ask in detail. I just glossed over this. Somehow I thought this was in the wizard (yep, bad reading comprehension).

With what file open do I access the UPS server behavior from the server behavior panel? And, if I've already created the checkout pages, once I alter this server behavior to send REAL sizes and weight, what changed pages will I need to upload to the live site?

Thank you.

Yes, you access it through the server behaviors panel.

only the page the server behavior is on will need to be uploaded.