Checklist: is your price list ready for an AI buyer?

Published 2026-11-10 · Istrate Laurentiu, Negotra

Procurement agents read structured data, compare it and ask again. A supplier whose prices, units and terms live in people's heads answers slowly and inconsistently. These checks take an afternoon and need no new software.

What the buyer's agent needs to read

  1. One product code per item, the same in the catalogue, the price list and the ERP.
  2. Units and pack sizes written out (piece, box of 100, pallet), with the minimum order quantity.
  3. Volume tiers as a table: from which quantity which price applies.
  4. Lead time per item or family, and what changes with stock on hand.
  5. Standard payment terms and the price of longer terms.
  6. Product pages with structured data (schema.org Product and Offer), so that software reads name, code, unit and availability without guessing.

What your team must decide before any agent negotiates

  1. Minimum margin per product or family: the price below which nobody may go.
  2. Contract prices per customer, kept in one place.
  3. Approval limits: order value and discount above which a named person decides.
  4. How far to move per round: large steps at first, smaller ones later, never past the floor.
  5. Response time target for requests for quote, for example within one working hour.
  6. One owner for the price list, so that every channel quotes the same price.

Check how an AI buyer sees you

On negotra.com you can request a free report on how easily procurement agents can read your website and catalogue, with the first things to fix. If you then want an agent to answer these requests for you, Negotra does it inside the limits above and asks a person above them.

Free 30-day pilot on your own price list, then you pay only 20% of the gain the agent brings. See how the pilot works →

Sources

  1. Schema.org: Product
  2. Schema.org: Offer
  3. Pactum: client list