Lifestyle Logistics

Application development consulting for a fast-fashion 3PL in Shanghai—coding standards, an API-centric WMS rebuild spec, and warehouse tooling that could ship without disrupting live operations.

Role Application Development Consultant

Domain Logistics / 3PL / Fashion Supply Chain

Focus Coding standards, WMS rebuild architecture, warehouse dashboard, vendor management

Website lifestyle-log.com

Lifestyle Logistics branded cover image with the company tagline 'Moving Fashion Forward' — Lifestyle Logistics — Hong Kong–headquartered, Shanghai-operated 3PL serving premium fashion brands across China

The Problem

Software That Had Outgrown Its Process

Lifestyle Logistics ran a custom .NET WMS that handled inbound, outbound, picking, and put-away across Shanghai, Beijing, and Shenzhen. The warehouse systems worked; the development operation behind them had not kept up. Developers worked in isolation, source control was effectively offline, and adding a new client label template could take hours of fragile, unversioned work.

Multi-Client Fast-Fashion Complexity

Multiple fashion brands shared the same physical warehouses—each with its own item master, SKU matrix, packaging rules, label formats, and customs attributes. Inbound cartons arrived mixed or organized, with or without ASN data. The system had to support all of that while keeping audit trails for cross-border and bond-warehouse operations.

No Shared Architecture

There was no shared API, no shared data model, and no common standard for how to write code. Customer integrations lived across spreadsheets, email threads, and ad-hoc scripts. Leadership wanted a real development operation—without disrupting the systems that already kept freight moving.

Constraints & Considerations

Consultant, Not Employee — Contracted through Lotus Creations, with no formal authority over the in-house team. Influence came from clear standards, solid documentation, and shipping working software inside a fixed monthly retainer.
Shanghai Team, Hong Kong Leadership — Day-to-day collaboration with IT and operations in Shanghai; weekly cadence with the CEO in Hong Kong. Travel between the two was part of the engagement.
China Network Constraints — Services outside the mainland firewall were unreliable. Deployment assumed AWS China, AliCloud, on-prem IIS, and locally hosted assets—not Western SaaS defaults.
Multi-City, Multi-Client — Three warehouses, each with its own update servers and user community. Dozens of clients with overlapping but distinct SKU matrices, label formats, and customs requirements.
Don’t Break What Works — The existing WMS and labelling systems ran production every day. Any rebuild had to coexist with them: phased modules, an API the legacy stack could talk to, and tools operations staff would actually use.

Role & Leadership

As application development consultant reporting to the CEO, I split time between standards and architecture—the work that compounds—and delivery that proved those standards were real.

Standards & SOPs

Wrote the development standards the team worked against—coding conventions for HTML / CSS / JS / PHP, MVC rules, testing expectations, source control, wireframe-first design, and sprint workflow. It gave a small, previously isolated team a shared baseline they hadn’t had.

API-Centric WMS Spec

Specified an OAuth2-based API as the single data-access layer for the WMS rebuild—so a new front-end, customer portals, mobile apps, and reporting could share one view of inventory, inbound events, and outbound orders. Modular subsystems could evolve independently without another rewrite.

Full Rebuild Specification

Documented inbound, outbound, inventory, warehouse management, and PDA workflows—including mixed-carton handling, pick/pack strategies, lot control, multi-client ownership, and offline barcode scanning. Wireframes (Balsamiq, then Clarity) became the visual contract vendors built against.

Vendor Management

Selected and managed external development partners for the WMS-v2 MVP and follow-on implementation. Structured subcontracting so the company could keep the rebuild moving without scaling my direct hours one-for-one.

Approach & Execution

Three threads ran in parallel: a fast first delivery to prove the standards, a warehouse dashboard built end-to-end under those standards, and the longer-arc WMS rebuild specs and wireframes.

QC Label Application

First ship: a small PHP / MySQL app for the QC team to track outstanding Marks & Spencer items—task entry, confirmation, image upload, search, multi-user support. Specified and launched in roughly two weeks to show that the new standards could produce something working, fast.

Warehouse Dashboard

First new application built end-to-end under the standards. CodeIgniter + MySQL with locally hosted assets for China use. Cargo Receiving, Operations, and Cargo Dispatch views; role-based access; English and Simplified Chinese; soft-delete; unit testing. Requirements and wireframes before code.

WMS-v2 Spec & Wireframes

A full feature specification covering inbound through PDA workflows, plus a complete admin wireframe set—warehouse and client management, permissions, pre-alert flows, create-operation events, worker mobile screens, and item tracking. Clear enough to hand off implementation to external vendors without ambiguity.

External Build Oversight

Negotiated scope and SOW for the WMS-v2 MVP with an external partner. Locked MVP around multi-warehouse, multi-client operations—clients belonging to warehouses, not the reverse—plus master files, worker task assignment, picking rules, and per-client reporting.

Legacy Labelling & Integrations

Documented the fragile C# / WinForms labelling system end-to-end and proposed a cleaner import-and-verify workflow. Supported and documented customer-specific systems (QC, CIQ, data consolidation portals) so they could be evolved safely rather than reinvented from folklore.

WMS-v2 warehouse list view wireframe showing multi-city Shanghai and Hong Kong warehouses with 5000 sq ft capacity each — Warehouse list wireframe—multi-city operations with capacity, zones, and client-per-warehouse assignment

WMS-v2 inbound operation reception pre-alert view showing fashion clients H&M, Lacoste, ZARA, and Forever 21 with status tracking — Inbound pre-alert wireframe—fashion clients tracked through approval and create-operation-event

Outcome & Impact

A Real Development Operation

Standards became the working SOP. Source control was centralized. The QC app and Warehouse Dashboard were the first projects built end-to-end under the new pattern—replacing isolated, unversioned development with a shared baseline.

Architectural Path Forward

The API-centric WMS-v2 specification—feature list, API design, wireframes, MVP scope—gave the company a clear rebuild path. External vendors were engaged against that spec, and implementation continued after my direct engagement ended.

Knowledge Transferred

Labelling documentation, WMS requirements, IT review, and system overview gave the team a written understanding of their own software. Customer integrations were documented end-to-end so they could be changed without tribal knowledge.

Engagement Close

Lifestyle Logistics is no longer operating. The standards, architecture, and documentation produced during the engagement remain the useful artifact—a runway for the rebuild that outlived the consulting role itself.

Key Takeaway

In operations-driven software, every architectural choice maps to a physical process that has to keep running while you refactor. The standards written for Lifestyle Logistics were ordinary as PHP conventions—and remarkable because they gave a small, isolated team a shared baseline. That shared baseline was the real deliverable.

Skills & Tools

CSS Mobile Responsiveness Performance Optimization Code Review Application Development Consulting Software Architecture & API Design CodeIgniter / PHP AngularJS (specified for WMS-v2) MySQL Database Design C# / .NET Integration (existing WMS) Coding Standards & SOPs MVC / Library-based Validation PHPUnit Testing Source Control (Git / Bitbucket) Vendor Management WMS / Warehouse Operations Fast-fashion 3PL Domain Knowledge Multi-warehouse / Multi-client Architecture CIQ (Customs) Integration Awareness Barcode / PDA Workflows Balsamiq Wireframing Requirements Documentation AWS China / AliCloud IIS / Windows Server Tuleap / Trello Project Management Cross-functional Team Coordination Subcontractor Management SOW / Consulting Agreement Drafting Stakeholder Communication

← Previous: Hitchbird Back to Work Next: Jou Sun →