B2B pricing¶
b2b-pricing
Price for business buyers with customer-group price lists, quantity tiers, contract prices, minimum quantities, net terms, and tax exemption, resolved on the server. Use when adding wholesale or B2B prices, tiered pricing, quotes, or company accounts to a store.
Version 0.3.2 · MIT · Source · Rule
Install this skill
Copy the skill and its rule into your project:
The skill goes to .agents/skills/ and the rule to .agents/rules/. See Command line for other directories.
Business buyers see different prices for the same SKU. The price must be resolved by one server function from the buyer's account, the quantity, and the date, and the same function must run in the catalog, the cart, and the order. Data shapes are in the price list notes.
Procedure¶
- Attach buyers to a company account, and the company to one or more customer groups. A person can buy for more than one company; the cart belongs to one.
- Store prices as price lists: a list has a currency, a validity window, a priority, and entries of SKU, minimum quantity, and unit price or a percentage off the base price.
- Resolve the unit price in one function: contract price for this company, then group price lists by priority, then the public price. Within a list, use the highest tier whose minimum quantity the line meets.
- Show the buyer the next tier ("10 or more: 8.50 each") so they can choose the quantity.
- Enforce minimum order quantities and pack sizes (order multiples) in the cart, with a message, not only at checkout.
- Recalculate prices on every cart change and again when the order is placed. The price stored on the order line is final.
Resolution¶
Run node scripts/resolve-price.mjs request.json lists.json to see which list and tier win for a line. It returns the unit price, the source, and the next tier.
Decide and write down what happens when two rules apply. The usual answer is the contract price wins if one exists. Otherwise the lowest price from the active lists wins. Some stores use priority instead. Pick one; mixing them gives prices nobody can explain.
Terms, quotes, and tax¶
- Net terms (Net 30) are a payment method that creates an unpaid invoice with a due date. Check the company's credit limit against open invoices before allowing it.
- A quote is a price offer with an expiry, created by staff or requested by the buyer. Accepting it creates a cart with the quoted prices locked until the expiry.
- Tax-exempt buyers need a stored exemption certificate or a validated tax id. In the EU, a cross-border B2B sale to a buyer with a valid VAT number (checked through VIES) can use the reverse charge. Store the check result on the order.
- Show prices with or without tax according to what the buyer's group expects, and say which one is shown.
Gotchas¶
- Computing the B2B price in the browser lets anyone see or send another group's price. Resolve on the server and render the result.
- Caching a product page that shows a group price serves that price to every visitor. Vary the cache by group, or load the price separately.
- A tier is per line by default. If the store promises mix-and-match tiers across a product's variations, sum the quantity across those lines first.
- Percent-off entries on a list need a defined base: the public regular price, not the sale price, unless the store says otherwise.
- Changing a price list must not change orders already placed.
Verification¶
- A guest sees the public price. A buyer in the wholesale group sees the wholesale price on the product page, in the cart, and on the order.
- With the example list in the notes, 9 units cost 9.00 each (the 1+ tier) and 10 units cost 8.50 each (the 10+ tier).
- A company with a contract price gets it even when a group list is lower, if the store's rule says contract wins.
- An order below the minimum quantity cannot be placed.
- Net terms are refused when open invoices plus the order exceed the credit limit.
Evaluation¶
Worked examples and the checks they must satisfy are in evals/tasks.json.
References¶
Price lists¶
Shape¶
{
"id": "wholesale-2026",
"currency": "EUR",
"groups": ["wholesale"],
"priority": 10,
"validFrom": "2026-01-01",
"validTo": "2026-12-31",
"entries": [
{ "sku": "MUG-RED", "minQuantity": 1, "unitPrice": 9.00 },
{ "sku": "MUG-RED", "minQuantity": 10, "unitPrice": 8.50 },
{ "sku": "MUG-RED", "minQuantity": 50, "percentOff": 20 }
]
}
A contract is a price list with companies instead of groups.
Rules¶
| Rule | Recommendation |
|---|---|
| Which lists apply | Lists for the buyer's company (contracts), then the buyer's groups, valid on the order date, in the cart currency |
| Tier inside a list | Highest minQuantity that is at most the line quantity |
| Several lists apply | Contract first. Then the lowest unit price, or the highest priority if the store chooses that. Record the rule in one place. |
percentOff base |
The public regular price of the SKU |
| Rounding | Round the unit price to the currency's minor unit, then multiply |
Request for the resolver script¶
{
"sku": "MUG-RED",
"quantity": 12,
"company": "acme",
"groups": ["wholesale"],
"date": "2026-10-30",
"currency": "EUR",
"basePrice": 11.0,
"strategy": "lowest"
}
Evaluation¶
Fixtures from evals/tasks.json. See evaluation fixtures for how the checks work.
tiered-wholesale¶
Wholesale buyers pay 9.00 per mug, or 8.50 each from 10 mugs. Guests pay 11.00. Describe where the price is computed and what a wholesale buyer sees for 9 and for 10 mugs.
Must include: server, price list, minQuantity, 9.00, 8.50
Must not include: compute the price in JavaScript in the browser
Worked example
The unit price is resolved on the server by one function used by the product page, the cart, and order placement. The wholesale group has a price list with two entries for the mug: minQuantity 1 at 9.00 and minQuantity 10 at 8.50.
A wholesale buyer ordering 9 mugs gets 9.00 each and sees "10 or more: 8.50 each". At 10 mugs the line is priced at 8.50 each. A guest matches no list and pays the public 11.00. The product page cache varies by group so the wholesale price is never shown to guests.
net-terms¶
A company account wants to pay by invoice on Net 30 terms. What checks run before the order is accepted?
Must include: credit limit, open invoices, due date
Worked example
Net 30 is offered only to companies with terms enabled. Before accepting the order, sum the company's open invoices and add this order total. If that exceeds the credit limit, refuse invoice payment and offer card payment instead.
If it fits, place the order as unpaid, create an invoice with a due date 30 days after the invoice date, and send it to the company's billing contact. Overdue invoices block further orders on terms.