One record per physical piece
The data model separates the catalogue entry for a model from the stock record of each physical piece. Every piece has its own location, notes, optional photo and purchase cost.
Coming soon
Where is each piece right now?
StockLab gives retailers with several shops and warehouses one view of their stock. Every physical piece has its own record, so any location can see what is available, what is on its way and what has been sold.
Who it is for
Furniture retailers and similar businesses that sell large, individual items from more than one place. A sofa in one shop is not the same as a sofa in another: it may have a different fabric, a mark on the arm or a customer waiting for it. Locations may be in different countries and price in different currencies. Staff need to find a specific piece and follow it when it moves.
The problem
When stock is tracked in spreadsheets and chat messages between locations, each shop only sees part of the picture.
- A salesperson cannot tell whether another location has the model a customer is asking about.
- A piece sent to another location drops out of sight while it travels, sometimes for weeks.
- Requests between locations get lost in message threads.
- There is no history of movements, so a discrepancy at stock count is hard to explain.
How it will work
This is the planned daily workflow. The data model behind it exists. The screens and actions below are not built yet.
- Staff open a dashboard with one card per location: pieces available, pieces on their way there and pieces sold this month.
- They look up a model in the catalogue and see how many pieces each location holds, then open the individual pieces.
- A location that needs a model sends a request. The location holding it picks the specific piece to send, or declines with a reason.
- The piece is marked in transit to its destination and marked arrived when it gets there. While it travels it stays visible, with the days elapsed.
- When a piece is sold, staff record the customer name, sale price and date. The piece leaves the available stock but stays in the history for reports.
What it does
Each card says whether the feature exists in the software today or is still planned. Today only the foundation is built.
Prices per location
A model can have a different selling price at each location, in that location's own currency. There is no currency conversion, by design.
Stock dashboard
The first screen: a card per location, a catalogue gallery with counts per location, a panel of pieces in transit and a panel of requests waiting for an answer.
Transfers and requests
Mark a piece in transit and mark it arrived. Ask another location for a model, and let that location choose the piece to send or decline with a reason.
Sales record
Mark a piece as sold with customer name, sale price and date. Sold pieces leave the stock views but stay in the history.
Reports and CSV export
Stock on hand per location, sales by date, location or customer with totals per currency, margin where the purchase cost is known, and CSV export.
Where it stands
StockLab is coming soon. It started as software scoped for one retailer and is being generalised so other multi-location retailers can use it. What exists in code today is the foundation: the data model for locations, models, physical pieces, prices and transfer requests, with a record of who created and last changed each entry. The dashboard, the transfer and sale actions, the reports and the two access roles (an admin who manages locations and the catalogue, staff who add, move and sell pieces) are planned.
Barcode scanning, offline use, invoicing and accounting export are outside the first version. If you sell from more than one location and lose track of pieces between them, tell us how you track stock today.
Other products on the way
StockLab
Selling from more than one location? Talk about StockLab.
Tell us how your team finds pieces, arranges transfers and confirms what has arrived. We will tell you plainly whether StockLab fits.