Checking custom price lists and negotiated terms

Use two customer accounts with different agreements and follow the same product from the signed-in view to the cart and resulting order. Include a product covered by the agreement, one outside it and one with a quantity rule; compare the displayed access, price and terms for each buyer.

Define the commercial rule

Record whether each standing price or access rule applies to a company, location, group or product variant. Note the configured quantity breaks, minimum order quantity, payment terms and any effective dates or approval requirements.

Test quantity rules just below, at and above each configured break, and test an order below the minimum quantity. Shopify names its B2B controls “quantity rules” and “volume pricing”; compare the configured rule with the price and order quantity available to the buyer.

For a temporary price exception, Pricefx terminology identifies temporary price lists and price overrides that are valid for a period. Check the buyer's displayed price while the override is active, and check any required approval: Pricefx approval workflows can require a specific user or group to approve when quote content breaches configured thresholds, such as minimum margin.

Check documented controls and limits

In Adobe Commerce B2B, Shared Catalogs can provide custom pricing for different companies. On the Shared Catalogs page, “Set Pricing and Structure” determines product selection and custom pricing, while “Assign Companies” determines which companies can access the catalogue; compare those assignments with each buyer's product view and price.

Adobe Commerce also has a documented permission rule: when Shared Catalog is enabled, it controls category permissions, and existing group permission settings are ignored. Use that rule to check product access; do not assume it establishes priority between overlapping prices.

BigCommerce B2B Edition company accounts are independent of customer groups. Groups can optionally set pricing and the viewable catalogue for a company or group of companies, so verify the intended company-to-group mapping and compare the signed-in buyer's actual price with the expected one.

For overlapping price agreements, compare the buyer's displayed price with the agreement intended for that account and location. If the configured result differs, record the difference rather than treating the list price or a group assignment as proof of the buyer's price.

Keep payment terms separate

In FlexiBake, assign a customer's default term in Maintain Customers, under Billing Details in the Payment Terms field. That term becomes the default for new sales orders, and terms can also be adjusted order by order; check the customer's assigned value and the resulting sales order.

For AWS Marketplace private offers, payment terms are selected in AWS Partner Central on the Configure offer pricing and duration page. Available choices include the customer's AWS default and Net 15, Net 30, Net 45, Net 60, Net 90 or Net 120; the selected term sets the time to pay from invoice issuance and applies uniformly to charges within the offer.

Do not treat a negotiated unit price as evidence that the buyer has the intended payment terms. For each account, compare the assigned term with the term on the resulting order or, for an AWS Marketplace private offer, the invoice due date.