Pricing and customer terms: every buyer sees the deal you agreed

Which system owns the price?

The ERP owns the price, because the ERP writes the invoice. A price in the store that differs from the invoice produces a credit note, a phone call or both. The store receives prices and never sends one back.

A general price is the simple part: one number per item. B2B pricing is the rest of the table. At 50 customers the exceptions are manageable by hand. At 500 customers there are thousands of customer-and-item combinations, and each one is a place where the store and the invoice can differ.

Pricing is one of the five flows on the integrations overview.

The four price layers

A B2B price is built from layers, from general to specific.

Take item 10482 with a list price of $12.50. The Wholesale price level gives 20% off: 12.50 times 0.80 is $10.00. From 100 units a quantity break gives 5% more: 10.00 times 0.95 is $9.50. Customer 10432 has a contract price of $9.60, valid from January 1 to December 31, 2026.

Customer 10432 orders 120 units. Which price applies depends on the rule in the ERP, and the three ERPs below do not use the same one:

The difference is $12.00 on one order line. A store that applies "lowest price wins" in front of an ERP that applies "most specific wins" is wrong on every order where a contract price sits above a quantity break. The integration reproduces the rule of the ERP it is connected to.

Discounts come in three forms: a percentage, an amount and a replacement net price. They stop being interchangeable when they stack. 20% and then 5% is 24% off, not 25%: 12.50 times 0.76 is $9.50, while 12.50 times 0.75 is $9.375. On 120 units that is $15.00.

What actually moves

No black box: these are the fields in a price flow.

Inside the integration a price record has one shape, whatever the source and target are:

{
  "sku": "10482",
  "currency": "USD",
  "unit": "each",
  "list_price": "12.50",
  "levels": [
    { "level": "Wholesale", "price": "10.00" }
  ],
  "quantity_breaks": [
    { "level": "Wholesale", "min_qty": 100, "price": "9.50" }
  ],
  "contracts": [
    { "customer": "10432", "price": "9.60",
      "valid_from": "2026-01-01", "valid_to": "2026-12-31" }
  ]
}

Amounts are decimal text with a currency, never a floating-point number and never a bare integer. Dates are ISO 8601.

Where the fields come from differs per ERP. In NetSuite a customer has a Price Level field, a Group Pricing list that sets a level per pricing group, and an Item Pricing list that sets a level or price per item. In SAP Business One an item has a price per price list, and a special price for a business partner carries validity periods with a quantity scale inside each period. In Business Central a sales price list applies to a customer, a customer price group or all customers, with a minimum quantity, a unit of measure and a starting and ending date per line.

On the store side, Shopify B2B holds prices in a price list attached to a catalog. A price list has a percentage adjustment against the base price and fixed prices per variant that override it. Payment terms on a company location are net 7, 15, 30, 45, 60 or 90, or due on fulfillment. Adobe Commerce B2B uses shared catalogs with custom prices per company. A credit limit, a PO number and a tax exemption travel with the customer and the order; those are part of B2B terms in the orders flow.

What goes wrong quietly

A factor of 100. One system sends 12.50, another sends 1250 and means cents. Read the wrong way, a $12.50 item is published at $1,250.00, or at $0.13. Every amount is carried with its currency and its unit, and a run in which a price moves by more than a set percentage is held for approval.

Rounding per unit or per line. A unit price of $9.375 times 120 is $1,125.00. Rounded to $9.38 first, it is $1,125.60. The store and the ERP differ by 60 cents, the payment does not match the invoice, and automatic matching in accounts receivable stops. The integration rounds where the ERP rounds. The notes on money, tax and rounding work through the cases.

Price per box, sold per unit. The ERP price is $114.00 per box of 12 and the store sells single units. Published without the conversion, one unit costs $114.00 instead of $9.50. The unit of measure moves with the price, and the conversion factor comes from the item record. See units of measure.

A contract that expired last night. The contract price for customer 10432 ends on December 31. On January 1 nothing changes in the ERP record, so no change event is sent, and the store keeps showing $9.60. The integration evaluates the valid-from and valid-to dates itself, every night, in the time zone of the ERP.

A promotion overwritten by the next run. Marketing sets item 10482 to $8.99 in the store for a week. At 02:00 the price run writes $12.50 back. Products with a manual arrangement go on an exclusion list with an end date, and the run skips them.

A price change while an order is placed. A buyer adds 120 units at $9.50 at 1:55 PM. At 2:02 PM the ERP price changes to $9.80. The order arrives at 2:05 PM with $9.50. The rule is set once: the confirmed price stands and the ERP imports the order with that price, with the difference of $36.00 flagged on the order.

Tax counted in. A list price that includes tax in one system and excludes it in the other is off by the tax rate on every item. Each price field is marked as including or excluding tax, per source.

Throughput and limits

A catalog of 8,000 items and 500 B2B customers is 4,000,000 customer-and-item prices when every combination is written out. Almost none of those are distinct. The same catalog stored as layers:

6 price levels x 8,000 items          48,000 prices
40 customers with a contract,
  80 contract items each               3,200 prices
total                                 51,200 prices

Shopify accepts up to 250 items in an array input, so 48,000 level prices are 192 calls and 3,200 contract prices are 13. A nightly change of 600 prices on one level is 3 calls.

Sources: Shopify B2B features by plan, NetSuite price levels for customers and Business Central operational limits, checked on October 3, 2026.

The catalog limit decides the design. The example above needs 6 catalogs for the levels and 40 for the contract customers: 46. That fits on Plus. On a plan with 3 active catalogs, three levels fit and contract prices need another mechanism, which the customer-specific pricing page describes.

On the ERP side the cost is in the reading. Customer item pricing sits on the customer record in NetSuite. Reading it customer by customer is 500 requests against an account that processes 5 to 20 at a time and shares that number with every other integration. One query that returns all customer-and-item prices in pages replaces them.

Scheduled, event-driven or checkout-time

A price reaches the store in one of three ways, chosen per price type.

A scheduled run is the easiest to check: one diff a day. Event-driven needs the ERP to report changes, and a nightly comparison to catch what an event missed. Checkout-time gives the exact ERP price and makes the checkout depend on the ERP: each request counts against the same limit as every other call, which is 5 concurrent requests on a NetSuite Standard tier account. A checkout-time lookup therefore has a time limit, and the last synchronized price is used when the ERP does not answer within it. Real time versus batch covers the choice per flow.

Where standard connectors stop

Standard connectors and iPaaS platforms are built around one price per item. The documented shape for the common NetSuite and Shopify connector is one price level for the selling price and one for the compare-at price, in one currency per store instance. A second or third price level is added through custom fields on the item that a script in the ERP has to keep filled. Tier pricing is mapped per customer group, and a price agreed with one customer is outside the mapping.

Per-customer catalogs exist there as a template next to the managed connector. A template is a starting point: after installation it receives no fixes and no new functionality, and orders from the B2B side have to be filtered out of the standard flow by hand so they are not imported twice.

In an integration built for your price structure, every layer the ERP uses is in the flow: levels, group pricing, contract prices with dates, quantity breaks and units. The per-customer catalogs page shows how assortment and price go together, so an account sees only what it may order.

You stay in control

A price run is compared with the current prices before anything is written.

• Dry run. The run calculates every price and writes nothing. You get the list of changes.
• Approval. Per price list, changes wait for approval or go through automatically.
• Exclusions. Products with a promotion or a manual price are skipped until their end date.
• Hold rule. A run in which more than a set share of prices moves by more than a set percentage is held.
• Diff per run. Item, customer or level, old price, new price and the ERP record it came from.

run 2026-10-02 02:00   source: NetSuite   prices compared: 51,200
changed: 612    unchanged: 50,574    excluded: 14
10482  Wholesale        10.00 -> 10.40   item record, edited 10/01/2026
10482  customer 10432    9.60 ->  9.75   contract renewed to 12/31/2027
10517  Wholesale        48.00 -> 4.80    held: change of -90%

The third line is a typing error in the ERP. It is held, shown in the dashboard and released or corrected by you. The dry run and approval page describes the controls in full.

In depth

• Customer-specific pricing: contract prices and quantity breaks for logged-in buyers, per platform.
• Per-customer catalogs: each account sees only its own assortment, at its own price.
• B2B terms: credit limits, payment terms such as Net 30, tax exemptions and buyer permissions.

Pricing connects to two other flows. Contract prices inside a procurement session are part of PunchOut. Whether an item with a price can ship is part of stock and availability.

Systems and platforms

ERP systems. NetSuite with price levels, pricing groups and item pricing per customer. SAP Business One with price lists and special prices per business partner, each with date ranges. Business Central with sales price lists and best-price calculation.

Store platforms. Shopify with B2B catalogs, of which 3 are active below Plus. Magento with customer groups, and shared catalogs in Adobe Commerce B2B. BigCommerce and WooCommerce.

Combinations. Shopify B2B and NetSuite, Shopify and NetSuite and Magento and SAP each have a page with the mapping for that pair.

Send us an export of one price list and the pricing rules your sales team applies, and you get a concrete answer on how they map. Tell us what you run.