Research library

Customer operations

B2B Customer-Specific Catalogs and Contract-Pricing Operations

A vendor-neutral operating guide to price ownership, company and location assignment, overlapping catalog rules, controlled changes, approval handoffs, quote-to-order boundaries, testing, and reconciliation.

Sources checked: October 13, 2026

Establish price ownership before building price rules

Start by separating the commercial instruction from the system representation. Record which approved internal role or process supplies a customer-specific price, which system stores the authoritative instruction, which commerce catalog presents it, and which integration carries it to the buyer and order record. Keep the product and variant identifier, customer or company key, location scope, currency or unit convention where applicable, approval reference, effective instruction, and change owner together in a reviewable specification. This is an operating model to adapt, not a claim that one data shape or contract interpretation fits every business. Route ambiguous commercial terms to the organization’s designated reviewer; this guide does not interpret customer contracts.

Assign catalog scope to the intended company context

A customer account may contain multiple company locations, divisions, or buyer contexts, and a price intended for one scope can be misapplied if assignment keys are too broad. Map each requested catalog to the smallest maintained company or location scope that reflects the approved instruction, then record the person responsible for assignment and a way to verify the storefront result. Shopify documents catalogs as controlling products and pricing available to B2B customers and supports assignment to companies and company locations. Adobe Commerce describes shared catalogs with custom prices for different companies, including custom catalogs available only to members of specific company accounts. These are product examples; confirm the exact entities and behavior for the configured product and account.

Define precedence for overlapping catalog and price rules

Before publishing a customer-specific arrangement, draw the rules that can apply to the same buyer and item: base price, catalog-level adjustment, item-specific price, volume or quantity rule, discount, quote, and any manual override in the actual stack. For each overlap, specify whether rules combine, replace, or exclude one another; identify the expected winning result; and run at least one example with the same product in multiple assigned catalogs. Shopify’s current Help page states that when multiple catalogs contain prices for a product, the lowest price displays to the customer. Do not assume that precedence in another platform or that it matches an organization’s intended contract-price hierarchy; test and document the observed result.

Govern start dates and rollout separately

Keep the approved start instruction, scheduled publication action, and observed customer-facing change as distinct events. Assign an owner to confirm time zone, release window, downstream propagation, rollback or pause criteria, and the point at which the new value is checked in the customer context. Shopify documents a rollout to schedule a catalog’s status change only for a catalog created for a market; a catalog assigned directly to a company or company location cannot be added to a rollout. That documented status-change feature does not establish support for effective dates on individual prices. For other arrangements, define timing using verified capabilities of the actual system rather than assuming a catalog rollout schedules each price.

Separate review, quote, approval, and order commitments

Draw the handoff from requested pricing to the reviewed instruction, any buyer-facing quote, internal approval, accepted quote, and submitted order. For each transition, name who may draft, review, approve, publish, accept, or correct it; whether the quote records the relevant company and location context; which changes require another review; and what happens when the quote is expired, revised, rejected, or submitted with a mismatch. Adobe Commerce documents company accounts, shared catalogs, negotiable quotes, and purchase-order approval features within its B2B product documentation. Those capabilities can inform a platform evaluation, but do not define the approval path or contractual meaning for another organization.

Keep change history and testing evidence usable

For each price or assignment change, retain the prior and new value, scoped company or location and item, request or approval reference, effective instruction, editor or integration, timestamps, release identifier, and validation result where those records are available. A practical pre-release matrix includes an in-scope buyer, an out-of-scope buyer, a company with multiple locations, overlapping catalog entries, quantity thresholds when configured, an approved quote, a revised quote, a rejected or expired case, and an order created around the release boundary. Record expected and observed prices in the relevant buyer context without exposing customer-specific information outside approved internal systems.

Reconcile the published catalog through the resulting order

After release, compare a sample of approved price instructions with catalog assignments, buyer-visible product results, quotes, submitted order lines, and downstream records that the operating team relies on. Match on stable product and company/location identifiers, and investigate missing, duplicated, stale, or unexpectedly selected records before treating a batch as complete. Define a queue for exceptions such as a wrong company context, an overlapping rule, a late update, an unapproved override, an order created with a prior value, or a quote/order difference. Each item should have an owner, evidence, resolution state, and retest where appropriate. Related reading below connects this workflow to B2B account onboarding, B2B EDI operations, PIM integration, and order-management architecture.

First-party capability examples and source limits

Shopify’s Help documentation describes company and company-location catalog assignment, overlapping catalog prices with the lowest price displayed, and a rollout that schedules a catalog’s status change only when that catalog was created for a market; it explicitly excludes directly assigned company or location catalogs from rollouts. Adobe Commerce describes shared catalogs with custom product prices for different companies, access restricted to members of specified company accounts, and related B2B company-account, quote, and purchase-order features. These source pages were checked October 13, 2026. Treat each statement as a description of the named product documentation, not a vendor-neutral requirement or a claim about individual price effective dates.

Editorial note

This guide is education-only technical research for B2B commerce teams. It does not provide legal, tax, accounting, financial, security, performance, pricing, compliance, or individualized implementation advice, and it does not interpret customer contracts. Confirm current vendor documentation, approved commercial instructions, your own policies, and operating constraints before making a change.

First-party source register

First-party documentation and standards referenced during editorial review.

Continue reading