Curated mall app — turning product trust into a transaction system that runs itself

A shopping app for a health-retail brand: self-operated quality assurance, curated and daily-plus zones, points redemption with its own points orders, share-to-earn commission, order and logistics notifications, and a wellness content channel — six capabilities across twelve core user flows. De-identified presentation.

Industry
Health retail / social commerce
System type
Mobile shopping app (iOS and Android)
Key technology
SKU and spec pricing · points ledger and points orders · referral commission chain · order and logistics push · secondary payment password · content channel
Jiding scope
Requirement shaping, interaction and UI, app and backend development, launch and iteration
6capabilities behind trust, repeat and referral
5product and content zones, one catalogue
12core flows from sign-in to payment password
2password layers: sign-in and payment
LEVEL 1 · FOUR BOTTOM TABS Home Categories Cart Account Search + trending terms Banner slot Five zone entries Content channel Curated feed (2 cols) Level-1 category tree Level-2 grid Five zone lists Items with spec and qty Select all, total, edit Checkout with count badge Four order states Favourites and points Redemption zone Support, complaints, invite Settings, payment password SHARED BY ALL FOUR TABS Order & logistics push Points ledger Referral commission Payment & 2nd password Content & news The five zones are both the priority entries on the home screen and standalone lists under categories: one catalogue, five ways of distributing it.
Information architecture: only four bottom tabs, with points mall, curated zone and daily-plus demoted to zone entries — the rarer but higher-value capabilities are reached from the home screen rather than occupying a tab

Three hurdles in selling health products

The category is not short of goods; it is short of "dare I buy this" and "will I remember to come back". Once the app existed we could see that these are three different system capabilities, not three screens.

  • You are selling trust, not stock. Health foods and skincare are high-ticket and slow to decide. A shelf of photos and prices can only compete on discount; before anyone pays, the app has to answer who makes it and why it is credible — hence self-operated lines and assurance information carried through to the list page.
  • Repeat purchase depends on being remembered. Supplements are consumed on a cycle nobody tracks. Without reminders, reasons and a balance, repurchase has to be bought again with ads, and acquisition cost stays on top of margin.
  • Growth is bought, not shared. Existing customers hold social relationships the platform never gives them a reason to use. Without a referral mechanism every user is a terminus; with a relationship chain and commission, a satisfied user becomes an entrance.

Six capabilities, three jobs

The operating manual lists six features. Architecturally they are three groups: trust (self-operated and assured), repeat (points, notifications, content) and referral (share and commission). Each needs its own data structure; none can be faked with a few extra pages.

Zone / capabilityWhat it solvesKey rules
Curated categoriesTrust: factory-direct, fair priceSelf-operated items are flagged and carry assurance copy on both list and detail; the tree covers daily goods, health food, appliances and books
Recommended zoneDecision: decide for the userEditorial selection plus ranking weight; the home feed and the zone list read the same product data
PLUS daily picksConversion: a reason to buy todayA daily refreshed discount pool, price next to strike-through price, discount expiring back to normal automatically
Points redemptionRepeat: turn a purchase into a balancePoints accrue on payment and buy goods; redemption runs as a points order, accounted separately from cash orders
Content channelRetention: a non-shopping reason to open the appWellness and product explainers on a schedule, with product cards inside articles
One-tap sharingReferral: customers bring customersShare links and QR codes carry a parameter; registration binds the relationship; commission is calculated on completed orders
Order notificationsReassurance: fewer "where is my parcel" ticketsPush on paid, shipped, delivered and reviewable; tracking follows order state
An easy judgement to get wrong: six features are not six pages, they are six views of the same product. So the model holds one catalogue and one SKU set, distributed by five flags — self-operated, recommended, discounted, points and content. Otherwise every new zone means another copy of the catalogue to maintain.

From zone entry to payment

Most mobile drop-off happens where the user cannot understand something or taps the wrong thing. The detail page therefore answers only four questions: how much, which spec, how many, and what the total is.

Zone entry five zones Product list image, name, price Detail spec, qty, total Add to cart stay browsing Buy now skip the cart Cart select all, total Checkout address, payment Order four states Add-to-cart keeps browsing uninterrupted; buy-now goes straight to checkout; favourites never occupy the cart — three routes, no invented choices.
Purchase path: price, spec, quantity and total are linked live on one screen, with the total recalculating on every change; add-to-cart and buy-now are parallel exits so "I want to keep looking" is never forced into checkout

Four fields that carry the whole order

  • Price comes from the selected spec, with strike-through and payable amounts side by side so the discount has a source.
  • Spec is laid out as flat tags ("6 boxes"); tapping switches the SKU and never mixes with quantity input.
  • Quantity uses a stepper plus manual entry, bounded by stock and per-order limits.
  • Total is unit price multiplied live and shares one calculation with checkout — so nobody sees one number and pays another.

The cart does one job: final confirmation before checkout. No recommendations, no promotion stacking — just the item list with spec in small print, quantity, select-all and total, and a checkout button carrying the item count. Edit and delete live behind a corner button, because rare and destructive actions should not sit under the thumb.

Four order states, four reasons to reach out

The order list answers one question: where is my parcel. For the platform, those same four states are four unobtrusive opportunities to talk — and every state change is a legitimate reason to push.

Pending payment order placed Pending shipment paid, not dispatched In transit trackable Pending review delivered Completed points post on completion Cancelled After-sales / refund auto-cancel when unpaid, stock returns available in transit or after delivery Each state change triggers one push: paid → shipped with tracking number → out for delivery → delivered and reviewable → completed (points and commission post)
Order state machine: four states are both the user's progress bar and four chances to reach out; cancellation and after-sales are branches, while stock rollback and points/commission posting hang off state transitions rather than being scattered across screens

In the manual, notifications are one line. In reality they are a subscription: placing an order subscribes that order number, and the server pushes a templated message on each state change. Marketing notifications can be switched off in settings, but transaction notifications (paid, shipped, delivered) cannot — they are not interruptions, they are part of fulfilment.

Two loops: points bring people back, commission brings people in

Points and commission both look like "just add a number", but they are two different ledgers: one is what the platform owes the buyer, the other what it owes the sharer. They must be separated in the data model.

POINTS LOOP · REPEAT Purchase Points balanceauditable ledger Points mallpoints-only catalogue Redeemcreates a points order my redemptions Key: points orders stand alone, accounted apart from cash COMMISSION LOOP · REFERRAL Invitetagged link or QR Bind on signuprelationship stored Friend purchasesamount is the base Commission postsafter the returns window invite again · the link survives one order Key: settle after the returns window, claw back on refund
Two loops: points are what the platform owes the buyer, accrued on payment; commission is what it owes the sharer, calculated on completed orders and withdrawable only after the returns window — separate ledgers keep refunds from tangling
  • Points never mix into cash orders. The easy route is "points as money" inside one order, which then raises three questions: at what ratio do you refund, what is the invoice amount, and which ledger reconciles against which. We made points items create their own orders: the points mall only runs points orders, cash orders only run money. Settlement, refunds and reconciliation stay independent, and operations can see clearly what was given away rather than sold.
  • Commission waits for the returns window. Sharers care when it lands; the platform fears chasing money back after a refund. Commission is first pending, becomes withdrawable after the window, and is reversed from pending if a refund happens. Showing this in the sharer's own ledger beats any agreement text: state and expected settlement date per line, and most support questions disappear.

The account tab: let people help themselves

Most commerce support cost comes from people not finding an entry. The account tab has one plain goal: anything the user can look up themselves should never become a ticket.

AreaContainsWhy
IdentityAvatar, nickname, masked mobile numberThe mobile number is the account; shown masked to balance recognition and privacy
AssetsFavourites, points balanceTwo numbers on the surface, detail one tap deeper: result first, process second
OrdersPending payment / shipment / receipt / reviewEach state carries a count badge so nobody has to enter a list and filter
RedemptionMy points, points mall, my redemptionsPoints go from visible to spent in three steps
ServiceSupport, complaints, invite friendsComplaint and invite side by side: one absorbs dissatisfaction, one amplifies satisfaction
SettingsProfile, payment password, notification switchesThe payment password has its own screen, set separately from sign-in

Two passwords, two doors. Sign-in supports account password or an SMS code, with recovery through the mobile number; the payment password is a separate secondary password, checked only at payment. The reason is practical: shopping apps keep users signed in for months, and phones get lent, lost or handed to family. The sign-in password protects the account from being opened; the payment password protects the money from being spent. Different risks, different locks.

Favourites are an underrated retention surface: a list the user builds themselves, and the most honest interest signal operations will ever get. We only do two things — one-tap save from the detail page, and a reverse-chronological list showing current price with a drop hint. No "you may also like" noise, because saving something already states the intent.

Twelve flows: how a user actually gets through the app

The manual was written screen by screen. We inverted it into one table — flow, path, responsibility — and handed it to both the client and the support team, who now use it to locate exactly where a user is stuck.

#FlowPathWhat it must accomplish
01Sign inLaunch → sign inAccount and password or SMS code; signup and recovery through the mobile number
02Curated categoriesHome entry / categories tabEnter a list from a level-1 category: daily goods, health food, appliances, books
03Recommended zoneHome entry / category pageBrowse editorially selected products
04PLUS daily picksHome entry / category pageSee the day's discounts with price and validity on one screen
05Points redemptionHome entry / category pageEnter the points-only catalogue
06Content channelHome entry / article stripRead wellness and product explainers that link straight to products
07Product detailTap an item in any listGallery and price, choose spec and quantity, see the total, add to cart or buy now
08CartBottom tab / after add-to-cartCheck items and specs, adjust quantity, select, check out together
09OrdersAccount → ordersFilter by four states, track logistics, start after-sales, review
10FavouritesAccount → favouritesSee saved items with current price and return to the detail page
11Points mallAccount → redemption → points mallRedeem with points, produce a points order, review it under my redemptions
12Payment passwordAccount → avatar / edit → settingsSet the secondary password that guards the payment step

The table doubles as acceptance: every flow maps to a reproducible sequence, so the client and we walk it once and the system is delivered. It is also the onboarding script whenever support or operations changes hands.

What the client got

  • One catalogue distributed across five zones, so self-operated and assurance information reaches the list page instead of hiding in a brand story.
  • Three low-cost routes to repurchase — points accrual, order notifications and a content channel — instead of buying every repeat visit with ads.
  • A referral path with relationship binding and commission settled by completed order, reversible on refund.
  • An order flow where every "completed" is a state the system produced, not a status someone typed.
  • A secondary payment password, separate from sign-in, for a device that stays logged in for months.
As agreed with the client, this page shows no client or brand names, no product photography and no screenshots of production screens. De-identified performance figures are available during a scoping call, by comparable scenario.

Building something similar?

Bring three things to the first call: how products are sourced (self-operated, distributed or both), how you reward repurchase today (points, coupons, nothing), and whether referral commission is part of the model. We will say first whether the bottleneck is catalogue, incentive or fulfilment, then propose scope and a phased quote. Related: how we build and the cloud-factory app case.

MORE CASES

More Related Cases

Curated mall app for a health-retail brand
EC AppE-commerce platform, distribution platform

Curated mall app for a health-retail brand

A shopping app for a health-retail brand: self-operated quality assurance, curated and daily-plus zo...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.

1.159824s