Purchase Receiving Discrepancies: How Shops Stop Stock Errors at the Door
A supplier can deliver ten cartons while the delivery note says twelve. One carton may contain fewer units than expected. A product may have the wrong size, colour or pack. Another box may be damaged in transit. If staff enter the supplier’s document total without counting what actually arrived, the stock record becomes wrong before the goods reach the shelf.
This is the operational problem behind the search for purchase receiving stock discrepancy Kenya controls. A reliable process compares what the shop intended to buy, what the supplier says was delivered and what staff physically accepted. It records shortages, excess quantities, substitutions and damage before updating available stock. This guide provides a receiving checklist, discrepancy workflow, management reports and demonstration questions for Kenyan retailers.
Why receiving accuracy matters beyond the storeroom
The received quantity influences stock availability, reordering, supplier history, product cost review and margin analysis. If the system records twelve units but only ten arrived, staff may later search for two units that never entered the premises. The business can mistake a supplier shortage for theft, a counting problem or a selling error.
An unrecorded excess creates the opposite issue. Physical units exist but the system cannot explain them. A wrong product can sit under the intended item code, causing cashiers to sell one thing while inventory reduces another. Damaged goods can inflate available stock even though they cannot be offered to customers.
Receiving is therefore a control point. Errors are easier to resolve while the driver, documents, cartons and responsible staff are present. Once goods are mixed onto the shelf, evidence becomes harder to separate and the next stock count inherits the problem.
The three quantities staff must not confuse
A good process distinguishes:
- Ordered quantity: what the retailer intended or authorised to buy.
- Document quantity: what the supplier’s delivery note or invoice says was sent.
- Accepted quantity: what staff physically counted, inspected and allowed into usable stock.
These figures may match, but the workflow should not assume they do. When there is a difference, record the product, quantity, reason, evidence and responsible people. Do not alter the ordered quantity afterward merely to make the documents agree; preserve the original expectation and the actual receiving event.
Common receiving discrepancies
Short delivery
Fewer units arrive than the supplier document or purchase expectation shows. Count inner packs as well as cartons when appropriate. A sealed-looking carton can still contain a different quantity, especially where products are supplied in cases and sold as individual units.
Over-delivery
More units arrive than authorised. Extra stock is not automatically free. The receiver should follow the retailer’s policy, record the discrepancy and obtain an approved decision before accepting or returning the excess.
Wrong product or variant
The description may look similar while size, colour, specification, flavour or pack quantity differs. Product codes and careful physical comparison reduce the chance that the wrong variant is posted under the intended item.
Damaged goods
Boxes may be crushed, wet, torn or tampered with, while the item inside may be affected or uncertain. Record the observed condition at receiving. Do not add questionable units to saleable stock simply because they appeared on the document.
Duplicate delivery
A supplier may repeat a previously received delivery or staff may try to post the same document twice. Check the reference, date, supplier and related purchase history before accepting the record.
Unordered substitution
A supplier sends an alternative product without the buyer’s prior decision. Even when the value looks similar, the substitute may not match customer demand or product setup. Require authorised acceptance and record it as the product actually received.
Cost or price difference
The document may show a different unit cost from the purchase expectation. Receiving staff should flag the issue for the authorised buyer or manager instead of silently changing the product cost. The physical quantity can be checked while the commercial difference follows its approval route.
A 14-step purchase receiving checklist
1. Prepare before the delivery
Know which supplier and products are expected. Assign a receiving area and an authorised staff member. Avoid unloading directly onto selling shelves where checked and unchecked stock can mix.
2. Identify the supplier and reference
Confirm the supplier, delivery document, date and any related purchase reference used by the business. Check whether the document appears to have been received already.
3. Count outer packages
Count cartons, sacks or containers before opening them. Note visible damage, broken seals or packaging differences. This first count gives an immediate basis for discussing missing packages with the driver.
4. Compare product identity
Match each delivered item to the intended product. Check the code, description, variant and pack size used by the shop. Do not rely on colour or a shortened description alone.
5. Count actual units
Where goods are bought in cases and sold individually, confirm the units per case. Record the quantity in the same unit the stock system expects. Mixing cartons and pieces is a common source of large errors.
6. Inspect condition
Separate acceptable goods from damaged or uncertain ones. Use a temporary controlled area while a manager decides what will be accepted. Never let uninspected goods merge with available stock.
7. Compare all three quantities
Review ordered, documented and physically acceptable units. Highlight every difference by product instead of writing one general note on the whole delivery.
8. Record a clear discrepancy reason
Use short reasons such as short delivery, excess quantity, wrong item, wrong variant, damaged packaging, damaged product, duplicate document, cost difference or awaiting inspection. Add a note where needed.
9. Capture supporting evidence under policy
Preserve relevant delivery documents and, where the business policy allows, photographs or signed notes that show the condition. Keep evidence connected to the receiving record and restrict access appropriately.
10. Obtain an authorised decision
Define who may accept an excess, substitution, damaged unit or cost difference. The receiver should not make every commercial decision simply because the delivery vehicle is waiting.
11. Post only the accepted stock
Update available inventory with the quantity and product actually accepted. Goods awaiting inspection should not appear as ordinary saleable units unless the business has a clearly controlled status for them.
12. Record what was rejected or left outstanding
Document quantities not accepted and the next action. A shortage may remain outstanding, be cancelled or require supplier follow-up. The receiving record should not promise what the supplier has not confirmed.
13. Sign off the receiving event
Record who counted, who approved exceptions and when the receiving was completed. If a later correction is necessary, preserve the original and the authorised correction reason.
14. Move accepted goods to storage or shelves
Only after posting should the accepted units join normal stock. This final boundary protects the reliability of the receiving count and prevents double handling from creating unexplained differences.
How purchases, receiving and stock records should connect
A purchase record says what the shop is acquiring. Receiving confirms the physical event. Inventory reflects the accepted result. If these are maintained as unrelated notes, staff must retype quantities and differences can disappear between steps.
The reviewer should be able to open a product and see relevant purchase and receiving movements together with later sales, returns and adjustments. This helps management answer whether a variance began at the door or occurred later. Review the POS inventory software buyer checklist for other questions about connecting stock transactions.
Supplier history should show recurring patterns. Frequent short deliveries, damage or substitutions from one source deserve a focused conversation. The system provides the history; the buyer should verify evidence and follow agreed commercial terms rather than assuming an automatic claim.
What to do when the driver cannot wait
Pressure at the receiving door is a common reason staff skip checks. Create a short priority routine: count packages, identify visible damage, compare key quantities, mark exceptions and obtain the appropriate acknowledgement under company policy. Do not sign that everything is correct when the count is incomplete.
If the delivery is too large for a full immediate unit count, define a controlled pending area and who will complete verification. The system quantity should reflect the business’s approved receiving state. Staff should not sell unverified stock or mix it with already counted units.
Plan deliveries where possible, maintain enough receiving space and assign cover so customer service does not force the receiver to abandon cartons midway. Process design is as important as software.
Daily discrepancy report for managers
A focused report should show the supplier, delivery reference, product, ordered quantity, documented quantity, accepted quantity, difference, reason, value context, receiver, approver, status and next action. Managers should be able to filter open discrepancies and open the related purchase or receiving record.
Prioritise:
- high-value shortages or excess quantities;
- damaged goods that remain unresolved;
- repeat discrepancies for one product or supplier;
- substitutions accepted without clear authority;
- cost differences that may affect selling price and margin;
- receipts corrected after completion;
- deliveries posted by a user outside the normal receiving role;
- unusually old pending inspections.
Do not close the exception simply because an email or phone call occurred. Record the actual outcome: corrected supplier document, accepted difference, returned goods, cancelled outstanding quantity or another approved resolution.
How receiving errors reach the sales floor
A wrong pack size can make the POS quantity and physical stock diverge immediately. A wrong variant can create customer returns. An unrecorded cost difference can reduce gross margin without a price review. Damaged goods counted as available can lead cashiers to promise stock that cannot be sold.
These connections are why receiving should be tested as part of the broader retail process. The retail POS implementation guide helps businesses map products, user roles, checkout, stock and reports before launch.
For deeper supplier-process questions, see the supplier management software guide. Use its principles carefully: system history supports a supplier discussion but does not replace agreed terms or human verification.
Controls that reduce repeat discrepancies
- Use clear product codes and units of measure.
- Keep supplier product descriptions mapped to the shop’s actual products.
- Separate receiving access from unrestricted product-cost editing.
- Require reasons and approval for discrepancies.
- Prevent casual duplicate receiving against the same reference.
- Keep checked and unchecked goods physically separate.
- Review supplier and product exception trends.
- Count selected received products again after shelving as a quality check.
- Train staff to distinguish cartons, packs and pieces.
- Preserve corrections instead of deleting the original record.
Questions to ask in a receiving software demo
- Show how staff compare expected and actually received quantities.
- Can we receive part of a purchase without marking everything complete?
- How are shortages, excess quantities and wrong products recorded?
- Can damaged goods be kept out of available stock?
- How does the system handle cartons versus individual pieces?
- Can a manager approve a substitution or cost difference using a separate role?
- What prevents the same supplier document from being posted twice?
- Can the reviewer see who counted and who approved?
- Does supplier history show repeated discrepancy reasons?
- How does a receiving correction appear in the audit trail?
- Can managers list open discrepancies and their next actions?
- Can we test a short delivery, a damaged carton and a wrong variant using sample data?
Do not accept a demo that shows only a perfect delivery. Ask the provider to enter ten ordered units, nine acceptable units, one damaged unit and a supplier document showing ten. Then inspect available stock, the discrepancy report and the approval history. The exception path is the real test.
Frequently asked questions
Should stock be updated from the supplier invoice?
Available stock should reflect what the business physically accepted under its receiving process, not blindly copy a supplier document. Preserve ordered and documented quantities so differences remain visible.
What if the supplier delivers more than ordered?
Record the excess and follow an authorised decision. Do not assume it is free or add it casually to stock. The correct action depends on the retailer’s policy and supplier agreement.
How should damaged goods be recorded?
Record the quantity, condition, evidence and decision. Keep uncertain or rejected units out of ordinary saleable stock and assign a follow-up action.
Why keep the original receiving record after correction?
The original and correction explain what changed, who authorised it and why. Deleting the first record removes information needed for stock and supplier review.
Who should receive deliveries?
Assign trained users with appropriate access. High-risk exceptions can require a manager or buyer. Avoid shared accounts so actions remain attributable.
Can receiving discrepancies explain stock-count differences?
Yes. If the wrong quantity or product was posted at the door, later counts inherit the error. Review purchase and receiving history before assuming the difference occurred during selling.
What report should an owner review?
Review open and high-value discrepancies by supplier, product, reason and responsible user, then open the underlying record. Also track recurring patterns rather than only single deliveries.
Does the software settle a supplier dispute?
No. It preserves operational records that can support a discussion. The outcome still depends on evidence, agreed terms and authorised communication between the parties.
Test the receiving door before stock reaches the shelf
Vega connects purchases, supplier history, stock movements, sales, returns, adjustments, roles, receipts, margins and reports. A useful demonstration should show how the accepted physical quantity becomes stock and how every difference remains visible for follow-up.
Register your interest in Vega and request an online Vega demonstration, or arrange an appointment-based in-person discussion with Zama Systems at its Karuguru Plaza office along Eastern Bypass. Bring a recent receiving example and ask to process the normal delivery, short delivery, wrong item and damaged-box paths before making a decision.