Some businesses sell online. Others need customers to find them online and buy locally — because the product is heavy, because it needs a technical decision, or because the channel runs on credit rather than cards. A tile manufacturer, a switchgear brand, a pump distributor and a plywood mill all have the same shape of problem, and it is not the one an eCommerce store solves.

The customer researches, compares and decides online. The order is placed with a dealer. And the manufacturer, who caused the sale, usually never sees that any of it happened.

What we build for this

A catalogue that survives being deep — thousands of items, filtered by the attributes that actually matter in your trade rather than by category alone. Technical selection, so a customer arrives at the right product instead of a list of twelve that look similar. Dealer locating by serviceable area rather than by a radius on a map. And enquiry routing that reaches the right dealer with the context attached: what they were looking at, what quantity, and where the job is.

Where it helps, we add the tools that turn a browser into an enquiry — quantity and coverage calculators, visualisers, sample requests, spares lookup. These are usually what make the difference between a catalogue people read and one they act on.

What this gives a manufacturer

Sight of demand you currently cannot measure. Which products are being researched, in which regions, at what project sizes — including the enquiries that never converted, which your dispatch data can never show you.

It also changes the dealer relationship. A dealer receiving a qualified enquiry with the product and quantity already decided is being given business, not having it taken. That is one of the few things a manufacturer can offer a dealer that the dealer genuinely wants.

Where we have done this

Building materials most deeply — tile, adhesives and the dealer networks that sell them, including our own products for the trade. Also B2B wholesale distribution, and publishing, where the catalogue runs to thousands of titles and finding the right one is the entire problem.

The trades differ. The structure does not: a deep catalogue, a technical or considered choice, a dealer channel in the middle, and a manufacturer who cannot see past dispatch.

What this covers

  • Catalogues that stay usable at several thousand items
  • Filtering on the technical attributes your trade actually selects by
  • Product selectors, so customers reach the right item rather than a list
  • Dealer locating by serviceable area, not a radius on a map
  • Enquiry routing with full context — product, quantity, location
  • Quantity, coverage and estimation tools built into the catalogue
  • Sample requests and spares lookup where the trade needs them
  • Demand reporting by product and region, including enquiries that did not convert
  • Local fulfilment flows where goods are too heavy to ship

How engagements work

  1. Catalogue audit

    How your product data is structured today, and whether it can support filtering. Usually the longest part.

  2. Channel mapping

    How your dealers are really organised — territories, overlaps, who serves what.

  3. Build

    Catalogue, selection, dealer locating and routing, plus whichever tools earn their place.

  4. Pilot

    One region and willing dealers first. Response times and fulfilment vary more than anyone expects.

Technology

  • PHP
  • Laravel
  • Node.js
  • React
  • PostgreSQL
  • MySQL
  • Elasticsearch
  • REST APIs

Related work

Where we have done this

Tell us what you are building

We will tell you how we would approach it, and whether we are the right fit.