Receiving, Inspection, Put-Away, and Replenishment

Introduction

Inbound warehouse operations convert an expected supply into inventory that is physically available, correctly identified, quality-approved, and positioned for subsequent storage or order fulfillment. Receiving is therefore not merely an unloading activity. It is a control point at which the warehouse confirms what has arrived, determines whether it is acceptable, records ownership and condition, and directs material into storage, cross-docking, quarantine, or another disposition.

Poor inbound design creates errors that propagate through the supply chain. An inaccurate receipt can produce false inventory availability; an undetected quality defect can reach a customer; weak labeling can make stock unlocatable; and poorly directed put-away can increase travel, congestion, replenishment frequency, and picking time. Conversely, a well-designed inbound process improves inventory accuracy, throughput, traceability, space utilization, and service reliability.

At graduate level, inbound operations should be understood as an integrated socio-technical system. Physical flows, information flows, labor, equipment, supplier behavior, warehouse-management-system (WMS) logic, quality rules, and capacity constraints must be designed together.

Learning Objectives

After completing this chapter, the reader should be able to:

1. Design an inbound appointment and dock-scheduling process.
2. Explain unloading, verification, inspection, labeling, quarantine, and release decisions.
3. Apply directed put-away using product, location, equipment, and service constraints.
4. Distinguish conventional receiving from cross-docking and flow-through operations.
5. Design replenishment triggers and coordinate reserve and forward-pick locations.
6. Develop exception-management controls for shortages, overages, damage, and documentation discrepancies.
7. Evaluate inbound performance using operational, quality, inventory, and safety metrics.
8. Assess the managerial, technological, ethical, and governance implications of inbound design.

1. The Inbound Operating Model

A typical inbound process consists of the following linked stages:

appointment → gate check-in → dock assignment → unloading → count and identification → inspection → labeling and system receipt → disposition → put-away or cross-dock → replenishment of downstream locations

These stages are not necessarily sequential in every facility. For example, a known, approved supplier may use advance shipping notices (ASNs) and receive through scan-based verification, while damaged goods may move directly from unloading to quarantine. The design question is not simply “What is the standard sequence?” but “What control is required at each decision point, and where should that control occur?”

The process should establish a clear inventory status model. Common statuses include:

A central principle is status integrity: the WMS should not represent material as available merely because a truck arrived. Availability requires a defined confirmation event, such as quantity verification and quality release.

2. Inbound Appointment and Dock Scheduling

2.1 Purpose of appointments

Appointments smooth the arrival profile, align labor and equipment with expected work, reduce driver waiting, and prevent simultaneous demand for limited doors. An appointment record should normally include supplier, carrier, purchase order, ASN, estimated arrival time, vehicle type, pallet or carton count, weight and cube, hazardous-material information, temperature requirements, special handling needs, and expected unloading duration.

Appointments also support pre-receiving. The warehouse can create expected receipt records, reserve staging space, prepare inspection resources, and identify materials requiring special authorization before the vehicle arrives.

2.2 Time-window design

A time window must balance carrier flexibility with operational control. Very narrow windows may create rescheduling and noncompliance; very broad windows may produce peaks. A practical schedule uses receiving capacity by period rather than assigning appointments without regard to labor or door constraints.

If the expected unloading workload in a period is measured in labor-hours, the basic capacity condition is:

Here, t_i is the labor time required for inbound load i, in labor-hours, and H_available is the labor capacity available during the period. The condition assumes that all work is expressed in comparable labor-hours. It is only a first screen: door availability, equipment, staging space, skill mix, breaks, and variability may impose tighter constraints.

A utilization measure is:

where ρ is planned capacity utilization. As ρ approaches 1, even modest variability can cause queues. A schedule that targets 100 percent utilization is therefore operationally fragile. The appropriate target depends on variability, service commitments, labor flexibility, and the cost of delay.

2.3 Dock assignment

Dock assignment should consider:

• product compatibility and contamination risk;
• temperature-controlled or secure areas;
• vehicle dimensions and dock equipment;
• proximity to inspection, quarantine, or cross-dock staging;
• outbound synchronization;
• congestion and pedestrian safety;
• workload balance across doors.

A door is not simply a location. It is a work system with a service rate, equipment requirements, safety zone, and downstream path. Assigning a load to the nearest available door can be inferior to assigning it to the door that minimizes total handling and congestion.

2.4 Appointment governance

Supplier scorecards should distinguish supplier-controlled delay from warehouse-controlled delay and carrier-controlled delay. Useful measures include on-time arrival, appointment compliance, ASN accuracy, loading quality, damage rate, paperwork completeness, and average unloading time. Penalties should not encourage unsafe unloading or concealment of defects. Governance should combine incentives, corrective action, and collaborative root-cause analysis.

3. Unloading and Receiving Verification

3.1 Safe unloading

Unloading begins with vehicle immobilization, dock-plate or ramp verification, inspection of the vehicle and seal, and confirmation of load condition. Procedures must address fall hazards, powered industrial trucks, unstable pallets, mixed-SKU loads, temperature excursions, and hazardous materials. Safety controls take precedence over throughput targets.

The receiver should record seal number where applicable, arrival time, vehicle condition, visible damage, temperature, and exceptions before material is moved extensively. Photographs and electronic records can strengthen evidence, particularly for claims.

3.2 Verification dimensions

Receiving verification normally covers four dimensions:

1. Identity: Is the item the expected SKU, lot, serial number, or configuration?
2. Quantity: Is the number of units, cases, pallets, or weight correct?
3. Condition: Is packaging and product condition acceptable?
4. Documentation: Do purchase order, ASN, certificates, labels, and regulatory documents agree?

The unit of account must be defined. Counting pallets when inventory is controlled in eaches creates avoidable errors unless pallet quantity and configuration are validated. For variable-weight products, the system should distinguish nominal quantity from actual measured quantity.

3.3 Tolerance and discrepancy policy

A receiving policy should specify when a discrepancy can be accepted, when a supervisor is required, and when the shipment must be held. Possible controls include quantity tolerances, approved substitutions, over-receipt authorization, short-shipment claims, and blind receiving.

Blind receiving hides expected quantities from the receiver, requiring an independent physical count. It can improve count discipline but may increase time and labor. It is most valuable for high-value, error-prone, or strategically important items rather than necessarily for every receipt.

The record should preserve both the expected quantity and the physically verified quantity. Overwriting the expected quantity destroys information needed for supplier performance analysis.

4. Inspection, Quality Release, and Exception Management

4.1 Risk-based inspection

Inspection intensity should reflect risk rather than treat every SKU identically. Risk factors include product criticality, regulatory requirements, supplier history, value, defect consequences, shelf life, counterfeit exposure, and damage susceptibility.

Possible inspection levels are:

• Identity and quantity check: appropriate for low-risk, stable suppliers.
• Packaging and visual inspection: checks damage, labeling, seals, and obvious defects.
• Sampling inspection: examines a defined sample using a documented acceptance rule.
• 100 percent inspection: appropriate where failure consequences are severe or traceability is essential.
• Specialist or laboratory inspection: required for technical, chemical, food, pharmaceutical, or safety-critical products.

Sampling is not equivalent to proving that every unit is defect-free. The acceptance plan must define the population, sample selection method, defect classification, acceptance criteria, and disposition of the uninspected units. Statistical sampling should be designed by competent quality personnel, especially where standards or regulations apply.

4.2 Quarantine and disposition

Quarantine must be physically and electronically distinct. A taped-off area without WMS status control is insufficient; a system hold without physical segregation is also unsafe. A controlled disposition may be:

• release as received;
• release after rework or relabeling;
• partial acceptance;
• return to supplier;
• scrap or destruction;
• concession or use-as-is approval;
• transfer to a specialist inspection process.

Authority for disposition should be defined. Receivers should not unilaterally release safety-critical or regulated material merely to relieve congestion.

4.3 Exception management

Exceptions should be coded, routed, aged, and closed. Typical codes include shortage, overage, wrong item, damage, undocumented item, expired product, temperature excursion, missing certificate, serial mismatch, and labeling failure.

An effective exception record identifies the event, time, location, affected quantity, responsible parties, containment action, evidence, decision owner, final disposition, and financial or service impact. Exception aging is important: unresolved holds consume space and create hidden inventory. Escalation thresholds should be based on time, value, customer impact, safety risk, and regulatory significance.

Root-cause analysis should distinguish isolated error from systemic error. For example, repeated shortages may result from supplier loading practices, unit-of-measure conversion, receiving-count methods, or master-data defects. Corrective actions should address the causal mechanism rather than merely adjust inventory.

5. Labeling, Identification, and Data Integrity

Labels connect physical material to digital records. A robust label identifies the item and, where relevant, lot, batch, serial number, quantity, unit of measure, manufacturing date, expiry date, country of origin, handling instructions, and destination. Barcode, two-dimensional code, or radio-frequency identification (RFID) may be used according to cost, read accuracy, environmental conditions, and interoperability.

A label is useful only if the master data behind it is correct. Common master-data failures include duplicate SKUs, inconsistent units of measure, incorrect case packs, missing dimensions, invalid shelf-life rules, and confusing supplier part numbers with internal item numbers.

The receiving process should validate the relationship among purchase order, item master, packaging hierarchy, and physical label. A case labeled “24 each” must not be received as one each or twenty-four cases because of an ungoverned unit conversion.

Traceability requires more than scanning. The system should preserve relationships among receipt, supplier, lot or serial number, storage location, inspection result, and subsequent issue or shipment. This is essential for recalls, warranty claims, regulated products, and forensic investigation.

6. Directed Put-Away

6.1 Concept

Directed put-away assigns material to a storage location using explicit rules rather than leaving the decision entirely to operator judgment. The objective may be to minimize travel, preserve product compatibility, maximize space utilization, protect inventory, support picking efficiency, or satisfy traceability and rotation requirements.

A put-away rule set commonly considers:

• item dimensions, weight, and handling unit;
• storage class and environmental requirement;
• velocity or demand frequency;
• lot, serial, expiry, and rotation policy;
• compatibility and segregation constraints;
• available capacity and location status;
• equipment and aisle restrictions;
• proximity to forward-pick or shipping areas;
• replenishment and picking consequences.

6.2 Storage policies

Dedicated storage reserves a location or set of locations for an SKU. It simplifies identification and may support stable operations, but it can waste space when demand varies.

Random or floating storage assigns any eligible available location and generally improves space utilization, provided the WMS maintains accurate location records. It increases dependence on scanning and system discipline.

Class-based storage divides inventory into velocity or handling classes, such as fast, medium, and slow movers. It provides a compromise between travel efficiency and space flexibility.

Family grouping places complementary or commonly co-used items near each other. It can reduce search and picking time but may conflict with velocity-based placement.

No policy is universally best. The choice should reflect demand variability, SKU count, inventory accuracy, facility geometry, and system capability.

6.3 A directed put-away decision sequence

A practical sequence is:

1. Confirm receipt and release status.
2. Determine handling unit, item dimensions, weight, lot, serial, and expiry attributes.
3. Filter locations that violate temperature, hazard, compatibility, security, or equipment rules.
4. Exclude locations lacking sufficient capacity or having operational holds.
5. Apply rotation rules such as first-expired, first-out (FEFO) or first-in, first-out (FIFO), where appropriate.
6. Rank eligible locations by travel, replenishment impact, cube utilization, and congestion.
7. Issue a task with source, destination, quantity, handling instructions, and scan confirmations.
8. Confirm completion and reconcile any short, damaged, or misplaced quantity.

A simple travel estimate for a put-away task can be represented as:

where each term is time for the respective activity. This is an operational decomposition, not a universal time standard. It assumes the task can be separated into those components and that congestion, waiting, and rehandling are either included in the relevant terms or measured separately.

Optimization should not minimize travel alone. A location with the shortest travel distance may be unsuitable because it creates frequent replenishment, blocks emergency access, or violates product-compatibility rules. A multi-objective ranking may therefore use weighted criteria:

Here, location j is evaluated using travel distance d_j, replenishment burden r_j, congestion contribution c_j, and other risk or quality cost q_j. The weights w₁, w₂, w₃, w₄ express managerial priorities. Because the components may have different units, they should be normalized before combining them. The score is a decision aid, not a scientifically universal law.

6.4 Rotation and expiry

FIFO uses receipt sequence; FEFO uses the earliest expiry date. FEFO is generally more appropriate when shelf life is the principal risk. Neither policy works if dates are missing, inaccurate, or ignored during task generation. Expiry controls should include minimum remaining shelf life at receipt, blocked allocation near expiry, cycle-count attention, and escalation for aging stock.

7. Cross-Docking and Flow Control

Cross-docking moves received goods to outbound staging or directly to an outbound vehicle with little or no conventional storage. It is appropriate when demand is known, inbound and outbound timing is synchronized, product is already labeled and allocated, and handling can occur reliably without prolonged staging.

Forms include:

• pre-distribution cross-docking: inbound units are assigned to customers before arrival;
• post-distribution cross-docking: units are received and then allocated according to current demand;
• opportunistic cross-docking: available inventory is matched to urgent or known demand at receipt;
• flow-through handling: goods may be sorted, relabeled, or consolidated before outbound movement.

Cross-docking does not eliminate inventory control. The system must record receipt, allocation, staging location, outbound assignment, and exception status. It also requires synchronization among supplier schedules, dock capacity, order release, transportation, and outbound labor.

Cross-docking is risky when inbound reliability is poor, demand is uncertain, labeling is inadequate, or outbound departures are infrequent. In such cases, the apparent storage savings may be replaced by staging congestion and missed service commitments.

Flow control limits work-in-process in receiving and staging. A useful operating rule is to establish maximum quantities for dock, inspection, quarantine, and cross-dock lanes. When a downstream area is full, upstream release should slow or stop rather than continue creating unsafe piles. This is a practical application of pull control and the broader principle that throughput is constrained by the system bottleneck.

8. Replenishment Design

Replenishment transfers inventory from reserve storage to forward-pick locations or production-feed locations. Its purpose is to maintain availability for picking while avoiding excessive forward stock and congestion.

8.1 Trigger methods

Common methods include:

• minimum–maximum: replenish when stock reaches the minimum, up to the maximum;
• order-point: trigger when projected available stock reaches a reorder point;
• top-off: replenish forward locations during planned low-activity periods;
• wave-based: replenish before a picking wave;
• demand-driven: trigger from actual orders or consumption;
• kanban or two-bin: trigger when a defined container or signal is consumed.

A basic order-point expression is:

where ROP is the reorder point in units, D_L is expected demand during replenishment lead time, and SS is safety stock. If average demand is d units per time period and lead time is L periods, then under stable conditions:

These expressions assume that demand and lead time are represented in compatible units. Safety stock is not automatically required to equal a fixed percentage of demand; it should reflect variability, service objectives, and replenishment risk.

For independent, approximately normal demand during a fixed lead time, one common approximation is:

where z is the standard-normal service factor and σ_L is the standard deviation of demand during lead time. This approximation assumes that the chosen service measure is compatible with the normal-loss model, demand observations are sufficiently stable, and the normal approximation is reasonable. It should not be applied blindly to intermittent demand, highly seasonal demand, very short data histories, or items with severe obsolescence risk.

If demand per period has standard deviation σ_d and lead time is fixed at L independent periods, then:

The square-root relationship assumes independent, identically distributed demand across periods and fixed lead time. If lead time varies or demand is autocorrelated, a different variance model is required.

8.2 Forward-location sizing

Forward locations should hold enough inventory to support expected picking between replenishments while accommodating case-pack constraints and practical space. A location that is too small causes frequent replenishment and picker interruptions; one that is too large consumes valuable pick-face capacity and may increase handling.

Replenishment tasks should be prioritized according to stockout risk, customer priority, wave timing, travel efficiency, and safety. A replenishment completed after the picker arrives is operationally late even if the inventory record is technically correct.

8.3 Coordination with put-away

Inbound put-away and replenishment compete for labor, equipment, and aisles. Policies should specify whether newly received goods may be placed directly into forward locations, whether reserve stock has priority, and how urgent replenishment is escalated. Direct put-away to the forward face can reduce handling, but it may create congestion or bypass reserve controls. The best choice depends on demand timing, quantity, location capacity, and product rotation.

9. Performance Measurement and Control

A balanced performance system should measure more than receiving speed.

Dock-to-stock time should be defined precisely—for example, elapsed time from physical arrival or unloading start to inventory release and confirmed storage. Different definitions produce non-comparable results.

Performance data should be segmented by supplier, SKU family, shift, door, carrier, and exception type. Averages can conceal a long tail of difficult loads. Percentiles, such as the 90th or 95th percentile of dock-to-stock time, may better reveal service risk, although the chosen statistic should match the managerial purpose.

10. Technology and AI-Enabled Operations

WMS-directed tasks, barcode scanning, RFID, computer vision, appointment portals, electronic proof of delivery, and supplier ASNs can improve visibility and reduce manual entry. Sensors may support temperature, shock, location, or door monitoring. However, technology does not repair ambiguous ownership, poor master data, unsafe layout, or weak exception governance.

AI and advanced analytics may forecast arrival times, predict unloading duration, identify damage from images, recommend put-away locations, or prioritize replenishment. Such systems should be deployed with human oversight and clear accountability. Models can reproduce historical bias, misclassify unusual products, or optimize a local metric at the expense of safety or service. A recommendation system should expose relevant factors, preserve override authority, log decisions, and be periodically validated against actual outcomes.

Cybersecurity and data governance are also operational concerns. Appointment and inventory systems may contain supplier, customer, pricing, and regulated-product information. Access should follow role-based principles, and changes to inventory status should be auditable.

11. Applied Case: Northstar Medical Devices (Illustrative)

Background

Northstar Medical Devices operates a regional distribution center serving hospitals. It receives sterile kits, diagnostic accessories, and capital-equipment components. The facility has experienced long receiving queues, frequent location errors, and occasional shipment of products with insufficient remaining shelf life. The following is an illustrative case rather than a report of an actual company.

Problem

Northstar uses broad arrival windows and assigns doors on a first-come, first-served basis. Receivers count cartons but sometimes record the supplier’s expected quantity without opening mixed cartons. Quality staff inspect selected items but do not always place system holds. Put-away is largely operator-selected. Forward pick locations frequently empty during afternoon order waves, while reserve locations contain excess stock.

Analysis

A process review identifies five interacting causes:

1. ASN data are incomplete, so labor and inspection needs are unknown.
2. Door assignment ignores temperature and cross-dock requirements.
3. Quality status is not linked consistently to inventory availability.
4. Put-away decisions do not use expiry or forward-location capacity.
5. Replenishment is reactive and competes with inbound unloading.

The symptoms are therefore not solved by adding receivers alone. More labor would increase activity but not necessarily improve status integrity or location accuracy.

Approach and solution

Northstar introduces two-hour appointment windows with load profiles captured in advance. Loads requiring temperature checks or specialist inspection receive compatible doors. A receiving checklist records seal, condition, quantity, lot, serial, and expiry information. The WMS creates “received-pending-inspection” status until the quality decision is recorded.

The company introduces risk-based inspection: stable low-risk suppliers receive identity, quantity, and packaging checks; new suppliers and critical sterile kits receive enhanced inspection. Quarantine locations are physically segregated and electronically blocked.

Directed put-away filters locations by temperature, product compatibility, expiry, weight, and capacity. FEFO is used for products with expiry risk. Fast-moving accessories are assigned forward locations sized by case pack and order-wave demand. Replenishment is triggered before the afternoon wave and escalated when projected available stock falls below the order point.

Cross-docking is used only for hospital-specific kits with a confirmed outbound order and departure time. Other goods enter reserve or forward storage. A daily review examines aged quarantine, late appointments, receipt discrepancies, and replenishment failures.

Outcome

The expected outcome is not simply faster unloading. Northstar should obtain more reliable inventory availability, fewer expiry-related exceptions, reduced search and rehandling, and better supplier feedback. Management should validate results using baseline and post-implementation measures, segmented by product class and supplier. If dock-to-stock time improves but quality escapes increase, the design has failed despite apparent speed gains.

Learning points

The case demonstrates that inbound performance is an end-to-end property. Appointment control, verification, quality release, master data, directed put-away, and replenishment must be coordinated. It also illustrates the importance of selective standardization: low-risk receipts can be fast, while high-risk receipts require stronger controls.

12. Challenges, Limitations, and Governance

Inbound systems face demand variability, supplier noncompliance, labor shortages, equipment failure, incomplete data, seasonal peaks, and physical constraints. Standard operating procedures can become obsolete when product mix or packaging changes. A design based on average workload may fail during peak periods, while a design based on maximum workload may be economically wasteful.

Governance should address:

• worker health and safety, including training and fatigue management;
• legal requirements for hazardous, food, pharmaceutical, or regulated products;
• accurate records for claims, recalls, and financial inventory;
• nondiscrimination and fair treatment in labor allocation;
• responsible use of surveillance and performance data;
• environmental controls for waste, packaging, and temperature-sensitive goods;
• segregation of duties for receiving, quality release, adjustment, and disposition.

Ethically, throughput targets must never encourage employees to ignore damage, falsify counts, bypass quarantine, or work unsafely. Inventory accuracy is an organizational responsibility, not merely an individual receiver’s obligation.

Best-Practice Design Principles

1. Design physical and information flows together.
2. Make inventory status explicit and auditable.
3. Match inspection intensity to risk.
4. Use appointments to balance capacity, not merely to control carriers.
5. Treat quarantine as both a physical and system control.
6. Direct put-away through eligibility rules before optimization criteria.
7. Use FEFO where expiry, rather than receipt date, drives risk.
8. Reserve cross-docking for synchronized, reliable flows.
9. Plan replenishment before stockout, not after a picker reports one.
10. Measure exceptions, queues, and variability—not only averages.
11. Protect safety and product integrity from productivity pressure.
12. Continuously reconcile master data with physical reality.

Chapter Summary

Receiving, inspection, put-away, cross-docking, and replenishment form an integrated inbound control system. Appointment scheduling aligns arrivals with doors, labor, equipment, inspection capability, and staging capacity. Unloading and verification establish the identity, quantity, condition, and documentation of received goods. Risk-based inspection and explicit quarantine protect customers and preserve traceability.

Labeling and master-data accuracy connect physical units to WMS records. Directed put-away applies eligibility constraints and ranked preferences to select appropriate storage locations while considering travel, capacity, compatibility, rotation, and downstream replenishment. Cross-docking can reduce storage and handling, but only when demand, timing, labeling, and outbound capacity are synchronized. Replenishment policies maintain forward-pick availability through minimum–maximum, order-point, top-off, wave, or demand-driven triggers.

Effective management uses balanced measures covering flow, accuracy, quality, service, productivity, supplier performance, and safety. Technology and AI can improve visibility and decision support, but they require sound data, human accountability, cybersecurity, and exception governance. The central managerial lesson is that speed without verification, quality release, and status integrity merely transfers cost and risk downstream.

Key Terms

Advance shipping notice (ASN): Electronic or structured information sent before arrival describing an expected shipment.

Appointment scheduling: Planned allocation of arrival time and receiving resources to an inbound load.

Blind receiving: Receiving in which the expected quantity is hidden from the receiver to encourage independent counting.

Cross-docking: Moving received goods toward outbound shipment with little or no conventional storage.

Directed put-away: System- or rule-based assignment of inventory to eligible storage locations.

Dock-to-stock time: Elapsed time from a defined arrival or unloading event until inventory is released and stored or otherwise made available.

Exception management: Identification, containment, escalation, resolution, and analysis of deviations from standard receipt or handling conditions.

FEFO: First-expired, first-out inventory rotation.

FIFO: First-in, first-out inventory rotation based on receipt sequence.

Flow-through handling: Receiving, sorting, relabeling, or consolidating goods for rapid outbound movement.

Forward-pick location: A convenient location from which order pickers obtain inventory for customer orders.

Inventory status: System classification indicating whether stock is expected, held, available, quarantined, or otherwise restricted.

Order point: Inventory position at which replenishment should be initiated.

Quarantine: Controlled physical and electronic isolation of material pending a quality or disposition decision.

Replenishment: Transfer of inventory from reserve or another source to a forward-pick or consumption location.

Reserve storage: Storage intended to supply forward locations or later demand rather than immediate picking.

Risk-based inspection: Allocation of inspection effort according to defect probability, consequence, and regulatory or operational risk.

Safety stock: Inventory held to buffer uncertainty in demand, lead time, supply, or operations.

Unit of measure: Defined quantity basis used to identify, count, store, transact, or report inventory.

WMS: Warehouse-management system that records inventory and directs or supports warehouse activities.

Review Questions

Short Answer Questions

1. Why should inventory not normally become available immediately when a truck arrives?
2. What information should an inbound appointment record contain?
3. Distinguish FIFO from FEFO.
4. What is the purpose of a quarantine status?
5. Identify two risks of cross-docking.

Long Answer Questions

1. Explain how appointment scheduling, dock assignment, and staging capacity should be designed as one system.
2. Compare dedicated, random, and class-based storage policies, including their operational trade-offs.
3. Describe a risk-based receiving and inspection process for a mixed-SKU inbound load.
4. Explain how directed put-away can improve both space utilization and order-fulfillment performance.
5. Discuss the role and limitations of WMS, RFID, computer vision, and AI in inbound operations.

Analytical / Application Questions

1. A warehouse has 48 labor-hours available in a receiving period. Planned loads require 12, 15, 9, and 14 labor-hours. Calculate planned utilization and explain why the result may still be operationally risky.
2. Daily demand for an item averages 80 units, replenishment lead time is 3 days, and safety stock is 70 units. Calculate the order point and state the assumptions behind the calculation.
3. Design an inbound process for a temperature-sensitive, lot-controlled product with uncertain arrival times and confirmed hospital orders. Specify appointment, inspection, status, cross-dock, and exception controls.

Multiple Choice Questions with Answers

Question 1

Which event most appropriately changes inventory from “received, pending inspection” to “available”?

A. The vehicle passes through the gate

B. The receiver begins unloading

C. Required verification and quality-release controls are completed

D. The supplier sends an invoice

Correct Answer: C. Required verification and quality-release controls are completed

Question 2

What is the principal purpose of an advance shipping notice?

A. To replace all physical counting

B. To provide expected shipment information before arrival

C. To authorize disposal of damaged goods

D. To determine customer selling price

Correct Answer: B. To provide expected shipment information before arrival

Question 3

A warehouse has 48 labor-hours available and planned receiving work of 12, 15, 9, and 14 labor-hours. What is planned utilization?

A. 75%

B. 90%

C. 100%

D. 104.2%

Correct Answer: D. 104.2%

Question 4

Which policy is generally most appropriate when expiry date is the main inventory risk?

A. LIFO

B. FEFO

C. Random selection

D. Largest-case-first

Correct Answer: B. FEFO

Question 5

Which condition is most necessary for reliable cross-docking?

A. Large quantities of unscheduled safety stock

B. Uncertain outbound demand and infrequent departures

C. Synchronization between inbound goods and outbound demand

D. Elimination of all inventory-status records

Correct Answer: C. Synchronization between inbound goods and outbound demand

Question 6

In the expression ROP = D_L + SS, what does SS represent?

A. Supplier schedule

B. Safety stock

C. Storage space

D. Shipment sequence

Correct Answer: B. Safety stock

Question 7

Which is a defining feature of directed put-away?

A. Operators always choose the nearest empty location

B. Locations are assigned using explicit eligibility and ranking rules

C. All SKUs receive dedicated locations

D. Inventory is stored without WMS confirmation

Correct Answer: B. Locations are assigned using explicit eligibility and ranking rules

Question 8

What is the strongest control for quarantined material?

A. A verbal instruction to the receiver

B. A physical sign without a system hold

C. A system hold combined with physical segregation

D. Immediate allocation to the highest-priority order

Correct Answer: C. A system hold combined with physical segregation

Question 9

If average demand is 80 units per day and replenishment lead time is 3 days, what is expected lead-time demand under the fixed-lead-time assumption?

A. 83 units

B. 160 units

C. 240 units

D. 320 units

Correct Answer: C. 240 units

Question 10

Why should supplier discrepancies be coded and retained rather than simply corrected in the inventory record?

A. To eliminate the need for inspection

B. To preserve information for claims, analysis, and corrective action

C. To increase the apparent receipt quantity

D. To avoid using appointment schedules

Correct Answer: B. To preserve information for claims, analysis, and corrective action