z. PRODUCT STUDIOZepto · product requirements
Final PRD · v1.0
Product requirements · Grocery discovery

Zealthy.

Make it easier to find groceries that fit your food preferences—and understand why each product matches.

Personal & household needsQuick-commerce grocery shoppersControlled pilot scope
UX prototype · static UX prototype screen showing a Zealthy product listing in a Zepto-inspired grocery app
Trust, not a health scoreShow the evidence behind each dietary attribute.
Final project PRD 5 October 2026 Product state: pilot-ready specification
53%

of surveyed Indian consumers say they actively work on their health. Source ↗

51%

say finding healthier options is difficult. Source ↗

61%

want health labels to be easier to understand. Source ↗

47%

do not fully trust health products or services. Source ↗

01 · The opportunity

Make the choice easier.
Make the match explainable.

A focused product-discovery layer inside grocery—not a new store, a diet plan, or a blanket promise that an item is “healthy.”

Customer problem

Preference matching takes too much work

Shoppers who follow food preferences often need to search across products and interpret labels to decide whether an item fits. Public consumer research reports difficulty finding healthier options, label-comprehension challenges and trust concerns. This PRD addresses that job with explicit attributes and evidence on each match.

Primary audience

Quick-commerce grocery shoppers with food preferences

People choosing packaged grocery for themselves or a household, across life stages and shopping contexts—such as students, working adults, caregivers and families. Targeting is by the preference being applied, not by occupation or age.

Core job
Find stocked grocery products that match my selected food preference, and see the evidence so I can choose confidently.

Evidence boundaryThe linked market and consumer research establishes category context. Zepto-specific adoption, repeat use, conversion and revenue impact are measured through the controlled pilot defined below.
02 · Market evidence

Signals support the need.
The pilot measures product impact.

Consumer research, quick-commerce scale and adjacent launches provide market context. Zepto-specific conversion, feature adoption and revenue impact are evaluated with the experiment below.

Browse all sources
Consumer signal

Shoppers say health discovery is confusing.

NIQ’s India survey reports difficulty finding healthier alternatives and low confidence in claims made by health products and services.

51%struggle to find healthier alternatives in the market
47%don’t fully trust products/services aimed at improving health
NIQ India findings from a 19-country online survey; India sample size is not stated in the release.
Label-literacy signal

Label comprehension is a real friction point.

A 2026 Pune higher-education student study surveyed 401 people.

51.6%showed poor label comprehension
54.4%found serving sizes difficult to interpret
36.1% also cited lack of time. One-city student sample—not representative of all grocery shoppers or Zepto users. Study
Platform scale

Large market; no feature-level lift estimate.

Zepto’s FY26 filing reports scale, not DAU or demand for Zealthy.

47.97Mannual transacting users
640.18Morders in FY26
Annual users ≠ DAU/MAU; no feature revenue claim. UDRHP
Quick-commerce context · industry estimate

Category scale and metro concentration make a focused pilot plausible; neither number sizes the Zealthy opportunity. Redseer report

50M+monthly transacting users estimated
70–75%of GMV from the top eight metros
Specialist grocery

FirstClub

TechCrunch reported 170,000 households and 1M+ orders in its first year, with about ₹1,200 average order value and 4+ orders per customer per month. Quality-led signal only—not evidence of health-filter demand.

Reported figures ↗
Adjacent experience

Swiggy

Introduced a no-added-sugar category in its food experience, a signal that attribute-led discovery is being explored.

Announcement ↗
Within Zepto

Zepto Cafe

Already lists a Healthy category for Cafe. The question is whether verified dietary-attribute discovery helps across grocery.

Category ↗

The gap to test: Do shoppers need grocery-wide discovery by verified dietary attributes, with clear evidence, inside their existing quick-commerce journey? Avoid claiming this is an untouched market or that Zepto would be first.

03 · Pilot scope

Small surface area.
Strong evidence bar.

Launch a focused grocery discovery flow using three clearly named attributes, location-aware availability and auditable product evidence.

In the v1 pilot

  • A Zealthy entry point in grocery discovery
  • Three pilot filters: No added sugar, High fibre and Gluten-free; explicit eligibility criteria are a launch gate
  • Location-aware, in-stock products only
  • Attribute badges plus a “Why this matches” evidence detail
  • Products with unknown evidence remain in normal browsing without a badge
No added sugarHigh fibreGluten-free

Not in the first pilot

  • Medical, pregnancy, infant-feeding, disease-management or personalized diet advice
  • A universal “healthy score” or implying untagged products are unhealthy
  • LLM-only eligibility decisions based on incomplete data
  • Changes to delivery promises, pricing, or fulfillment
  • Quietly relaxing a dietary filter when there are no matches
Scope boundary: The prototype also depicts high protein, vegan and Jain-friendly options; they are not part of v1. Pregnancy, baby-suitability and disease-related filters are excluded from v1 because they require specialized review and governance.
04 · Shopper experience

A short path from intent to confidence.

The four Canva UX screens are bundled with this page. Select any screen to open the zoom viewer.

Open editable Canva file
01EnterGrocery home or search
02ChoosePick dietary filters
03CompareScan matching items
04VerifyInspect “Why this matches”
05BuyAdd to cart as usual
Prototype status: Static UX frames with illustrative sample products and content. Product names, images, claims, nutrition, availability, location, delivery timing and offers are not production catalog data. Final build must use Zepto design tokens and approved catalog evidence.
05 · Requirements

What the pilot must do.

P0 requirements are necessary to run a safe, measurable test. Feedback collection is useful but not a launch blocker.

FR-1

Reach the section

Expose Zealthy from the agreed grocery entry point in the pilot.

P0
FR-2

Filter eligible products

Only approved, verified attributes and selected-location availability appear in results.

P0
FR-3

Combine and clear filters

Keep selected filters visible; clear-all restores the unfiltered section.

P0
FR-4

Explain every match

Each displayed badge has a source record and a human-readable explanation.

P0
FR-5

Handle no stock or no evidence

Explain empty states; never relax or substitute a dietary filter silently.

P0
FR-6

Measure the funnel

Track section view, filter selection, results, item view, add-to-cart and order completion.

P0
FR-7

Capture trust feedback

Offer a lightweight feedback action after viewing match evidence or completing an order.

P1
AI + catalog controls

AI can assist. Rules decide.

An AI-extracted attribute is not a shopper-facing claim until its evidence is reviewed and the approved rule says it qualifies.

01 · INPUTLabel / maker data

Package image, ingredient list, nutrition panel, manufacturer spec.

02 · AI ASSISTExtract attributes

Suggest structured attributes with evidence snippets and confidence.

03 · REVIEWHuman confirmation

Reviewer records source, date, status and change history.

04 · RULESDeterministic eligibility

Versioned rules—not generative output—decide which SKU qualifies.

05 · SHOPPERBadge + explanation

Show only supported attributes; keep unknown or conflicting data hidden.

Required safeguards: Missing, stale, low-confidence or conflicting evidence stays out of filters. AI-drafted copy must be grounded in the stored record and must not introduce unsupported health benefits or medical claims.
Catalog requirementsRequired fields for every pilot SKU
SKU + variant IDIngredientsNutrition panelPack label / manufacturer specApproved attributesEvidence source + versionReview status, owner + dateCity / dark-store availabilityInventory + price

Products without complete, current approved evidence stay unbadged and out of attribute-filtered results. Launch only in service areas where pilot SKU evidence and stock coverage pass the audit.

06 · Expected outcomes

Faster discovery.
Incremental orders and revenue.

Success is defined by observed user and business outcomes in a controlled pilot—not by a forecast inferred from market size.

Expected pilot outcomes · decision targets, not forecasts
Customer

Find a matching item faster

Higher task completion and lower median time-to-match than the current grocery search journey.

Conversion

More completed grocery orders

Positive treatment-versus-control lift in completed-order conversion for eligible shoppers.

Revenue

Incremental value per shopper

Positive treatment-control net revenue delta per eligible shopper, with a two-sided 95% confidence interval above zero.

Trust

Every badge can be explained

100% of live pilot SKU-attribute pairs audited against current approved evidence before exposure.

MetricSuccess criteriaExpected outcome
Primary · purchase conversionCompleted-order rate for eligible users assigned to treatment vs. randomized control; intent-to-treat. Success: positive lift with a two-sided 95% confidence interval above zero.Incremental orders attributable to the discovery experience.
Incremental net revenue per eligible shopperNet order revenue after discounts, refunds and cancellations ÷ all users assigned to each cohort. Success: positive treatment-control difference in ₹ per user with a two-sided 95% confidence interval above zero. Report contribution margin alongside revenue when finance data is available.Observed incremental revenue contribution from the feature, measured in the experiment—not projected from platform totals.
Discovery success and time-to-matchTask completion rate and median time from a shopper’s stated preference to a qualifying product page, compared with the current browse/search flow.More shoppers find an item, with less search effort.
Feature activation and repeat useZealthy visits, filters applied, add-to-cart, completed order and 30-day return purchase, segmented by selected preference and self/household shopping context.Clear view of feature adoption and repeat utility; app DAU/WAU remain secondary context, not promised lift.
Evidence comprehensionShare of usability participants who can correctly identify why an item matches and what evidence supports its badge; record a 1–5 confidence rating.Shoppers understand the attribute rather than relying on a vague health claim.
Launch quality gate · attribute correctnessAudit every shopper-visible SKU-attribute pair in the launch assortment before exposure; require an approved, current source for each pair and zero unsupported badges.Complete evidence traceability before the pilot is exposed to customers.
Guardrail · core grocery healthCompare overall grocery conversion, cancellation rate, unavailable-item rate and net revenue per order against control; pre-register a non-inferiority margin before randomization.Zealthy adds value without materially harming core order outcomes.
Report actual lift, not a made-up forecast.Conversion lift = treatment rate − control rate

Incremental revenue (₹) = (net revenue per eligible treatment user − net revenue per eligible control user) × eligible treatment users. Include confidence intervals and report contribution margin alongside revenue when finance data is available.

These are decision targets, not predicted results. No Zepto-specific baseline or feature-level impact data is available in this PRD, so it makes no numeric DAU, MAU, order-volume or rupee-revenue forecast. The randomized pilot will estimate those outcomes and their confidence intervals. DAU/WAU are monitored as secondary diagnostics rather than attributed to this feature without causal evidence.

Step 01

Research the job

Interview 5–8 quick-commerce grocery shoppers spanning self and household shopping, work, study and caregiving contexts.

Step 02

Verify the catalog

Audit all pilot SKU evidence, eligibility rules and inventory in the selected service area.

Step 03

Usability test

Compare the prototype with current search; measure task completion, time, evidence comprehension and trust.

Step 04

Run randomized pilot

Assign eligible users to treatment/control; calculate sample size from observed baseline and a pre-agreed minimum effect.

Step 05

Evaluate full outcome

Read the experiment after sample size and the full 30-day repeat window mature; apply quality and conversion guardrails.

Rollout rule: Expand only when the primary order-conversion outcome is positive, all shopper-visible tags pass the evidence gate, and core grocery outcomes stay within the pre-registered guardrails.
07 · Risks & launch gates

Clear the evidence gates before exposure.

The pilot can proceed when customer research, product-claim governance, catalog quality and experiment instrumentation meet the entry criteria below.

!
Catalog gaps or stale data

Audit source fields and verified-tag coverage before selecting the pilot area.

!
Ambiguous health language

Use named attributes with explicit meanings; never label the full assortment healthy.

!
Incorrect or misleading badge

Keep evidence provenance, review dates, audit sampling, correction and removal paths.

!
Medical interpretation

Keep pregnancy, infant and disease-related suitability out of v1; obtain specialist review before any future exploration.

Pilot entry criteria
  1. Complete shopper discovery with participants across self-shopping and household-shopping contexts; confirm the three scoped attributes meet a repeated need.
  2. Document an expert-reviewed definition, evidence hierarchy, owner and correction path for No added sugar, High fibre and Gluten-free.
  3. Audit every shopper-visible SKU-attribute pair in the selected service area; suppress products with missing, stale or conflicting evidence.
  4. Assign product, catalog and customer-support owners for eligibility rules, evidence review, corrections and escalations.
  5. Before randomization, register baseline, minimum detectable effect, sample size, primary metric, analysis window and guardrail margins.
08 · Sources

Evidence, with its limits.

Source links are attached to the specific market and platform signals they support. Study population and forecast limits are stated alongside the figures.

Market scale, competitor activity and survey responses provide context; none of these sources measures Zealthy adoption or causal revenue, conversion, DAU or retention impact. Those outcomes are measured in the randomized pilot.

Prototype screen

Use + and − to zoom · arrow keys switch screens · Esc to close