Stalife
StalifeAI Commerce

Stalife Guide

User Guide

Stalife AI Commerce: join, list, respond to demand, pay, fulfill, and settle — end to end

Partner joinBusiness contact

1. What is Stalife AI Commerce?

Outwardly a steady-state chronic-care service; inwardly an OPC private-domain operating system.

Stalife is not a single-SKU marketplace. It is a network for steady-state health services plus private-domain checkout and fulfillment.

The core object is the User Package Instance (UPI): tasks, orders, fulfillment, risk, settlement, and reports all hang on it.

The only storefront is the steady-state card page (/app/shop/card/[token]). After checkout, users complete consent, contract, real payment, then fulfillment.

  • External packaging: chronic steady-state care (plan + OPC care + necessary supplies)
  • Internal capability: WeChat-group demand response, card checkout, follow-ups, wallet splits
  • Money path: real payment → split ledger → release on sign/service → partner wallet → withdraw → HQ marks paid
No medical diagnosis; no cure / stop-medication claims. Content is boundary-checked.

2. How do I join?

Register as a user, then apply by role. Region nodes are created by HQ only.

Public entry: /join. Phone registration supports CN / MY / SG numbers.

RoleHow to joinNotes
Consumer / userRegister → Approle=user; buy, sign, view data
OPCRegister → Profile → More → Onboarding → HQ reviewThen “Enter workbench” to refresh role
Professional (Pro)Same onboarding (professional)Orders, service notes, settlement
SupplierSame onboarding (supplier)List, stock, ship, goods wallet
RegionNo self-serveCreated by Admin
Business inquiry only/contactJoin intent redirects to /join
After approval, click “Enter workbench” to refresh the JWT — no re-login needed.

3. How do I list products?

Supplier creates SKU → submit review → active after HQ approval; can delist/relist.

All supplier product actions bind to the logged-in supplier account. States: draft → pending_review → active/rejected; active ↔ inactive.

  1. 1

    Open supplier workbench

    After approval, enter /dashboard/supplier via “Enter workbench”.

  2. 2

    Create product master

    Name, specs, price, package links — save as draft.

  3. 3

    Submit for review

    Moves to pending_review; HQ reviews in Product Review.

  4. 4

    Outcome

    Approved → active; rejected with reason — edit and resubmit.

  5. 5

    List / delist

    Active items can be set inactive and reactivated later.

Unapproved products never appear for sale or card checkout.

4. Inventory & product funds?

Batch restock controls sellable qty. Goods funds = released supplier split into wallet.

Inventory: adjust batch qty (positive in / negative out). Sellable stock follows batches; orders reserve stock.

Product funds: after payment, a split ledger is created; by default supplier lines release into the goods wallet after user sign-off.

Prepaid: HQ may credit prepaid wallets (separate from goods splits) for deposits or campaigns.

Withdraw: request in wallet → HQ pays offline → Admin marks paid. No automatic bank payout yet.

  • Stock: Supplier → Inventory → Adjust
  • Funds: Supplier → Wallet (after split release)
  • Definition: released supplier split rows — not a separate virtual currency

5. How do we serve demand & connect channels?

We serve demand — not eyeballs. Live today: WeChat-group AI assistant responds to intent and issues cards. Other scenes are planned or not connected.

All channels should connect existing steady-state demand to the card for consent, contract, and payment.

OPC “AI Steady Assistant”: open group → pick package → bind nicknames → respond to intent with cards (boundary-checked copy).

WeChat groups + AI assistant

Live

Live. Multi-tenant by OPC. Production Worker supported. Card: /app/shop/card/[token].

WeChat Mini Program

Planned

Planned as a card/fulfillment shell on the same UPI — not open yet.

WeChat Channels (Video Account)

Planned

Planned for content that surfaces demand → private-domain/card fulfillment — shop/pay not connected.

Shopee

Not connected

Not connected. Do not promise Shopee-native split settlement.

Lazada

Not connected

Not connected. No official shop API fulfillment loop yet.

LINE

Planned

Planned for SEA private domain — Bot/shop not live.

Only channels marked Live are available. Use /contact for partnership discussions.

6. How do consumers pay & receive goods?

Real payment after consent/contract; supplier ships with real tracking; user signs.

Pay: card or App package path → consent → contract → enabled gateway.

Settlement follows async notify (WeChat Pay / Stripe / Alipay). Then UPI opens and splits generate. Unconfigured channels cannot checkout — no mock success.

Ship: carrier + real tracking number; optional delivered mark; user signs on Delivery.

  • Gateways: wechat_pay / stripe / alipay (per Admin enablement)
  • No fake tracking; related splits release after sign-off per rules

7. How do partners share revenue?

Configurable split ratios. OPC ratio follows L1–L3 level.

Parties: platform, region, OPC, supplier (goods), logistics, professional. HQ configures rules (sum ≤ 100%).

Supplier lines attribute by product; each role only sees own settlements/wallet.

PartyDefault ratio (configurable)Notes
Platform10%HQ ops & system
Region5%Region node
OPCL1 15% / L2 18% / L3 20% (L0=0)By level; OPC row read-only in config
Supplier (goods)20%Per product ownership
Logistics8%Fulfillment partner
Professional10%Service milestone
Defaults from seed data — live ratios follow Admin Split Rules.

8. When can partners get paid?

Two steps: release into wallet by milestone, then withdraw → HQ marks paid.

Default release triggers (configurable):

  • Only released balance can be withdrawn
  • Withdraw waits for HQ offline payout + “marked paid”
  • OPC follow-up node earnings also land in wallet before withdraw
PartyDefault triggerMeaning
Platform / Regionon_paymentAfter payment notify
OPC / Supplier / Logisticson_signAfter user sign-off
Professionalon_service_completeAfter service confirmation
Wallet credit ≠ bank deposit. Bank arrival = Admin marked paid.

9. SOP (standard operating procedure)

End-to-end checklist from onboarding to payout.

Run one full loop in this order:

  1. 1

    HQ prep

    Enable at least one payment channel; verify split rules; staff onboarding & product review.

  2. 2

    Partner onboarding

    OPC / Pro / Supplier: register → apply → approve → Enter workbench. Region by HQ.

  3. 3

    Catalog & stock

    Supplier creates product → review → restock → keep active.

  4. 4

    Respond to demand & issue card

    OPC WeChat AI assistant → package → bind members → issue cards.

  5. 5

    Checkout

    User card → consent → contract → real pay; confirm notify + UPI open.

  6. 6

    Ship & sign

    Real tracking → user sign-off (optional delivered mark).

  7. 7

    Service (if any)

    Pro completes service notes; OPC completes follow-up nodes.

  8. 8

    Split & withdraw

    Confirm wallet release → withdraw → Admin marks paid.

Respect medical boundaries (no diagnose/cure/stop-med claims). R3+ risks force pause per platform rules.

Ready to operate with Stalife?

Join as OPC / professional / supplier to unlock ops and fulfillment tools.

Partner joinConsumer FAQ