Before comparing two supplier prices, a buyer needs to know whether they refer to the same thing. A photograph of a carton, a price per piece and a minimum order stated elsewhere can make a simple comparison unnecessarily difficult.

The ambiguity is not always caused by poor English. A perfectly translated description can still confuse the selling unit, the contents of a pack and the minimum quantity accepted for an order. Each answers a different question. Combining them into one quantity label transfers the work of interpretation to the buyer.

Google’s Merchant API product-attribute documentation, updated September 4, distinguishes identical-item multipacks from bundles containing different products. Those distinctions are useful for thinking about an offer. They do not mean that every B2B supplier should use Merchant Center or that a catalogue field determines the supplier’s commercial terms.

What does the displayed price buy?

Start at the price rather than the packaging photograph. Is the price for a piece, a pack or a complete set? State the answer close to the amount, where someone making a comparison is likely to look.

Consider a hypothetical product sold as six identical cups in one pack. That differs from a cup and saucer offered together as a set. A buyer needs the contents in each case, but the information is doing different work: counting the identical items in one offer versus describing the components of a combined offer.

Neither description establishes how many packs or sets the supplier will accept in an order. In the hypothetical six-cup pack, six tells the buyer what is inside. It does not say whether buying one pack meets the supplier’s minimum or whether the pack can be split.

If imagery shows more than the priced unit, explain that relationship clearly. Do not depend on a distant footnote to undo the impression created beside the price. Likewise, the information submitted to a product-discovery channel should represent the offer that the visitor will find on the page, rather than an attractive fragment of a different offer.

Put the purchasing threshold in its own place

For a quote-led supplier, some conditions may be standard and others may require discussion. State only the standard conditions that the company can support. Mixed-model orders, customization and sample arrangements may need separate treatment if the actual policies differ.

The point is not to publish every possible negotiation outcome. It is to prevent the buyer from making the wrong initial calculation. They should be able to distinguish the price basis from the amount needed to place an order and recognize which remaining details need confirmation.

Where a condition is unknown, leave it for confirmation rather than inheriting it automatically from a similar product. Closely related models can have different packaging or ordering arrangements. A convenient default can turn a minor catalogue shortcut into a confusing quotation.

International terminology adds another opportunity for ambiguity. Words such as pack, set and piece should refer to a defined unit for that particular product. Repeating the same English word across every catalogue item is not useful if its underlying meaning changes from page to page.

Follow a quantity into the inquiry

A practical check is to follow an explicitly authorized test quantity through the page and inquiry form. If the visitor selects packs, does the form retain that unit? When the sales team receives the request, does it still contain both the number and what is being counted?

A number without a unit can look complete in a database while remaining commercially unclear. The salesperson may interpret it using their experience of the product, but the buyer may have intended something else. Ask for clarification when necessary; do not silently alter the original request to make the record appear consistent.

Internal systems may legitimately use different units. A warehouse may count individual items while a catalogue sells packs. The conversion should be explicit at the point where the information moves between them. Testing this should not create a real order or send unapproved external messages.

For buyers assembling quotations from several suppliers, consistent units make comparison less laborious. They also make it easier to identify the next question: whether a quoted amount covers the required configuration, whether the minimum purchase fits the project, and which charges are still outside the stated basis.

Our discussion of product metadata mapping addresses the broader problem of retaining meaning across systems. Here the immediate task is more focused: make the saleable unit intelligible before the buyer calculates anything.

Read the page once as someone unfamiliar with your factory’s conventions. If you cannot explain what the displayed price buys and what the minimum purchase requires without guessing, rewrite the information beside the price first. Another image carousel will not resolve an undefined unit.

Sources