The plugin prices orders by weight, value, destination, and product group. Some shipping questions sit outside those four, and it is quicker to say where the edges are than to let you find them at checkout. Each section below names a limit and the way people work around it — often a small change of approach covers the need completely.
Per-item and quantity rates
There is no "charge per item" field and no quantity condition. Rules see total weight and total value, never a count.
When a product line has a uniform weight, weight is quantity: charging $4.00 every 0.5 kg for a product weighing 0.5 kg charges $4.00 per unit. Quantity based shipping builds that out, including bulk pricing. For carts mixing products of very different weights, the trick stops being accurate. Tree Table Rate Shipping has a real quantity condition and a per-item rate — its conditions and calculations page shows how they are written.
Dimensions and volumetric weight
Box sizes are not read, and volumetric weight is not calculated. A large light parcel and a small heavy one are the same to the rules if they weigh the same.
The practical workaround is to put bulky goods in their own shipping class and price that class higher, or to enter a dimensional weight in the product's weight field when it is consistently the larger figure. Neither is a substitute for a genuine volumetric calculation. Tree Table Rate Shipping does have a volume condition and a volume rate; conditions and calculations covers them alongside the weight equivalents.
Packaging weight and box packing
There is no field for the weight of the box, and no attempt to decide how many parcels an order needs. The plugin prices one shipment from one total weight.
If your carrier charges by gross weight, shift the rule boundaries down by the packaging: a 1–3 kg carrier bracket with a 0.15 kg box becomes a 0.85–2.85 kg rule. For genuine multi-box splitting you need a plugin that models packing: Tree Table Rate Shipping groups order items into packages before pricing them, which is explained in packages and grouping.
Postcodes inside rules
Rules match countries and states, not postcodes. Postcode precision comes from WooCommerce shipping zones, which accept lists, wildcards, and ranges, and the method inside such a zone inherits that geography — see Shipping zones and the global method. What you cannot do is vary prices by postcode within one zone without creating a zone per area. Tree Table Rate Shipping matches postcodes in the rule itself, with wildcards and ranges — see its zip or postal codes guide.
Customer and payment conditions
Rules cannot depend on the user role, the customer group, or the chosen payment method. Wholesale customers with their own free-shipping threshold are outside what the plugin expresses. Tree Table Rate Shipping has a customer condition for exactly this case.
Payment is a special case worth explaining, because it is a sequencing problem rather than a missing feature: in WooCommerce the customer picks shipping first and payment second, so a shipping price cannot react to the payment method. Cash on delivery is done the other way round — offer a shipping option for it, and restrict the Cash on Delivery gateway to that option with its own Enable for shipping methods setting.
Price caps and formulas
Charge fields take numbers, not expressions. There is no minimum or maximum shipping price, no percentage of the order value, and no arithmetic beyond the four kinds of charge. A cap is expressed as a weight bracket that charges the capped amount flat. If you need real minimum and maximum bounds on a calculated price, Tree Table Rate Shipping applies them as a modifier on the result.
Changing what the customer sees
The plugin produces shipping options and hands them to WooCommerce. It does not render the cart or checkout, sort the options, preselect one, or hide options belonging to other methods. It cannot display the cart weight on the checkout page, or hide Flat Rate when your free rule applies — those belong to WooCommerce or to the theme.
Shipping option titles are yours to write, in your own language, and they are translatable — the admin interface itself is English only. Compatibility covers the translation route.
When another plugin fits better
If your prices really do depend on item counts, volume, packing, customer roles, or postcodes at rule level, we would rather point you at a tool built for that. Tree Table Rate Shipping covers those cases, with a steeper learning curve in exchange: rules form a tree, each rule can capture part of the order, and the overview explains the model in a few minutes, while the crash course builds a working setup step by step. If you are unsure which side of the line your setup falls on, describe it to us, including the prices you want to end up with. We will tell you which of the two fits, and if it is this one, how to build it.