MONIN's B2C customers bought only the flavors they already knew. I hypothesized that the professional recipe library, which direct-to-consumer customers never saw, could become the storefront's product discovery surface. I led the feature end to end: a consumer recipe library, recipe modules on product pages, a custom recipe API, and rich-snippet SEO targeting "how to make" searches, launched as a coordinated program with marketing, culinary, and brand partners against adoption metrics defined before the build. Within six months, organic traffic grew 30% (6,480 additional unique visits per month), recipe-view-to-purchase conversion rose 4%, and customers branched into flavors they had never bought.
Product Launch: Turning a B2B Recipe Library into a Consumer Discovery Engine
Food & beverage e-commerceUndated
+30%
Organic traffic
Rich-snippet rankings on "how to make" searches brought new buyers straight to recipe pages.
Within 6 months
+6 pts
60-day repeat purchase rate
Customers who engaged with recipes repurchased within 60 days at a higher rate than those who didn't.
Approximate
+4%
Recipe-view-to-purchase conversion
The adoption metric committed before the build: recipe views turning into product purchases.
Within 6 months
Broader
Baskets and repeat visits
Customers bought flavors new to them and returned to the recipe library between purchases.
Directional
Company context
Company context
Global flavor solutions company known for premium syrups, sauces, fruit purées, concentrates, and beverage innovation for cafés, restaurants, hospitality, and foodservice teams.
- Company fact
- International
- Company fact
- Premium beverage flavoring brand
- Company fact
- B2B - cafés, restaurants, hospitality, and foodservice
The insight
MONIN sells hundreds of flavors. Its wholesale customers, baristas and culinary professionals, understood the range and ordered across it. Consumer order data showed something different. Home buyers repurchased the one or two flavors they already knew, so a customer who loved caramel bought caramel again. The catalog was deep, and a typical customer explored almost none of it.
The gap was knowledge, and MONIN already owned the fix, a professional recipe library that showed exactly what to make with every product. Direct-to-consumer customers never saw it.
The hypothesis
Expose that library to consumers in a friendly format, and recipes become the way customers find products they would never search for directly.
Search engine demand for "how to make..." needed to land on MONIN recipe pages.
Every recipe introduces the products it uses, with a direct path to buy.
Existing customers branch into new flavors, because a recipe teaches them what to do with the bottle.
Before any build work, I defined the adoption signals the feature would be judged on: recipe views leading to product actions (recipe-view-to-purchase conversion) and cross-sell from recipe placements on product pages.
What shipped
A consumer recipe library on the storefront, browsable and searchable, rewritten in plain consumer language.
Recipe modules on product pages. Each product surfaced recipes that used it, and those recipes exposed the other flavors they called for, turning every product page into a cross-sell surface.
Recipe schema for search, earning rich snippets and rankings on "how to make" queries.
The launch
Launch ran as a coordinated program across teams. Recipe schema and the library went live alongside email features, homepage placement, and social and email promotion, so existing customers were exposed to recipes that used flavors similar to what they had ordered in the past at the same moment search traffic started arriving.
Measuring adoption
I instrumented the recipe-to-purchase funnel in analytics and guided the email implementation: entrances on recipe pages, clicks from recipe to product, purchases in those sessions, and cross-sell events from product-page recipe modules. Post-launch reporting ran against the metrics committed before the build.
Impact
Within six months of launch:
Organic traffic grew 30% (6,480 additional unique visits per month), driven by rich-snippet rankings on "how to make" searches.
60-day repeat purchase rate increased by 8 points.
Recipe-view-to-purchase conversion rose 4%, the committed adoption metric.
Baskets broadened and repeat visits climbed as customers bought flavors new to them and returned to the library between purchases.
The professional recipe library became the storefront's discovery engine. New customers arrived through search, and existing customers could expand their in-home flavor profiles with knowledge of how to use new products.
- MONIN's catalog held hundreds of flavors, and consumer buyers repurchased only the one or two they already knew.
- Wholesale customers such as baristas understood the full range; home customers had no way to learn it.
- A professional recipe library already answered "what do I make with this," and consumers never saw it.
Challenge / opportunity
- MONIN's catalog held hundreds of flavors, and consumer buyers repurchased only the one or two they already knew.
- Wholesale customers such as baristas understood the full range; home customers had no way to learn it.
- A professional recipe library already answered "what do I make with this," and consumers never saw it.
Hypothesis and metrics
- Exposing the recipe library in consumer-friendly form would turn recipes into the storefront's product-discovery surface.
- "How to make" search demand would land on MONIN pages and introduce buyers to the products each recipe uses.
- Success metrics committed before the build: recipe-view-to-purchase conversion and product-page cross-sell.
What shipped
- A browsable, searchable consumer recipe library on the storefront, rewritten in plain language.
- Recipe modules on product pages that cross-linked every product to the flavors its recipes called for.
- A custom API and SDK over the internal recipe database to serve recipes without manual content work.
- Google-friendly recipe schema that earned rich snippets on "how to make" queries.
Launch program
- Built the case to marketing that recipe search demand was an acquisition channel the brand was giving away.
- Secured culinary and brand sign-off to rewrite professional recipes for consumers.
- Coordinated schema, email features, homepage placement, and social promotion into a single launch window.
How the work unfolded
- 1
Insight
Order data showed consumer repurchasing concentrated in one or two familiar flavors per customer while the wholesale audience bought across the range.
- 2
Hypothesis and metrics
Framed the professional recipe library as a consumer product-discovery surface and committed to adoption metrics: recipe-view-to-purchase conversion and product-page cross-sell.
- 3
Build
Shipped the consumer recipe library, product-page recipe modules, a custom recipe API and SDK, and Google-friendly recipe schema.
- 4
Launch
Won marketing and culinary/brand buy-in, then coordinated SEO, email, homepage, and social so existing customers and search traffic arrived together.
- 5
Results
Reported against the committed metrics: organic traffic up 30% (6,480 additional unique visits per month) and recipe-view-to-purchase conversion up 4% within six months.
Need feature adoption you can measure?
I run this loop on marketplace and platform features: define the adoption metric, ship the launch with the teams who own each channel, and report the result.