Retail inventory management software holds what you own and where it is: items and their variants, quantity by location, the movements that changed the quantity, the state each unit is in, what each unit cost, and how many days of sales the current stock represents. With Pentoggle, a retailer can describe how stock actually moves through the store and generate the starting application around it.
This page is about the stock record itself. The related workflows have their own guides: Retail Goods Receiving Software for stock coming in, Retail Inventory Audit Software for counting it, Retail Replenishment Software for reordering it, Retail Multi-Store Inventory Software for the same item across locations. This page is the record they all read from and write to.
Most retailers already run an accounting system such as QuickBooks, Tally or Xero, which holds inventory as a value on the balance sheet, and a POS that deducts what it sells. Those stay where they are. What is often still managed outside them is the unit-level truth: how many of this size in this colour are on the shelf right now, how many are in the back, how many are damaged, and how many are on hold for a customer.
Key takeaways
- Stock on hand is the result of a ledger of movements. A system that holds the number without the movements can show that the number is wrong but not why.
- A unit of stock has a state, not just a location. Sellable, damaged, reserved, on display, in transit and returned-awaiting-inspection are different things, and treating them as one figure overstates what you can sell.
- Variants are the unit. A store that holds "shirt" when it sells shirts in six sizes and four colours has a stock record for something it does not actually sell.
- Cost belongs on the unit. Margin by item, dead stock value and write-off cost all depend on knowing what the stock on the shelf actually cost, not what the last purchase cost.
- A useful number is days of cover by item: stock on hand divided by average daily sales.
The spreadsheet is often not the problem
A stock sheet with one row per item and a quantity column, updated from the POS and from deliveries, is a working system for a small store, and many run one carefully.
The trouble starts at identifiable points.
When the sheet holds a number and not a history
The sheet says 40. The shelf has 31. Nine units went somewhere between the last count and today, and the sheet cannot say whether they were sold, damaged, transferred, returned to the supplier or never received in the first place.
When variants are collapsed
The sheet has "denim jacket: 24". The store has size S in three colours and size XL in none. The number is true and useless, and the customer asking for an XL finds out before the owner does.
When stock is in more than one place
Some on the floor, some in the back store, some in a second location, some in transit between them. One quantity column holds the total, and the total answers no question anyone at the counter is asking.
When the state is not recorded
Three units are damaged, two are on hold for a customer who is collecting Saturday, one is the display piece. The sheet shows six sellable units. The counter sells the display piece.
What retail inventory management software holds
Item master with variants
Every item with SKU, barcode, category, supplier and the variant dimensions that apply, such as size, colour, pack size or finish, each variant a stock unit of its own.
Stock on hand by location
Quantity per variant per location, including floor, back store, warehouse and any other place stock sits.
Movement ledger
Every change to quantity with type, date, quantity, location, the document or transaction behind it, and who recorded it.
Stock states
Sellable, damaged, reserved, display, in transit, returned awaiting inspection, and any state your store uses, each held as a quantity of its own.
Cost per unit
The cost at which stock was received, carried through to the unit so that margin and stock value are calculated on what was actually paid.
Adjustments with reasons
Corrections from counts, write-offs and found stock, each with a reason code and an approver.
Days of cover
Stock on hand against average daily sales per variant, showing what is close to running out and what is sitting.
Stock value
Quantity times cost, by item, category and location, reconcilable to the value your accountant carries.
Stock is a ledger, not a number
The difference between an inventory system that works and one that is abandoned after three months is usually whether it records movements or overwrites totals.
A system that overwrites totals asks the user to type the new quantity. It is fast, and it destroys information every time it is used. When the count disagrees with the system, the only available response is to type the count in, and the discrepancy vanishes without explanation. Over time the store learns that the system's number is whatever was typed last, and stops trusting it.
A system that records movements never asks for the total. It asks what happened: received 60 against this purchase order, sold 3 at the POS, transferred 10 to the other store, wrote off 2 as damaged, counted 31 against an expected 34 and adjusted by 3 with a reason. The total is derived. When the count disagrees, the adjustment is a movement like any other, with a date, a quantity, a reason and a name, and the history shows what happened between the last count and this one.
The practical benefit appears the first time a discrepancy is investigated. The ledger for a variant over the last month is a short list, and the entry that explains the gap is usually visible in it: a receipt recorded at the wrong quantity, a transfer sent and never received, a return that went back to the shelf without going back to stock. Without the ledger, the same investigation is a conversation between three people's memories.
Stock has states, not just locations
Most stock systems hold quantity by location. Fewer hold quantity by state, and the second matters as much as the first.
A unit on the floor that is damaged is not sellable. A unit in the back that is reserved for a customer collecting on Saturday is not sellable either. A unit that came back as a return and has not been inspected is not sellable until someone looks at it. A unit in transit between stores belongs to neither store's sellable count. A display piece may or may not be sellable depending on the store's policy.
When all of these are one figure, the store overstates what it can sell, and the overstatement shows up in specific ways. The counter sells the reserved unit and the Saturday customer is disappointed. The online store shows availability of a unit that is damaged. The replenishment report sees enough stock and does not reorder, because it counted units that cannot be sold.
Holding states separately is a small addition to the record and it changes what the store can promise. Sellable is what the counter and the website can sell. Reserved has a customer and a date. Damaged has a decision pending: return to supplier, mark down or write off. Returned-awaiting-inspection becomes sellable or damaged when someone looks at it, and the ledger records which.
Cost follows the unit
A stock record that holds quantity without cost can tell you what you have. It cannot tell you what it is worth, what you make when you sell it, or what you lose when you write it off.
Cost on the unit means the cost at which that stock was received, carried with it. The same item bought twice at different prices holds both costs, and the method by which cost is assigned to a sale, whether average, first-in-first-out or another, is a choice to make with your accountant and then apply consistently. The application holds the method as a setting and applies it; it does not decide it.
With cost on the unit, several reports become possible that are otherwise guesswork. Margin by item after discounts, using the cost of the stock actually sold. Stock value by category, reconcilable to the figure your accountant carries. Dead stock as a value rather than a count, which is what makes the markdown decision concrete. Write-off cost by reason, so that damage in transit and damage on the floor can be told apart.
It also makes supplier comparison honest. Two suppliers of the same item at different costs are only comparable once the stock from each is tracked at its own cost through to sale.
Where inventory management looks different by business type
- Apparel Retail Software, where every style is a size and colour matrix and the stock unit is the variant, not the style.
- Grocery Store Software, where thousands of items move daily, many are sold by weight, and expiry is a stock state.
- Electronics Retail Software, where each unit is a serial number and the ledger has to follow the individual unit.
- Jewelry Retail Software, where stock is high in value and low in count, and a piece out on approval is a state that has to be visible.
- Hardware Store Software, where the same item is stocked in one unit of measure and sold in several.
- Furniture Retail Software, where floor stock, warehouse stock and made-to-order stock are three different things with three different lead times.
Why retailers choose Pentoggle for inventory management
Movements, not overwrites
Every change to stock is a dated entry with a reason and a name, so the number can be explained when it is wrong.
Variants and states as first-class quantities
Size, colour and pack held as separate units; sellable, damaged, reserved and in transit held as separate states.
Cost carried on the unit
Margin, stock value and write-off cost calculated on what the stock actually cost.
Built for the phone in the back store
Receipts, transfers, adjustments and counts recorded where the stock is, by the person holding it.
Sits around your accounting and your POS
QuickBooks, Tally, Xero and comparable systems continue holding inventory as a value in the books. Your POS continues deducting what it sells. Pentoggle adds the unit-level record between them.
A useful number for inventory management
Days of cover by item: stock on hand divided by average daily sales of that item.
It is more useful than the quantity alone, because a quantity means nothing without the rate at which it sells. Twelve units of a fast-moving item is a stockout next week. Twelve units of a slow-moving item is a year of stock.
Read the two ends of the list rather than the middle. Items with very few days of cover are the reorder list, and a reorder point is a days-of-cover threshold in disguise. Items with very many days of cover are the dead stock list, and the markdown, transfer or return decision starts there.
Calculate it on sellable stock only, and on sales over a window long enough to smooth a slow week but short enough to notice a change. A seasonal item needs a seasonal window, which is a setting rather than a rule.
Ready to build retail inventory management software?
You know how many you have.
You may not be able to say how many are sellable, how many are reserved, what they cost you, or where the nine missing ones went.
Describe your items, your variants, where stock sits and how it moves to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.