Merchant Center catalog operations workshop / 6 MIN READ
Map package content and comparison measure into the right feed fields
Create a measure-mapping test sheet with source quantities, allowed units and independently checked calculations.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-07
Unit pricing in a feed is a relationship between offer price, total included quantity and a comparison denominator. Each input must describe the same sold configuration before the resulting ratio is useful.
What you will leave with: Create a measure-mapping test sheet with source quantities, allowed units and independently checked calculations.
Use this when
- A supplier provides mixed package sizes and units for feed export.
- The displayed unit price looks implausible despite a correct package price.
Not legal advice on unit-pricing obligations or a guarantee that Google displays the submitted comparison base unchanged.
Identify the two measurement roles
Google documents unit_pricing_measure as the product's total amount and unit, while unit_pricing_base_measure supplies the comparison denominator. The platform may display a different base to support comparison. Check current supported units, base values and country-specific requirements before mapping the fields.
Start with the exact offer represented by the price. Record the quantity the customer receives, not the container's shipping weight or a convenient number from the supplier spreadsheet. Then choose an appropriate supported comparison base. Keep those inputs separate from the computed unit price. A number such as 100 can mean milliliters in the package, grams in the base or a count of pieces; a column without its meaning and unit is unsafe to export.
Normalize quantities without losing their dimension
Maintain the original supplier value, its unit and the normalized export value. Convert only between compatible dimensions. Weight and volume are not interchangeable without justified product-specific information, and a shipping dimension does not establish usable coverage area. Resolve ambiguous source labels with the supplier rather than inferring from neighboring products.
Review nested packs, concentrates and products sold by area. A retailer combination may need the total included content rather than one inner package's content. A dilution claim does not automatically change the physical quantity sold. For flooring, confirm whether the stated area is the actual offer coverage or a theoretical estimate affected by waste. Route regulatory interpretation to qualified owners and record the approved basis used in the feed.
Test the arithmetic independently of the export formula
Calculate the expected unit price from the offer price, included measure and comparison base using consistent units. Use a simple independent check rather than copying the production formula into the test sheet. Include a deliberately mismatched unit fixture so the validator proves it can reject an invalid dimensional comparison.
Check ordinary and sale-price situations, multiple pack sizes and decimal quantities. Look for factor-of-ten, hundred or thousand errors and confusion between count and volume. Reconcile rounding only after the underlying quantities agree. The acceptance question is not whether two rounded numbers happen to match, but whether both derive from the same sold quantity and legitimate base. Keep tolerances explicit where display rounding differs.
Verify the processed fields and explain display differences
After processing, compare the stored measure and base with the approved mapping. Inspect any available customer-facing result without assuming a particular annotation must appear. A changed displayed base can be consistent with the same ratio; an incorrect quantity cannot. Convert the observed result back to a common basis before declaring a discrepancy.
When a package changes size, review both its price and measurement inputs as a single representation change. Keep old and new configurations distinguishable so a supplier shrink in content does not inherit the previous quantity. Build regression examples for every conversion family the catalog uses. The maintained output is an explainable mapping from physical offer to feed fields, rather than a manually corrected ratio that the next import overwrites.
Make the reasoning concrete.
A fictional pantry retailer sells a two-jar offer containing 400 grams per jar for 12 units of currency. Its export uses the total offer price but only one jar of content, doubling the calculated comparison price.
Patch the displayed ratio
Opening: Manually halve a report value while leaving the feed measures unchanged.
Hypothesis: The spreadsheet looks reasonable.
Risk: The underlying offer representation remains wrong.
Repair the measure mapping
Opening: Record 800 grams of total content and a supported comparison base, then recalculate.
Hypothesis: The ratio follows the actual two-jar purchase.
Risk: Other nested packs need the same semantic audit.
The team corrects the quantity source and independently checks the calculation. It verifies the processed inputs and treats any platform-selected display base separately from data accuracy.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Offer
What total content does the submitted price purchase?
Units
Are source and normalized quantities dimensionally compatible?
Base
Which supported comparison denominator is appropriate?
Calculation
What independent arithmetic result should these inputs produce?
Change
Which package-size changes must update the mapping?
Watch for the wrong conclusion.
- Pairing a multi-package price with one inner package quantity.
- Converting weight into volume without valid evidence.
- Treating a different displayed base as proof the feed ratio is wrong.
Your next action
Independently calculate one nested-pack unit price and trace both feed measures to their source.
Sources & scope
Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.
- Google Merchant Center: Unit pricing base measure →Primary platform documentation · Supports: Supports the denominator role, supported formats and possible use of a different displayed base. Mapping and arithmetic test methods are original editorial analysis.
- Google Merchant Center: Unit pricing measure →Primary platform documentation · Supports: Supports submitting the total amount and unit for the offered product and checking country-specific requirements.