What your customers find - and what they miss

"Product discovery is not a feature. It is the gap between what you built and what people actually reach."

This is built for a specific kind of problem - is it yours?

You run a store, a catalog, or a marketplace, and your analytics tell you that people arrive, browse briefly, and leave without converting. You have tried better photography and faster load times. The gap persists. The issue is not the product - it is how shoppers encounter it. When a customer searches for something and the wrong result appears, or nothing appears at all, that is a discovery failure. It is quiet, invisible in most dashboards, and expensive.

This program is designed for people who already understand their product but are unsure how search ranking, filtering logic, and category architecture shape what buyers actually see. It is for those who have read about dhl express tracking workflows or usps priority mail tracking integrations and realized that the logic behind "what surfaces first" applies equally to their own catalog. It is not for beginners looking for a general introduction to e-commerce.

If you have ever asked why a specific SKU underperforms despite strong reviews, or why your best-margin item sits on page three of search results, this program addresses that question with structured exercises, real data sets, and a testing methodology you can apply immediately.

What a few participants noticed after working through the material

"I had been treating our search results like a black box. After the third module I realized we had a synonym gap - customers were searching for 'dispatch notification' and our system was returning nothing because we had only tagged items as 'shipping update.' "Once I mapped the language our customers actually used, three product lines started appearing in searches they had never reached before." It took about two weeks to see the shift in click-through."

- Odalys Fenwick, catalog operations lead, mid-size apparel retailer

"We integrated with multiple carriers - fedex tracking international, amazon order tracking, evri tracking number - and our support team was drowning in 'where is my order' tickets. The discovery module helped me understand that the problem was not the tracking itself but how we surfaced order status information in search. "After restructuring our help content taxonomy, ticket volume dropped noticeably within the first month." I did not expect a product discovery course to solve a support problem."

- Thibault Renard, head of customer experience, logistics software company

Team working through product discovery exercises

Participants arrive with different starting points. Some manage e-commerce catalogs. Others work on internal tools where employees search for procedures or documents. A few work in logistics - they understand how tracking canada post or usps certified mail tracking systems present information to end users, and they apply that same logic to their own product surfaces.

The common thread across all of them is that they came in knowing something was wrong and left with a framework for diagnosing it. Not a guaranteed fix - discovery optimization depends on your specific data, your platform constraints, and how much you can test. But a structured way of asking the right questions, which is where most of the real work begins.

When you get stuck - what is actually available

Async review threads

Each module has a dedicated discussion thread where you can post your work - a filter structure you built, a query you ran, a result set that confused you. Instructors respond within two business days. Responses are specific to what you submitted, not generic encouragement. Other participants can see the thread and often add context from their own experience.

Monthly group sessions

Once a month, a live session runs where participants bring real problems from their current work. These are not lectures - they are working sessions. Someone shares a screen, walks through a discovery issue, and the group works through it together. Attendance is optional, and recordings are available for seven days after each session.

Reference library

A searchable collection of annotated examples - real catalog structures, search log analyses, filter taxonomy decisions - drawn from previous cohorts with identifying details removed. When you are working through a problem at 11pm and the thread is quiet, this is where most participants go first. It covers scenarios from dhl ecommerce tracking catalog structures to lasership tracking result page optimization.

Belu Dorvexan instructors and curriculum designers

The people who built this, and what they worked on before

Belu Dorvexan was founded in 2015 by a small group of practitioners who had spent years inside e-commerce operations - not consulting on them from the outside. The curriculum was built from the inside out: starting with the specific failures they had encountered personally, then working backward to identify what knowledge would have prevented those failures.

The instructors who deliver the material have direct operational backgrounds. They have managed search configurations for platforms processing thousands of daily queries. They have debugged why a purolator tracking number lookup returned irrelevant results and why speedpak tracking data was surfacing in the wrong product category. They understand that discovery problems are often invisible until you know exactly where to look.

The curriculum is reviewed and updated each quarter. When platform algorithms shift - and they do, often quietly - the material reflects it. Participants who completed an earlier cohort can access updated modules at no additional cost.

Vesna Okafor

Search systems, 14 years in catalog ops

Radek Szymański

Filter taxonomy, former marketplace lead

Anneliese Bauer

Discovery analytics, data systems background

Fionn Callahan

Curriculum design, logistics tech specialist

What the commitment looks like before you decide

Program: Discovery Optimization
Format:  Self-paced + monthly live
Modules: 8 core + 3 applied labs
Time:    6–9 hrs/week, 10 weeks
Access:  12 months after enrollment
Support: Async threads + live sessions
Updates: Included for enrolled cohort
Track:   dhl tracking international
dpd tracking number systems
ems express tracking logic
us post office tracking UX

What the structure produces

By the end of the ten weeks, you will have audited your own catalog using the methods taught in the program. You will have a written discovery gap report - identifying where your current setup loses shoppers and what changes are worth testing first. This is not a certificate exercise. It is a working document you can act on.

Pricing is tiered by team size. Individual enrollment, small team access for up to five people, and organizational licensing for larger groups are all available. Exact figures are on the enrollment page, along with a breakdown of what each tier includes and does not include.

The time commitment is real. Six to nine hours per week for ten weeks is not a passive video-watching experience. The exercises require you to pull data from your own systems, make decisions about your own catalog, and write up what you found. Participants who treat it as background material tend to get less from it than those who block time and treat it like a work project.

There is a 14-day window after enrollment during which you can request a full refund if the material does not match what you were expecting. After that point, access continues for twelve months regardless of when you complete the modules.

The doubt most people carry when they reach this point

The most common hesitation is not about price or time. It is the suspicion that the problem is platform-specific - that whatever is causing your discovery failures is a quirk of your particular setup, and that a general program will not reach it. This is a fair concern, and it deserves a direct answer.

The methodology taught here is platform-agnostic by design. It does not assume you are on Shopify or Magento or a custom-built system. It works from the data your platform already produces - search logs, filter interaction rates, zero-result queries - and teaches you how to read that data regardless of where it comes from. The same analytical approach that helps someone understand why their dhl express tracking results surface incorrectly also applies to a furniture catalog where "oak" and "natural wood" are treated as separate categories.

Platform-specific constraints are real, and the program acknowledges them. Some changes you identify will not be possible without developer involvement. Some will require negotiating with a platform vendor. The program does not pretend otherwise. What it gives you is the ability to name the problem precisely - which is often the hardest part of getting it fixed.

If after reviewing everything here you are still uncertain, the enrollment page has a short intake form where you can describe your specific setup. Someone from the team will respond with an honest assessment of whether the program is likely to be useful for your situation, before you commit to anything.