Catalog Buying

Catalog buying is a purchasing method where the buyer orders against a vendor's pre-agreed price list rather than negotiating each order. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Catalog Buying

Catalog buying is a purchasing method in which a buyer orders items or services directly against a vendor's pre-agreed price list, called a catalog, rather than negotiating price on each individual purchase order. The catalog functions as the pricing authority for every order placed under it.

It is common wherever the item set is large and repetitive: MRO parts, Class C consumables, safety supplies, standard fasteners. The efficiency it buys AP teams is exactly what makes catalog drift easy to miss, because a correctly matched order can still be priced against the wrong version of the list.

1. How does catalog buying work in a vendor contract?

A vendor and buyer agree on unit prices for a defined item set upfront, published as a catalog, usually with an effective date and an update schedule. Individual purchase orders then reference the catalog rather than restating price. The buyer's AP or procurement system pulls the price from its own stored copy of the catalog, not from the vendor at the moment of order, which is where version drift starts.

The stored copy is the risk point. A catalog is a document with a version and a date, not a fixed fact, and both sides need their working copy to match the one currently in force.

Vendors revise catalogs on their own schedule, sometimes quarterly, sometimes on demand. Contract terms typically require notice before a price change takes effect, but the buyer's internal system update does not always happen on the same day the vendor's notice arrives. Between those two dates, orders can be priced from either the correct or the stale list depending on which copy the ordering system holds.

2. How is catalog buying different from a rate card?

A catalog prices discrete, countable items by SKU, ideal for parts and consumables where the unit is fixed. A rate card prices labor, service calls, or time-based work by hour, shift, or job type, where the unit varies by scope. Both are pre-agreed pricing authorities that an invoice should be checked against, but they attach to different kinds of spend and fail in different ways.

Confusing the two references is itself a source of drift. An AP team that checks a labor invoice against a catalog built for parts, or a parts invoice against a rate card built for hours, has picked a reference document that cannot answer the question being asked of it.

3. What goes wrong when catalog pricing drifts?

An invoice can match its purchase order exactly, and the purchase order can match the receipt exactly, and the unit price on all three can still be wrong if the catalog version behind the purchase order was already superseded. Three-way matching verifies internal consistency between the invoice, order, and receipt. It does not independently verify that the order was built from the vendor's current catalog.

That gap is structural, not a lapse by any one person. The control was built to answer a different question than the one that produces this error, so passing it proves nothing about catalog currency.

4. How is catalog drift found and corrected?

Finding it means comparing the vendor's current, dated catalog against the price actually stored in the buyer's ordering system, item by item, and against what was actually invoiced. Where the three disagree, the difference is either a missed price decrease, a stale increase applied too early, or a rebate layer never reconciled against the base catalog price. Each is corrected differently: credit memo, going-forward price fix, or rebate claim.

The correction path depends on which of the three failed, so the comparison has to name which document was wrong before a fix can be applied.

  • Missed price decrease: The vendor lowered a price and the buyer's stored copy never updated, so orders continued at the old, higher rate.
  • Stale increase applied early: A price increase was loaded before its contractual effective date, charging the new rate ahead of schedule.
  • Rebate layer unreconciled: A volume-based discount on top of catalog price was never matched against actual purchase volume, so it went unclaimed.

For the wider pattern this sits inside, start with the margin drift guide.

5. Frequently Asked Questions (People Also Ask)

What is catalog buying in vendor contracts?

Catalog buying is a purchasing method where the buyer orders directly against a vendor's pre-agreed price list, or catalog, instead of negotiating each purchase order individually. The catalog itself, not the individual transaction, is the pricing authority. It is common for MRO, Class C consumables, and standard parts.

Is catalog buying the same as a rate card?

They serve the same purpose for different spend types. A rate card typically prices services by hour, shift, or job type. A catalog prices discrete items by SKU. Both are the pricing authority the invoice should be checked against.

Why does catalog buying create audit risk?

Catalogs update on a schedule set by the vendor, and the version an AP team references at invoice time is not always the version in force on the order date. If the wrong version is used as the reference, invoices that match it perfectly can still be wrong against the contract.

Who is responsible for keeping the catalog current?

Contract terms usually specify update frequency and notice requirements, but responsibility for reconciling the AP team's working copy against the vendor's current version is rarely assigned explicitly. That gap is where stale-catalog billing survives unnoticed.

Does three-way matching catch catalog pricing errors?

Three-way matching checks that the invoice quantity and price agree with the purchase order and the receipt. It does not independently verify that the purchase order itself was built from the current catalog version, so an error carried into the PO passes the match.

Which categories typically use catalog buying?

MRO and Class C consumables, safety supplies, and standard parts commonly use catalog pricing because the item set is large, repetitive, and stable enough to price in advance rather than negotiate per order.

How do rebates interact with catalog pricing?

Some catalog agreements bundle a rebate or tier discount on top of listed unit prices once volume thresholds are met. If that layer is not tracked separately from the base catalog price, the rebate portion can go uncollected even when the base pricing is correct.

1. How does catalog buying work in a vendor contract?

A vendor and buyer agree on unit prices for a defined item set upfront, published as a catalog, usually with an effective date and an update schedule. Individual purchase orders then reference the catalog rather than restating price. The buyer's AP or procurement system pulls the price from its own stored copy of the catalog, not from the vendor at the moment of order, which is where version drift starts. The stored copy is the risk point. A catalog is a document with a version and a date, not a fixed fact, and both sides need their working copy to match the one currently in force. Vendors revise catalogs on their own schedule, sometimes quarterly, sometimes on demand. Contract terms typically require notice before a price change takes effect, but the buyer's internal system update does not always happen on the same day the vendor's notice arrives. Between those two dates, orders can be priced from either the correct or the stale list depending on which copy the ordering system holds.

2. How is catalog buying different from a rate card?

A catalog prices discrete, countable items by SKU, ideal for parts and consumables where the unit is fixed. A rate card prices labor, service calls, or time-based work by hour, shift, or job type, where the unit varies by scope. Both are pre-agreed pricing authorities that an invoice should be checked against, but they attach to different kinds of spend and fail in different ways. Confusing the two references is itself a source of drift. An AP team that checks a labor invoice against a catalog built for parts, or a parts invoice against [a rate card](/glossary/rate-card) built for hours, has picked a reference document that cannot answer the question being asked of it.

3. What goes wrong when catalog pricing drifts?

An invoice can match its purchase order exactly, and the purchase order can match the receipt exactly, and the unit price on all three can still be wrong if the catalog version behind the purchase order was already superseded. Three-way matching verifies internal consistency between the invoice, order, and receipt. It does not independently verify that the order was built from the vendor's current catalog. That gap is structural, not a lapse by any one person. The control was built to answer a different question than the one that produces this error, so passing it proves nothing about catalog currency.

4. How is catalog drift found and corrected?

Finding it means comparing the vendor's current, dated catalog against the price actually stored in the buyer's ordering system, item by item, and against what was actually invoiced. Where the three disagree, the difference is either a missed price decrease, a stale increase applied too early, or a rebate layer never reconciled against the base catalog price. Each is corrected differently: credit memo, going-forward price fix, or rebate claim. The correction path depends on which of the three failed, so the comparison has to name which document was wrong before a fix can be applied. - [Missed price decrease](/glossary/missed-credit-memo): The vendor lowered a price and the buyer's stored copy never updated, so orders continued at the old, higher rate. - Stale increase applied early: A price increase was loaded before its contractual effective date, charging the new rate ahead of schedule. - [Rebate layer unreconciled](/glossary/rebate-gap): A volume-based discount on top of catalog price was never matched against actual purchase volume, so it went unclaimed. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide.

Questions & Answers

What is catalog buying in vendor contracts?

Catalog buying is a purchasing method where the buyer orders directly against a vendor's pre-agreed price list, or catalog, instead of negotiating each purchase order individually. The catalog itself, not the individual transaction, is the pricing authority. It is common for MRO, Class C consumables, and standard parts.

Is catalog buying the same as a rate card?

They serve the same purpose for different spend types. A rate card typically prices services by hour, shift, or job type. A catalog prices discrete items by SKU. Both are the pricing authority the invoice should be checked against.

Why does catalog buying create audit risk?

Catalogs update on a schedule set by the vendor, and the version an AP team references at invoice time is not always the version in force on the order date. If the wrong version is used as the reference, invoices that match it perfectly can still be wrong against the contract.

Who is responsible for keeping the catalog current?

Contract terms usually specify update frequency and notice requirements, but responsibility for reconciling the AP team's working copy against the vendor's current version is rarely assigned explicitly. That gap is where stale-catalog billing survives unnoticed.

Does three-way matching catch catalog pricing errors?

Three-way matching checks that the invoice quantity and price agree with the purchase order and the receipt. It does not independently verify that the purchase order itself was built from the current catalog version, so an error carried into the PO passes the match.

Margin Drift Resources