Skip to content

Product schema confuses the pack price with the unit price

Check product unit-pricing markup against the pack quantity and selling price, repair referenceQuantity mappings, and verify the page and feed together.

By Crawlito · 5 min read

In short

  • The price paid for a pack and the comparison price per unit are different values.
  • Google's unit-pricing example uses the selling price with quantity and reference-unit information.
  • Verify arithmetic, selected variant, visible content, and structured data together.
On this page

If product markup shows the price per 100 ml as though it were the price of the whole bottle, inspect the mapping between the selling price, pack quantity, and unit-pricing reference quantity. These values describe different parts of the offer. Correct the source mapping, verify the arithmetic, and compare the visible page, structured data, and any product feed for the same variant.

Do not change a real selling price merely to silence a structured-data warning. The repair should make the published representation agree with what the customer can actually buy.

Record one concrete offer before editing markup

Choose a single product variant and write down its selling price, currency, net quantity, and displayed comparison unit. Use the currently available offer rather than a category card that combines variants.

For a hypothetical example, a 500 ml bottle costs USD 12.00 and the page compares prices per 100 ml. Its comparison price is USD 2.40 per 100 ml.

These are invented demonstration values, not a claim about a real product or a measured outcome.

Check the selected variant, sale state, and customer context. A 250 ml bottle and a 500 ml bottle are different offers even when they share the same product title.

The product schema guide provides the broader offer context. Here the task is narrower: identify which number represents the purchasable pack and which represents a comparison basis.

Keep a screenshot or controlled record of the visible values and their source fields so the mapping can be reviewed precisely.

Read the unit-pricing structure in the delivered page

Inspect the actual JSON-LD returned by the public product URL. Find the offer associated with the selected variant rather than assuming the first price object is the relevant one.

Google's merchant-listing documentation describes unit pricing through UnitPriceSpecification and referenceQuantity.

Compare the selling price with the quantity and base quantity. A syntactically valid object can still place the comparison price in the field intended for the actual offer.

Inspect duplicate markup from commerce plugins or themes. One correct object does not eliminate a conflicting object generated elsewhere on the page.

Check the initial public response as well as any later variant update. A client-side display can show one size while the delivered structured data continues to describe another.

Record the responsible generator and source field names. This helps distinguish a catalog-data error from a template that incorrectly interprets otherwise accurate values.

Calculate the expected comparison price independently

Use the pack price and quantity to verify the comparison value before changing code. For the hypothetical bottle:

Selling price: USD 12.00
Pack quantity: 500 ml
Comparison basis: 100 ml
Comparison price: 12.00 / 500 * 100 = USD 2.40 per 100 ml

The arithmetic is a diagnostic cross-check. It does not determine which units or display rules apply to every market or product category.

Keep units consistent throughout the calculation. Dividing a quantity in liters by a base expressed in milliliters without conversion can create a large error while every individual field looks plausible.

Check decimal parsing too. A catalog system, localized display, and structured-data serializer may use different representations.

Do not round intermediate values more than the application design requires. Compare the final customer-facing result using the commerce system's approved rounding rules.

For a multi-pack, establish what the listed quantity refers to. The total sale quantity and the size of one component are not automatically interchangeable.

Map the selling price and quantities deliberately

For the hypothetical example, this offer fragment illustrates the relationship:

json
{
  "priceSpecification": {
    "@type": "UnitPriceSpecification",
    "price": 12.00,
    "priceCurrency": "USD",
    "referenceQuantity": {
      "@type": "QuantitativeValue",
      "value": 500,
      "unitCode": "ML",
      "valueReference": {
        "@type": "QuantitativeValue",
        "value": 100,
        "unitCode": "ML"
      }
    }
  }
}

This is a partial example, not a complete Product object. The surrounding product and offer still need the applicable documented fields and accurate public content.

The important distinction is that the offer price represents the pack being sold, while the quantity fields describe its comparison basis.

Use Google's currently supported unit codes for the relevant representation. Do not assume a feed-only unit is automatically supported by the structured-data feature.

Repair the generator's mapping rather than manually overriding one product's output. Preserve the correct behavior for products that do not use unit-pricing comparisons.

Reconcile variants, promotions, and product feeds

Repeat the comparison for another size or pack count from the same product family. A hard-coded base quantity can appear correct for one variant while misrepresenting the rest.

Check the selected offer during a promotion. The pack price, comparison price, and markup should reflect the same active selling state.

The sale-price mismatch guide covers timing differences between the page and product data.

If the site also submits a product feed, inspect the corresponding record. Match the record by its actual identifier and variant, not only by a human-readable title.

The variant identifier guide explains why two different sellable variants should not be casually combined during diagnosis.

Avoid treating a feed field and a JSON-LD property as identical merely because their labels sound similar. Follow each format's documented meaning and compare their represented offer.

Keep any intentionally different market or currency configurations separate in the test record.

Validate the published object and purchase context

Run the public URL through the supported structured-data testing tool and inspect the extracted offer. Then compare it with the visible price and selected quantity on the page.

A passing syntax check does not verify your arithmetic or the actual catalog record. Keep the independent calculation as part of the acceptance evidence.

Follow the ordinary purchase path far enough to confirm the intended pack and selling price, using a safe test process that does not place an unwanted order.

Check the public response after the normal deployment and cache path. A corrected administrative preview does not establish that visitors receive the new markup.

Test the original product, a different size, and a product without unit pricing. This small set helps detect a fix that accidentally applies one product's quantity structure everywhere.

Record the final selling price, pack quantity, comparison basis, and release time. Those four details make the result reviewable without sharing customer information.

Keep the content claim narrower than the commercial result

Report the actual defect and repair: the generator confused the comparison price with the pack price, and the public object now matches the intended offer.

Do not claim that correcting the markup guarantees a merchant feature, ranking, or conversion increase. Those outcomes depend on additional requirements and later evidence.

For ongoing maintenance, make quantity and unit fields part of the product-data contract. A packaging change should update the source values used by both the visible page and the structured-data generator.

Assign ownership of unusual cases such as bundles, variable quantities, and mixed-unit catalogs. They should not inherit a simple bottle example without review.

Keep the example calculation in a product-specific test where useful. Its purpose is to protect the meaning of the offer, not merely to mirror the JSON serialization code.

A reliable implementation helps customers compare products while keeping machine-readable data consistent with the same public facts.

Frequently asked questions

Is the price per 100 ml the same as the selling price?

Only when the actual offer quantity makes them equal. Usually they describe different values, so verify the pack quantity and comparison basis.

Can valid JSON-LD still show the wrong unit price?

Yes. Syntax validation cannot establish every catalog fact or arithmetic relationship. Compare the object with the actual offer.

Should every product get referenceQuantity?

Use it when it accurately represents the relevant unit-pricing information under the supported format. Do not invent quantities for products that do not use that comparison.

After validating the product data, run the public page through the free Crawlito check to inspect its access and broader page-level signals.

Filed under Structure and schema. Topics: ecommerce, structured-data, product