SETUP GUIDE · WOOCOMMERCE
The Best WooCommerce Price-Per-Kg Plugin, Explained Properly
If you weigh what you sell before you package it, your store shouldn’t be forcing every product into one fixed price. Here’s what a real price-per-kg setup needs to do, and how to build it properly.
- 0.750 kg selected
- $56 / kg rate
- $42.00 total
Why WooCommerce Fights You On This
It’s not that WooCommerce is badly built. It just wasn’t designed with weight in mind. Every product gets a single price tag, and quantity just multiplies that number. A customer buying 300 grams of coffee at $56 a kilo should see $16.80 on screen. Someone buying 1.7 kilos of cheddar at $42 a kilo should land on $71.40. Left alone, WooCommerce has no mechanism for either calculation, let alone a better rate for a wholesale buyer ordering 8 kilos at once.
Fixed variations
A separate SKU for every weight. Twenty products at six weights each is 120 variants to keep priced correctly, forever.
Quantity as grams
Typing 500 into a quantity box to mean 500 grams. Almost nobody reads it that way, and it breaks normal cart behaviour.
"Contact us" pricing
Pulling weighed items off the automated path entirely. Feels safe, quietly kills conversion, and someone now prices orders by hand.
What a Real Solution Needs to Do
Before picking a plugin, it’s worth pinning down what “handles price per kg properly” actually means. Hold any option against this checklist.
Core pricing
Price per kg or lb, calculated live, shown clearly on product and cart.
Weight selection
Fixed pack sizes, or free entry with a min / max and step control.
Tiered & role pricing
Automatic weight thresholds, plus separate wholesale rates by user role.
Stock & checkout
Per-package stock or a weight pool, running through standard checkout.
The Plugin That Ticks All of It
Weight Based Products for WooCommerce is built around exactly this checklist. Instead of stretching a Simple or Variable product to cover weight, it introduces its own dedicated product type, one where weight and price per kilogram are the starting assumption, not something bolted on afterward.
That’s really the whole difference. Every workaround treats weight as an exception. This plugin treats it as the rule.
1. Create the product
Choose Weight Based instead of Simple, then set a price per kilogram or per pound.
2. Pick a weight mode
Fixed Packs for pre-portioned sizes, or Free Weight with a live slider between a min and max.
3. Layer in tiers & roles
Automatic rate drops at weight thresholds, plus separate wholesale pricing by user role.
How a Tier Structure Actually Looks
A real example: spices priced at a base $56/kg with volume breaks built in.
0 – 499 g
$56.00 / kg
500 g – 1.9 kg
$48.00 / kg
2 kg and above
$40.00 / kg
The product page can quietly tell a shopper how close they are to the next tier while they’re still deciding. It’s a small nudge, and it tends to lift average order size without discounting anything upfront.
Minimums, Options, and Not Overselling
Some products genuinely can’t be sold below a certain amount, a thin sliver of cheese, a token pinch of saffron. Set a minimum in the product editor and it’s enforced in more than one place: presets below the floor get hidden, a note tells the shopper how much more to add, Add to Cart stays disabled, and the server double-checks on submission regardless of what happened in the browser.
You can also collect extra details alongside weight, grind type, cut preference, certification grade, as button selects, dropdowns, radios, or a free text box. Configure an option once, attach it to any product, and mark the important ones as required so checkout won’t proceed without an answer.
On the stock side, fixed-size packs track inventory the normal WooCommerce way. Free-weight products work off a total pool, say 15kg of a spice blend for the week, shrinking in real time as orders land so you never sell more than what’s actually on the shelf.
Pricing and Getting Started
$79
1-year plan — updates & support included
$126.40
2-year plan — save 20% vs. annual
Both plans include a 30-day money-back guarantee, so there’s not much risk in trying it against a handful of real products before committing your whole catalogue.
Still deciding between this and a custom build?
If your dev team already tried variations or a custom-fields hack and it's holding together with duct tape, let us know what broke first, tiered pricing, stock syncing, or just the sheer number of SKUs. Drop it in the comments below.