Overview
Your catalog can have base pricing while individual buyers use a named tier or a custom override. Review the relationship currency and purchasing denomination when setting prices and minimum order quantities.
Choose a buyer's pricing
- Open the buyer relationship and the relevant product settings.
- Review the base price and MOQ.
- Select base pricing, a named pricing tier, or a custom price/MOQ where the form offers it.
- Review the effective values and save.
A named tier uses its configured values. Custom pricing keeps a buyer-specific override. Returning to base pricing clears the tier or override in that selection workflow.
Check quantity and currency
Make sure the price applies to the offered pack. Review currency separately from the displayed amount. A product's individual-unit price and its case price cannot be compared as if they have the same denominator.
Set payment terms
Use the buyer relationship's available payment-term controls to record the arrangement you agreed with that buyer. Check the terms shown on a created order because an order can retain its own terms.
Maintain pricing over time
Review affected relationships when changing catalog prices or named tiers. Do not assume a base-price change removes every buyer override. Check historical orders against their own agreed prices rather than rewriting them to match today's catalog.
If the buyer sees an unexpected price
Check the product and variant, relationship currency, selected tier, price override, MOQ override, and the order's stored information. Compare the intended agreement with the effective buyer-facing values.
Related: Product setup and Payment processing.