B2B eCommerce Personalisation: How to Show Every Customer Their Own Prices, Products and Terms
B2B eCommerce personalisation means each trade account logs in to see a storefront built around their contract: their negotiated pricing, the SKUs they’re approved to buy, their credit terms, and their order history. It runs on account data held in your ERP, the system that already runs your customer master, stock, and pricing. It does not run on browsing behaviour. In Apex, a gated storefront identifies the account, its pricebook and hierarchy decide what applies, and a targeted homepage assembles the result at login.
Watch it work on a live storefront, then read on for how the pieces fit together.
Key Takeaways
- B2B personalisation isn’t just recommendations. It’s showing each trade account its own contract prices, product range, and payment terms before anything else happens.
- It starts at the login, not the homepage. A gated storefront identifies the account. The account’s pricebook and hierarchy decide what loads next.
- A targeted homepage is the output, not the feature. Reorder lists, account-specific promotions, and the buyer’s own catalogue, assembled from data your ERP already holds.
- This is a cost-to-serve lever. Every “what’s my price on this?” call your team fields is a question the storefront should have answered.
- It ships in weeks, not months, because the workflows are pre-built rather than custom-scoped.
What is B2B eCommerce personalisation?
We know the reality of trade selling. No two customers pay the same price, and half of them can’t buy half your catalogue.
Consumer personalisation is behavioural. It watches what someone clicks and guesses what they’d like. B2B personalisation is contractual. It reads who the buyer works for, what their business agreed to, and renders the storefront accordingly. Nothing is guessed. It’s already sitting in your system.
Three pieces of data do most of the work.
The account hierarchy. This is the structure of a customer’s business: a head office, its branches, and the individual buyers under each, with different permissions and approval limits at every level. A depot manager in Cork and the group buyer in Dublin belong to the same customer. They shouldn’t see the same screen.
The pricebook. This is the set of negotiated prices attached to an account or a group of accounts. Contract rates, volume breaks, tiered pricing, promotional lines.
The approved range. This is what the account is actually entitled to buy. Exclusive lines, restricted products, region-locked stock.
Get those three right and personalisation stops being a marketing feature. It becomes the thing that makes the site usable at all.
Why does B2C style personalisation fail in B2B?
Because it answers the wrong question. Consumer tools are built to help someone discover something new. Trade buyers aren’t discovering. They’re reordering, checking prices, and getting back to work.
|
What a consumer homepage does |
What a trade buyer needs on login |
|
Shows a hero campaign to everyone |
Shows their reorder list and saved carts |
|
Displays one list price |
Displays their contract price, per line |
|
Recommends what’s trending |
Recommends based on their purchase cadence |
|
Assumes the buyer can buy anything |
Enforces their approved range and credit limit |
|
Optimises for browsing |
Optimises for a repeat order finished in under a minute |
Force the first column onto a wholesaler, and you get a familiar result. Buyers log in, don’t trust the price on screen, and pick up the phone. The site turns into a catalogue with a form on it. The manual order cycle carries on exactly as it did before.
What does a targeted homepage actually show?
It’s the assembled output of the account data. For a returning buyer, that usually means:
- Recent purchases and saved carts, front and centre. The fastest route to a repeat order.
- Their pricebook applied everywhere, from the homepage tile to the cart line.
- Account-specific promotions. A campaign aimed at one customer group, not blasted at the whole base.
- Targeted product recommendations, driven by their own reorder pattern rather than site-wide bestsellers.
- Content and messaging by segment. A different homepage for food service accounts than for retail accounts, on the same platform, without a developer.
That last point matters if you own the roadmap. Launching a campaign to one customer segment shouldn’t need a ticket, a sprint, and a wait.
How does Apex decide what each buyer sees?
Four steps, in order.
- The gated storefront. A login wall over the whole store. No pricing and often no catalogue is visible to the public. Trade pricing stays where it belongs, which is behind the account.
- Identify the account and its place in the hierarchy. Which business, which branch, which buyer, and what they’re allowed to do.
- Apply the pricebook. Pulled from your ERP, with pre-built integrations for SAP, Microsoft Dynamics, NetSuite, Intact IQ, Epicor, and others. Where product data lives separately, it’s pulled from your PIM, the system that holds descriptions, specs, images, and categorisation.
- Render the targeted homepage. The buyer lands on a store assembled from their own data.
Steps one to four aren’t custom-built each time. They’re pre-built B2B workflows, already proven across trade sectors. That’s why this launches in weeks rather than months. Apex is built around the realities of B2B, not retrofitted from a consumer platform.
What does this change for your team?
Two things, mostly.
Cost-to-serve drops. Pricing questions, “can I buy this?” questions, and order status checks are all things the storefront can answer without a human. That’s time handed back to your sales and support teams.
And buyers actually use the site. A buyer who trusts the price on screen places the order on screen. A buyer who doesn’t email your rep a spreadsheet. Personalisation is what earns that trust.
Some orders will still arrive by email, PDF, or WhatsApp. Legacy buyer behaviours don’t disappear on launch day. Apex Order IQ captures those unstructured orders and converts them into structured ones, so the manual channel stops being a black hole.
Can we set this up without replacing our ERP?
Yes. That’s the point of integration-first architecture. Apex sits as a commerce layer over the systems you already run rather than replacing them. Your ERP stays the source of truth for pricing and stock. Apex reads it and renders it.
Want to know where your own setup stands before talking to anyone? Start with the B2B eCommerce Readiness Checklist.
Would you rather see your own pricing structure running on a live storefront? Book a demo, and we’ll walk your pricebook and hierarchy through it.
