Skip to content
Back to selected work

JINVERSE DIGITAL / OWNED WORK / STOCKROOM

STOCKROOM — A replenishment workflow you can inspect and export

Branded operations & data workflows

An owned local-first operations front end with eight fictional products, stock filters, validated quantities, restock costing, persistent drafts and real CSV export. No ERP or orders.

Self-initiated studio work, not a client commission. No adoption, revenue or business uplift is claimed.

STOCKROOM original product operations table and replenishment draft interface
Original front-end workflow with eight fictional products and procedural SVG illustrations. Costs and stock are demonstration data; the interface uses Traditional Chinese.

The design problem

A small retail brand needs to understand what requires attention before preparing replenishment. STOCKROOM turns that workflow into an inspectable interface with search, priority, quantity decisions and a portable draft, rather than a dashboard that only displays static numbers.

The implementation

Eight fictional products share a deterministic data model. Search, category, low-stock and sort controls feed the same product view. A detail dialog validates integer quantities from 0 to 500, and the draft calculates costs, supports notes and persists locally. CSV output implements BOM/CRLF, quoted fields and formula-prefix protection for a practical data handoff.

Deliverables to inspect

  • Responsive product table with name/SKU search, category and low-stock filters, sorting and clear empty-result states.
  • Quantity editor, suggested replenishment, per-item removal, total cost, notes and versioned browser-local draft restore/reset.
  • Actual CSV download with quoting and formula-prefix handling, plus editable HTML/CSS/JavaScript and the product/validation model.

Scope and limits

  • The products, costs and stock are fictional. This is not an ERP, POS or procurement integration: it does not update real stock, place orders, send email, collect payments or upload the draft.
  • Browser storage may be cleared and is not a shared authoritative database. Production adoption still requires data ownership, permissions, integration and reconciliation; no time saving, customer adoption or revenue result has been measured.