Short answer
Retail store procedures list the recurring routines around the shop floor: opening and closing checks, receiving, backroom handling, replenishment, price and label changes and shelf recovery. They give a planner the order, the checks and the exceptions. They do not show how to pick, face or place products, and they cannot tell a robot what a particular store looks like.
Why stores are a distinct source
Stores are one of the few settings where the work is repetitive, indoors and open to the public, which is why retail often appears in humanoid and mobile-manipulation discussions. The work is also governed by a stack of routines that nobody sees from the aisle: what is checked at opening, when freight is received, how the backroom is organized, when shelves are replenished and what happens when a product does not fit its slot.
Those routines are written down in store operations manuals, shift checklists and training materials. For a buyer, they provide the structure that perception and manipulation data lack. Shelf images tell you what a facing looks like; procedures tell you when and why a facing is restocked. Treat them as complementary and source them separately. Planogram files, which specify where products should sit, are covered in retail planograms.
Three routine families
Opening and closing. Walk-through checks, safety and alarm steps, floor and entrance condition, cash-handling hand-offs, equipment start-up and shutdown, and end-of-day recovery of misplaced goods. The text is mostly checklist-form, with owner and time-of-day attributes.
Receiving and backroom. Verifying a delivery against paperwork, staging by category, rotation rules for dated goods, damage handling and storage constraints. This overlaps with the warehouse side of the pack; see the warehouse cluster for dock and inventory data.
Replenishment and shelf recovery. Triggers for restocking (gaps, scans, counts), bringing product to the aisle, facing and straightening, price-label changes and promotional resets. The procedure typically says what to check; the physical method is learned on the job.
What to extract
A store operations manual is long and mixed. Useful extraction separates:
- steps by routine family and by role;
- time triggers (start of shift, delivery arrival) from state triggers (empty facing, damaged item);
- decision points, such as what to do with an item that does not match its shelf label;
- conditions that restrict action, such as customers present, wet floors or restricted product categories;
- the artifacts that confirm completion, such as a signed checklist or a scan.
The final item matters for evaluation. A step that ends with a recorded confirmation is checkable; a step that ends with "ensure shelves look good" is not. See checklists as success criteria for how to separate the two.
Illustrative package for a retail procedure purchase
The package below is Illustrative: it is a way to describe a request, not a statement of what any supplier holds.
| Component | Example content | Note |
|---|---|---|
| Opening/closing checklists | Role-tagged, versioned, per format | Format may be small store, big box or convenience |
| Receiving procedures | Delivery verification, staging, rotation | Brand and vendor names redacted |
| Replenishment SOPs | Triggers, sequence, exception handling | Keep decision points |
| Planogram reset instructions | Reset notices and sequences, if licensable | Often supplied by brands, not the store |
| Shelf recovery guidance | What to do with misplaced goods | Short, high value |
| Tools and equipment list | Ladders, pallet jacks, scanners | See tools and materials lists |
| Frequency data | How often each routine occurs, if the supplier records it | Supports prioritization |
Frequency, where it exists, helps decide what to automate first; task frequency for prioritizing procedures explains how to use it.
How perception data fits in
The SKU-110K dataset illustrates the gap. It is an annotated dataset of densely packed retail shelves, designed for detecting tightly packed and often identical objects (Goldman et al., 2019). It supports shelf perception: finding items and counting them. It says nothing about the replenishment routine around them, and the procedures say nothing about how to detect a gap. A robot that restocks needs both, plus manipulation data, and the product side is covered in product catalog data for robot perception. Catalog listings themselves are a separate marketplace category; see product catalogs and descriptions.
What this data cannot support
Store procedures cannot train a humanoid to restock. They contain no motion, force or grasp information, no depth or contact data, and nothing about how to pick a deformable bag or a glass jar. A humanoid's control policy needs robot or teleoperation data; procedures and store footage alone cannot supply it.
Specific limits:
- Layout. Procedures are written for a format, not a store; aisle widths, backroom geometry and fixture types vary.
- Corporate versus actual. A chain's manual describes the intended routine; stores adapt it. Evidence of actual practice requires observation.
- Staffing assumptions. Many steps presume two people or a customer-facing interruption pattern that a robot would change.
- Brand constraints. Promotional resets and compliance rules come from brand owners and change quickly.
- Public-facing safety. Procedures cover employee safety, rarely the behavior of a robot near customers, children or carts.
Permissions and provenance
Chain manuals are usually confidential and often include text from vendors, brands and franchisors. Franchisees typically use a franchisor's manual under license and may not be able to pass it on without the franchisor's consent; franchise operations manuals covers the chain of rights. Some procedures reference loss-prevention measures that the company will not release. Redaction should preserve the logic of a step while removing the sensitive parameter, and it does not settle ownership. This is not legal advice.
Questions to ask suppliers
- Does the supplier own the manual, or is it licensed from a franchisor or brand?
- Which store formats does each procedure cover?
- Are opening, closing, receiving and replenishment documents separate or bundled?
- Do the documents include exception handling and decision points, or only the happy path?
- Are brand-supplied planogram or reset notices included, and who can license them?
- How often are procedures revised, and are older versions kept?
- Are loss-prevention or security steps present, and can they be withheld without breaking step order?
- Can any recordings of store staff accompany the procedures, and what consent applies?
Discuss your requirements
If store operating procedures belong in your plan, describe the format, routines and rights you need through a buyer request. SourceX reviews the requirement and follows up about potential sources; a request does not guarantee a match. For the broader picture, see the procedures hub and the humanoid training-data section.
Discuss your humanoid training-data requirements with SourceX.
Sources
- Precise Detection in Densely Packed Scenes — SKU-110K, an annotated dataset of densely packed retail shelves.