Warehouse Operations Guide

Warehouse Receiving Process: A Practical SOP for Small US 3PLs

A warehouse receiving process identifies the owner, reconciles SKU and quantity, completes inspection, records location, and verifies which units can enter picking. Track the delivery scan, warehouse custody, verification, putaway, and release separately. Status names vary by warehouse management system (WMS).

Picture 20 cartons at the door and orders due to ship this afternoon. The receiver has signed for the cartons, but no one has matched them to the client’s inbound reference. Or the count is finished and the stock is still at the receiving bench. Ask which checkpoint has evidence and who owns the next one. The delivered parcel investigation guide covers the separate situation where staff cannot locate a carton at all.

Use this suggested SOP for ordinary US ecommerce replenishment arriving in parcels or cases. Agree with each client on checks, hold authority, and release rules before the shipment leaves. Returns inspection, hazardous storage, refrigerated goods, customs, powered equipment, and automated facilities require their own procedures. In a small team the same employee can cover several roles, but keep the receiver, reviewer, and release authority visible in the record.

For consumer returns arriving at the facility, use the warehouse returns processing SOP to inspect each unit, track holds and verify authorized stock actions.

Illustrated small warehouse receiving bench with numbered cartons, a scanner, a count sheet, storage bins and a separate shelf for a dented carton.
Warehouse receiving bench illustration with fictional carton numbers.

1. Get a usable inbound notice before arrival

Start with the customer account and destination facility. The warehouse coordinator assigns or validates a unique inbound reference for the shipment, then links it to the purchase order (PO), advance ship notice (ASN), or receiving order required by that warehouse. A PO describes the purchase. An ASN describes the planned shipment. ShipBob uses a warehouse receiving order (WRO) to manage its own inbound workflow. Keep carrier delivery proof and the warehouse’s count record alongside these documents with their own identifiers. ShipBob receiving documentation

Ask the brand for the estimated arrival and time zone, facility or door, shipper or driver contact, and a decision contact at the brand. Require the expected carton count and a unique identifier for each carton. For mixed cartons, request contents per carton, including SKU, variant, color, size, quantity and unit of measure. If the master carton contains inner packs, record both levels and the conversion to the inventory unit. Retain the version of the carton plan that the counter used.

Collect the mapping from each scanned code to the client, product, and packaging level. Record lot, serial, or expiry data when the product or client requires it. Agree on which seals may be opened, what qualifies as damage, when sampling is allowed, and who can authorize a relabel or overage. A packing slip helps explain the sender’s intended contents. The receiver still needs a record of the observed contents and the method used to check them.

Compare ordered, dispatched, in transit, and expected on this delivery as separate quantities. If the supplier revised the shipment after printing the first notice, ask for a new version with a change reason. Keep the old version and record which one is approved for receiving. An email promising to send the balance next week can explain a difference, but the warehouse should keep the balance open until the remaining boxes arrive or the client authorizes a different disposition.

Give the floor a versioned copy with the client, carton IDs, and quantity basis at the top. Keep the full notice for decisions. If a brand mixes cartons and eaches in one column, clarify the units before loading it into the queue. The approved copy preserves the expectation used at the bench.

When the notice is complete, reserve space, confirm the window, and make the owner’s mappings available at the station. When part is missing, request the exact field ahead of delivery and decide what staff may still do, such as record custody while holding unverified contents. When ownership cannot be established, escalate before arrival. Follow the facility’s intake agreement on acceptance. If the warehouse takes custody, assign a temporary intake ID and a hold location, with client inventory posting blocked until identification.

2. Take custody and count against the right record

The dock receiver first checks the facility, receiving area, and inbound reference. Compare the cartons handed over with the expected identifiers and carton count. Record the time, count observed at handoff, visible crushing, wet marks or disturbed seals, and any tracking or handoff reference. Attach photos of the affected carton and label when allowed. If a carrier signature is requested before opening, keep the scope of the handoff record clear and follow local acceptance instructions for discrepancies.

Assign the shipment a staging position that staff can find by its ID. Mark a mixed or unidentified carton separately, and keep each owner’s shipment and counted work apart from the next. The counter opens one receiving record at a time and moves each finished carton to a marked position or applies a counted tag. If interrupted, record the last finished carton and what remains open. This makes the restart point visible to the next shift.

Before recording units, match the product and variant to the approved client mapping. Compare the actual color, model, size or kit contents with the line description. A scanner can decode a valid code while selecting the wrong packaging level or client. Resolve the match in the owner’s account, and document conflicting or unreadable labels before replacing them. An inbound carton label identifies the box, a product barcode identifies an item or pack, a location label identifies the bin, and the outbound shipping label identifies the transport package.

Choose the counting method by risk and the client agreement. Count individual inventory units for loose goods, mixed cartons, unfamiliar case configurations, or suspect seals. For verified uniform cases, count intact cases and apply the approved conversion if the agreed process allows it. Use sampling only against an agreed sample scope and escalation rule. If a sample fails, hold the affected scope and expand inspection as agreed. Record which cases were opened, what was observed, and which quantities were inferred by conversion or sampling.

For mixed cartons, record each SKU and relevant lot, then reconcile back to the carton. For sealed cases, distinguish a contents check from a conversion using the approved case specification. That detail lets the lead trace a mismatch to a count or a pack assumption.

Record the physical count separately from the inspection result. A damaged unit may still be physically present. Verify the checks specified for the line, such as packaging condition, variant, lot, expiry, or serial. Save the inspection evidence against its carton and quantity. ShipHero documents receiving expected quantities and recording rejected units within its PO workflow. Use any expected-quantity shortcut only after verification under your own SOP. ShipHero PO receiving help

Label inbound measurements as bare unit, retail pack, or case. A replenishment case can contain several sale units. At packout, measure the actual sealed parcel for the outbound quote and label.

When two people count the same inbound, divide the work by carton and record each assignment before opening boxes. The lead reconciles the two worksheets by carton ID. If assignments overlap, check the physical stock and transaction history before merging the records.

The receiver tags accepted units and held units separately, then hands the count record and open discrepancies to the lead. The lead compares original quantities, units of measure, carton IDs, checks, and posting history before approving putaway. If a double scan is suspected, stop posting and compare the event history with the physical carton and count worksheet. Use one numbered, versioned record per receipt. Notes on paper can support it once attached and attributed to the shift that made them.

Match the owner and receipt, then count and inspect. Route unresolved identity, quantity, damage or label issues to a hold record. Recheck after resolution, then put away and verify picking.
Suggested workflow. Record a shortage on the log and hold any affected physical stock separately.

3. Resolve exceptions at the affected line or carton

Record exceptions while the carton and its evidence are still together. Open a discrepancy ID for the affected owner, receipt, carton, and line. Write what was expected, what staff observed, the unit of measure, which pieces are present, and where they are. Give each open record a decision owner and a next update time. If an issue affects the whole box, state that scope so another shift does not accidentally pick from it.

IssueImmediate actionHold or stagingEvidenceDecision ownerRelease condition
ShortRecount lineLog missing balanceCount and carton IDsLead and brandVerify present stock, resolve balance separately
OverSeparate excessMarked overage toteRecount and carton listBrand and leadWritten acceptance and approved posting
Wrong variantCheck actual SKUHold affected unitsItem photos and mappingClient catalog ownerCorrect match and inspection
Code conflictRetain original labelHold affected scopeCode, item, ownerCatalog owner and leadApproved mapping or relabel
DamageDocument and separateDamage binPhotos, quantity, check resultAuthorized disposition ownerInspection and approval, or other disposition
Owner unknownAssign intake IDUnidentified areaBox ID and dispatch recordCoordinator and shipperConfirm owner and receipt
Split arrivalIdentify arrived cartonsStage only arrived boxesArrival IDs and balanceCoordinator and leadApprove received portion under partial receipt rules
Duplicate entryPause and audit postingHold affected balance from picksEvent history and countInventory leadAuthorized correction and recheck

Use hold controls that the picker actually encounters. In a small spreadsheet operation, move the goods to a marked bin and exclude those rows from the pick sheet. In a WMS, verify the hold and location behavior through the order workflow, including an already generated pick task if one exists. For a shortage, leave an open quantity or discrepancy record. With no unit present, there is no physical hold location to assign.

Separate immediate containment from the later commercial decision. The dock team can identify and protect questionable goods. The client may need to decide whether to keep extra units, approve a new label, request return, or authorize disposal. Keep the disposition linked to the stock movement and capture the quantity remaining on hold afterward. When part of a held group is cleared, split the record by disposition and move only the authorized units.

In this teaching example, the expected receipt is 100 units of SKU A, 60 of B, and 40 of C. The counter finds 96 of A, including 6 damaged, 60 of B, including 10 with labels to verify, and 44 of C, including 4 overage units awaiting approval. The lead can approve 90 of A, 50 of B, and 40 of C for the release path if the agreed inspections pass. The damaged, label review, and overage quantities stay in their documented locations.

SKUExpected unitsPhysical countCleared unitsHeld on siteOpen difference
A100969064 short, 6 damaged
B6060501010 labels pending
C40444044 extra pending
Total200200180204 missing, log only
Teaching example. SKU A 100 expected, 96 counted, 90 cleared and 6 held. B 60, 60, 50 and 10. C 40, 44, 40 and 4. Totals 200, 200, 180 and 20. Record the 4 missing A units separately from held stock.
Fictional unit counts. The A shortage and C overage remain separate even though the totals match.

The physical count is 200 and the expectation is also 200. Compare by line before checking the total. Four fewer A units and four more C units are separate differences, even if their costs are similar. The missing A units are absent from the premises. The 20 held units are the 6 damaged A units, the 10 B units with label questions, and the 4 extra C units. Record separate positions or clearly identified containers so the lead can check each group.

The model counts physical units and their disposition. Your system may account for damaged or unknown stock in a separate record and reserve different meanings for received quantity. ShipBob’s WRO integration documentation distinguishes expected, received, and stowed quantities. It also documents an automatic close path where some unarrived boxes are cancelled and the WRO becomes Completed. Reconcile the line and box detail before interpreting that status as the entire original shipment being present. ShipBob receiving documentation

For a hold spanning more than one shift, check that the physical quantity and location still match the log. If the goods must move, post the move with the hold intact. The next owner should find the goods without depending on the receiver’s memory.

The 180 cleared units are candidates for putaway and release. Sales-channel availability also depends on the approved destination, existing allocations, holds, and integration rules. Ask the client for a decision on the excess before updating the original forecast or returning anything. Keep any approval, revised quantity, move, and downstream correction tied to the discrepancy ID. Report the observed difference to the client while the cause is still being investigated.

4. Record putaway and verify the conditions for picking

Give each work area a distinct function. Receiving staging is where the warehouse can locate goods awaiting a count. The exception area keeps unresolved stock identifiable and out of routine picks. Storage holds verified stock, including reserve inventory awaiting replenishment. Pick locations are the bins your process can route a picker to. A small site can use marked shelves and totes for these functions. Keep each owner’s positions distinct or explicitly record owner and quantity within the facility’s approved storage setup.

The putaway associate takes the approved list and confirms the source label before moving anything. Record owner, SKU, quantity, applicable lot, source, destination, employee, and time. If the destination is full or belongs to another client, stop that move and ask the lead for a permitted alternative. If stock is split across locations, write a move per destination and check that the totals match. Extensiv Warehouse Manager describes receiving into a dock bin followed by a move to a shelf location as one workflow. Extensiv receiving overview

Work areas connect staging, counting, verified storage and pick bins. Client X and Y have separate IDs. The exception area holds affected stock for recheck before it moves onward.
Example of functional relationships for a small warehouse. Building, fire protection and equipment layout require site-specific plans.

Ask what your system means by on hand, sellable, allocated, and pickable. On hand is a stock balance under the system’s rules. Sellable affects what may be offered to buyers. Allocated usually denotes a reservation to demand. Pickable indicates whether warehouse operations can direct a pick for those units. ShipHero documents a sellable, non-pickable location setting under which inventory can affect channel availability and allocate to an order while pickers are still blocked from that location. Check the settings in use before relying on this behavior. ShipHero receiving location help

Test a new staging or hold location before using it for live receipts. Check whether posting to it changes the channel quantity, reserves stock against open orders, or sends a task to a picker. Repeat after moving a small test quantity to the destination. Record who can change the location settings and have the lead review existing open orders if the settings change. The same checks apply when an approved emergency location is used.

Have the lead compare the physical bin, move record, and resulting eligibility. Then check every line of the order that needs the replenishment, including existing allocations and holds. An urgent order can justify prioritizing the count and putaway, or using an approved temporary pick location after checks. Record the move and release before directing the picker there. For an authorized correction, preserve the original quantity, corrected value, reason, approval, and any effects on picks or published inventory.

For dated goods, preserve the original lot, date type and receipt time for the outbound decision. See the FIFO and FEFO allocation guide.

5. Work through four teaching cases

Case 1. Matching totals conceal a line shortage

The 200-unit example comes in under one client and the count method is agreed. The lead sees the receipt total match, then reconciles by SKU and identifies the A shortage alongside the C overage. They ask the counter to verify those lines against the carton worksheet and set aside the affected pieces. They separate the B label review from the quantity comparison because B has the expected count.

The lead records the held quantities and locations, plus a shortage record with no physical position. The brand’s contact gets the carton evidence and next update time. The approved quantities can go through putaway without waiting for an unrelated label decision if the client permits a split release. The shift handoff states which lines are cleared and which issues still require decisions. Closing the cleared moves does not close the shortage or establish who caused it.

Case 2. Verified case packs can be converted

A replenishment arrives as 12 sealed cases of one SKU. The client’s approved pack specification and carton labels state 24 units per case. The receiver confirms the owner and variant, checks each case identifier and seal, and performs any agreed verification of the contents. If all conditions for case counting pass, 12 cases × 24 units per case = 288 units. The dock count of 12 and the inventory receipt of 288 can both be correct because their units differ.

The record includes the case count, conversion, specification version, inspections performed, and operator. The lead checks that the posting uses the base inventory unit once. If a changed supplier pack, loose pieces, or inconsistent markings make the conversion uncertain, hold the affected cases and verify the pack or count individually. After confirmation, move the approved stock to the recorded location and verify its status. Keep the carton and unit records linked to avoid interpreting the next scan as another 288 units.

Case 3. Receive the first delivery and keep the balance open

Eight cartons of one SKU are expected, and six arrive. Each arrived carton is verified to contain 20 units. The intake record identifies the six cartons physically present and the two still expected. The current receipt is 120 units and the pending balance is 40 units under the forecast. Ask the shipper for tracking or dispatch evidence for the other cartons. Until the evidence supports a conclusion, describe them as not yet received.

If the workflow supports partial receipts, post the verified 120 and check whether the brand’s inspection and putaway rules permit release. If the platform requires a separate child receipt or prevents partial release, follow that workflow while retaining the six-carton evidence. When the two later cartons arrive, verify their carton IDs and contents and post only the new receipt. In this example they add 40 verified units, bringing cumulative receipts to 160. Compare prior transactions before retrying a posting after a connection failure.

Case 4. A product scan cannot assign the owner

Two clients carry the same item. A box has a readable item code but no reliable client identifier. The counter can record the package condition, observed code, provisional count if opening is permitted, and temporary location. They cannot resolve the client from the first matching product in the WMS. The lead assigns a temporary intake ID and holds the box outside each client’s sellable balance.

Ask the shipper or designated brand contacts for a carton-level match to a shipment reference and account. Verify evidence such as the box identifier, dispatch list, and tracking reference against the warehouse’s original intake record. Restrict client-facing evidence to what each client may see. Once ownership and the inbound reference are confirmed, match the SKU under that account and complete verification before posting and putaway. If the evidence remains ambiguous, leave the hold assigned for follow-up. Each client’s inventory stays separate throughout.

6. Measure both elapsed time and the cost of work

Decide what starts the clock and keep the timestamp. For an internal receiving metric, physical check-in at the intended site is one useful start. Measure time to first usable stock from that event to the first verified release. Measure time to full processing separately, with an explicit definition covering the last required move and reconciliation or an authorized disposition for remaining issues. When shipments arrive in waves, state whether the clock is per arrival or across the whole inbound. Report open receipts with their current age.

Define dock-to-stock in your own reporting dictionary. If you end the clock at putaway, keep release delay as a separate interval. State local time zone and whether a report uses elapsed or staffed hours. Track exception age from the discrepancy’s opening to decision or approved disposition, and keep the age of unresolved items visible. For line discrepancy rate, divide the number of checked receiving lines with at least one issue by the number of checked lines. If one line is damaged and short, count it once for that metric and tag both causes for review.

Review the intervals alongside the receipts that generated them. A quick first release can coexist with a long wait for the last damaged carton to be resolved. If counting finished early but putaway waited for a free bin, a count target alone misses the bottleneck. If most held units are waiting for client responses, record that waiting stage so the warehouse can discuss approval coverage with the client without treating it as time worked.

For a teaching calculation, assume 100 person-minutes of ordinary receiving, counting, recording and putaway, plus 45 person-minutes of exception work. At an assumed $24 per person-hour, the base cost is 100 ÷ 60 × $24 = $40. Exception labor is 45 ÷ 60 × $24 = $18, giving $58 total. Person-minutes add time worked by all employees. If two people work concurrently, their combined effort can exceed the minutes on the clock.

Using the example’s 200 physical units gives $58 ÷ 200 = $0.29 per physical unit received. Dividing by the 180 approved for release gives approximately $0.32 per approved unit. The first denominator measures handling across all units present. The second shows the labor associated with making units available for the next step. For comparisons, use the same cutoff and define release consistently. The example uses assumed labor only. A client’s receiving quote may also include space, equipment, software, supplies, overhead, and margin under the service agreement.

7. Run the shift with a checklist and one discrepancy log

Have the lead close each checkpoint against evidence. The next shift needs the carton location, pending decision, and posting status. Preserve the original expectation and actual count when revising a notice.

PhaseCheck and actionRecordRole
Before arrivalMatch client, reference, carton plan and unitApproved notice versionCoordinator
CustodyCheck facility, carton IDs and visible conditionIntake log, time, photosReceiver
CountVerify mapping and quantity basis, separate holdsCount sheet, inspection and discrepancy IDCounter
PutawayConfirm source, destination, move and eligibilityApproved move and release recordPutaway associate and lead
CloseReconcile posted quantities and assign remaining issuesReceipt reconciliation and open logInventory lead

Record the unit and separate held stock from shortages. Link evidence and assign a decision owner and update time.

Field groupRecord fields
IdentityDiscrepancy ID, client, receipt, carton, SKU and unit
ObservationExpected, actual, issue type, held, missing, physical location and evidence
ResolutionOwner, decision, authorization, update time and next check

Fill in the receipt IDs and update times with a time zone. Say whether stock passed inspection, was put away, or is ready to pick.

Confirm a quantity difference

For receipt [ID], we counted [actual] [unit] of [SKU] in [cartons] against [expected]. Please confirm the carton contents and any later shipment by [time and zone]. We will update you at [time and zone].

Confirm a partial release

We put away and cleared [quantity and SKU] for picking on [receipt]. [Held quantity and SKU] remain on hold for [issue]. Please have [contact] confirm [decision]. Our next update is [time and zone].

Request identity or mapping

We logged [carton] under [intake ID] and are holding it. Please send the client ID, inbound reference and approved SKU or pack mapping for [code] by [time and zone]. We will follow up at [time and zone].

At closing, reconcile the arrival record, count, all moves, and each unresolved line. Use the same local cutoff for receiving and stock reports. If the platform can close a transaction while an exception stays open elsewhere, link the open record and confirm its owner and next action before closure. On the next shift, reconcile any late arrivals or delayed postings back to the earlier carton IDs before opening a new task.

Give the next shift a list of cartons still expected, stock held on site, and moves still awaiting confirmation. These queues have different owners. A single status column that says pending gives the next shift too little information to act.

A controlled workbook can work at low volume if there is one authoritative file, restricted posting and adjustment permissions, and a documented reconciliation at shift end. Record approved corrections as transactions and keep a version history. Prevent simultaneous posting against the same carton. When multiple shifts, clients, lots, and cartons overlap, consider WMS support for owner-specific scanning, lot controls, location moves, allocation blocks, and a traceable correction history. Choose controls by the failure your records show.

8. Hand verified stock to outbound fulfillment

Ongoing checks after putaway need their own process. The 3PL cycle counting SOP defines owner and location scope, controls period movements, investigates differences and rechecks affected orders before release.

After the lead confirms identity, quantity, bin, and order readiness, send the approved work to picking. A small team can group orders with a batch picking workflow once the task list points to eligible stock. At the packing station, verify the order, seal the package, and measure its final weight and outside dimensions before comparing postage.

Use the 3PL shipping operations guide to assign the downstream handoffs for different clients. For enabled shipping channels, EasyShippingX supports rate comparison, shipping label creation and tracking, with Portal, bulk Excel order upload, and API options for shipment workflows. The receiving and inventory release decisions stay with your warehouse records and process. EasyShippingX features

Warehouse receiving FAQ

Use an approved alternative only if the warehouse accepts it. Link the verified client, receipt and cartons to that record. If those details are missing, document custody under a temporary ID while the coordinator confirms them.

Block affected picks, check downstream reservations, and request a traceable correction. Include the prior value, recount, approved change and effects on availability.

Compare location eligibility, reservations, the outbound inventory feed and the store’s mapped SKU and location. Identify where the quantity stopped before sending another update.

Expedite verification and record the approved location and release first. A quick review still needs to match the physical goods to the client, receipt and order.

Sources and methodology

Sources reviewed November 6, 2026. The SOP is a suggested workflow. Platform examples describe the cited product. The cases and labor calculation use fictional inputs.