Quick definition
Contract pricing is the price a B2B supplier agrees with a specific customer for a period, a volume or a set of products, and which replaces the list price. On an e-commerce portal it is shown only after the buyer signs in, because each account sees a different price list.
What does it mean?
In B2B commerce almost nobody pays the public price. The price depends on the contract: a price list per customer, volume discounts, project pricing or terms that change by branch and payment method.
The system that holds those rules is usually the ERP. The commerce portal queries them in real time, using the buyer’s identity as the key.
Why is it important?
If the portal shows only the list price, a buyer with a contract cannot trust it and ends up asking for a quote by email. That is where the digital channel loses its advantage.
For an AI agent the problem is bigger: without the account’s price it cannot compare suppliers or decide. A public price higher than the agreed one leads it to discard the right supplier.
How does an AI agent quote with contract pricing?
It needs three things. An identity the portal recognizes as authorized by the customer (see session authentication). A query endpoint that returns that account’s price for a product and a quantity. And a response that states what it includes: validity, currency, taxes and minimum quantity.
Traditional connections already solve this between systems: a PunchOut catalog hands the customer’s purchasing system the prices of its contract. The step most portals are missing is exposing that same query to an agent.
Applied example
A maintenance buyer asks an agent to quote twenty filters with three suppliers. Two respond with list price because the agent could not identify itself. The third recognizes the account, returns the agreed price with its validity and wins the purchase, even though its public price was the highest.
Related concepts
Contract pricing relies on an API-first architecture, because the portal must query it live. It goes hand in hand with session authentication and multi-branch fulfillment, and it is one of the four problems specific to agentic commerce in industrial distribution, along with the part cross-reference. For market context, see the study B2B e-commerce in Mexico.
Common mistakes
Copying price lists to the portal once a day, so the price shown no longer matches the ERP. Showing “price on request” across the whole catalog. And calculating the contract price only at the end of the order, when the buyer has already decided using other data.
Edgebound Labs perspective
At the lab we measure contract pricing with a simple question: can another system, with the customer’s permission, ask how much this product costs for this account and get a complete answer? If the answer depends on a person, the digital channel is not finished yet.
Frequently asked questions about contract pricing
Are contract pricing and customer-specific price lists the same thing?
In practice, yes. A customer-specific price list is the most common way to implement contract pricing; the contract can add volume discounts and validity periods.
Why does a B2B portal not show prices without signing in?
Because each customer has a different price and that information is confidential. The portal needs to know who is buying before showing it.
Where is contract pricing managed?
Usually in the ERP. The commerce portal queries it in real time through an integration.
Can an AI agent see my contract price?
Only if the portal lets it identify itself with the account’s permission and has a price query endpoint. Without that, the agent sees only the public price.
Keep exploring the glossary
Does your portal return each account’s price?
We audit your B2B commerce operation and tell you what it needs so that people and agents can buy from you, with clearly defined success metrics.