They asked why the shop wasn’t selling. Nobody could find the shop.
This wasn’t a traffic problem or a demand problem. A complex buying process had been forced into an out-of-the-box template, and the friction stacked up at every step.
A pharmaceutical supplier invested heavily in launching an e-commerce site. Online sales were significantly disappointing, and the investment wasn’t returning. They wanted to understand why.
- The e-commerce funnel: drop-off at each stage, from viewing a product through purchase.
- Traffic sources and entry pages, including the organic search terms bringing people in.
- A page-by-page content and UX walkthrough. I looked at what a first-time visitor sees and reads at each step, and what’s missing. For example, nothing on the site explained that an account was required, or how to create one.
- A competitor comparison of navigation and content architecture.
- Usability testing: can people find the shop?
- Site search and filtering tests.
- Consideration: No one on our team had worked on the original build. I opened discovery by asking the client team which phases they had worked through, to separate known decisions from new findings.
- Navigation & information architecture
- E-commerce funnel & checkout
- Product page template
- Shop filtering & site search
- Help content
- Analytics, tracking & attribution
- Email & sales channel integration
A stack of friction across information architecture, user experience, and buyer journeys. Buyers couldn’t find the shop. Those who did hit confusion at every step after. Underneath it all, a complex purchasing process had been forced into an out-of-the-box template that couldn’t support it.
- The shop was hidden. No navigation menu mentioned products or shopping. Products could only be reached contextually, from deep inside research content.
- The path to purchase was full of friction. There was an account requirement no one was told about, a product page template that didn’t read as a product page, a filter that looked broken, and search that needed exact scientific names.
- The biggest buyer group had no online path. Most institutional buyers purchase through a purchase order, a process that happened offline and wasn’t mentioned anywhere on the site.
Abandoned between viewing the cart and beginning checkout
Visitors who saw a product at any point in their journey
Entering traffic from organic search, much of it searching for specific product names
The plan: how to optimize.
Just because you can bend a pattern into working doesn’t mean it’s the right one.
Want to know what Kinetic Pencil will uncover on your site?
Start with a live, 30-minute consultation.
The full story.
The brief
The client had launched an e-commerce site and invested heavily in it. Online sales were significantly disappointing, the investment wasn’t returning, and they wanted to know why.
What we found
The issues fell into three groups:
- Information architecture that hid the shop entirely.
- A user experience full of unexplained steps and broken-looking tools.
- Buyer journeys that didn’t fit how this audience actually purchases.
It wasn’t a customer problem, and it wasn’t a traffic problem. The site wasn’t converting the demand it already had.
What was working
- Strong organic traffic, much of it from people searching for specific products.
- Strong email engagement. The newsletters performed well.
- A content-to-product connection that set them apart. Published articles and abstracts linked research topics to related products.
The funnel didn’t match buyer intent
Only ~30% of visitors saw a product at any point in their journey. Of those who did and added it to their cart:
| For every 100 buyers who added to cart | Remaining | Stage drop-off |
|---|---|---|
| Added to cart | 100 | — |
| Viewed the cart | 63 | 37% abandoned |
| Began checkout | ~35 | 45% abandoned |
| Completed purchase | ~34 | — |
YOUR_FIGURE_IMAGE
Adding to cart is a strong signal of intent, yet two out of three of those buyers never purchased.
- Almost all of the loss happened before checkout began. Once buyers started checkout, nearly all of them finished.
- That pointed to what buyers were (or weren’t) learning on the product and cart pages: that an account was required, who was allowed to purchase, and how institutions pay. The investigation started there.
Information architecture: the shop was hidden
There was no Shop link anywhere in the navigation.
- No menu mentioned products or shopping. You could only find products contextually, as related items deep inside research topics.
- Every competitor we reviewed led its navigation with Products, organized by product category.
- In usability testing, most people asked to find the shop couldn’t.
- The client’s reasoning was that buyers would read the research first and then purchase. That suits some buyers. Most arrived knowing exactly which product they needed.
Users were relying on search engines to navigate the site. The evidence:
- Organic search traffic landed on specific product names. People were using Google to reach products they couldn’t find on the site.
- “Acme Pharmaceutical + shop” was a common entry search: people knew the company sold products online, and couldn’t find where.
- The help page was one of the most heavily trafficked pages on the site.
- YOUR_CONFIRM: “help” was a common internal site search term. (Keep this line only if confirmed; delete it otherwise.)
User experience: friction at every step
The account requirement came as a surprise.
- Anyone could add to cart, but purchasing required an account. That wasn’t stated clearly anywhere, and nothing explained how to create one.
- The client hadn’t flagged the requirement as part of the funnel. It only surfaced during the discovery presentation, even though it shaped who could complete a purchase.
The product page template didn’t read as a product page.
- It was an out-of-the-box template made to fit. Key details sat far down the page and required heavy scrolling.
- Next to competitor product pages, the difference was obvious at a glance.
The shop filter looked broken.
- Selecting filters expanded the left rail to thousands of pixels tall, while the few matching results sat at the top of the page, out of view.
- The filter worked. It just looked like it didn’t.
Search only worked on exact scientific names.
- Partial or approximate product names returned nothing, and buyers rarely type the complete scientific name.
The help page used the wrong pattern.
- Each question sat in a card designed for promoting blog posts, so every answer opened on a separate page. Users had to click forward, check, go back, and try again.
- The page also mixed in other content types, which made it harder to tell what users were actually struggling with.
User journeys: the biggest buyers had no path
It wasn’t clear who could buy.
- These are pharmaceutical products sold to qualified buyers, not the general public. The site made it look like anyone could purchase.
- That also meant the add-to-cart numbers likely included unqualified visitors, so the demand the client believed they had may not have been accurate.
Institutional buyers had to leave the site to purchase.
- Most sales came through institutional procurement, tied to a purchase order and handled offline through email and the sales team.
- None of this was explained on the site. Buyers used it for discovery, then completed the purchase another way.
- Some site traffic was likely researchers planning purchases and sending links to their procurement teams. That activity couldn’t be tracked or attributed.
The channels weren’t connected.
- Email and the sales team drove most revenue, while e-commerce served colder audiences. The two didn’t connect.
- Existing customers had no reason or reward to buy through the site.
Why it happened
None of this came from a lack of effort. The team knew their products and their buyers, and they built a site that worked. What happened here happens on a lot of web projects: budget gets spread across many priorities, and user experience is often the piece that gets trimmed. A template looks like the efficient choice, and the team then spends the project making their business fit the template.
E-commerce is where that tradeoff costs the most. Every unexplained step between interest and purchase loses buyers, so the user experience has to be right, and it can’t be skipped.
A few common decisions added up:
- A complex purchasing process was adapted to an out-of-the-box template. Much of the functionality was made to work. But several parts of the journey needed custom builds the template couldn’t support.
- Information architecture was handled in-house to manage costs. The team brought real product knowledge to it. Without a user experience lens, though, the structure reflected how the organization sees its products rather than how buyers look for them.
- There was no dedicated UX review or testing before launch. Each piece was checked at a high level (“the filter works”). The issues that only appear when you walk through the site as a buyer went unnoticed.
- The business had outgrown its tracking and attribution setup. Connecting site, email and sales activity takes enterprise-grade analytics, and one person was carrying the site, email and tracking at once.
The optimization
1Make the shop findable
- Add a prominent Shop link to the primary navigation.
- Restructure the information architecture so products and product categories lead, consistent with buyer expectations and competitor conventions.
2Remove friction from the path to purchase
- State the account requirement before add-to-cart, with a clear prompt and setup instructions.
- Rebuild the product page template so it reads clearly as a product page, with key details visible without scrolling.
- Fix the filter layout so results stay in view while filtering.
- Rebuild site search to handle partial and approximate product names.
- Launch a cart abandonment program to recover high-intent buyers.
3Build a journey for every buyer type
- Make clear who can purchase, and how.
- Support purchase order buyers online: explain the process, add a purchase order path at checkout, and let buyers send a cart to procurement, tracked for attribution.
- Connect e-commerce with email and sales, so existing customers have a reason to buy online.
4Answer questions where buyers have them
- Identify what users were searching the help page for, and place those answers on product, cart, and checkout pages.
- Separate help content from other content types, and replace click-through cards with expand/collapse FAQs.
5Invest in infrastructure that fits the business
- Scope custom builds where the template can’t support the purchasing process.
- Implement event tracking and attribution that connect site, email, and sales activity, so the team can see where buyers drop off and which channels drive revenue.
Key learnings.
Saving money on the build cost more later. The template, the in-house information architecture, and the skipped UX review each looked like savings. Together they produced an e-commerce investment that didn’t return. The demand and traffic were already there. A complex purchasing process needed infrastructure built for it, and an ecosystem designed to work as one system.
Other case studies.
The brief was: fix the navigation. The navigation was fine.
B2B wedding-industry SaaS platform — vendor acquisition funnel & information architecture
Read the case study →They thought they’d been clear. AI answers were built from Reddit.
Global food & beverage brand: AI search visibility & content architecture
Read the case study →Their email list converted at 29x the rate of their website. They treated both the same.
Independent business and tech newsroom: subscription funnel, offer & lifecycle audit
Read the case study →Choose Your Starting Point
Have a specific question or need help clarifying the opportunity?
Book a Clarity CallExploring an assessment, organizational transformation, or team engagement?
Discuss an Opportunity