Standard Operating Procedures for Retail Store

Standard Operating Procedure: Retail Store Operations (RSO)

1. Document Control Block

---

2. Executive Summary & Scope

This SOP defines the standardized operational framework for the daily administration, sales execution, and safety compliance of Template Registry retail outlets. The scope encompasses opening/closing procedures, inventory integrity, point-of-sale (POS) reconciliation, and site safety protocols. This document adheres to local commerce regulations, PCI-DSS payment standards, and OSHA safety guidelines. All personnel are strictly bound by these procedural mandates.

---

3. Prerequisites & Tool Requirements

• Access Credentials: Authorized POS PIN, back-office ERP system credentials, alarm system security code.
• Equipment: Handheld barcode scanners, POS terminal, secure cash counting equipment, daily deposit bags.
• Safety PPE: Slip-resistant footwear (mandatory), box cutters with retractable safety guards, step-ladders (inspected).
• Documentation: Daily Reconciliation Log (DRL), Incident Report Forms, Physical Inventory Count Sheets.

---

4. Roles & Responsibilities (RACI Matrix)

(R=Responsible, A=Accountable, C=Consulted, I=Informed)

---

5. Step-by-Step Operational Procedure

Phase I: Pre-Opening Security & Readiness

• Deactivate security alarm system; verify connection to central monitoring.
• Inspect store perimeter and front facade for signs of forced entry or structural integrity issues.
• Execute POS "Start of Day" function; verify system connectivity to the central server.
• Perform cash drawer reconciliation; verify current funds match the "Start of Day" baseline.

Phase II: Operational Sales Execution

• Verify floor layout aligns with the current planogram and marketing directives.
• Process customer transactions via authenticated POS protocols; ensure digital receipts are offered.
• Monitor shelf stock levels; initiate replenishment workflows if levels fall below "Minimum Threshold" markers.

Phase III: Closing & Reconciliation

• Execute "End of Day" POS reporting; match physical cash against digital sales report.
• Secure excess cash in the time-delay drop safe; record deposit slips.
• Conduct a final floor sweep to ensure all security tags are active and displays are reset.
• Arm the security system; verify all exits are locked and secondary locks are engaged.

---

6. Quality Assurance & Verification Criteria

• Financial Accuracy: Cash variance threshold must remain below ±$2.00 per shift. Deviations exceeding this require an immediate Incident Report (IR).
• Planogram Compliance: Displays must match the weekly directive with a minimum 95% accuracy score during audits.
• Safety Audit: Daily inspection of egress paths; zero blockage of fire exits is permitted.
• System Uptime: POS terminals must maintain 99.9% connectivity during core business hours.

---

7. Practical Troubleshooting Scenarios

Scenario A: POS Connectivity Failure

• Symptom: Terminal unable to communicate with transaction server; transaction pending/failed.
• Corrective Action:
  1. Verify physical ethernet connection.
  2. Reboot POS hardware once.
  3. If persistent, switch to "Offline Mode" (only if authorized for specific merchant tiers) or process via manual credit card imprinter as a last resort. Notify IT Support immediately.

Scenario B: Inventory Discrepancy (Excess/Shortage)

• Symptom: Physical stock count deviates from ERP digital records by >3 units.
• Corrective Action:
  1. Perform a blind recount.
  2. Review security footage for the previous 24-hour cycle.
  3. If unresolved, log as "Adjustment" in the inventory module and flag for Manager review.

Scenario C: Security Alarm Failure

• Symptom: Alarm fails to arm upon store closure.
• Corrective Action:
  1. Perform a secondary visual inspection of all perimeter points (ensure doors/windows are fully seated).
  2. Clear all "Zone Faults" on the keypad.
  3. If failure persists, contact the security provider's 24/7 dispatch and remain on-site until a representative arrives or site security is verified.

---

Authorized by: Julian Vance, Chief Operations Architect, Template Registry.