What we tested in Stockroom /
The tests behind Stockroom: inputs, actions, observed results and the limits of that evidence.
A practical inventory table, searchable SKUs, stock filters and an item inspector keep the day-to-day workflow in view. Example adjustments update quantities and preserve their reasons within the interface.
Internal local testing, using synthetic inputs and owned assets. The results below establish the observed software behavior in those scenarios. They do not establish customer ROI, uptime or external deployment readiness.
The stock equation held through the UI
A synthetic workspace created one SKU and one bin through the forms. Receiving ten units produced ten available. Reserving three kept ten on hand, with three reserved and seven available. Confirming dispatch left seven on hand and no reservation. A physical count of six created a minus-one correction with a reason.
An offline receipt was recorded once
Playwright disabled the browser network before a two-unit receipt. The application exposed one pending operation with the synthetic reference. After network restoration and Sync now, the ledger contained one corresponding plus-two movement. Reloading and selecting the saved item and bin showed eight on hand, zero reserved and eight available.
The export matched the movement history
The downloaded CSV contained four movements: plus ten received, minus three dispatched, minus one counted and plus two received after reconnection. The UI retained those records after reload. Mobile screenshots showed no page-level overflow; the wider movement table used its own horizontal scroll container. The fresh online page had no runtime console errors.
Conflict tests covered separate failure paths
Fourteen recorded HTTP checks covered simultaneous allocations, one-time dispatch and release, stale counts, missing count versions, replay and counts below reserved stock. Final browser retests verified named quantity fields, a clear offline banner and retained last-loaded balances. These are bounded local checks, not evidence of physical scanner compatibility, warehouse adoption or uninterrupted operation during a prolonged outage.
What this evidence does not establish
This release focuses on whole-unit items and bin balances. Lot valuation, accounting, shipping-carrier execution and ERP synchronisation are not established by the tested workflow.
The offline test covered an already open page, one pending receipt and online resynchronisation. Cold offline startup and device loss were not tested.
Camera hardware and keyboard-emulating barcode scanners still require physical-device verification.
The CSV currently identifies item and bin by internal IDs; the interactive ledger displays their readable labels.
The synthetic stock movements are software evidence, not real warehouse transactions.
A similar problem in your business?
Bring a real workflow, representative inputs and the result that needs to be reliable.
Shape a project brief