Coffee Kit: the full product vision
12 November 2026. This is the complete product to present and discuss, followed by an implementation sequence. The smaller initial pilot in the business plan is a way to validate and deliver it; it is not the limit of the product concept.
Coffee Kit: the complete solution for selling coffee on Shopify. Manage coffee data, improve search and AI discoverability, build subscription experiences, offer loyalty rewards and plan upcoming stock needs. Merchants can use designed storefront components or have an agency build their own presentation on the same rules and data. This is the proposed product positioning, not a claim that the concept prototype already operates these services.
1. Seven connected product areas
| Area | Merchant promise | Tangible experience |
|---|---|---|
| Coffee workspace | Turn the bag and the source sheet into a coffee ready to sell | Review extracted facts beside the source; map existing products; approve details once; preview cards, product pages and offers |
| Demand & stock | See upcoming subscriptions and physical rewards against available coffee | Due cycles, unallocated club demand, issued gifts, customers near a reward, forecast assumptions, shortages and actionable alerts |
| Storefront experiences | Make every coffee easier to understand and choose | Rich coffee cards, origin/process stories, tasting notes, source-backed profiles, quick buy, grind/size controls, finder, saved coffees and brew guides |
| Subscription studio | Sell coffee the way your customers want to receive it | Simple refills, curated clubs, customer-built boxes, personalized selections, prepaid gifts and office programs; model-specific merchant configuration |
| Loyalty | Give customers a clear reason to return | Bag rewards, points or stamps, a visible reward wallet, eligible subscription earnings, redemption, and a distinct café/POS program where supported |
| Customer journeys | Keep the relationship useful after the first order | Upcoming delivery, coffee choices, deadlines, skip/change options, reward progress, suitable new-lot suggestions and connected marketing messages |
| Design and connections | Keep your brand and the tools that serve you | Shared styles, Coffeetale integration, supported theme adapters, loyalty/email/pickup connections, migration assistance and agency/plain rendering |
Each area needs a real demonstration. A six-item feature list above a single reused screenshot is not an adequate product pitch.
Coffee data is a maintained product service, not a one-time scan: import, map, review, publish and keep current. Search and AI discoverability deserve a dedicated presentation with visible facts, compatible structured data, native channel mapping and quality diagnostics. See the discoverability specification.
2. Subscription studio: six genuinely different products
| Product | What the shopper does | What the merchant controls |
|---|---|---|
| My usual coffee | Chooses a known coffee, grind, bag size, quantity and frequency | Eligible variants, plans, refill pricing, sold-out behavior and management terms |
| The roaster's club | Compares Classic, Discovery or Rare-style offers and trusts the roaster's selection | Club tiers, coffee categories, first shipment, each cycle's physical selection, fixed-price boundaries and exceptions |
| Build my box | Picks several coffees, quantities and valid grinds into a box with visible progress | Minimum/maximum bags, eligible catalog, duplicate rules, price model, choice window, next-cycle editing and no-response fallback |
| Find my coffee | Answers a short taste/brew questionnaire and reviews an explained selection | Hard constraints such as decaf, matching rules, rotation variety, preference editing and no-match handling |
| Give coffee | Chooses a recipient, message, number of deliveries and start/redemption option | Prepaid entitlement, gift activation, remaining deliveries, shipping treatment, recipient changes and refund policy |
| Coffee for the team | Estimates consumption, chooses larger formats and adjusts delivery rhythm | Supported quantities and price tiers, editable consumption assumptions, payment method and permitted delivery schedules |
The visual compositions must differ: a compact PDP control, editorial club comparison, coffee selection grid with a box tray, guided finder, gift composer, and consumption calculator. They share commercial truth and core components, rather than being one form with six different titles.
The full subscription product specification defines configuration, pricing, stock, renewal and customer-control behavior. The reference atlas maps the supplied merchants to the actual patterns observed. Platform constraints and provider economics stay in the subscription evidence.
Advanced operating rules must be designed with actual merchants. A club roaster and a customer-built-box merchant should show their real allocation, cutoff and exception processes before we commit to automation. New-enrollment capacity, existing renewal demand and stock reservation are different jobs. The operations discovery plan and demand/inventory specification define the evidence and backend flows required. No studio setting by itself guarantees an inventory hold or a stopped charge.
3. Loyalty is a product surface
Loyalty belongs in the app navigation, the merchant website and the customer experience. It should not disappear into an integrations list merely because a provider may operate the ledger.
The merchant designs a clear offer: which purchases count, what customers earn, when they can redeem, whether subscriptions qualify and how returns affect the balance. The shopper sees understandable progress and a reward they can actually use. A café stamp program counts eligible drinks or visits; an online bag program counts a different unit. Presenting them together requires explicit rules and identity handling.
The proposed demo shows a bag-reward program, a customer card, earning/redemption/refund events and subscription eligibility. The underlying product can begin with an affordable provider experience and later use confirmed APIs or a narrow owned ledger where the custom workflow justifies it. The desired product is richer than the first integration method. See loyalty product specification and current provider evidence.
Physical free-coffee rewards also create stock exposure. Show issued entitlements separately from customers approaching the threshold, and both separately from actual orders. A €10 voucher has monetary exposure; it is not a reserved coffee bag. Forecasts, stock review and operational alerts belong in the same product experience as earning and redemption.
4. The complete customer relationship
A customer can discover an adventurous coffee, build a recurring box, return before a selection deadline, swap one coffee, see what arrives next, and understand their reward progress. The same approved catalog supplies recommendations and explains replacements. An identified, eligible event can reach the merchant's existing email system; marketing consent remains separate from a quiz answer or purchase.
The conceptual customer account combines My next coffee, My box/preferences, My rewards and Saved coffees. Each control must have a real operational owner. A provider portal handoff is acceptable when necessary; the long-term product experience should remain coherent. The prototype should show these relationships even before the integration route is selected.
5. A powerful merchant builder without an empty canvas
Start from an offer template, then configure meaningful choices. A roaster should not have to invent their own subscription architecture. The builder adapts its settings to the selected product: box limits for boxes, recipient and duration for gifts, selection categories for curated clubs, and earning rules for loyalty.
Keep three layers separate:
- Business rules: eligible products, constraints, price, cadence, reward policy and customer promise.
- Presentation: cards, inline forms, guided steps, full pages, style and content.
- Operation: draft, ready, published, upcoming changes, customer action required and exceptions.
Changing a layout must not alter the price or stock behavior. Agencies should be able to replace the presentation while reusing the reviewed data and validated business rules. The developer/designer handoff defines those shared foundations.
6. Merchant-facing presentation
Use the requested Kitenzo site as a benchmark for the breadth and clarity of a product presentation: an understandable promise, capability stories, distinct use cases, interactive examples, visual configuration and an agency route. Coffee Kit needs its own coffee-specific story and actual Coffeetale visual system. Do not borrow another product's adoption numbers, customer logos, testimonials or technical claims.
Provisional merchant narrative, incorporating the latest requested order. Subscriptions and loyalty precede the deeper finder/purchase-option story; this presentation sequence is not a frozen MVP architecture:
- The complete solution for selling coffee on Shopify. Identify the product, platform and breadth immediately.
- Coffee product data, organized and maintained. Show existing catalog mapping, source review and ongoing updates.
- SEO and AI discoverability for your coffee. Explain useful public facts, accurate commercial data and supported channel mapping.
- Rich coffee cards and product pages. Demonstrate the reviewed catalog in merchant-facing storefront components.
- Coffee subscriptions, from refills to custom boxes. Let visitors explore six distinct journeys.
- Loyalty and coffee rewards. Demonstrate earning, progress, physical rewards and redemption.
- Inventory planning for subscriptions and rewards. Show upcoming demand, shortages, assumptions and alert previews.
- Coffee finders and purchase options. Show discovery, recommendations, grind/size selection and quick buying after the recurring-commerce story.
- A customer portal for deliveries and rewards. Show next-lot choices, customer controls and connected messages.
- APIs and flexible design for agencies. Demonstrate visual configuration and plain rendering.
- Data migration and subscription switching. Explain supported routes and human help.
- Plans and pricing. Present proposed pricing and a real next step.
Use a discreet, persistent concept label. Keep architecture gates and release sequencing in the internal pitch. A concept site can confidently demonstrate the proposed outcome without inventing a launched app or measured revenue uplift.
7. Delivery sequence and investment
The complete vision is intentionally larger than the first release. Rank its parts by merchant value, exact platform feasibility and ongoing support burden, while keeping the full concept visible in design and sales testing.
- Foundation: approved coffee catalog, experience configuration, real variants/plans, shared design and review.
- Operational discovery: real club/box merchants, historical replay and a shadow view of scheduled demand and rewards before automatic capacity promises.
- First connected release: select one operational subscription path and one loyalty delivery path, with useful data and storefront experiences. The exact promise and price must be tested together.
- Expansion: customer-built recurring boxes and preference-led choices, using a proven physical-stock and cycle model.
- Further programs: prepaid gifting, office-specific requirements, broader POS, more providers/themes and deeper agency interfaces.
Advanced models and an owned loyalty ledger are additional scope beyond the business plan's initial-app allowance. Estimate them explicitly after the architecture tests. The internal decision must compare a full product that is worth switching to with the team's real capacity; neither a narrow demo nor an unlimited launch promise resolves that decision.
Source: FULL_PRODUCT_BLUEPRINT.md The complete Markdown handoff and private datasets remain in the local project. This web edition includes selected supporting visuals and scenario downloads.