Skip to content
WPJury
No. 00789 WooCommerce

WooCommerce Table Rate Shipping: powerful, but expensive for basic rules

The verdict WooCommerce Table Rate Shipping is worth paying for when your store needs carefully controlled rates based on destination, weight, price, item count, or shipping class. It is not the best-value choice for simple weight brackets or a small catalog, because the annual price is high and the setup remains manual and rule-heavy.
Situational The ruling
Get v3.7.2

via WorldPressIT · complete package

Best for
  • stores with complex shipping zones
  • retailers using shipping classes
  • catalogs with mixed weights and product types
  • agencies managing detailed WooCommerce rules
Skip it if
  • you only need basic weight-based rates
  • you need live carrier quotes
  • you want box-packing calculations
  • you dislike maintaining rate tables
Version 3.7.2 Updated 17 Sep 2026 Licence GPL
WooCommerce Table Rate Shipping: powerful, but expensive for basic rules screenshot

WooCommerce Table Rate Shipping is a capable rules engine, not a complete shipping automation system. It lets store owners create multiple rates inside WooCommerce shipping zones and calculate charges from destination, product price, weight, item count, or shipping class. That makes it a strong fit for stores where a single flat rate would either overcharge light orders or destroy margins on heavy ones. The official documentation also supports four calculation approaches: per order, per item, per line, and per shipping class. ([woocommerce.com](https://woocommerce.com/document/table-rate-shipping/))

Its best feature is the level of control without requiring custom code. You can add handling fees, minimum and maximum costs, tax options, rate labels, priorities, and different rules for different shipping classes. A clothing shop could charge by weight, a book store could use item-count bands, and a mixed catalog could apply separate logic to bulky and lightweight products. The method works inside WooCommerce shipping zones, so the structure is familiar if you already understand WooCommerce shipping settings. ([woocommerce.com](https://woocommerce.com/document/table-rate-shipping/))

There is also a useful operational feature that is easy to overlook: the plugin supports CSV import and export for rate tables. That is valuable when an agency is moving a configuration between stores or when a carrier changes dozens of rates at once. The limitation is that the CSV covers the rate rows, not every surrounding setting, so importing a table does not eliminate all manual configuration. ([woocommerce.com](https://woocommerce.com/document/table-rate-shipping/))

The main weakness is complexity. WooCommerce’s own documentation warns that setup requires planning around shipping classes, zones, and the rates supplied by your courier. Overlapping rules, incorrect product weights, or a missing shipping class can produce incorrect checkout prices, and there is no built-in packaging algorithm that adds the weight of boxes or calculates how products should be packed. WooCommerce feature requests specifically call out missing container weight, volume conditions, product-level table rates, and limitations around calculating some multi-product orders. ([woocommerce.com](https://woocommerce.com/document/table-rate-shipping/))

Cost also changes the verdict. The official WooCommerce marketplace lists Table Rate Shipping at $119 annually and shows a 3.5 rating from 19 reviews. That is a substantial price for a plugin that still expects you to build and maintain the tables yourself. The review record is not a disaster, but it is noticeably less convincing than the free WordPress.org Table Rate Shipping for WooCommerce plugin, which lists a 4.6 average from 73 reviews. Those are different products, so the ratings are not a direct quality comparison, but they do show that cheaper options exist. ([woocommerce.com](https://woocommerce.com/products/?utm_source=openai))

Compared with WooCommerce Flat Rate Shipping, this extension is much better for tiered and conditional pricing; Flat Rate is enough when you only need a standard charge per order, item, or shipping class. Flexible Shipping is the more obvious alternative for stores that mainly need weight-based tables and want to start with a free plugin. PH Advanced Table Rate Shipping is worth comparing when you need similar conditions plus CSV management and product- or category-oriented rules. ([woocommerce.com](https://woocommerce.com/document/flat-rate-shipping/?utm_source=openai))

Verdict: buy it when shipping accuracy depends on several interacting rules and you value a WooCommerce-native extension. Otherwise, start with Flexible Shipping or WooCommerce’s built-in Flat Rate Shipping; they are easier to justify for simpler stores.

Questions people ask

Is WooCommerce Table Rate Shipping worth it?
Yes, if you need rates based on multiple conditions such as destination, weight, item count, price, and shipping class. For simple weight or flat-rate shipping, cheaper alternatives are usually better value.
Does WooCommerce Table Rate Shipping calculate live carrier rates?
No. It calculates rates from the tables and rules you configure. You must obtain your carrier pricing separately and enter the rules yourself.
Can WooCommerce Table Rate Shipping import shipping rates?
Yes. It supports CSV import and export for rate rows, although the surrounding shipping-method settings may still need to be configured manually.
Can it calculate shipping by product dimensions or box size?
The documented conditions focus on destination, price, weight, item count, and shipping class. It does not provide a full box-packing system, and WooCommerce has an open request for adding packaging weight.
What is the best alternative to WooCommerce Table Rate Shipping?
Flexible Shipping is the most obvious alternative for straightforward weight-based tables. PH Advanced Table Rate Shipping is a closer competitor when you need broader product, category, and CSV-based rule management.

Get WooCommerce Table Rate Shipping: powerful, but expensive for basic rules 3.7.2

Complete package, ready to install, via WorldPressIT.

Download

Other rulings

Markite: worth it for a focused digital marketplace, not a general store Markite is worth considering if you are building a WooCommerce marketplace for downloadable products and want a ready-made Elementor design with Dokan support. It is not the safest choice for a serious long-term store: the product has a small sales footprint, mixed feedback about bugs and demo differences, no WordPress.org presence, and relies heavily on third-party plugins for its core marketplace features. Situational Gravity Perks: worth it for serious Gravity Forms stores Gravity Perks is worth buying if Gravity Forms already powers your order, quote, booking, or payment forms and you need polished features such as tax, discounts, subtotals, inventory, or advanced calculations. It is not a sensible replacement for WooCommerce, and buying the whole suite for one small enhancement is hard to justify unless that enhancement solves a real business problem. Situational WPC Fly Cart for WooCommerce: worth it for a simple side cart WPC Fly Cart is worth using when you want a lightweight floating cart without rebuilding your checkout, especially because the free version covers the core drawer experience. It is not the best choice for heavily customized stores: single-product AJAX behavior requires a separate plugin, styling can demand custom CSS, and support or compatibility problems have appeared in real-world reports. Buy the premium version only if instant checkout, coupon entry, shipping calculations, or paid customization support justify the extra cost. Situational WPC Smart Points & Rewards: promising, but not proven enough yet WPC Smart Points & Rewards is worth considering for a small WooCommerce store that wants a straightforward loyalty system with VIP tiers, checkout redemption, shortcodes, and basic analytics. It is not a confident choice for a serious loyalty program yet: the WordPress.org listing has fewer than 10 active installations, no reviews, limited public documentation, and a support history that shows some requested features are still being developed. Situational