← Reading listSUBMIT THE PRICE OF THE QUANTITY A CUSTOMER CAN ACTUALLY BUY
Text

Merchant Center catalog operations workshop / 6 MIN READ

Submit the price of the quantity a customer can actually buy

Create a minimum-purchase mapping with item quantity, payable product total and separate order constraints.

Published by SNS Media Tech

AI-assisted research and analysis for the SNS Creative Fieldbook

Sources checked 2026-11-07

A unit price can be useful comparison information without being a purchasable offer. Distinguish product-level minimum quantities from order-level spending rules before deciding what the price field means.

What you will leave with: Create a minimum-purchase mapping with item quantity, payable product total and separate order constraints.

Use this when

  • Wholesale or made-to-order products require several units per purchase.
  • A low per-piece price is exported while checkout enforces a larger quantity.

Not unit-price display design, tax advice or a claim that all cart minimums should be multiplied into each product price.

Identify the level at which the minimum applies

Google's price guidance says to submit the total for the minimum quantity of a product customers must buy. It distinguishes that from order-level minimum value settings and describes separate cases for mixed-product quantity requirements. Read the current rule for the actual constraint rather than applying one multiplication formula everywhere.

Ask whether the customer must buy several identical units, spend a minimum amount across the basket or choose a minimum count from an assortment. Record the answer in plain language with an example that checkout accepts and one it rejects. A field named minimum is insufficient. Its scope determines whether the product offer itself is a pack-sized purchase or one item within a constrained overall order.

Sources for this sectionGoogle Merchant Center: Price →

Derive the payable product total from the approved pricing rule

For an item-level minimum, identify the quantity, applicable unit rate and any mandatory customization included in that product offer. Use the rate that applies at the minimum quantity rather than a cheaper high-volume tier. Keep quantity increments separate: a minimum of twenty with increments of ten does not mean the first purchasable quantity is ten.

Build a test sheet showing the source price ladder, selected quantity and resulting offer total. Include promotions only when their actual conditions apply. Route fees and tax treatment through current platform guidance and the appropriate finance owner; do not hide a product charge in an unrelated field to make the headline smaller. Preserve the evidence so a later pricing update can recalculate the same offer correctly.

Reconcile title, page defaults and checkout constraints

Make the represented quantity clear in the offer information. Open the submitted product link and check its initial quantity and pricing explanation. A page may show a per-piece amount for comparison, but the minimum purchase should be understandable without discovering an unexpected multiplier at checkout.

Test the exact configuration named in the feed. Personalization, material or size selections may change the minimum quantity or unit rate. Include a product sample if the business sells one, but keep its identity and description distinct from the full production order. Do not advertise a sample's small price as though it purchases the bulk offer. Confirm that the feed row, selected configuration and accepted basket describe the same transaction.

Test price-ladder and minimum changes as one mapping

When the minimum or tier thresholds change, re-evaluate the submitted total even if the single-unit reference price remains unchanged. A new minimum can alter the purchasable offer materially. Have pricing and catalog owners approve the transition, including its effect on unit measures and customer-facing quantity statements.

Create regression cases for a fixed minimum of one item, a mixed-assortment basket rule and a spend threshold. The validator should keep these meanings separate rather than reporting all as quantity errors. After processing, inspect the product price and relevant order settings. The outcome is a faithful representation of what can be bought under the offer, not a claim that a lower-looking number will produce more qualified traffic.

Make the reasoning concrete.

A fictional print shop charges 3 USD per notebook at a minimum of 30 notebooks, while its 2 USD rate applies only at 300. The export sends 2 USD for a product page whose first valid order is 30.

Export the lowest unit rate

Opening: Use the most attractive number from the price ladder.

Hypothesis: The advertised amount appears competitive.

Risk: It cannot purchase the submitted minimum configuration.

Price the actual minimum offer

Opening: Use the approved 30-notebook configuration and its applicable rate, producing a 90 USD product total before separately governed charges.

Hypothesis: The feed represents a real purchasable quantity.

Risk: Order-level constraints and local price rules still need independent checks.

The owner verifies the 30-unit offer and keeps the higher-volume comparison rate out of its product price. A separate basket minimum, if present, is mapped under its own rule.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

  1. Scope

    Is the minimum per product, mixed basket count or total spend?

  2. Quantity

    What is the smallest valid purchase of this offer?

  3. Rate

    Which approved price tier applies at that quantity?

  4. Page

    Can a customer understand and select that exact configuration?

  5. Change

    Which minimum or tier update requires recalculating the feed?

Watch for the wrong conclusion.

  • Submitting the cheapest volume-tier rate as a purchasable product price.
  • Multiplying every product by an unrelated basket minimum.
  • Using a sample price for the full bulk order.

Your next action

Reconstruct the smallest accepted basket for one bulk product and compare its product total with the feed.

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: Price →Primary platform documentation · Supports: Supports total price for an item-level minimum quantity and the distinction from minimum order value and mixed-basket rules. Pricing reconstruction and test cases are original editorial analysis.