SKQ-037

Seller App QA

Mobile fit and wording gate

Aasaan alfaaz

Yeh gate seller app ko phone par check karta hai: footer nahi, heavy wording nahi, andar wali team wali zuban nahi, text overlap nahi, aur button thumb-friendly hon.

Screens

8

Rules

32

Fit

100%

Seller app QA ready. Check mobile fit, plain wording, no footer, and touch safety before demo.

Seller screens

Choose routes to gate

Mobile rules

No footer

Seller pages should not end like a marketing website. Bottom navigation is allowed; footer blocks are not.

App screen only

Plain wording

Use shop words: request, reply, proof, hold, issue, pickup. Avoid control-room and back-office words in seller UI.

No heavy terms

No overlap

Cards, chips, buttons, and text must not collide or create horizontal scrolling at 390px.

Fits phone width

Touch-safe

Buttons and controls should have stable height and spacing for real seller phones.

Thumb friendly

Language guard

Seller words only

Use words a shopkeeper understands during rush time. Internal finance, support, and compliance language belongs behind staff gates.

Website-style footer blocks
Customer web navigation such as discovery, basket, or profile links
Heavy business-suite words on seller phone screens
Control-room language meant for internal teams
Hidden score, private notes, payout, risk, document, or investigation wording
Buttons squeezed together or text running wider than the phone

Touch and overlap

Thumb-safe by default

Buttons should stay tall, cards should not jump, and long labels must wrap cleanly inside phone width.

Core

4

Variants

4

Safety

0

QA packet runner

Pass-ready

Looks safe for mobile demo after browser check.

Screens

8

Evidence

0

Fit

100%

Local QA packets

No QA packet saved yet. Save only after route matrix, wording, mobile fit, and touch rules are reviewed.

Hidden from seller mobile QA

Private customer data, family notes, exact address, phone, payment secrets, and support details
Internal risk labels, hidden scores, ranking rules, investigation comments, and private complaint identities
Supplier cost, seller margin, fee rules, ledger journals, tax internals, payout rules, and settlement records
Production release switches, server secrets, provider credentials, and store upload controls

Boundary locks

QA evidence is not release

Seller App QA Gate creates local QA evidence only; it does not publish, block, verify, penalize, rank, pay, settle, close issues, or change seller trust.
A pass-ready label here means demo readiness, not production approval. Runtime still needs backend permission, privacy, and role-scope checks.
The gate must check phone behavior first: no footer, no customer web navigation, plain seller wording, no overlap, and stable touch targets.
Screens with sensitive flows such as medicine, home visits, family delivery, cash handling, and issue review require extra human review before public use.
QA packets can guide cleanup, but cannot mutate orders, stock, payment, ledger, settlement, disputes, or visibility by themselves.

Connected QA surfaces

End-to-end demoSeller trustPrivacy QASeller homeRequest inboxOffline mode