How do we stop the storefront and sales team giving the same trade buyer different answers?

Stop letting your website and your ERP calculate prices using separate rules. Either pass the exact pre-calculated ERP price lists (and rounding rules) into your eCommerce platform's B2B pricing tables on a monitored schedule, or query the authoritative price directly against the parent Account ID, and make sure both online and phone orders read from that same table.

Which system should be the source of truth for B2B pricing and credit terms?

In our experience, for an established trade or wholesale business, the ERP or accounting system that generates the legal invoice should be the source of truth for pricing, tax treatment, pack multiples and credit limits. If a sales rep agrees a special rate in the CRM, that change should update the ERP price list first, which then feeds the website.

Why do some people at a trade customer see their trade prices while their colleagues don't?

Because the store is tying trade status to an individual email login rather than a parent company account. When a second buyer or site manager at the same contractor registers on the website, the store treats them as a new retail shopper. Structuring your customer data and identity matching around a parent Account -> child Contact hierarchy solves that cleanly.

When a trade customer sees the wrong price, which system owns the answer?

Trade buyers seeing retail prices or outdated credit terms when they log in? How to fix source-of-truth and sync rules between ERP, CRM and B2B eCommerce.

When a trade customer sees the wrong price, which system owns the answer?

Nothing kills adoption of a B2B or trade website faster than a regular account customer logging in, looking up a product they buy every month, and seeing the wrong price on screen. They don't place the order online and ask for a credit note later. They close the browser tab, pick up the phone to their account manager, and go back to emailing or phoning every order through by hand. When we trace why that happened, we rarely find a single broken line of code on the product page. Instead, we find **three different systems (the ERP, the CRM and the eCommerce storefront) all claiming to own the customer's price and account status at the same time.** ## Tracing one trade price from the back office to the basket On a consumer store, price is simple: one SKU has one retail price, plus an occasional promo code. On a B2B or trade site, the price a logged-in buyer should see depends on a chain of five separate facts: 1. **Who the buyer is (Contact identity):** Which individual login is browsing the site. 2. **Which company they belong to (Parent Account):** Linking that individual buyer to the contracting trade account rather than treating them as a standalone shopper. 3. **Their agreed p