Get Incoming Stock from the Loading Dock to Available for Sale
Connect shipment records, receiving appointments, stock checks and channel updates so incoming inventory becomes available without hiding shortages or held goods.
The Short Answer
Agree what must happen between delivery and stock becoming available for customer orders. Prepare accurate item mappings, packing quantities and shipment notices, confirm the destination appointment and track physical arrival separately from counting, inspection and release.
Keep missing, held and available quantities distinct, with an owner for each exception. Verify that approved inventory reaches the correct product and location in the sales channels, including safe handling of repeated updates. Measure the separate delays so supplier, warehouse and integration problems receive the right correction.
Key takeaways
- A delivered shipment is not necessarily inventory available for sale.
- Appointments and shipment notices must describe the actual movement and contents.
- Separate missing units from received stock that is held for a decision.
- Finish by verifying the correct available quantity in the customer-facing channel.
A carrier says the shipment was delivered. The supplier considers the job finished. The website still shows the product as unavailable, and the warehouse asks which purchase order the cartons belong to. Everyone can be telling the truth while the brand loses selling time.
Receiving is the work between physical arrival and usable inventory. It connects the supplier's shipment, the carrier's delivery, the warehouse's checks and the stock your sales channels can actually promise. Treating it as a tracking update leaves important decisions unowned.
I would manage the process around one question: what must be true before these particular units can fulfill a customer order? That question makes the preparation, appointment, count, inspection, storage and system update part of the same job. It also prevents a launch date from being built on the wrong milestone.
Agree on the finish line before booking the shipment
Define the states your team needs to distinguish. At a minimum, separate stock expected from the supplier, stock physically received, stock held for a decision and stock released for fulfillment. Use the warehouse's actual definitions, then map them to language the brand team understands.
A delivery receipt does not establish that every unit is present, correctly identified or suitable for sale. Similarly, a completed warehouse task may still need an inventory update to reach the website. Ask where each responsibility ends and who confirms the next handoff.
For a concrete provider example, ShipBob's receiving documentation distinguishes expected, received and stowed quantities in its Warehouse Receiving Order process. Those fields help explain why a shipment's announced quantity and the quantity added to inventory can differ. Your provider may use different names; verify its definitions rather than copying the labels into a report.
Agree on the receiving service, including what counts as a ready shipment, when the processing clock starts, what pauses it, which checks are included and what happens to exceptions. Get the applicable terms for your warehouse and shipment type. There is no useful universal promise that every delivery will become available within a particular number of hours.
Before committing a promotion, distinguish the expected arrival date from the expected availability date. Build the customer promise around the latter, with an explicit decision for delays. That may mean waiting to announce availability, reducing the promoted quantity or using a clearly explained preorder arrangement where the business supports one.
Give the warehouse a shipment it can recognize
Start with a shared product record. The supplier's description, your SKU and the warehouse's item identifier need to refer to the same physical variant. Color, size, bundle configuration and packaging changes are not minor details if they affect what a customer receives.
Confirm the counting unit. Ten cartons containing twelve individual items each are not ten sellable units. A retail multipack may be one sellable unit even though it contains several pieces. Write the conversion down and test it with an actual packing example rather than assuming each system uses the same meaning of quantity.
Prepare a shipment record that the supplier, carrier and receiving team can connect to their own records:
| Information | Question it should answer |
|---|---|
| Shipment and purchase-order references | Which movement and purchase does this delivery belong to? |
| Destination and warehouse reference | Which exact facility has agreed to receive it? |
| Item and variant mapping | What physical product should each line represent? |
| Quantities and counting units | How many cartons, packs and sellable units are expected? |
| Carton or pallet contents | Where should the team find each item? |
| Handling information | Which agreed checks or restrictions apply to these goods? |
| Carrier details and contact | Who can resolve a delivery change? |
For products that need lot, batch, expiry or other traceability, confirm those requirements before packing. Do not add an arbitrary date field and assume the warehouse knows whether it means manufacture or expiry. Agree on the meaning, format and treatment of mixed batches.
Use the warehouse's required labels and placement instructions. The purpose is reliable identification during its real receiving process, not merely producing a barcode that looks professional. Send a sample for approval when setting up a new arrangement, and check that the final printed version remains readable after packing.
Where partners use GS1 logistic labels, an SSCC identifies a logistic unit; it is not simply another product SKU. The GS1 Logistic Label Guideline also connects shipment notices with the contents actually staged or loaded. Follow the standard and partner requirements that apply to your arrangement rather than assuming every warehouse uses the same labeling system.
Make the appointment and the shipment notice agree
An estimated arrival date is a forecast. A confirmed receiving appointment is an arrangement with the destination. Sending a date in a spreadsheet does not establish that the warehouse has accepted that slot.
Check who books the appointment: the supplier, freight partner, carrier or your team. Give that person the correct facility instructions and references. Confirm the delivery format, such as parcels, pallets or a floor-loaded container, because the labor and equipment requirements can differ.
Keep the confirmation with the shipment record. Include the local timezone, delivery window, arrival instructions and contact for changes. Ensure the driver or delivery partner receives the relevant information rather than leaving it in an email only the brand can access.
Prepare the advance shipment notice using the actual dispatch details. An advance shipment notice is simply the information sent ahead so the warehouse knows what to expect. Your partner may call it something else or collect it through a portal. The important point is that the notice describes what was sent, not what the supplier originally hoped to send.
If quantities, carton contents, arrival timing or the destination change, update the affected parties through the agreed process. Keep a revision trail so the receiver can identify the current instruction. Avoid creating a second unrelated inbound record for the same physical goods just because the first record needs correcting.
For a split shipment, identify which portion is on each movement and what remains outstanding. A truck arriving with part of the order should not cause the entire purchase order to appear complete. Connect the physical shipment to the remaining balance without losing the original purchasing commitment.
Keep arrival, counting and release as separate checks
At arrival, capture the evidence relevant to the receiving agreement: which delivery arrived, when, and whether there were visible discrepancies. Follow the agreed process for photographs, packaging damage and carrier documentation. This is an operational record, not a conclusion about who is financially responsible.
Next, identify and count the items according to the agreed receiving service. Record discrepancies against the expected lines using the same units. If the count is uncertain, request the appropriate recount instead of changing the expected quantity simply to make the screen balance.
Keep held goods separate from available inventory, both in the physical workflow and the system. A unit awaiting a product decision should not accidentally become available because the warehouse recorded that it exists. The location and status should tell the next person what they may do with it.
Decide how the unaffected stock can proceed. One damaged carton should not necessarily stop every good unit in a shipment, but partial release must be supported by the warehouse process and the brand's requirements. Ask for the specific lines and quantities that can move forward rather than demanding an all-or-nothing status.
Assign someone on the brand side who can answer exceptions promptly. That person needs access to the approved product information and authority for the relevant decisions, or a clear route to obtain them. A warehouse cannot resolve an unidentified product change by knowing your launch deadline.
Reconcile the quantities without hiding the problem
Consider this fictional shipment. The supplier notice lists 1,000 individual units. The warehouse counts 960. Of those, 20 are damaged and held; the other 940 pass the agreed checks and are put away for fulfillment. Assume there are no earlier reservations or other restrictions in this example.
| Quantity | Meaning |
|---|---|
| 1,000 expected | What the shipment record said should arrive |
| 960 physically received | What the warehouse counted |
| 20 held | Received units not released for sale |
| 940 released | Received units eligible for fulfillment in this example |
| 40 not received | Difference between expected and physically received |
The brand is 60 units below the expected sellable quantity, but that is not a single 60-unit shortage. Forty were not received and twenty are physically present but held. Combining those into one adjustment makes the next action harder to understand and can lead to counting the same loss twice.
Investigate the 40 against dispatch evidence, packing records and any remaining shipment. They may be a true shortage, a partial delivery, an incorrect expected quantity or a counting issue. Keep the state unresolved until the evidence supports a conclusion.
For the held 20, record the reason, location, decision owner and next action. Release, rework, return or disposal each needs the appropriate approval and system treatment. A decision to pursue a supplier claim does not itself make damaged stock sellable.
Close each discrepancy with the supporting evidence and the inventory consequence. Keep physical quantities separate from compensation or credits. Money recovered later does not mean the missing goods arrived, and replacement goods should enter through their own identifiable receipt.
Confirm that available inventory reaches the sales channels
Choose the authoritative inventory source and describe how its states become quantities in each sales channel. Make the distinction between received, available and reserved stock explicit. Otherwise a well-run physical process can still create an overselling problem through the integration.
Trace a completed receipt from the warehouse record to the connected system and the customer-facing product. Check the correct variant and location, not just the product's headline total. A quantity sent to an inactive location or mapped to the wrong size has not completed the business task.
Test repeated and delayed updates. If a receiving message is retried, the integration should recognize that receipt or update rather than add the same stock again. If updates arrive out of order, the chosen design should prevent an older state from replacing the accepted current one. Have the integration owner demonstrate the behavior with controlled test data.
Keep failures visible with an owner and a recovery action. “The webhook was delivered” is not proof that the inventory was accepted by the destination. Conversely, a failed acknowledgment is not always proof that nothing changed. Inspect the destination before replaying an adjustment.
Use a small controlled receipt to verify the complete route when adding a warehouse or changing the connection. Include one normal line and one exception if the testing arrangement allows it. The website release-checking guide provides a connected approach to verifying customer journeys after a system change.
Measure the delay you can actually improve
Track separate intervals: dispatch to arrival, arrival to receiving work, receiving work to release, and release to the sales-channel update. Those timestamps show where stock is waiting. A single average from supplier departure to website availability mixes transportation, warehouse operations and integration delays into one number.
Use the definitions agreed with the provider when evaluating its service. If the contracted processing period starts only after correct documentation is present, show the earlier documentation delay separately. Hiding it would make the warehouse look faster without improving the customer's outcome.
Review incomplete receipts as well as completed ones. An average calculated only from finished shipments can look good while one important delivery remains unresolved. Show the age, affected quantity and next action for outstanding stock that matters to current demand.
Connect the findings to a practical change. Repeated label problems may need supplier training and a sample check before dispatch. Long waits for brand decisions may need a backup approver. A channel-update delay may require integration work rather than a different warehouse.
Ask for the applicable receiving and exception charges before choosing a corrective process. Relabeling, extra handling, missed appointments or storage arrangements can affect the economics where the agreement provides for them. Compare the actual quoted or billed work; do not assume every provider charges the same fee.
The inventory planning guide helps connect these observations to replenishment decisions. Use your observed availability lead time rather than treating the carrier's delivery estimate as the entire restocking period.
Give the next shipment a clear owner from start to finish
For the next inbound movement, choose one brand owner who can see the shipment record, appointment, exceptions and final inventory confirmation. Other people still perform their specialist work; the owner ensures that nothing falls between their responsibilities.
Before dispatch, confirm the product mapping and actual contents. Before arrival, confirm the appointment and current notice. After arrival, review missing or held quantities. Before promoting newly available stock, verify the relevant channel's accepted inventory state and the customer promise.
After the receipt is closed, review the important delay or discrepancy with the party able to prevent it. Change a specific instruction or check, then see whether the next shipment improves. A longer checklist is not progress if nobody uses it or understands which failure it prevents.
My recommendation is to make “available for the intended customer order” the operational finish line, while retaining every earlier state. That lets you distinguish a late truck, an unclear shipment, a genuine stock problem and a broken update. You can then solve the right problem without asking the warehouse or the website to hide it.
Questions about inbound stock and receiving
Does a carrier's delivered status mean we can sell the stock?
No. Physical delivery is one milestone. The warehouse may still need to identify, count, inspect and put away the goods, and the inventory update must reach the relevant sales channel. Confirm the applicable available quantity before changing the customer promise.
Should we change the expected quantity to match a short receipt?
Do not overwrite the original expectation just to remove a difference. Keep the expected and actual quantities, investigate the reason and record an approved correction or remaining shipment when supported. The history should explain what changed and what still needs action.
Can we release good units while damaged units are held?
Often the process can be designed to separate them, but confirm that your warehouse, product requirements and integration support partial release. Identify the exact quantities and statuses. Never assume a whole shipment is available merely because some units have passed the checks.
Explore the warehousing guides for decisions about fulfillment partners, warehouse locations and the wider operation that receiving supports.
Sources
Still have a question?Ask the DTCUP Community ↗


Leave a Reply
You must be logged in to post a comment.