Distributors

You sell other people's products. Tens of thousands of them, to thousands of customers, most of whom will never justify a sales visit. Your field team knows the top few hundred articles and sells them well. The rest of the range sits in the ERP as working capital that nobody can see: the M6×35 screw in A4 stainless has a record, a stock figure and a price, but no page, no description and no photograph. When your customer's buyer needs it at nine in the evening, they search the web and find someone else's page for it. That is the whole of the long-tail problem, and it is not a logistics problem.

The second half of your reality is upstream. Your catalog is not yours. It arrives from several hundred suppliers in whatever shape each of them sends: a clean BMEcat from the large ones, a spreadsheet with merged cells from the small ones, an archive of images named by article number from someone's marketing agency. And it changes every quarter. Meanwhile an Innendienst colleague works through thirty orders a day from email, fax and the phone, retyping article numbers that the customer already had in a file. Both halves have the same answer: your margin is in the work you do not have to do.

What is different about your business

Your catalog is other people's data, and ingestion is your core competence. A manufacturer's catalog grows by a few hundred articles a year and every one of them is written in-house. Yours grows by a supplier at a time, and you control none of the quality. What you can control is the rule: what a record must contain before it may be sold, and what happens to the ones that fail.

The long tail only pays if nobody touches it. The margin on a fourteen-euro line does not survive a phone call, a manual price lookup or a retyped order. Judge every feature you build for the tail by whether it removes a human step.

Search is your shop. With six figures of articles nobody browses a category tree. Buyers arrive with a manufacturer's article number, their own internal number, a fragment of a description, or a specification. Your zero-results report is a demand signal and a roadmap.

Your customers are many, small and mostly unknown to you. New accounts arrive by self-registration rather than through a salesperson, which means credit checks, payment terms and approval have to work as a routine process rather than a favour.

Your discount structure is a matrix, not a price list. Fourteen per cent on product group A, eight on group B, per customer group, with exceptions. Maintained in a spreadsheet, it is correct until the next supplier price increase, and then it is three days of manual work during which your quotes are wrong.

A large part of what you sell repeats. Consumables, packaging, protective equipment, fasteners. The customer does not want to decide again every six weeks; they want it to arrive.

Your path

Phase 1: Build a supplier data pipeline, not an import

The point of this phase is that loading supplier number 300 costs an afternoon, not a project. If your first import is a one-off, you have bought a catalog that is accurate on the day it lands and stale for ever after.

1. Publish a digital product catalog: the goal page for this phase.
2. How product information management works → The catalog data model
3. Plan your data model. With several hundred suppliers, decide the shared spine first: Attributes and attribute groups, Families, Categories.
4. Catalog exchange formats: what BMEcat gives you and what it does not.
5. Prepare your import file → Import products in bulk → Edit many products at once
6. Completeness and readiness: the rule that decides what is sellable.
7. Data quality in practice

Phase 2: Make the tail findable and orderable without you

Now open it, first to your existing customers, then to search engines.

1. Move existing customers online and Reach more customers: the two goal pages for this phase, in that order.
2. How B2B buyers actually search → Configure the index → Facets and filters → Synonyms, stop words and rules
3. Quick order and cart import and Order lists and recurring carts, for buyers who already have the numbers.
4. Contract prices for a customer and Scale and volume prices, then Rounding, defaults and resolution rules for the matrix.
5. Self-registration → Approve a registration → Payment terms and credit limits
6. Working the zero-results report: start this in week one and never stop.

Phase 3: Take the routine work out of the Innendienst

Only now is it worth automating, because only now is the volume there to automate.

1. Cut manual work → Connect your ERP → Integration patterns → Deciding your system of record
2. Build recurring revenue → How smart reordering works → Standing orders → Configure reorder suggestions
3. For the accounts large enough to mandate it: Connect via punchout.
4. Sell through marketplaces and channels: the same catalog, cut per channel.
5. Monitor your syncs and Search analytics: the two dashboards this business runs on.

The mistakes we see most in your industry

• Waiting for the catalog to be complete. It never will be. Define what a record needs in order to be sellable, publish everything that clears the bar, and keep the rest out of the index. A partial catalog that is honest beats a full one that lies about stock and specification.
• Importing each supplier by hand as a small project. Then nobody dares re-import, because the manual corrections would be lost, and the catalog is frozen at its import date. Build the rules so a re-import is routine and the corrections survive it.
• Treating search as configuration rather than a job. Synonyms, boosts and zero-result terms need a named owner and an hour a week, permanently. In a long-tail business this is the highest-return hour on the calendar.
• Keeping the discount matrix in a spreadsheet after go-live. It was already fragile when only the Innendienst saw it. Once customers see the output live, every stale cell is a lost order or an argument about an invoice.
• Reporting one conversion rate across two hundred thousand articles. The number is meaningless. Segment by how the buyer arrived: article-number search, category, quick order, reorder. Those four behave nothing alike.

What to measure

• Revenue from articles outside your top 500. The definition of long-tail progress, and the only number that proves the project. Track it monthly as a share of total.
• Distinct articles ordered per month. Breadth, not volume. A rising count means the tail is being found.
• Zero-result rate, and the top zero-result terms. Fix the top twenty every month; most are synonyms, unit notation or a missing supplier.
• Orders per Innendienst colleague, and the share that arrived without retyping. The efficiency case for the whole programme.
• Days since the last successful import, per supplier. The freshness metric. A supplier at ninety days is selling stale prices through your shop.
• Share of order lines that came in through quick order or file upload. These are your cheapest lines; when the share stops rising, the entry path has a defect.
• Time from self-registration to first order, and how many registrations never place one. That gap is usually credit approval, not interest.

Where to start reading

1. Prepare your import file: everything downstream inherits the shape you choose here.
2. How B2B buyers actually search: the tail is only worth having if it is findable.
3. Reach more customers: the commercial case, with the obstacles named.

What you're building

A catalog that is fed, not typed: supplier files land in an import profile, pass a sellability rule, and appear in the shop with the customer's matrix price. Unknown buyers register themselves and pay without credit risk until someone upgrades them. Orders leave for the ERP without a person in between, and the ERP sends stock and prices back. Search over that catalog is where most of the revenue starts, which is why the attributes underneath it are the investment.

flowchart LR
  SUP["Suppliers: BMEcat, CSV, images"]
  ERP["Your ERP"]
  subgraph IS["Integration Studio"]
    IMP["Import profiles and SFTP"]
    WF["Workflows"]
  end
  subgraph CS["Commerce Studio"]
    P["Products: shared attribute spine"]
    PR["Price lists: matrix per segment"]
    C["Organizations and segments"]
    OL["Order lists and cart import"]
    O["Orders"]
  end
  subgraph XS["Experience Studio"]
    SF["Storefront with self-registration"]
  end
  SUP -- "catalog files" --> IMP
  IMP -- "records that pass the rule" --> P
  ERP -- "stock, prices" --> WF
  WF --> PR
  SF -- "registration" --> C
  SF --> OL
  OL --> O
  O -- "order" --> WF
  WF --> ERP
  SRCH["Search app (planned)"]:::planned
  SRCH -.-> SF
  RE["Reorder suggestions (planned)"]:::planned
  RE -.-> OL
  classDef planned stroke-dasharray: 5 5

What you need

• A shared attribute spine that every supplier's data maps onto, decided before the first import — Plan your data model
• A written sellability rule: what a record must contain before it reaches the shop — Completeness and readiness
• One import profile per supplier format that can be re-run without losing your own enrichment — Prepare your import file
• The discount matrix as price lists per customer group, with contract entries for the exceptions — Design your price lists
• A default price list and a payment method with no credit exposure for buyers you do not know yet — Payment terms and credit limits
• Self-registration that creates an organization in an unvetted segment — Self-registration
• Article numbers that match between your ERP and the catalog, including the supplier's number as an attribute — Field mapping
• A named owner for search terms and zero results, one hour a week — Working the zero-results report

Build it

1. Decide the attribute spine, the families and the category tree that every supplier maps onto — Plan your data model
2. Write the sellability rule as a completeness requirement for the web channel — Completeness and readiness
3. Build the import profile for your largest BMEcat supplier and run it twice, to prove re-import is safe — Import products in bulk
4. Repeat for the next five suppliers, one profile per format, until a new supplier is an afternoon — Catalog exchange formats
5. Publish everything that clears the rule, with filters on the attributes buyers search by — Publish a digital product catalog
6. Model the discount matrix as segment price lists and load it from the ERP — Import prices in bulk
7. Give ten regular customers their contract prices, quick order and order lists, and watch them use it — Move existing customers online
8. Switch on self-registration with a default price list and prepayment — Reach more customers
9. Start the weekly zero-results routine and assign it to a person — Working the zero-results report
10. Connect the ERP: orders out immediately, stock in by the minute, prices in nightly — Connect your ERP
11. Route every order that fails the happy path to a named person with a reason — Cut manual work
12. Turn the recurring baskets of your twenty steadiest customers into order lists, then into standing orders once the planned surface ships — Build recurring revenue
13. Connect the two or three accounts that mandate punchout — Connect via punchout

Decisions you'll need to make

Related product areas

• Commerce Studio — Products · Import · Attributes · Categories · Price lists · Segments · Payment terms · Order Lists · Cart import/export · Orders
• Experience Studio — Sites · Forms · Messaging
• Integration Studio — Import export · Sftp server · Workflows · Runs · Field mapping