The commercial problem

The catalogue is smaller than the business behind it

What a business can deliver is often larger than what it can sell online.

Businesses can often deliver more than they show online. They may support different materials, dimensions, configurations, modifications, production methods and supplier options. Yet the webshop presents only the products that have already been defined, priced, photographed, described and published.

When a customer cannot find an exact fit, the interface commonly concludes that no answer exists. The business itself may never have made that decision.

Traditional ecommerce is organised around products that already exist in a catalogue. That works well when the customer wants one of those products. It works less well when the customer begins with a requirement, a room, a technical constraint, a combination of needs, or an outcome nobody has published yet.

What follows is not one conversion problem. It is a connected set of commercial failures across discovery, customer intent, merchant knowledge, custom sales, digital visibility and fragmented fulfilment, and each one makes the others harder to solve.

One

The webshop exposes products, not the full business

Ecommerce is shaped by how products are represented, and a product has to travel a long way before it becomes commercially visible.

  • Defined and approved
  • Priced
  • Photographed or rendered
  • Described and categorised
  • Entered into a system and published
  • Maintained afterwards

Every one of those steps is work, and work has to be justified by expected volume. So a business publishes the combinations it expects to sell often, and leaves the rest unpublished. That is a rational decision. The problem is what it looks like from the outside: identical to not being able to do it at all.

Deliverable capability

  • Materials
  • Dimensions
  • Finishes
  • Components
  • Production methods
  • Supplier options
  • Modifications
  • Made-to-order work

Published catalogue

  • Published products
  • Listed options
  • Photographed variants
The published catalogue sits inside deliverable capability. The outer boundary is real but undrawn, because nobody has written it down.

Catalogues are useful. They give customers clarity, comparability, speed and confidence, and most purchases should stay exactly that simple. The problem is not that catalogues exist. It is that the catalogue gets treated as the complete boundary of what the business can answer.

Nor is everything outside the published set possible. Capability is governed by real constraints: what a machine can hold, what a material tolerates, what a supplier stocks, what an engineer will sign off. The gap between published and deliverable is not a list of free options. It is a set of possibilities that nobody has evaluated.

A missing product page does not necessarily mean a missing capability.

Two

Customers often choose the place that can complete more of the job

Customers do not always evaluate products one category at a time. Somebody furnishing a room needs furniture, lighting, textiles, storage, delivery, installation and occasionally advice, and they would rather solve that once than seven times.

For many multi-product purchases, completeness and convenience influence the decision before individual product quality is fully considered. A larger platform can offer one search, one account, one checkout, coordinated delivery, simpler returns and a clearer sense of progress. A specialist merchant may hold the better product in one category and still lose the broader purchase.

Competing with a large platform is not only a matter of price. It can mean competing with:

  • Assortment and completeness
  • Delivery coordination
  • Search quality and personalisation
  • Brand familiarity
  • Purchasing simplicity

None of this makes large platforms harmful. Their convenience solves a real customer problem and they earned it. The open question is whether specialist merchants can offer comparable completeness without surrendering their identity or turning themselves into generalists.

A specialist product may lose before its specialist advantage is considered.

Three

The moment a requirement becomes specific, discovery often stops

Discovery works by matching customers to products already in the catalogue. The customer is expected to pick a category, use the merchant's terminology, select filters and choose from supported configurations.

When the combination they need does not exist, the interface says no results, this combination is unavailable, out of stock, or contact us. Those messages describe the state of the interface. They do not describe a decision the business has made.

  • Modify a near match
  • Substitute a different material
  • Source an alternative
  • Produce a custom size
  • Adjust the delivery plan
  • Refer the request to a specialist
  • Have an expert review it
  • What was the customer trying to achieve?
  • Which requirements are essential and which are flexible?
  • Would a near match be acceptable?
  • Could the product be modified?
  • Could a different capability satisfy the same need?

What happens now

Search
Filters
No result
Exit

What the request needed

Requirement
Clarification
Capability and constraint evaluation
A responsible outcome

The second sequence is what the first one is missing. It is a description of the problem rather than of a shipped feature.

High-intent customers are often lost at the moment their needs become most informative.

Four

Demand beyond the catalogue becomes manual work

When the webshop cannot answer, the request moves into email, phone calls, contact forms, spreadsheets, shared documents and individual employees' memory.

What that produces, reliably:

  • Slow responses and repeated questions
  • Missing information discovered late
  • Inconsistent pricing between similar requests
  • Unclear ownership of an open enquiry
  • Decisions that are made but never recorded
  • Constraints found after a commitment has been implied
  • Little visibility for anyone managing the pipeline
  • Dependence on whichever person happens to know

Human involvement is not the inefficiency. Expert judgement is frequently the most valuable part of the process and some requests should never be answered without it. The waste is that experts are repeatedly required to reconstruct information that could have been structured the first time somebody established it.

The objective is not to remove expertise. It is to use expertise where judgement is required rather than where information is merely missing or scattered.

This has a commercial consequence that is easy to miss. A request can be perfectly deliverable and still get declined, because the cost of understanding, pricing and coordinating it exceeds what the order is worth. The refusal looks like a capability limit. It is actually a processing-cost limit.

Some custom demand is rejected not because it cannot be fulfilled, but because it is too expensive to process manually.

Five

Analytics record behaviour more easily than unmet need

Ecommerce analytics are good at what happened inside the interface and weak at what the person wanted.

Search terms enteredTells you the words used, not the requirement behind them. Somebody may search a product name while trying to solve a much broader problem.
Filters selectedTells you which options were available to click, not which dimension, material or date was actually essential.
Zero-result sessionsTells you a search failed. Not what was needed, whether a near match would have been accepted, or what the customer did next.
Abandoned sessionsTells you somebody left. Not whether they left because the price was wrong, the lead time was impossible or the product simply did not exist.

A clickstream shows what the customer did inside the interface. It does not necessarily show what the customer was trying to achieve.

  • Product development and assortment
  • Procurement and supplier relationships
  • Pricing
  • Capacity investment
  • What the website gets optimised for

The demand that disappears without a transaction can still contain valuable commercial information.

Six

The business knows more than its systems do

A merchant's real capability is usually distributed across founders, salespeople, craftspeople, engineers, suppliers, drawings, price lists, old emails, spreadsheets and production systems.

That knowledge typically covers:

  • What can be changed and what cannot
  • Which dimensions are achievable
  • Which materials are compatible
  • Which exceptions are acceptable, and to whom
  • Which supplier can help with what
  • What requires approval before it is offered
  • What affects price and what affects lead time
  • Which alternatives are responsible to suggest

The knowledge is usually accurate. It is simply not reachable. A customer cannot query it, employees have to explain it again each time, and when the person who holds it is unavailable, the business looks less capable than it is.

Making that knowledge usable is not a matter of copying notes into a database. To be worth relying on, it has to be:

  • Structured rather than narrative
  • Current, with somebody responsible for it
  • Connected to the constraints that govern it
  • Connected to who has authority to approve an exception
  • Protected, because much of it is commercially sensitive

The webshop sells what has been published. The business may be able to deliver what has only ever been known.

Seven

AI can only work with what the merchant makes understandable

Customers increasingly research and describe what they need through AI assistants, AI-enhanced search and conversational interfaces. That is becoming another route by which merchants and products get found.

An AI system cannot represent a business accurately when the information it needs is missing, vague, contradictory, out of date, buried in an image, spread across unrelated pages, or expressed in terminology nobody else uses. A merchant can have an excellent product and still be difficult to describe correctly.

The facts most often absent from a product page, and most often needed to answer a real question:

  • Dimensions and materials
  • Compatibility and intended use
  • Variants and configuration rules
  • Availability and lead time
  • Delivery limitations
  • Certifications and care requirements
  • Pricing conditions
  • What can be modified, and what cannot

When those are absent, an assistant may:

  • Fail to surface the product at all
  • Recommend something less suitable
  • Misread the intended use
  • Fill a gap with an assumption the merchant never made
  • Compare it incompletely against alternatives
  • Route the customer to a larger or better-documented competitor
  • Products need many interactions to reach
  • Important content exists only in a client-side state
  • URLs are unstable, or variants share one address
  • Internal linking is weak and navigation labels are unclear
  • The same product is described differently in different places

This is not an argument that JavaScript blocks AI systems. It is a question of whether the information a merchant intends to be found stays accessible, stable and interpretable across the channels they want to sell through.

The goal is not to manipulate AI systems. It is to make the merchant's real products, capabilities and limits easier to understand accurately.

Different AI systems obtain and use commercial information in different ways, most of them undisclosed and all of them subject to change. Clear, accessible, structured information improves the possibility of accurate representation. It does not guarantee inclusion, citation or recommendation, and anybody selling that guarantee is selling something they cannot deliver.

There is a harder point underneath this, and it is the reason the section exists at all. Even a perfectly described catalogue exposes only the products already published. A merchant can improve every page and leave the rest of the business invisible. So there are two separate questions:

  1. Can an AI system understand the published products?
  2. Can it understand what the merchant may responsibly provide beyond them?

AI visibility is not only a distribution problem. It is also a capability-representation problem.

  • An assistant may interpret the request.
  • Published and structured information may support discovery.
  • Capability and constraints have to come from sources the merchant controls.
  • Current price and availability have to come from approved systems.
  • A commercial commitment requires explicit authority, from a person or a rule somebody signed off.

Making a business understandable to AI is useful. Making the answer trustworthy requires authoritative capability, constraints and approval.

Eight

Digital commerce rewards investment at scale

Every independent merchant has to support some version of the same list: product information, photography, content, search, navigation, filters, configuration, checkout, analytics, integrations, support, security, machine-readable data and continuous maintenance.

A large platform spreads that investment across many merchants, enormous catalogues, high transaction volumes and dedicated engineering teams. An individual specialist cannot match it alone, and mostly should not try.

This is not a claim that small merchants have less to offer. They frequently have:

  • Better products
  • Deeper technical knowledge
  • More flexible production
  • Stronger service and judgement
  • Specialist materials and supplier relationships

Specialist capability does not automatically produce specialist discoverability.

The waste here is cumulative duplication. Many businesses separately fund similar infrastructure, each arriving at something less complete than the platforms they are competing with, while the thing that actually distinguishes them stays invisible through the interface.

Nine

No single specialist has to hold the complete answer

One merchant may satisfy one part of a broader request. A table, or the lighting, or the textiles, or the installation, or the bespoke component, or the technical review. Rarely all of them.

Today the rest of that demand is usually:

  • Lost
  • Left to the customer to coordinate
  • Redirected informally, on trust
  • Split across separate searches and checkouts
  • Captured by a larger platform that can cover more of it

What merchants lack is not goodwill. It is a commercial system for:

  • Discovering complementary capability
  • Combining parts of one outcome
  • Sharing only the information the other party needs
  • Coordinating quotations and constraints
  • Being clear about who is responsible for what
  • Preserving who owns the customer relationship

Complementary merchants often compete separately because they lack the infrastructure to fulfil demand together.

None of this is simple, and it would be dishonest to present it as a matter of recommending another merchant. A workable system eventually needs agreed rules for:

  • The customer relationship and data access
  • Pricing and quotation authority
  • Payment, liability and warranty
  • Fulfilment, returns and quality
  • Attribution, revenue sharing and disputes

The opportunity is not to refer work elsewhere. It is to make complementary capability commercially actionable while letting specialists stay specialists, which is a governance problem at least as much as a technical one.

One request

How this looks from inside a single enquiry

I need a table for twelve people, made for this room, in a durable material, delivered before September.

  1. The catalogue

    Standard sizes only

    Six, eight and ten seats are published. Twelve is not, because it sells rarely enough that nobody photographed it.

  2. Search and filters

    No matching products

    The filter combination returns nothing. The interface reports the absence of a product, not the absence of a capability.

  3. The contact form

    A generic message

    The customer writes a paragraph. Nothing in the form asks about the room, the material tolerance or the September deadline, which are the three facts that decide the answer.

  4. Sales

    Four clarifying emails

    Somebody reconstructs the requirement by hand. They know which materials hold at that length and which supplier could meet the date, because they have done it before.

  5. Afterwards

    Nothing is retained

    Whether the order lands or not, the requirement, the constraints that governed it and the reasoning behind the answer stay in a mailbox.

  6. An AI assistant

    Sees the standard product

    It reads the published page, finds a ten-seat table, and has no way of knowing the business makes longer ones on request.

  7. The complete purchase

    Goes somewhere else

    The customer also needs seating and installation. A larger platform covers more of the job, and the specialist loses a sale it was better qualified to fulfil.

Every step in that sequence is a reasonable decision by somebody. The failure is structural rather than anybody's mistake, which is exactly why it does not get fixed by trying harder.

The connection

These are not separate conversion problems

Each of the nine makes the others harder to solve. That is what makes the whole thing durable, and why fixing any single one of them tends to disappoint.

A merchant publishes a limited catalogue
The customer cannot express the complete requirement
Search returns no suitable result
The customer leaves, or starts a manual enquiry
The request is expensive to process
The underlying intent is never captured
Capability stays undocumented
Products and capability stay hard for AI systems to interpret
The merchant has weaker digital reach
Complementary merchants stay disconnected
A larger platform captures the broader purchase

A sequence rather than a cycle. Each step makes the next more likely; none of it is automatic, and the chain can be broken at several points.

Each failure makes the others more difficult to solve.

What it costs

Who this affects, and how

For customers

High-intent requirements reach dead ends.

  • You have to learn the merchant's terminology before you can describe what you need
  • Custom and complex purchases need repeated clarification
  • Suitable specialist products are hard to find
  • You coordinate fragmented suppliers yourself
  • An assistant may give you an incomplete or unsupported answer

For merchants

Demand beyond the catalogue is lost rather than declined.

  • Custom orders stay expensive to process
  • Capability stays hidden and dependent on individuals
  • Product and market decisions use only the demand the catalogue could receive
  • Products may be poorly represented in AI-mediated discovery
  • Complementary merchants compete instead of collaborating

For producers and suppliers

Flexible production capability stays commercially invisible.

  • Constraints are discovered late, after expectations are set
  • Responsible alternatives surface too late to be useful
  • Production knowledge stays disconnected from customer demand
  • Investment decisions use incomplete market signals

For the commercial system

Published products get treated as the limit of possibility.

  • Aggregators gain an advantage from completeness rather than capability
  • Specialist capacity stays fragmented
  • Unmet demand disappears without becoming information
  • The same requirements get reconstructed over and over

Businesses can end up selling only a fraction of what they are capable of delivering.

The distinction

Traditional ecommerce begins with what has already been published

That is the single sentence underneath all nine problems. The interface is organised around the products that exist, which is why it fails whenever the customer starts somewhere else.

A commercial interface built the other way round would start from a different set of questions:

  • What is the customer actually trying to achieve?
  • What can this merchant responsibly deliver?
  • Which constraints govern the answer?
  • Is an existing product enough?
  • Would a configuration or a modification work?
  • Does this need expert review?
  • Could another specialist contribute part of it?
  • And if the demand cannot be served, what should be recorded?

What that looks like as a product, and which parts of it exist today, is the subject of the Vision page rather than this one.

The commercial interface should represent not only products, but demand, capability, constraints and decisions.

The dead end is often in the interface

A customer can fail to find a product even when the business could have answered the need. A specialist can lose a sale even when its product is better suited. A merchant can receive valuable custom demand and gain no structured knowledge from it.

An AI assistant can overlook or misrepresent a business whose products and capabilities are hard to interpret. Several complementary businesses can each hold part of the answer while the complete purchase goes somewhere else entirely.

None of these are isolated website defects. They are what happens when commerce is organised around a fixed published catalogue while productive capability, customer intent and digital discovery all become more dynamic than the catalogue can express.

The catalogue is smaller than the business behind it.

That gap is where the commerce goes.

What follows

Two ways to go further

The Vision page sets out what Specify is building in response, and where the boundary is between what exists today and what does not. The thesis explains why the commercial model is changing underneath all of it.

Or start with one difficult request. The complimentary Enquiry Audit takes a real enquiry the catalogue could not answer and shows what a structured reading of it produces.