Retail Desk
Retail operations
One item. Every step.
Follow a sample item through the staff workspace, then open a customer catalog. Select a step to explore.
Inventory
Sample inventory · 4 items
RD-1042
Field / 01
€680 · Steel
Item record
Ready for the shop floor
Reference, condition, supplier and media belong to one stock record.
- Condition
- New
- Reference
- RD-1042
- Branch
- Central
- Status
- Available
Item added · reference RD-1042
Start with one item record: its reference, condition, branch and asking price. The same record follows the item through the workflow.
About the project
Retail Desk is an adapted presentation of a retail management application I developed. It connects the work behind a specialist shop: receiving an item, keeping track of its location, reserving it and recording its sale. The screens here are reconstructed with sample products and records.
My work covered the frontend, backend and API. The application has individual item records, branch and supplier management, transfers, sale requests, reporting and customer catalogs. Staff work with the same inventory throughout, rather than keeping separate lists for each stage.
How it works
Add & reserve stock
Transfer & review
Record the sale
Staff add an item with its reference, condition, photos, purchase details and asking price. A reservation keeps its status visible to the team. If another branch needs the item, a transfer records the origin, destination and handover stages.
A sale request brings the proposed price and customer together for review. Once approved, the final sale retains its own commercial record. Separately, staff can choose and order products in a curated catalog, then share an expiring link with a customer without exposing the internal workspace.
The main challenges
The difficult part is keeping item availability consistent across reservations, transfers and sales. An item cannot be treated as available in one workflow while another workflow has already committed it. Each change needs a clear state and a record of who made it.
Commercial history also needs to survive later edits. The sale keeps a snapshot of the relevant item and financial details. Customer catalogs present a different boundary: they expose a selected set of products through a private link while leaving staff records and internal costs out of view.
The simpler parts
Inventory rows, item details and search filters share a consistent structure. Once the item model and workflow states were defined, those screens could use the same references, branch names and status labels.
Curated catalogs reuse product information from inventory. Staff choose the items, their order and the link expiry, rather than maintaining a second product database.
What works well
The application covers both sides of retail: staff can manage stock and sales, and customers can browse a focused selection. Branch transfers, reservations and sale requests keep the operational steps explicit.
Item history and commercial snapshots make past decisions easier to review. The customer catalog provides a useful way to show relevant stock without giving access to the staff workspace.
