Use shipping classes to group products that need different delivery charges, such as standard and bulky items. A class identifies the product group; a compatible shipping method supplies the actual rate.
IN THIS ARTICLE
01 Plan the classes
Choose a small set of meaningful classes based on fulfilment requirements. Avoid creating one class per product unless that is necessary for the pricing model. Document how a mixed cart should be charged, because combining classes can produce a different result from testing each item alone.
02 Create and connect the classes
- Open WooCommerce > Settings > Shipping > Classes.
- Add the required class names, slugs and descriptions.
- Edit products and assign the appropriate class in their shipping data, including variation-specific overrides where needed.
- Edit the relevant Flat rate or other compatible shipping method in each intended zone.
- Set the class costs, the no-class cost where relevant and the supported calculation mode.
- Save and test single-class and mixed-class carts.
Does creating a class make a new checkout option?
No. Shipping classes do not independently create customer-facing methods. If no method uses the class, it may have no pricing effect. The customer generally sees the shipping method's label rather than the internal class name.
Why does a mixed cart cost more than expected?
A Flat rate calculation can add costs for each applicable class or use a different configured aggregation. The base cost can also be added. Inspect all components and compare the result with the written mixed-cart rule rather than subtracting amounts until the total happens to match one example.
03 Check inherited variation settings
A variable product can provide parent shipping data with individual variation overrides. Test the actual selected variation, especially if only a large size requires a bulky class. Confirm that virtual items do not accidentally participate in a physical shipping calculation.
04 Maintain accurate assignments
Review new products and CSV imports for missing classes. Products without a class can fall into the method's no-class rule, which may be too cheap or unavailable. When renaming or retiring a class, inspect product assignments and every method that references it. Keep the shipping configuration and product catalogue changes coordinated so a routine edit does not silently change delivery prices.