Online grocery unit pricing: checking multipacks, bundles and product pages

For Australian online grocery retailers, the key question is not whether you have a large physical store. It is whether your online business sells goods from all 11 grocery categories covered by the Unit Pricing Code. If it does, unit pricing needs to appear online wherever an applicable selling price is shown. That makes online compliance a practical product-page issue as much as a legal one, especially when you sell multipacks, discounted lines or grouped offers.

The detail matters because the Code treats the same-item multipack differently from a bundle of different products, and a unit price that is correct on the product detail page can still create problems if the collection page or promotional tile shows a live selling price without matching unit information. This article is general information only and is not legal advice. It focuses on online grocery ranges, how to tell whether the Code covers your site, when unit pricing is required for multipacks and bundles, and how to keep the displayed unit price aligned across live product-price displays.

Online coverage depends on the grocery range

The starting point for an online retailer is the product range, not floor space.

The ACCC says online businesses that sell items from all of the listed grocery categories must follow the Unit Pricing Code guidance. Those categories are bread, breakfast cereal, butter, eggs, flour, fresh fruit and vegetables, fresh milk, meat, rice, sugar and other packaged food.

That means an online store with a broad supermarket-style range can be covered even if it has no customer-facing shopfront at all. By contrast, not every food website is covered. A smaller online store with only part of that range may fall outside the Code.

This distinction matters because some businesses incorrectly borrow the physical-store threshold and assume that online coverage depends on store size. For online retailers, that is the wrong test. The physical floor-space rule is for physical businesses. It does not set an online shortcut.

A practical example helps. If your site sells bread, cereal, dairy, meat, produce and pantry staples across all 11 categories, you should assess your online range on the basis that the Code is likely to apply. If you sell only fruit boxes, specialty meat packs or a narrow health-food range, coverage may be different because the full set of categories is not there.

Where businesses get caught out is growth. A store that began as a niche operator may add enough products over time to move into covered territory. Founders should review the range whenever category expansion, new supplier onboarding or marketplace integrations add grocery lines that fill previous gaps.

What does a compliant online unit price need to look like?

If the Code applies, the online unit price is not just background comparison data. It is pricing information that must sit properly beside the selling price.

The ACCC says unit prices must be prominent, proximate, legible and unambiguous. In plain English, they should stand out enough to be easily seen, be close to the selling price, be easy to read, and be accurate and clear in meaning.

The Code's display rules distinguish the amount: a unit price of $1.00 or more is shown in dollars and whole cents, while a price below $1.00 may be shown in dollars and whole cents or in whole cents. Work it out to the nearest cent, rounding half a cent upwards.

The correct unit of measurement depends on the product type and how it is usually sold. Beverages must be priced per litre. Fruits, vegetables and meats must either be priced per item or per kilogram if they are usually sold by weight. The right measure is about meaningful comparison, not whatever happens to be easiest for the website template.

For online stores, the practical challenge is consistency across every place a live selling price appears. If a category grid shows a product name, selling price and discount badge, and the product detail page shows a different or better-formatted unit price, the grid can still be a risk point if the Code applies there. The same issue can arise in search results, variant selectors, "specials" panels and static promotional blocks that pull a current selling price from the catalogue.

That does not mean every image, banner or brand mention on your site must always include a unit price. The better question is narrower: where are you displaying an applicable selling price for a covered grocery item? Those are the places that should be checked carefully.

From an operations perspective, make sure the data fields behind the product feed can handle both the selling price and the correct comparison unit. Then test how they render on mobile and desktop. A unit price that exists in the product database but disappears on sale tiles or app views is not much use.

Multipacks, bundles and grouped offers are not all treated the same

This is where many online grocery businesses make avoidable mistakes.

The ACCC says unit pricing must be displayed where two or more of the same grocery items are offered for a single price. But bundles of different types of grocery items do not require unit pricing. It also says unit pricing is not required where similar items of different sizes and weights are sold at a single price.

So there are three different outcomes.

First, if you are selling multiple units of the same item for one price, unit pricing is required. For example, if you offer six identical 600 mL bottles of sparkling water for a single total price, the unit price should be calculated using the total volume of 3.6 litres. If the pack sells for $9.00, the unit price would be $2.50 per litre. The arithmetic matters because using the single-bottle volume instead of the full multipack volume would overstate the unit price.

Second, if you create a bundle made up of different grocery items for one combined price, unit pricing is generally not required for that bundle. Think of a breakfast box containing cereal, milk and bananas sold together for one promotional price. That is different from a same-item multipack.

Third, if you offer similar items of different sizes or weights at one price, unit pricing is also not required for that grouped offer. A practical example might be selected pasta packs in different gram weights all marked at one selling price.

The product setup in your catalogue needs to reflect these distinctions. If the merchandising team labels everything as a "bundle", but the customer is really buying three identical tins for one price, that does not change the legal character of the offer. What matters is what is actually being sold and how the price is presented.

It is also worth checking your promotional engines. Some ecommerce platforms automatically build mix-and-match offers, same-price ranges and multibuy deals from one pricing rule. Legal treatment can differ even when the front-end graphic looks similar.

When discounts and exemptions really apply

Not every product needs a unit price, and not every reduced item keeps one. But the exemptions are specific.

The ACCC says some products do not require unit pricing at all, including alcoholic beverages, meals made for immediate consumption, cigarettes and tobacco products, and various non-grocery categories such as toys, furniture and many household or electrical goods. For a grocery retailer, that matters most where the same website sells mixed categories.

The ACCC also identifies exemptions for different grocery items sold together for a single price, a range of different items offered for the same price, perishable items marked down as they approach their use-by date, products marked down because they or their packaging are damaged, and products marked down because they are discontinued.

The practical trap is assuming any sale badge creates an exemption. It does not. A standard promotion, temporary price drop or catalogue special does not automatically remove the need for unit pricing. The marked-down exemptions described by the ACCC are narrower and linked to the kind of product or the reason for the markdown.

For example, if yoghurt is on weekly special at a reduced selling price, you should not assume unit pricing disappears just because the product is discounted. On the other hand, a perishable item reduced because it is close to its use-by date may fall within an exemption. The reason for the markdown matters.

For founders and operations teams, this is usually a rules-engine issue. Discount types should be tagged clearly in the back end so ordinary promotions are not accidentally treated the same as damaged, discontinued or genuinely perishable markdown lines.

Why online product pages, grids and variants need to stay aligned

Online unit pricing problems can arise when catalogue data and display templates become disconnected.

If your site displays a compliant unit price on the product detail page but omits or misstates it on the collection page, you may be giving customers inconsistent comparison information. The same can happen when a variant change updates the selling price but not the unit price, or when a static content block keeps an old calculation after a pack size change.

A few common pressure points are worth checking.

• Category grids that show live prices pulled from the catalogue.
• Search-result cards that are styled differently from the main store template.
• Variant selectors where pack size changes from single item to multipack.
• Promotional modules for featured products or weekly specials.
• Mobile app displays where some pricing fields are hidden or truncated.

Pack changes are particularly risky. If a supplier shifts a juice carton from 1 litre to 900 mL, the selling price and unit price may both need updating. The same is true where a multipack changes from four units to three, or where the total price changes during a promotion. Every live product-price display that relies on those data points should update with it.

That does not require a legislated audit protocol. It is simply sensible ecommerce practice. Make sure product data includes the comparison unit, total quantity for multipacks, the applicable measurement basis and clear flags for exempt offer types. Then test a sample of regular products, multibuys, markdowns and variant combinations before pushing price changes live.

Where third-party apps or marketplace connectors are involved, check whether they recalculate the unit price themselves or merely copy a text field. A copied field can become inaccurate if quantity data changes upstream.

Practical examples for founders and ecommerce teams

Example one: a store sells pantry staples across all 11 grocery categories. It lists a single 500 g pasta pack and a three-pack of that same pasta for one total price. The store is likely covered, and the three-pack still needs unit pricing because it is multiple units of the same item sold for one price.

Example two: the same store offers a "breakfast starter" bundle containing one cereal box, one litre of milk and a punnet of berries for a combined price. That bundled offer is treated differently because it contains different grocery items.

Example three: a category page shows a discounted cheese price, but the unit price appears only after clicking through to the product detail page. If the category page is displaying the selling price for a covered item, that page should be checked for compliance rather than relying on the deeper page alone.

Example four: a fresh produce listing is usually sold by weight and priced per kilogram, but a seasonal promotional tile describes it loosely while showing the live selling price. If the tile is functioning as a price display for that product, the unit-pricing presentation should be included in a pricing display review with the same care as the ordinary listing card.

Frequently Asked Questions

Does every online food business need unit pricing?

No. Online businesses selling items from all 11 listed grocery categories must follow the Code. A limited-range online food seller may not be covered.

Do different-item gift boxes need unit pricing?

Generally, no if they are different grocery items sold together for a single price. That is different from a multipack of the same item.

What if products are on special?

A normal sale or promotion does not automatically remove unit-pricing obligations. Some marked-down products may be exempt, such as certain perishable, damaged or discontinued items, but the reason for the markdown matters.

Can we just show unit pricing on the product detail page?

If the Code applies, you should review all places where an applicable selling price is displayed online. A compliant detail page does not fix an omitted or misleading unit price elsewhere in the buying journey.

Key Takeaways

• For online retailers, Unit Pricing Code coverage depends on whether your business sells goods from all 11 listed grocery categories, not on physical floor space.
• If the Code applies, unit prices should be prominent, close to the selling price, easy to read, clear, and correctly rounded. Prices below $1.00 may use whole cents or dollars and whole cents; prices of $1.00 or more use dollars and whole cents.
• The correct unit of measurement depends on the product and how it is usually sold, with beverages per litre and many weighted fresh items per kilogram or per item as appropriate.
• Multipacks of the same grocery item sold for one price need unit pricing, while different-item bundles and same-price offers across similar items of different sizes or weights may not.
• Do not assume every discount is exempt. Standard promotions can still require unit pricing, while some perishable, damaged or discontinued markdowns may be treated differently.
• Check category grids, product pages, search results, variants and promotional price displays so pack-size or price changes flow through everywhere a live selling price appears.

If you run an online grocery business and need help reviewing pricing displays, ecommerce product-page wording, promotional mechanics or your online shop terms, Sprintlaw can help. Call 1800 730 617 or email team@sprintlaw.com.au to discuss your setup.