> For the complete documentation index, see [llms.txt](https://storecall.gitbook.io/storecall/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://storecall.gitbook.io/storecall/use-cases/retail.md).

# Retail

## 🛍️ Retail Operations Use Cases

**Optimizing store performance, visibility, and accountability**

Retail operations often involve managing dozens of branches, each requiring consistent standards, quick escalations, and formal approval chains. Traditionally, these workflows are spread across WhatsApp chats, email threads, and phone calls, leading to lost information, inconsistent execution, and lack of accountability.

With Storecall’s dynamic template system, you can streamline your retail operations with **Audit**, **Log**, and **Approval** templates that reflect real-life processes.

***

### ✅ Audit Templates

**Used for structured checklists and reviews with scoring where applicable.**

#### 1. **Daily Store Standards Checklist**

**Purpose:** Ensure each store opens clean, stocked, and compliant.\
**Pain Point:** Usually done via WhatsApp group messages or calls from regional managers. No historical tracking or scoring.

{% hint style="info" %}
**Storecall Advantage:** Automatically score performance, attach images, and generate reports by date and location.
{% endhint %}

#### 2. **Monthly Regional Manager Store Visit**

**Purpose:** Capture detailed performance feedback across departments (cleanliness, stock, staff, compliance).\
**Pain Point:** Typically submitted via emailed Excel sheets or paper forms, then manually summarized.<br>

{% hint style="info" %}
**Storecall Advantage:** Use dynamic templates with sections, image uploads, scoring, and historical logs.
{% endhint %}

#### 3. **Backroom Safety Inspection**

**Purpose:** Check for hazards, expiry items, overstocking, or fire risks.\
**Pain Point:** Often noted via WhatsApp or verbally and rarely followed up.<br>

{% hint style="info" %}
**Storecall Advantage:** Set auto-actions for violations, track trends over time by location, and view photo evidence.
{% endhint %}

#### 4. **POS (Point of Sale) System Audit**

**Purpose:** Ensure tills, card machines, and printers are functioning correctly.\
**Pain Point:** Staff escalate via call or text when problems arise, leading to delays.<br>

{% hint style="info" %}
**Storecall Advantage:** Standardized checks ensure preventive issues are caught early.
{% endhint %}

#### 5. **Promo Display & Branding Compliance Audit**

**Purpose:** Validate whether national campaigns are properly displayed.\
**Pain Point:** Staff send photos via WhatsApp with no structured proof of compliance.<br>

{% hint style="info" %}
**Storecall Advantage:** Create a photo-based checklist with timestamps and location tagging.
{% endhint %}

***

### 🔁 Log Templates

**Used for workflows that trigger updates and follow-ups over time.**

#### 1. **Damaged Stock Logging**

**Purpose:** Log damaged goods to be written off or returned.\
**Pain Point:** Usually captured on paper or informal messages. No audit trail.<br>

{% hint style="info" %}
**Storecall Advantage:** Assign follow-ups to area managers or procurement with attached images and reason codes.
{% endhint %}

#### 2. **Customer Incident Log**

**Purpose:** Track customer injuries, complaints, or escalations.\
**Pain Point:** Often phoned in or noted in store diaries with no formal investigation follow-up.<br>

{% hint style="info" %}
**Storecall Advantage:** Real-time alert with optional escalation path to head office.
{% endhint %}

#### 3. **Fridge/Freezer Breakdown Log**

**Purpose:** Report equipment issues that could cause stock loss.\
**Pain Point:** Sent via WhatsApp or calls, often missed.<br>

{% hint style="info" %}
**Storecall Advantage:** Assign to maintenance team, track resolution time, and log asset issues centrally.
{% endhint %}

#### 4. **Daily Sales Logging by Franchisees**

**Purpose:** Franchisees input daily revenue or foot traffic numbers.\
**Pain Point:** Sent via WhatsApp or email, consolidated manually in Excel.<br>

{% hint style="info" %}
**Storecall Advantage:** Digital logging with export-ready data and charts.
{% endhint %}

#### 5. **Stock Transfer Between Stores Log**

**Purpose:** Track internal store-to-store transfers.\
**Pain Point:** Handwritten logs or informal texts lead to mismatches.<br>

{% hint style="info" %}
**Storecall Advantage:** Real-time entry, approval chain, and stock tracking transparency.
{% endhint %}

***

### 📝 Approval Templates

**Used when decisions or permissions are required.**

#### 1. **Leave Request Approval**

**Purpose:** Staff apply for leave to be approved by store manager or regional.\
**Pain Point:** WhatsApp messages or verbal requests with no visibility.<br>

{% hint style="info" %}
**Storecall Advantage:** Track who approved what and when, with full audit trail.
{% endhint %}

#### 2. **Price Override or Discount Approval**

**Purpose:** Authorize exceptions to standard pricing.\
**Pain Point:** Calls made on the spot with no documentation.<br>

{% hint style="info" %}
**Storecall Advantage:** Store staff submit requests with reason, item, and expected impact.
{% endhint %}

#### 3. **New Staff Onboarding Request**

**Purpose:** Request to onboard new hires or casuals.\
**Pain Point:** Sent by email, sometimes delayed or overlooked.<br>

{% hint style="info" %}
**Storecall Advantage:** Ensure all steps (IT access, uniforms, etc.) are followed before approval.
{% endhint %}

#### 4. **Emergency Maintenance Approval**

**Purpose:** Request urgent contractor call-outs or equipment replacement.\
**Pain Point:** Usually via text or call; delays happen when no budget authority is reachable.<br>

{% hint style="info" %}
**Storecall Advantage:** Predefined approval hierarchy ensures no downtime waiting for decisions.
{% endhint %}

#### 5. **Store Closure Request**

**Purpose:** Formal request to close early due to safety, protest, or system outages.\
**Pain Point:** Requires manual escalation and multiple phone calls.<br>

{% hint style="info" %}
**Storecall Advantage:** Securely logs justification, alerts relevant stakeholders instantly.
{% endhint %}

***

### ✅ Bonus: Actions & Notifications

Across all templates:

* **Actions** can be created within submissions or logs to delegate follow-up tasks.
* Actions are automatically assigned to the responsible person, with **email notifications and daily reminders** until resolved.
* This ensures that no issue gets “lost in the system” and everything is **tracked and time-stamped** for accountability.

***

### 💡 Summary

Retail operations deal with high volume, high pace, and high risk if things go undocumented. Storecall transforms the messy paper-WhatsApp-email system into a structured, accountable, and easily reportable digital workflow.

* Ensure **real-time visibility** across teams and regions
* Reduce **operational leakage and miscommunication**
* Create **accountability** across all levels
* Improve **reporting speed and accuracy**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://storecall.gitbook.io/storecall/use-cases/retail.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.