Skip to content
MousaBatarseh
Back to all notes

· By Mousa Batarseh

B2B Wholesale Collections That Match How Retailers Actually Shop

Most wholesale sites I have seen organize products the way the supplier thinks about them: by brand, by internal category, by whatever the product feed came with. That makes sense from the inside. It does not match how a retail buyer shops. B2B wholesale collections work better when they are built around restocking, because that is the job the buyer came to do.

I spent years on this at Universal Wholesale, running the Universal Wholesale and United Textile stores, and later on the wholesale B2B site at Wild Bill’s Tobacco. Here is how I think about it now.

How retail buyers actually use a wholesale site

A store owner restocking is not browsing. They are standing in their store, or sitting with a list, trying to refill specific shelves before a specific time of year. They know what sold, what is running low, and what season is coming. What they want from the site is to get to those items fast and order the right quantities.

That means the menu should answer the questions they already have in their head: what do I need for the next season, what goes in this section of my store, and what comes in a pack size that fits my shelf.

How should I organize collections on a B2B wholesale store?

I build collections along four lines. Not every store needs all four, but most benefit from at least two.

  1. By season. Back to school, summer, holidays, winter gear. Retailers plan around these dates and order ahead of them. A seasonal collection that goes live early gives them one place to build that order.
  2. By use. What the product is for, in plain words a shop owner would use. Workwear, home textiles, smoking accessories, party supplies. Not the internal category code.
  3. By pack or case size. A small corner store and a larger chain buy differently. Being able to filter for the pack sizes that fit their shelf space saves them from opening every product.
  4. By the retailer’s aisle. This is the one I like most. Group products the way they sit in the customer’s store, so the buyer can walk their aisles in their head and restock each one in order.

A product can sit in several of these at once. Shopify collections and WooCommerce categories plus tags both handle that, and it is fine. The goal is that the buyer finds it from whatever direction they come in.

Setting it up in Shopify

In Shopify I lean on automated collections driven by tags and product type. When the tags are consistent, a new product lands in the right seasonal and use collections the moment it is published, with no one remembering to add it by hand.

The work is in the tagging scheme. I write it down in a spreadsheet: the exact tag names, what each one means, and which collection it feeds. Then I clean the catalog against that list before building collections. Tags like Summer, summer and Summer2 will each create their own mess.

Setting it up in WooCommerce

WooCommerce gives you categories, which can be nested, plus tags and attributes. I use categories for the main use based structure, attributes for pack size so they can be filtered, and tags for seasons since those come and go.

With a large catalog, I do all of this through CSV imports rather than editing products one at a time. Export, fix the columns in Excel, import, then spot check a sample of products on the live site. It is the only sane way to restructure thousands of products.

Keep the old URLs working

Restructuring collections changes URLs. Retailers bookmark category pages, and search engines have them indexed. Every time I renamed or merged collections during a migration, I built a redirect map: old URL in one column, new URL in the next, loaded into the platform’s redirect tool. Then I tested the top pages by hand. Skipping this is how a store loses its regular buyers’ bookmarks and its search traffic in the same week.

Use promos and coupons inside the structure

Seasonal promos work better when they sit on top of the collections instead of beside them. On the stores I ran, a promo page usually pointed into an existing seasonal collection with a coupon applied, rather than a one off page with a hand picked product list. When the season ended, the promo came down and the collection stayed useful.

Check what buyers actually click

Once the structure is live, GA4 shows which collections get traffic and which get skipped. Search Console shows what retailers type into Google before landing on the site. If buyers keep searching the site for a term that is not a collection name, that is a collection you should probably build.

Keep the product titles working with the collections

Collections only get the buyer to the right shelf. Once they are there, the product grid has to make the choice easy. On wholesale catalogs I make sure every title includes the detail a buyer compares on, usually the pack or case size and the variant, so two similar items do not look identical in a grid. I also sort seasonal collections by what reorders most, not by newest added, because the buyer is usually looking for last season’s best seller first.

I also ask the sales team. People who take wholesale orders by phone hear how customers describe products, and that language belongs in the menu.

If your wholesale menu still mirrors your supplier categories, start small. Build one seasonal collection for the next season coming up and one collection grouped by a store aisle your best customers stock. Watch whether those pages get used, then expand from there.

Have a related task to discuss?

Email Mousa