Distribution Mini App

01 / BACKGROUND

Background

Offline distribution and pickup activities lacked a unified way to manage distributor profiles, QR information, and actual scan records. Without stable links between people and pickup events, historical relationships could become difficult to verify after profile changes or deletion, while repeat scans and abnormal QR data were also hard to investigate. The project introduced a mini app that establishes agent-distributor relationships and turns every pickup scan into an independent, queryable record. Entry points were placed in the service-account menus used by each commerce company, with session persistence reducing unnecessary repeat logins.

02 / MY ROLE

My Role

Mapped the complete flow from service-account entry, login, first-time profile completion, distributor management, QR pickup, and scan-history queries. Defined required and optional profile fields and session rules; designed distributor creation, editing, soft deletion, and sorting; restricted editing once scan records exist while still allowing soft deletion; defined QR domain, URL structure, and business-parameter validation; allowed repeated scans of the same QR code while preserving each event independently; specified 50 records per page ordered by newest entry time; enabled admin lookup of agents, distributors, and scan details through the business string; and covered invalid QR codes, missing parameters, deleted distributors, repeated scans, empty states, and query failures in QA scenarios.

03 / CORE PROBLEMS

Core Problems

Agent, distributor, and QR relationships need to remain stable even though the same QR code may be scanned repeatedly. QR data must be validated at both the source and parameter level before records are written. Distributor deletion must not remove historical scan data, and editing must be restricted after records exist to avoid rewriting history. Active and deleted distributors still need consistent query and sorting rules, while the admin side requires fast reverse lookup from a scan string to the full relationship.

04 / SOLUTION

Solution

Split the product into five areas: login and profile, distributor management, QR pickup, scan history, and admin lookup. Distributors use soft deletion so historical data remains available, with active records shown before deleted ones and newer entries first. Before recording a scan, the system validates the QR domain, URL structure, and required parameters, then parses the business string and creates an independent scan record. Repeated scans of the same QR code are allowed to match real pickup behavior. Once a distributor has scan history, editing is restricted to protect historical consistency. Admins can use the business string to trace each scan back to its related agent and distributor.

05 / PROCESS & RULES

Process & Rules

06 / RESULT & REVIEW

Results & Reflection

Delivered a complete mini-app solution covering agent profiles, distributor maintenance, QR validation, pickup scans, history queries, and admin traceability. Offline relationships and pickup actions were converted into structured records, with every scan preserved independently and historical links remaining available after deletion. Validation, repeat-scan handling, soft deletion, edit restrictions, and sorting rules reduced the risk of invalid data, relationship confusion, and lost history.

ReflectionThe main challenge was not scanning itself, but preserving relationship and historical consistency around each scan. When the same QR code can appear repeatedly, deleted distributors must remain traceable, and editing becomes restricted after records exist, the product must separate current object state from historical events. A business QR code does not need to be unique, but each scan event should be independently stored and traceable. For offline workflow digitization, soft deletion, permission rules, historical preservation, and reverse lookup are often more important than the scan action itself.