How Goods-In Errors Cause Stock Discrepancies Weeks Later (and How to Stop Them at the Dock)

Goods-in errors cause stock discrepancies weeks later because a receiving mistake writes a wrong number, code, batch or location into the warehouse system, and nothing flags it until a pick, a replenishment or a count tests that record. By then the original delivery is long gone. Catching errors at the dock, through ASN-driven receiving, scanning and photographed exceptions, is far cheaper than finding them in week four.

A goods-in error is any difference between what physically arrived and what the warehouse recorded at receipt: quantity, product, batch, condition or location. At Fulfil with Synergy, the receiving process is built on the technology and automation at Fulfil with Synergy, so every inbound delivery is scanned at pallet and carton level against pre-advice before it becomes sellable stock.

‍

Below, six common errors are traced from the dock to the point you notice them. For wider causes of drift, see the most common causes of falling inventory accuracy across channels. For damaged deliveries specifically, read how a 3PL should handle damaged stock at goods-in.

Wrong carton quantity accepted > orders pick normally in week 1 > short picks and oversells by week 4

A supplier packs 22 units in a carton labelled 24, and goods-in receives by carton count multiplied by the label quantity. The record is now two units high per carton, with no physical evidence of the gap.

‍

Week 1: Orders pick normally from the first full cartons. Your sales channels show healthy stock.

‍

Week 4: The last cartons run dry before the system says they should. Pickers report short picks, orders sit in exception, and your Shopify or Amazon stock feed has already sold units that do not exist.

‍

What stops it: QC sampling of carton contents at receipt, especially for new suppliers, new SKUs and any carton whose weight does not match the expected weight. Cubiscan weights for each SKU give a reference to check against.

Mixed SKUs in one carton > wrong item shipped in week 1 > two SKUs out by the same amount in week 4

A carton labelled as one shade of a foundation contains a mix of two shades. If goods-in scans only the outer label, every unit is booked to the first SKU.

‍

Week 1: The first wrong-shade orders go out. Customers notice before you do, and returns start arriving with "wrong item received" as the reason.

‍

Week 4: Two SKUs are out by mirror-image amounts. One is overstated and sells out early, the other shows stock that physically belongs to its neighbour. By the time a count reveals it, refunds and replacements are already paid.

‍

What stops it: Opening and scanning samples at unit level, not only at carton level, for multi-variant products. Imagery captured by Cubiscan at goods-in, surfaced at pack benches and on scanning devices, gives packers a visual check against what the product should look like.

Barcode mismatch > units booked to the wrong SKU in week 1 > phantom stock and missing stock by week 4

A product arrives with a new barcode after a packaging refresh, or a supplier uses a retailer's code instead of the brand's own GTIN. Goods-in books it to the wrong SKU or forces it through.

‍

Week 1: The SKU with the correct barcode looks fully stocked while the new stock sits unrecognised or attached to the wrong product record.

‍

Week 4: You have phantom stock on one line and stock that cannot be sold on another.

‍

What stops it: No manual overrides at receipt. New or changed barcodes should be set up before the delivery arrives, and unrecognised codes go to an exception area, not into stock. GS1 UK explains how pallet SSCCs scanned at receipt can be matched to information sent in advance.

Wrong batch or expiry captured > FEFO picks the wrong stock in week 1 > short-dated or blocked stock in week 4

For supplements, skincare and other dated products, batch and expiry are part of the stock record. If goods-in keys the wrong date or merges two batches, the system rotates stock on false information.

‍

Week 1: FEFO sends pickers to the batch it thinks expires first, which may actually be the newest stock.

‍

Week 4: The truly short-dated stock is found too late to sell through a promotion or a discount channel. If a retailer or marketplace has a minimum shelf-life rule, those units may be rejected. In a recall, a wrong batch record means you cannot say which customers received affected units.

‍

What stops it: Scanning or capturing batch and expiry at receipt as mandatory fields, checking them against pre-advice, and segregating mixed-batch deliveries. Automatic FEFO only works if the data entering it at goods-in is correct.

Putaway to the wrong location > stock "missing" in week 1 > write-offs and found stock in week 4

Putaway errors happen after a correct receipt. The units are counted correctly, then placed in a location other than the one the system recorded.

‍

Week 1: Pickers go to the system location and find nothing. The stock is marked as missing or adjusted out, and the SKU may be flagged as out of stock on your channels while units sit a few bays away.

‍

Week 4: A cycle count or a picker finds the stock in the wrong place. If it was adjusted out, you now have a write-off and a found-stock adjustment that cancel each other on paper but cost you sales in between.

‍

What stops it: Scan-to-confirm putaway, where the operative scans both the stock and the destination location before the move completes.

Unadvised delivery > stock in limbo in week 1 > duplicate receipts or lost stock by week 4

A pallet arrives with no ASN, or with a purchase order number the warehouse has not seen. It cannot be matched to expected stock.

‍

Week 1: The pallet waits in a holding area while someone chases paperwork. Your team believes the stock is in the warehouse, but it is not available to sell.

‍

Week 4: Either the stock was received in a hurry with guessed quantities, or the late ASN was received again later, creating a duplicate. Both leave a discrepancy with an incomplete paper trail.

‍

What stops it: Pre-booked dock slots tied to pre-advice, so the warehouse knows what is coming and when. Unadvised stock should be received into a quarantine status and reconciled with the brand before it becomes available.

Dock controls: which error each one stops

The most effective goods-in controls stop the error before the stock record is written. The list below matches each control to the error it prevents and the question to put to your 3PL.

‍

• ASN-driven receiving. Which error it stops: Unadvised deliveries, duplicate receipts. What to ask your 3PL: "Do you receive against pre-advice, and what happens to stock that arrives without it?".
• Pre-booked dock slots. Which error it stops: Unadvised deliveries, rushed receipts. What to ask your 3PL: "Do you book inbound slots, and how do you handle unplanned arrivals?".
• Pallet and carton level scanning. Which error it stops: Wrong carton quantity, barcode mismatch. What to ask your 3PL: "Do you scan every carton, or receive by label count?".
• QC sampling at unit level. Which error it stops: Mixed SKUs, wrong carton quantity. What to ask your 3PL: "When do you open cartons to check contents, and how many?".
• Mandatory batch and expiry capture. Which error it stops: Wrong batch or expiry. What to ask your 3PL: "Is batch and expiry captured at receipt and checked against the ASN?".
• Product weight, dimensions and imagery per SKU. Which error it stops: Mixed SKUs, wrong item at pack. What to ask your 3PL: "Do you capture product data at goods-in, and is it shown at pack?".
• Scan-to-confirm putaway. Which error it stops: Putaway errors. What to ask your 3PL: "Does putaway require a location scan before it completes?".
• Photographed, logged exceptions. Which error it stops: All of the above. What to ask your 3PL: "How quickly will I see a discrepancy, with evidence?".
• Inbound visibility against pre-advice. Which error it stops: Delayed discovery. What to ask your 3PL: "Can I see received versus advised for each delivery myself?".

‍

If the answer to any of these is "we check that later", the error is already in your stock.

How Fulfil with Synergy handles goods-in

Fulfil with Synergy treats goods-in as the first accuracy control in the building. Fulfil with Synergy is a founder-led UK 3PL and growth partner for ambitious, fast-growing consumer brands, running a technology-led fulfilment centre in Northampton for health, wellness, beauty, supplement and lifestyle brands across D2C, marketplace, retail and wholesale.

‍

The inbound process at the Northampton site works like this:

‍

• Pre-booked dock slots and ASN-driven receiving. Brands raise pre-advice through the 24/7 client portal, and deliveries are booked into dock slots so the team knows what is arriving.
• Pallet and carton level scanning. Each delivery is scanned and matched against the pre-advice in RedPrairie Dispatcher WMS, which tracks stock in real time down to unit, SKU, batch and location, with a time-stamped audit trail for every movement.
• Quality control sampling. Agree when cartons will be opened and sampled to check contents, condition and quantities against pre-advice.
• Cubiscan capture. Weight, dimensions and imagery are recorded for each SKU and surfaced at pack benches and on scanning devices, so packers see what the product should look like.
• Putaway to the right home. Stock is put away to the 57,000-tote AutoStore grid, pallet or shelf locations. AutoStore is a goods-to-person system with a pick accuracy of 99.99% at Fulfil with Synergy.
• Discrepancies handled in the open. Fulfil with Synergy's transition process flags, photographs and logs discrepancies for joint resolution. Agree how those checks and notifications apply to routine deliveries during onboarding.

‍

Brands see inbound activity against pre-advice in the client portal, including items receipted, exceptions flagged and putaway completion. That visibility is what turns a week four surprise into a day one conversation. For more on that, read what a fulfilment client portal should show you.

‍

Fulfil with Synergy also has a dedicated Inventory Manager, Anna Gawrys, and a named Client Manager on every account, so a goods-in exception goes to someone who knows your range. As Gary Rees puts it: "As a founder-led business, we make our decisions with the knowledge that every one of our clients also has a founder who loves their business as much as I do."

FAQ

What kind of goods-in error is hardest to spot?

Quantity errors are often the hardest, usually a carton holding fewer or more units than its label says, booked in at the label quantity. They hide well because the paperwork looks correct. Unit-level sampling and comparing carton weights against reference weights for each SKU help catch them. Barcode and SKU mismatches are another frequent trap, particularly after packaging changes or when a new supplier sends its first delivery before product data has been set up.

How long should goods-in take at a 3PL?

Goods-in time depends on delivery type, ASN quality and how many checks a product needs, so there is no single standard. A fully advised, single-SKU pallet is quicker than a mixed carton delivery with batch capture. Ask your 3PL for its receiving service level in writing, and what pauses the clock. An unadvised or mislabelled delivery will take longer because it has to be reconciled before stock goes live, which is the right trade-off: a day's delay costs less than a month of wrong stock.

Who pays for a stock discrepancy caused at goods-in?

Responsibility depends on where the error started and what your contract says. If the supplier packed short, the claim usually sits with the supplier, which is why photographed evidence at receipt matters. If the warehouse booked stock incorrectly, liability is set by your 3PL agreement, so check the stock loss clause and any agreed tolerance before you sign. Clear goods-in records, with photos and timestamps, make either route faster to resolve and stop the same argument repeating every month.

Can a good ASN prevent receiving errors on its own?

No. An accurate ASN tells the warehouse what to expect, but it does not prove what arrived. Suppliers make packing errors and pre-advice can be wrong, so the 3PL still has to scan and check physical stock against it. In a 10-month Auburn University RFID Lab study reported by Retail Dive, audits of ASNs against received goods using legacy barcode data recorded an order inaccuracy 69% of the time. The ASN's value is that it gives receiving something to compare against.

How do I know if my stock problems started at goods-in?

Look for patterns tied to deliveries rather than to sales. If short picks or count variances cluster on SKUs from one supplier, one inbound date or one recently changed product, receiving is a likely source. Ask your 3PL for the receipt record, photos and putaway history for the affected SKU. A WMS with a time-stamped audit trail lets you trace a variance back to the exact receipt and the operative who handled it, which shows whether the fix belongs with the supplier or the warehouse.

Goods-in errors cause stock discrepancies weeks later because the wrong record is written at receipt and only tested when stock is picked or counted. The fix is a goods-in process that checks physical stock against pre-advice, captures batch and product data, confirms every putaway and shows you exceptions on the day they happen. Fulfil with Synergy runs that process in Northampton with RedPrairie Dispatcher WMS, Cubiscan and AutoStore, and a team that resolves discrepancies with you rather than around you.

‍

If your stock keeps drifting and you suspect it starts at receipt, speak to the Fulfil with Synergy team about your goods-in process.

‍