Retail goods receiving software handles the moment a delivery arrives: which order it belongs to, what the delivery note says, what was actually counted, what was short, damaged or different, what was accepted, and where it went. It produces the receipt that the stock record, the supplier's performance and the invoice check all depend on. With Pentoggle, a retailer can describe how deliveries actually arrive and generate the starting application around it.
This page is about the door. The order the delivery is checked against is Retail Purchase Management Software. What happens to the discrepancy afterwards, as a claim against the supplier, is Retail Supplier Management Software. Comparing the invoice to the receipt before paying is Retail Vendor Payment Software. This page is the record they all start from.
Most retailers already run an accounting system such as QuickBooks, Tally or Xero, which records the supplier's invoice, and a stock record of some kind. Those stay where they are. What is often still managed outside them is what happened at the door: how many actually arrived, in what condition, and whether anyone compared that to what was ordered before the driver left.
Key takeaways
- Receiving is the point where stock and money meet. A delivery accepted without a count is stock the store may not have and an invoice it may pay anyway.
- The count has to happen at the door, on the delivery, while the driver is present. Counted later, a shortage is a stock discrepancy nobody can attribute.
- The discrepancy has to be recorded when it is found. A shortage noted on the delivery note and mentioned to someone is often gone by the time the invoice is paid.
- Received stock needs a state as well as a quantity. Units that arrived damaged are not sellable and should not enter the sellable count.
- A useful number is the share of receipts with a recorded discrepancy, by supplier.
The spreadsheet is often not the problem
A delivery signed for on the supplier's note and entered into a stock sheet later that day is a working system for a store receiving a few deliveries a week, and many run one without trouble.
The trouble starts at identifiable points.
When the count is a signature
The driver is waiting. The cartons look right. The delivery note is signed. What was in the cartons is discovered when the shelves are filled, and by then the driver, the note and the moment are gone.
When the delivery is entered from the note
The delivery note says 60. The stock sheet is updated with 60. The carton held 54. The stock sheet is now wrong by six and the invoice for 60 is paid, and neither error is visible until the count.
When the shortage is a conversation
The person at the door noticed the shortage and told the manager. The manager meant to call the supplier. The invoice was paid by someone who was not told. The claim exists in two memories.
When damaged units go into stock
Three units arrived crushed. They went into the back store with the rest because there was nowhere else to put them. The stock record shows them as sellable, the counter tries to sell one, and the customer is the one who finds the damage.
What retail goods receiving software holds
Expected deliveries
Open purchase orders by expected date and supplier, so the door knows what is due and can pull up the order when it arrives.
Delivery record
Supplier, date, time, delivery note reference, who received it, and the purchase order or orders it relates to.
Counted quantities
Per line, the quantity counted at the door, recorded on a phone, against the ordered quantity and the delivery note quantity.
Discrepancies
Short, over, substituted, wrong variant, damaged, each recorded per line when found, with a photo where useful.
Accept, hold or reject
The decision per line or per delivery, with who made it, so that held or rejected stock does not enter the sellable count.
Putaway
Where the accepted stock went, floor, back store or other location, and in what state.
Labelling
Items arriving without a usable barcode flagged for labelling before they go to the shelf.
Discrepancy handover
Each discrepancy passed to the supplier claim and to the invoice check, with its status visible from the receipt.
The door is where stock and money meet
Every other stock movement in a store changes the quantity of something the store already owns. Receiving is different: it is the moment the store takes ownership, and the moment the supplier's claim to payment becomes real.
If the count at the door is right, the stock record starts right, the invoice can be checked against a real number, and any shortage is the supplier's problem from the start. If the count at the door is skipped, the stock record starts from the supplier's document, the invoice is checked against the same document, and any shortage becomes the store's problem later, appearing as a count variance that could have any cause.
This is why receiving is often the first workflow worth building. It is a small change in what the person at the door does, from signing to counting on a phone, and its effect runs through everything downstream: stock accuracy, supplier claims, invoice payment and margin.
It is also the workflow that is easiest to skip under pressure, because the driver is waiting and the delivery is large. The application has to make the count faster than the signature it replaces, or nearly so, which means scanning rather than typing, the order pre-loaded, and discrepancies recorded with a tap and a photo rather than a form.
Count what arrived, not what the note says
There are two ways to count a delivery, and they produce different results.
The first is to check the delivery note: read each line, find the item, confirm the quantity matches. It is fast and it tends to confirm the note, because the person is looking for agreement and the note tells them what to expect.
The second is to count the delivery first, without reference to the note, and compare afterwards. It is slower and it finds more, because the person is recording what is in front of them rather than confirming what a document says.
Which approach suits a store depends on the delivery. A weekly delivery of thirty cartons from one supplier may justify a blind count. A daily delivery of two hundred lines of fresh goods may only allow a check against the note with spot counts. The application can support either, and the useful design is to make the comparison automatic: the counted quantity is entered, the ordered and noted quantities are shown beside it, and any difference is a discrepancy without anyone having to notice it.
Whichever method is used, the count has to be recorded per line, on the delivery, before acceptance. A total carton count is not a receipt. It is a signature with a number on it.
The discrepancy has to survive the day
A shortage found at the door is worth money only if it reaches two places: the supplier as a claim, and the invoice check before payment. In many stores it reaches neither, because the path from the door to those two places runs through a conversation.
Recording the discrepancy on the receipt, per line, with a type and a quantity, gives it a life of its own. It becomes a record that can be seen by the person who pays invoices, who can hold the invoice or short-pay it. It becomes a record that can be seen by whoever handles supplier claims, who can raise it. And it stays visible on the receipt with a status, so that a shortage from six weeks ago that was never credited is a line on a list rather than a forgotten complaint.
Damage deserves the same treatment and one more step. Damaged units need a photo at the door, because a claim for damage in transit is far easier to make with evidence taken while the carton is open and the driver is present. They also need a state, so they enter the stock record as damaged rather than sellable, and a decision, return, claim or write-off, that someone owns.
Substitutions are the discrepancy most often missed, because the quantity is right. Sixty units arrived, sixty were ordered, but the variant is different. Scanning the barcode at the door catches this where a count does not.
Where receiving looks different by business type
- Grocery Store Software, where deliveries are daily, lines are many, fresh goods are checked for condition and date as well as count, and the driver cannot wait.
- Supermarket Software, where a receiving dock handles several suppliers at once and the count has to be per pallet and per carton.
- Apparel Retail Software, where a delivery is a size and colour matrix and the wrong ratio is a discrepancy even when the total is right.
- Electronics Retail Software, where each unit's serial number is captured at the door so that warranty and returns follow the individual unit.
- Beauty Retail Software, where batch numbers and expiry dates are recorded at receipt because they decide what can be sold and for how long.
- Multi-Store Retail Software, where receiving happens at a central warehouse and at stores, and the transfer from one to the other is itself a receipt.
Why retailers choose Pentoggle for receiving
The order at the door
The purchase order pre-loaded on a phone, so the count is against what was ordered rather than what the note says.
Discrepancies recorded when found
Short, over, wrong and damaged captured per line with a photo, before the driver leaves.
Received stock with a state
Accepted units become sellable; damaged and held units do not, so the counter and the website only see what can be sold.
One receipt feeds three checks
The stock record, the supplier claim and the invoice comparison all read from the same count.
Sits around your accounting
QuickBooks, Tally, Xero and comparable systems continue recording the invoice and the payment. Pentoggle adds the receipt the invoice is checked against.
A useful number for receiving
The share of receipts with a recorded discrepancy, by supplier.
It measures two things at once: how often deliveries differ from orders, and whether the store is catching the difference. A supplier with a high figure is a supplier to talk to. A supplier with a figure of zero over many deliveries may be excellent, or may be a sign that nobody is counting.
Read it alongside the value of discrepancies and their status. A high count of small discrepancies that are all credited within a week is a well-run relationship with a sloppy supplier. A low count of large discrepancies that are still open after a month is a problem in the store.
Track it by receiver as well as by supplier. If discrepancies appear only on one person's receipts, either that person is the only one counting or that person is receiving the difficult deliveries. Both are worth knowing.
Ready to build retail goods receiving software?
You know what you ordered and you know what you paid for.
You may not be able to say what actually came through the door, or how much of the difference you ever got back.
Describe how deliveries arrive, who receives them and what goes wrong to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.