# Fast WordPress for B2B & Wholesale Catalogues — xSpeed Cache

> Wholesale catalogues are enormous, logged-in, and priced per customer — the hardest case for naive caching. How B2B suppliers speed up WooCommerce with xSpeed Cache, including the exact AI prompt.

Page: https://xspeedcache.com/use-cases/for/b2b-wholesalers/
Category: Retail & ecommerce
Also covers: wholesale, wholesaler, b2b, distributor, manufacturer, supplier, trade prices, bulk, industrial, components, catalogue, catalog, spare parts, trade counter, procurement

## The speed brief

- **Who arrives** — A buyer at work with a part number and a deadline
- **What they want** — The right SKU, their trade price, and stock
- **How long you get** — The length of their patience with a supplier portal

## When speed decides the outcome

1. **The lookup** — They know the part number. They just need your site to find it quickly.
2. **The price** — Trade pricing is per-account, so the interesting page can never be cached whole.
3. **The order** — Slow procurement sites get replaced by whichever supplier is less annoying.

## The story

A wholesale catalogue is the case generic cache plugins quietly give up on. Priya’s company lists eleven thousand parts, and the price on any one of them depends on which account is logged in — so the page that matters most is the page you must never serve from a shared snapshot.

Giving up on caching entirely was the status quo, and it showed: every category browse and every search ran the full stack, and buyers who use the site all day felt every second of it.

The split that works is not page-level, it is layer-level. Public catalogue pages and spec sheets cache as static HTML; the priced, logged-in views are excluded but sit on an object cache, so the queries behind them come from memory. Nobody ever sees another account’s price, and nobody waits.

## What a site like this needs

- **Per-account pricing that is never shared** — This is the correctness requirement that outranks everything. Logged-in, priced views must never be cached across accounts.
- **A catalogue that browses quickly** — Eleven thousand SKUs means heavy taxonomy and meta queries on every category page.
- **Speed for people who live in it** — Trade buyers use the site daily. Small delays compound into a reason to call a competitor.

## The xSpeed features doing the work

- **Cookie-based exclusions** — Logged-in and per-account priced views are excluded by cookie, so a trade price is never served to the wrong account. Guide: https://xspeedcache.com/docs/excluding-pages-urls-and-cookies
- **Object cache (Redis / Memcached)** — The repeated queries behind category browsing and search are answered from memory, which is what speeds up the uncacheable pages. Guide: https://xspeedcache.com/docs/object-cache-redis-memcached
- **Custom cache rules** — Public spec sheets and catalogue pages cache aggressively while account areas are carved out precisely. Guide: https://xspeedcache.com/docs/custom-cache-rules

## The exact AI prompt

Connect via xSpeed MCP (https://xspeedcache.com/docs/mcp-server-setup) or xSpeed Hub, then paste:

```
Using xSpeed, optimise my B2B WooCommerce catalogue. It has 11,000 products and customer-specific pricing for logged-in trade accounts. Set up cookie-based exclusions so no logged-in or priced page is ever cached, cache the public catalogue and spec pages aggressively, and connect Redis object caching to speed up the category and search queries. Verify that a logged-in account never receives a cached page, then benchmark before and after.
```

What happens: Your AI configures the exclusions, confirms no priced page is cacheable, connects the object cache, and reports the improvement on category browsing.

## FAQ

### How can I be certain a trade price is never shown to the wrong account?

Logged-in requests bypass the page cache, and any cookie your pricing plugin sets can be added to the exclusion list so those responses are never stored. You can verify it directly: the cache status of a logged-in priced page should report as excluded, and your AI can check that for you.

### If the priced pages are not cached, what actually gets faster?

The object cache. Those pages are slow because of repeated database queries for taxonomy, product meta, and pricing rules; serving those from memory cuts the page generation time substantially even though the HTML itself is built fresh every time.

## More

- [Full playbook: xSpeed for WooCommerce stores](https://xspeedcache.com/use-cases/woocommerce/index.md)
- [Retail & ecommerce: Fashion & apparel stores](https://xspeedcache.com/use-cases/for/fashion-boutiques/index.md)
- [Retail & ecommerce: Electronics stores](https://xspeedcache.com/use-cases/for/electronics-stores/index.md)
- [Retail & ecommerce: Handmade & craft sellers](https://xspeedcache.com/use-cases/for/handmade-sellers/index.md)
- [Retail & ecommerce: Car dealerships](https://xspeedcache.com/use-cases/for/car-dealerships/index.md)
- [All use cases](https://xspeedcache.com/use-cases/index.md)
- [Free plugin](https://wordpress.org/plugins/xspeed/)