A visual notebook from Shubham Chandra. What you’re looking at, why it matters, and how I approached the work.
Story 01 / Jewellery operations
Reserve the piece. Not just the product.
When every item is different, a reservation needs to follow the physical piece across brands and branches.
ITEM / IDENTITY
One physical piece
01Piece identity↗
02Exact reservation↗
03Branch location↗
The same identity, through every handoff.
Workflow illustration · not a product screenshot
01 / The visual
What you’re looking at
An illustration of one jewellery piece connected to its identity, reservation, and branch location. It shows the operational relationship rather than an application screen.
02 / The problem
Why this needed attention
A product quantity is not enough to describe jewellery stock. Each piece has its own HUID, weight, components, and location. Across two brands sharing physical stock, an estimate or reservation needs to refer to the exact item a customer selected.
03 / The response
What I did to address it
I connected individual-piece identity, locations, stock movements, estimates, reservations, orders, and invoices through shared inventory and backend services. The physical piece remains the reference point as staff move from customer interest to reservation and order.
Story 02 / Hardware operations
A component changes. The history stays.
A refurbished computer is more than a model number. Its parts, checks, and branch movements belong to the same record.
UNIT / CONTINUITY
One physical unit
01Barcode identity↗
02QC + component history↗
03Branch movements↗
The record moves with the device.
Workflow illustration · not a product screenshot
01 / The visual
What you’re looking at
An illustration connecting a computer’s barcode identity with quality checks, component changes, and branch transfers. It is a simplified view of the lifecycle, not a screenshot or an automatic process.
02 / The problem
Why this needed attention
New and refurbished hardware needs to be followed at unit level. A device can go through intake, quality checks, component additions or removals, and a branch transfer before fulfilment. Those events need to stay connected to the same physical unit.
03 / The response
What I did to address it
I brought intake, quality checks, component additions and removals, barcode tracking, branch transfers, fulfilment, and the online catalogue into the scope of one operational system. The unit’s identity provides the connection between these parts of the hardware lifecycle.
For the wider client context and engagement scope: