E-commerce Admin Rebuild

01 / BACKGROUND

Background

As the commerce business expanded, product management accumulated variants, multiple user roles, commissions, purchase limits, inventory, promotions, media resources, and multi-company synchronization. The original admin system grew by adding features over time, leaving fields and actions scattered across pages and making product-, variant-, and role-level states difficult to interpret. At the same time, a central server needed to distribute product configuration to many company servers while inventory had to remain centralized and shared in real time. Media requirements also expanded from image-only management to mixed image and video content, cross-page selection, resource movement, and sync failure handling. The rebuild therefore focused on clarifying data ownership and operational boundaries without breaking existing products or historical data.

02 / MY ROLE

My Role

Mapped the full lifecycle of product creation, editing, bulk publishing, variant setup, role-level sales states, commissions, purchase limits, inventory adjustments, media selection, promotions, and sync tasks. Redefined the relationship between products, variants, and four user roles so the actual sales state comes from variant-role configuration and product lists only aggregate the result. Moved commissions into variant configuration and separated purchase limits into an independent module. Designed centralized shared inventory with order reservation, cancellation recovery, full-refund recovery, and idempotency rules. Defined image and video upload, grouping, cross-page selection, movement, deletion restrictions, and sync failure feedback. Also specified mixed image-video galleries, thumbnails, zoom, autoplay, playback control, and audio-state recovery, while covering legacy data, concurrency, duplicate requests, media failures, and sync exceptions in QA.

03 / CORE PROBLEMS

Core Problems

Product, variant, and role publishing states existed at multiple levels, creating conflicting sources of truth. Commission, purchase-limit, role, and inventory settings were tightly coupled, making change impact hard to understand. Product data needed to sync to many company servers while shared inventory had to remain centralized and untouched by synchronization. Inventory adjustments, reservations, cancellations, and refunds required idempotency and concurrency protection. Image and video workflows introduced many upload, selection, movement, and sync edge cases. The rebuild also had to preserve existing products and historical data without changing their effective states.

04 / SOLUTION

Solution

Reorganized the admin system around products, variants, role configuration, shared inventory, media resources, and sync tasks. Bulk publishing remains available at product level, but the actual sales state is stored only in each variant's four-role configuration; product lists aggregate these states into published, partially published, or unpublished. Commission belongs to variants and purchase limits are managed independently to reduce hidden coupling. Inventory is centralized on the main server and shared in real time, while sync tasks distribute product data, variants, pricing, and role states without overwriting inventory. Orders reserve inventory immediately, while cancellation and full refunds restore it through idempotent operations. Media management supports both images and videos with clear upload, selection, movement, deletion, and failure-recovery rules.

05 / PROCESS & RULES

Process & Rules

06 / RESULT & REVIEW

Results & Reflection

Delivered a complete admin rebuild covering product data, variants, role configuration, shared inventory, media resources, and synchronization. State ownership across products, variants, and roles became clearer, while shared inventory was separated from sync workflows and given explicit idempotency and concurrency rules. Image and video resource operations were standardized under one media model. The solution also defined legacy-data compatibility and exception boundaries, giving development, migration, and regression testing a consistent implementation basis.

ReflectionThe key lesson from a large admin rebuild is that interface redesign matters less than identifying the true owner of each state and data object. When products, variants, roles, inventory, and resources all carry overlapping state, complexity grows quickly. A better approach is to define one source of truth and let other views aggregate or present it. For shared inventory and multi-server synchronization, product requirements must also define which data can be copied, which must remain centralized, and where final concurrency decisions are made. Reducing state layers and configuration coupling is more effective than adding more explanatory text.