Abstract
Practitioners and researchers describe inventory service level with metrics that communicate the likelihood of demand fulfillment without considering the ongoing capabilities of the supplier, for example, in‐stock and fill rate. We develop a method for measuring inventory service level that incorporates such supplier capabilities, namely consistency (the ability of a supplier to fulfill orders repeatedly) and recovery (the ability of a supplier to fulfill orders after a lapse in service). Using data from two retail supply chains, we illustrate our approach. To demonstrate the impact of consistency and recovery on supply chain performance, we model a retailer purchasing from competing suppliers with different levels of consistency and recovery. The model incorporates the retailer's uncertainty about demand and the retailer's uncertainty about its suppliers' service levels. We characterize how the retailer's orders and profitability change with a supplier's delivery performance through numerical experiments calibrated with field data. We find notable differences in market share across suppliers with similar traditional inventory service level metrics but differences in consistency and recovery. Further, we observe that a retailer can increase its profitability by determining orders via consistency and recovery in lieu of common metrics like in‐stock. Given the influence of consistency and recovery on supply chain outcomes, we discuss implications for practice and future research.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.