When the website qualifies the buyer but doesn’t close the sale, every architecture decision changes. M.L. Campbell® is a Sherwin-Williams® industrial wood-coatings brand sold entirely through a distributor network. A cabinet shop can’t buy a five-gallon pail of conversion varnish from the website; they buy it from the distributor twenty minutes down the road, who stocks it, knows what tints into what, and will answer the phone on a Tuesday afternoon when something’s gone sideways on a finishing line.
The website’s job is to get the right product into the right finisher’s head, then hand them off to that distributor before they bounce to a competitor. That one constraint reshaped every decision in the build.
The constraint as the brief
Most manufacturer sites are organised the way an internal catalogue is organised: by brand family and by SKU series, the way the marketing team that maintains it likes to see it laid out. It is the wrong organising principle for the buyer.
A finisher evaluating a topcoat doesn’t think in SKU families. They think in application categories: clear topcoat, wiping stain, vinyl sealer, conversion varnish. They may not know M.L. Campbell’s internal product line structure, and they shouldn’t need to. The information architecture (IA) on this site is built around the job the finisher is trying to do — categories first, brand names and SKUs underneath, where someone who already knows “I want Krystal™” can drill straight in without the detour.
I came to this build already running the M.L. Campbell Distributor Training Centre, so I knew the channel. Training the distributors taught me what a finisher actually asks before they pick a topcoat — usually some version of “will this spray through the gun I already own and recoat in the window I have between the morning and afternoon runs.” That context did more for the information architecture than any discovery workshop could have.
Product pages are spec sheets
For a finisher evaluating a coating, the Product Data Sheet, Safety Data Sheet, and Environmental Data Sheet are not “resources.” They are the page. The PDS tells them whether the product will spray through their gun, what the dry times are, and what it can be recoated with. The SDS goes to the shop’s safety binder. The EDS goes to the LEED® submittal or the architect’s spec request.
The download table lives directly on the product page, beside the can shot and the performance bullets. There’s no accordion, no tab, no “click here for resources” interstitial — the data sheets sit on the page beside the can shot. If the GREENGUARD® certification matters for a school job, the badge is visible without a scroll. If the PDS matters for a shop evaluation, it is one click away from the product name.
That sounds obvious, but it is not what most manufacturer sites do. Most treat technical documentation as supporting material, buried in a resources section somewhere below the fold. For a professional buying on spec, that treatment signals that the brand doesn’t understand how buying decisions are actually made in the trade.
The locator is the buy button
The conversion event for this site happens when a buyer punches their postal code into the locator and gets the address of someone who can put the right pail in their truck.
So the distributor locator is treated like a checkout: fast, clean, no friction, no requirement to hand over an email address to see results. Buyers see what matters at the counter — phone, address, stocked product lines, and on-site capabilities like colour-matching. Every product page funnels to the locator as the primary call to action, with the postal-code field one click away from any spec sheet a finisher might be reading.
What the site can and can’t do
A channel-distributed brand’s website operates in a narrow lane. It can educate and qualify the buyer, but the close happens off the page. The mistake I see consistently on sites like this is treating them like consumer e-commerce that happens to lack a shopping cart. That gets the architecture backwards.
The job is to make the buyer confident enough to walk into the distributor already knowing what they want, then put the distributor’s address one click away. Build for that job, and the rest of the site decisions — navigation, product page layout, documentation treatment, the locator UX — fall into place. Build for an imagined e-commerce conversion that isn’t available to you, and the site spends its energy on the wrong job.
Where this pattern transfers
Any business where the website qualifies a buyer but doesn’t close the sale runs on this same architecture. Regulated industries where the spec sheet is the sales tool. Professional equipment sold through dealers, where closing happens on a phone call or a showroom floor. The architecture question is the same in each case: what does a qualified buyer need to know before they call the person who can actually sell them what they came for, and how do you put that person one click away?
Picture the finisher at 4:50 on a Friday afternoon. The shop has a Monday-morning deadline and they’ve burned the last of the conversion varnish on the panel that almost worked. They search “wood coating high build clear topcoat,” land on a product page that tells them in thirty seconds whether this is the right product for the job, punch their postal code into the locator, and walk into the distributor’s counter twenty minutes later. The distributor hands them a five-gallon pail of Krystal and a colour chip for next week’s stain order. That moment — pail in the truck, deadline still makeable — is what the entire architecture exists to produce. The website’s job ends the second the postal code goes in. Everything before that is in service of the handoff.
Talk through your channel-distributed website architecture
Book the call. We’ll walk through whether your site is doing the qualification work it should be, and what changes if it isn’t.
