Shelf Availability Problem Solving
A worked shelf-gap investigation shows store teams how to record an observed empty location, compare it with approved inventory views, and send replenishment partners a clear, evidence-based handoff.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Grocery retail · Supermarkets · Convenience retail · General merchandise retail
Overview
Shelf Availability Problem Solving is a single-page worked procedure for investigating an observed product gap without treating an inventory count as proof of physical availability. Its fictional Northstar Market example follows an empty shelf location for Northstar Oat Drink, 1 L, at Cedar Street on 14 May. The page records the observation time, compares it with an approved inventory view showing 12 units and an 08:55 transaction timestamp, then prepares a question for a replenishment partner.
The page is useful when store colleagues need to communicate a shelf observation alongside what an approved view actually displays. It separates the facts seen at the store from the system evidence and from possible explanations, such as a shelf-replenishment gap, a stock-record discrepancy, or a receipt or movement handoff. The timeline and completed handoff provide a concrete example of what to capture and what to leave unresolved. In the fictional outcome, a partner confirms a receipt timing issue; that is an illustrative result, not a promised outcome or universal process.
Use this as a starting point for a local procedure only after confirming which views are approved, who may access them, and which store-to-replenishment and escalation routes apply. It is not a live stock feed, an inventory correction workflow, a response-time commitment, or a substitute for local policy. Do not use it to infer where units are from a displayed count, declare product unavailable elsewhere, or establish a cause without supporting evidence. Keep the example clearly marked as fictional, and maintain one authoritative home for any linked local procedure.
Standards & compliance context
- The page is an illustrative operating aid, not a regulatory interpretation or a substitute for applicable company and location-specific inventory procedures.
- Limit inventory-view instructions to systems and information approved for the reader's role and location; confirm access and handling requirements locally.
- Use clear headings, readable text, and descriptive link labels so the procedure remains navigable and aligns with WCAG 2.1 AA accessibility practices.
- Do not present the fictional observation, quantity, timestamps, or outcome as live inventory data or a verified company incident.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Investigate the gap before settling on a cause
This introduction sets the evidence-first approach and clarifies that the example is fictional rather than live stock information.
-
For store teams and replenishment partners tracing an observed product gap Fictional worked example: At Northstar Market's Cedar Street store, a shopper-facing shelf was empty for Northstar Oat Drink, 1 L, on 14 May. The example shows how the store team recorded what it could observe, compared it with approved inventory views, and handed the unresolved question to replenishment. It is not live stock information or a local operating policy. Start with the observed gap and its time and location. Check only inventory views approved for your role and location. Record what each view actually shows, then label possible causes as questions until evidence supports them.
Illustrative incident notice — 14 May, 09:20
The notice anchors the example to one recorded product, location, and observation time without implying current availability.
-
Fictional example, Northstar Market, Cedar Street: the shelf location for Northstar Oat Drink, 1 L, was observed empty at 09:20. This notice records one observation; it does not monitor current availability or indicate that the product is unavailable elsewhere.
What happened in the example
The timeline shows how the fictional team moved from observation to comparison, handoff, and learning.
-
Record the shelf gap A store colleague observed the named product absent from its usual shelf location. The observation was recorded with the store, product description, and time. 14 May, 09:20 Compare approved inventory views The example team checked its approved store inventory view and recorded a positive on-hand quantity alongside a recent transaction timestamp. This suggested a record-to-shelf mismatch; it did not prove where the units were. 14 May, 09:28 Ask replenishment to review the handoff The store shared the observation and view details with its replenishment partner, asking whether a recent receipt or movement could explain the mismatch. No delivery or correction was assumed. 14 May, 09:40 Capture the learning For this fictional example, the partner confirmed that a recently recorded receipt had not yet been reflected in the shelf-replenishment handoff. The teams agreed to include receipt timing in similar investigations; this is an example outcome, not a universal process. 14 May, 11:15
Separate what was seen from what a view suggested
These paired examples make the distinction between a shelf observation and inventory-view evidence explicit.
-
Keep direct observations distinct from system information and interpretation. A mismatch is a useful lead, not a confirmed explanation. Observed at the store At 09:20, the usual shelf location for Northstar Oat Drink, 1 L, appeared empty. Store: Cedar Street Observation time: 14 May, 09:20 Recorded fact: product absent from the usual shelf location Shown in the approved view The example inventory view showed 12 units on hand and a transaction timestamp of 08:55. Record the view name and its displayed timestamp. Treat the difference as a discrepancy to investigate. Do not infer physical location or availability from the count alone.
Possible causes to distinguish
The cards offer investigation questions for common mismatch types without presenting any as a confirmed diagnosis.
-
Use these as investigation questions, not conclusions Shelf-replenishment gap The product may be recorded on hand but not present at its usual shelf location. Compare the shelf observation time with relevant approved-view timestamps. Record any location or movement information available through approved channels. Stock-record discrepancy The displayed quantity may differ from the quantity physically available. Note the displayed quantity and last transaction time. Ask the responsible inventory role to review the discrepancy through the established local process. Supply or receipt handoff A recent receipt, transfer, or other handoff may not align with what the store view shows. Record known receipt or movement references only if available in an approved view. Ask the replenishment partner which handoff detail remains unverified.
Completed handoff example
The sample note demonstrates how to give replenishment partners the context, checks, and unresolved question in one concise handoff.
-
A concise note keeps facts, checks, and the open question together Subject: Shelf gap with positive on-hand count — Northstar Oat Drink, 1 L Location and time: Northstar Market, Cedar Street; usual shelf location observed empty on 14 May at 09:20. Approved-view finding: Store inventory view showed 12 units on hand; displayed transaction timestamp was 08:55. The view name and timestamp are included so the receiving partner can identify the source of the finding. Already checked: The team compared the shelf observation with the approved view and found a difference between the observed shelf and displayed count. The team has not established where the units are. Question for replenishment: Does a receipt or movement around the displayed transaction time explain the difference, or should the inventory discrepancy be reviewed through the local process? Handoff principle: Send this information through the established store-to-replenishment route. If the discrepancy remains unresolved, use the escalation path defined for the applicable role and location; this example does not create a new route or response time.
How to use this template
- Confirm the intended store audience, approved inventory views, and established replenishment and escalation routes for the locations where the page will be used.
- Replace or retain the Northstar example as clearly marked fiction, and add verified local references without inventing a contact, response time, or workflow.
- When a shelf gap is observed, record the product description, store and usual shelf location, and observation date and time.
- Open only the inventory views approved for the colleague's role and location, then record the view name, displayed quantity, and transaction timestamp exactly as shown.
- Compare the observation with the view, label possible explanations as questions, and send the facts plus one clear open question through the established replenishment route.
- If the discrepancy remains unresolved, follow the applicable local escalation path and update the page owner when the underlying procedure or approved views change.
Best practices
- Record the date, time, store, and usual shelf location with every observation so a partner can understand where and when the gap was seen.
- Write down the inventory view name and its displayed timestamp alongside any quantity rather than reporting a count without its source.
- Keep direct shelf observations, system information, and interpretations in separate sentences or fields.
- Treat a positive on-hand count as a discrepancy to investigate, not proof of a unit's physical location or shelf availability.
- Frame possible causes as questions and request the specific receipt, movement, or inventory review that remains unverified.
- Use only views and channels approved for the colleague's role and location, and preserve the local escalation route.
- Keep the fictional example visibly labeled and replace its sample figures and dates before presenting them as a real incident.
- Review the page when approved views, role responsibilities, or local handoff procedures change, and maintain one authoritative copy.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kind of shelf availability problem does this template cover?
It covers an observed empty shelf location when an approved inventory view may show stock on hand. The example distinguishes the shelf observation, system information, and possible explanations. It is not a live availability monitor or a guide to every cause of an out-of-stock.
How often should store teams use this guide?
Use the procedure when a colleague observes a shelf gap that needs investigation or a handoff. The example does not set a recurring inspection cadence or response-time target. Follow the applicable local process for how often shelves are checked and when unresolved issues are escalated.
Who should run the investigation and receive the handoff?
A store colleague records the observed product, location, and time, then compares the observation with inventory information approved for their role and location. The example directs the question to a replenishment partner, while noting that unresolved discrepancies should follow the established local escalation path. Confirm role ownership and routing locally before adopting the page.
Does this template establish a regulatory or company policy?
No. It is a fictional worked example, not a local operating policy, regulatory interpretation, or assurance of compliance. Use the inventory views and escalation procedures authorized for your location, and link to the authoritative internal policy if readers need binding instructions. Make the page accessible to its intended audience, including through clear headings and readable text.
What is the most common mistake when investigating a shelf gap?
Treating a positive on-hand count as proof that units are physically available or knowing where they are. The template treats a difference between the shelf and the view as a lead to investigate, not a confirmed cause. Record the view name, displayed quantity, and timestamp, and keep interpretations labeled as questions.
What should we customize before publishing this page?
Replace the fictional Northstar Market example with an appropriately labeled local example or retain it clearly as fiction. Identify the approved inventory views by their actual names, clarify which roles may use them, and link the handoff and escalation references only after confirming they are valid for the intended location. Do not add an invented response time or route.
Does the template connect to inventory systems or trigger replenishment?
No. The page describes a manual comparison using approved inventory views; it does not contain a live stock feed, transaction, or automated workflow. Readers must open the systems already approved for their role, then use the established store-to-replenishment channel. Explain any access or connection requirements through your organization's existing setup process.
How does this compare with an informal message about an empty shelf?
An informal message can omit when and where the gap was observed, what view was checked, or what remains unknown. The completed handoff example groups those details with a specific question for replenishment. Teams can adapt its structure while retaining local routing and avoiding unsupported conclusions.
How should we roll this out to store teams?
Confirm the intended audience, approved inventory views, and local handoff and escalation routes before sharing the page. Walk through the fictional timeline and ask colleagues to distinguish observed facts from system evidence and hypotheses. Make the page easy to find from the relevant store or replenishment navigation, and assign an owner to review it when local systems or procedures change.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Shelf Availability Problem Solving ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
