We are developing ways to connect product information, restaurant menus and demand signals from dining.
In development · Pilot target: August 2027
Illustrative product information, not a screenshot of a supplier application.
Flavor and stories from the producer
Product details alongside local sales options
Understand the details and choose to your taste
Connection example · Sharing product information is distinct from sharing personal information.
Ingredient attributes and uses
Linked as an ingredient in a dish
Understand the details and choose to your taste
Connection example · Sharing product information is distinct from sharing personal information.
Register product details and content
Use that information to build a menu
Compare the product with personal preferences
Producers explain their products; restaurants put that information to use. Customer choices and feedback provide signals for understanding aggregate demand.
Orders and feedback for linked menus
Exposure · Seasonality · Stock · Lead times
Improve the product story · Discuss supply
Designed to inform decisions with aggregate information, not to pass personal booking requests or contact details to suppliers.
Illustrative data and assumptions, not actual forecasts or confirmed purchase quantities.
Find suitable menus and the restaurants that serve them.
Prepare the offer and its terms around the selected menu and product relationship.
Present product information and an offer at the relevant menu or restaurant touchpoint.
Review offer views, product quantities ordered and repeat quantities separately.
Compare demand assumptions with stock and scheduled receipts.
Review the next sourcing plan using stock, lead time, production capacity and product-specific supply conditions.
Which menu and venue fit the product?
Find suitable menus and the restaurants that serve them.
A menu with a pairing relationship to Wine A
Tell us about your products, supply regions and proposed collaboration.
