Pricing for AI agents, and the quote problem

A useful price includes currency, scope and the conditions that change it. Whether you sell a fixed-price product or a custom service, make those details clear and keep each published version consistent.

Reviewed October 1, 2026 · 6 min read

On this page6 sections
  1. Four places your price exists
  2. Check the price through checkout
  3. How to describe a service that needs a quote
  4. Give each price enough context
  5. The freshness problem, which is the actual failure mode
  6. What to do

A customer comparing offers needs more than a number. They need to know what it buys, which currency applies and whether the final amount can change. An assistant helping with that comparison needs the same context.

You do not need to invent a fixed price for work that requires a quote. Publish what you can state accurately, explain the remaining variables and provide a clear route to a firm total. For retail products, also check that feeds, pages and checkout describe the same item and price.

Four places your price exists#

A retail price often appears in four places. Compare the same variant, currency and customer conditions across them:

WhereWhat it isHow it breaks
Merchant Center feedThe price attribute you submitStale after a sale ends
Landing pageThe most prominent price shownLocation-based dynamic pricing
Structured dataThe Product markup on that pageNever updated when the page was
CheckoutWhat the buyer is finally chargedFees appear only at the last step

Google's price mismatch guidance explains how inconsistent prices can affect item or account eligibility. The remedy and review process depend on the issue shown in Merchant Center. Inspect that diagnosis rather than assuming every discrepancy triggers the same enforcement sequence.

Check the price through checkout#

The landing page is only the start of the comparison. Check the selected variant, cart and checkout total, including destination-dependent charges. A low headline price is misleading if the shopper cannot purchase the advertised offer on those terms.

Follow the destination's rules for product price, shipping, tax and other fees. Google's checkout requirements distinguish these charges and include exceptions for some government-mandated fees. Do not apply a blanket rule that every fee belongs in the same field.

Compare the total the customer will actually pay

For example, a $40 item with $12 shipping is not cheaper than a $48 item with free shipping. Show the relevant costs early and identify any that require a destination or other input. Do not assume either a person or an assistant will tolerate a surprise charge.

How to describe a service that needs a quote#

A quote-based service can still be compared on scope, qualifications, response time and the quotation process. The goal is to explain uncertainty, not hide it or replace it with an unreliable number.

If you publish a typical range, say what it covers and what makes a job fall outside it. If an assessment costs money, show that fee and explain whether it is credited against later work. Keep staff and any automated phone enquiry process aligned with those terms.

A useful example is 'Boiler diagnosis: $95 per visit, credited toward an approved repair. Parts and repair labor quoted after inspection.' It gives the customer a real commitment without pretending the entire repair has a known price.

Inspect the prices your pages expose

Run a Nexez scan to inspect public offer information and structured data. Compare any extracted price with the visible terms and the current purchase or quotation flow.

Scan your site free

Give each price enough context#

Review these details wherever a price appears:

  1. Currency and unit: per item, hour, visit, room or billing period.
  2. Included scope: the work, quantity or entitlement covered by the amount.
  3. Conditions: eligibility, minimum quantity, location, renewal terms or surcharges that change the total.
  4. Validity: promotion dates, quote expiry or the point at which a final amount is confirmed.
  5. Consistency: visible copy, structured data, feeds and checkout must describe the same offer.

The freshness problem, which is the actual failure mode#

Price drift often comes from update timing, cached pages or variant mapping. For current Google integrations, use the Merchant API guidance; the older Content API reached sunset in August 2026. An API can shorten update delays, but still needs monitoring and error handling.

Generate outputs from maintained source data where possible, then inspect each result. A shared database does not prevent stale caches or failed feed ingestion. The product feed guide covers those checks.

What to do#

  1. Compare a representative product or service from its public page through the final quote or checkout, using a test flow where available.
  2. Check structured data for the same variant, price and currency.
  3. For variable services, publish an honest range, starting point or assessment fee only where it is useful and supportable.
  4. Place important conditions close to the price.
  5. Test a promotion ending and an unavailable variant, then verify that each destination receives the update.

Clear pricing helps people choose and helps your team honor the offer. Keep the uncertainty where it belongs: in an explained quote process, rather than in conflicting numbers or charges discovered at the last step.

Maintain one clear description of each offer

See how Nexez uses listing data to publish offers and supported purchase or booking actions. Review the final outputs against your current prices and terms.

See how it works

Frequently asked questions

Does Google really check my checkout page prices?

Google's merchant policies cover price consistency through checkout, not just on the product page. Compare the same variant and currency, with charges represented according to the relevant rules. Use Merchant Center diagnostics to identify the actual issue and required remedy.

Where do I put shipping, handling and service fees?

Use the fields required by the destination and the type of charge. Product price, shipping, tax and government-mandated fees can have different rules. Disclose applicable costs clearly and consult the current checkout policy instead of combining every charge indiscriminately.

What happens if my feed price and my site price disagree?

The mismatch can affect item or account eligibility. Check Merchant Center for the exact issue, correct the relevant outputs and follow its review process. Do not assume a fixed review duration or that updating one copy immediately refreshes every other copy.

I run a service business and my prices genuinely vary. What should I publish?

Explain the quote basis: scope, main cost drivers, any supportable range and the step that establishes a firm amount. A fixed diagnostic fee can be useful when applicable. Do not invent a number just to fit a comparison table.

How should I describe costs that are not known yet?

Name the missing input, such as delivery location or inspection results, and explain when the final amount becomes available. Show known charges separately and obtain the customer's approval before commitment. Clear uncertainty is more useful than an inaccurate fixed total.

How often do I need to update prices?

Update at a rate that keeps the customer-facing offer accurate, and monitor propagation to feeds and caches. Frequently changing data may need an API or event-driven process. Check ingestion errors and revalidate the final price before a transaction.

Does structured data pricing matter if my feed is correct?

Yes. A consumer may read the page markup separately from the feed. Compare the structured price, visible price and selected variant, and test the published page. A plugin or common source database does not guarantee that all outputs are current.

Keep reading