# Store Action Report

The "Store Action Report" is your detailed report for every operational change made to your stores. Think of it as a security log that helps you audit actions, understand a store's history, and troubleshoot issues with confidence.

This guide explains each field in the report, helping you track who did what, when, and on which online platform.

## **Store & Brand Identification**

These fields help you pinpoint the exact store and brand that an action was performed on.

### Brand & Brand ID

* What it is: The name and unique internal code for your brand.
* Why it's useful: If you have a multi-brand setup, this is crucial for filtering actions by brand.

### store\_id & ref\_id

* What it is: The unique internal code (`store_id`) and the unique external ID (`ref_id`) for your store on the aggregator platform.
* Why it's useful: These are your primary keys for identifying the store in both your internal and external systems.

### store

* What it is: The name of your restaurant location where the action was performed.
* Why it's useful: Provides a clear, human-readable name for the store, making it easy to see which location was affected.

## **Action Details**

These fields give you the specifics of the action that was performed.

### action\_time

* What it is: The exact date and time the action occurred.
* Why it's useful: This is the most critical field for auditing. It creates a historical timeline of all changes, which is vital for troubleshooting.

### platform

* What it is: The specific online platform or channel where the action took place (e.g., "zomato," "Growthfalcons").
* Why it's useful: Helps you track which platforms are being managed and if there are any platform-specific issues.

### action\_performed

* What it is: The specific action that was taken (e.g., "publish," "enable," "disable").
* Why it's useful: This tells you exactly what was done to your store's status.

### application\_src

* What it is: The source of the action, such as an API call, a user in the UI, or an internal system.
* Why it's useful: Provides context on how the action was initiated, which is valuable for security and troubleshooting.

### status

* What it is: The result of the action (e.g., "ack\_success," which means the action was successfully acknowledged).
* Why it's useful: Indicates whether the action was completed successfully or if it failed.

## **User Details**

These fields tell you who or what performed the action.

### username

* What it is: The username of the person or system account that performed the action.
* Why it's useful: Essential for accountability and security.

### user\_first\_last\_name

* What it is: The full name of the user who performed the action.
* Why it's useful: Provides a human-readable name for auditing and understanding who is responsible for a particular change.

This "Store Action Report" is a valuable record of all operational changes. By using these fields, you can audit your processes, ensure accountability, and troubleshoot any store-level issues with confidence!