Products your customers cannot find. Stock your systems cannot trust. Prices the software buying on their behalf cannot read. Six recurring platform failures, what we changed, and what happened next.
For businesses that sell from a catalogue, to trade accounts, on contract prices, from branch stock.
Free · 37 pages · PDF
Get the Report
What this is
This is Not a Survey
Most reports on the state of B2B commerce are built from questionnaires. Several hundred executives are asked what their priorities are, and the answers become a chart. Those reports describe intent.
This one describes outcome. Every pattern in it was observed on a platform that was trading at the time.
The evidence base
Six long-running engagements across automotive aftermarket, motorcycle parts, confectionery wholesale and multi-market trade. Three technology stacks.
The boundary
Where those conditions hold, we expect many of these failure modes to transfer: plant and machinery, industrial MRO, marine, powersports. We have not yet built in those categories, and the report says so on the page.
Part Two
Six failures that show up in almost every catalogue business
Each one carries what the condition cost, what we changed, what measurably changed afterwards, and the risk the fix introduced. That last part is the one most reports leave out.
PATTERN 01
The overnight truth
Your platform is not describing your business. It is describing your business as it stood at some point last night.
PATTERN 02
The catalogue that cannot answer
A zero-result search is a customer telling you what they intended to buy, and receiving nothing back.
PATTERN 03
The portal nobody uses
The digital channel exists, works, and is bypassed. Adoption failure is often an operations failure in a user experience costume.
PATTERN 04
Eight systems, no single view
Channel expansion without an order layer underneath produces reconciliation work that grows faster than revenue.
PATTERN 05
The plugin tax and the concurrency ceiling
Extensions bought to compensate for platform limits become the limit, and the constraint only shows itself under load.
PATTERN 06
One business, many markets, many codebases
Growth handled by copying the platform turns every improvement into a multiplication problem.
16h →17m
Catalogue import cycle on an aftermarket platform, after delta imports replaced full-file processing
2.16% →
0.73%
Zero-result search rate, alongside a 27% rise in unique searches and fitment-bundle order value roughly 57% above a typical order
8 →
1
Codebases consolidated across six markets, with no drop in organic visibility across millions of part-number URLs
Who it is for
Three ways in, depending on what you are accountable for
1If you own the number
Start at the delivery record
The plateau you are looking at is mostly caused by things that do not appear on any report you currently receive.
2If you own the operation
Start at the blockers
They are structural and organisational. The second kind is the reason the first kind survives.
3If you own the platform
Start at the machine layer
Being cited and being transactable are different capabilities. Most current investment buys only the first.
Before you download it
What we deliberately left out
A fix presented without its cost is marketing rather than evidence. So every intervention in the report is published with the risk it introduced, and the following are not in it at all.
No client named without written permission
No corporate capabilities section
No logo wall, no team biographies
No figures converted, annualised or rounded up
No prediction presented as a finding
One call to action, at the end
Five checks you can run on your own site this week
Search your catalogue for a partial part number. Then a common misspelling. Then a superseded number. Check whether your fitment data is exposed in a form a machine can read. Check whether availability is shown by branch or only in aggregate.
All five are in the report, with what to do about each.
Ask Sol
Powered by Net Solutions
Skip the search. Start the conversation.
Ask Sol anything about digital products, AI, engineering, or growth, and get answers drawn from years of Net Solutions thinking and experience.
Our assistant helps you find content on our website. By asking a question, you acknowledge that we will process your data in accordance with our Privacy Policy, and consent to anonymous tracking of your conversation to help us improve the experience. Please avoid sharing personal or sensitive information, and close this page if you do not agree to these terms. While we strive for accuracy, AI responses may be inaccurate.By chatting you accept our Privacy Policy and anonymous analytics. Do not share sensitive information. AI answers may be inaccurate.