# Order Transactions Report

The "Order Transactions Report" provides a detailed view of every online order, enabling you to track sales, understand customer behavior, and manage your operations more effectively.

Each row in this report represents a single order, and each column (or "field") provides specific information about that order.\
\
Let's break down what each piece of data means for your business.

***

## **Order Identification & Source**

These fields help you identify each order and know where it came from.

### **ID**

* What it is: A unique order ID in UrbanPiper for each order record in our system.
* Why it's useful: Helps you quickly find and reference orders for internal tracking.

### **Order ref ID**

* What it is: The unique order number provided by the online platform (like Swiggy or Zomato).
* Why it's useful: Essential for cross-referencing orders with the aggregator's records if you need to discuss a specific order with their support.

### **Brand**

* What it is: The name of your brand that received the order (useful if you operate multiple brand names).
* Why it's useful: Helps you analyze performance across your different brands.

### **Brand ID**

* What it is: A unique internal code for your brand.
* Why it's useful: For internal tracking of your multi-brand operations.

### **External Platform ID**:

* What it is: Another unique ID assigned to the order by the online platform.
* Why it's useful: Provides an additional reference point for reconciling with the aggregator.

### **Channel:**

* What it is: The specific online platform where the order was placed (e.g., "zomato", "swiggy").
* Why it's useful: Shows you which platforms are generating your sales.

***

## **Order Status & Timing**

These fields tell you about the order's journey and when it was placed or expected.

### **Created At**

* What it is: The exact date and time when the order was first recorded in the system.
* Why it's useful: Crucial for tracking when orders come in and managing preparation times.<br>

### **Order State**

* What it is: The current status of the order (e.g., "Completed", "Pending", "Cancelled").
* Why it's useful: Gives you an immediate overview of how orders are progressing.<br>

### **Request Delivery Time:**

* What it is: The time the customer asked for the order to be delivered.
* Why it's useful: Helps you plan deliveries and meet customer expectations.<br>

### **Time Slot Start / Time Slot End:**

* What it is: If the customer chose a specific delivery window, these show the start and end times of that slot.
* Why it's useful: Important for managing scheduled orders and optimizing delivery logistics.

***

## **Payment & Financials**

These are critical fields for understanding the money side of your orders.

### **Payment Mode**

* What it is: How the customer paid (e.g., "payment\_gateway" for online payments, "aggregator" if the aggregator collects payment, "COD" for Cash on Delivery).
* Why it's useful: Helps with financial reconciliation and understanding payment preferences.<br>

### **Payment Transaction ID:**

* What it is: The unique ID for the payment transaction from the payment gateway or aggregator.
* Why it's useful: Essential for matching online payments with your bank statements.<br>

### **Coupon applied**

* What it is: Indicates if a coupon or promo code was used for the order. It will show "None" if no coupon was applied, or the coupon code itself.
* Why it's useful: Helps you track the effectiveness of your marketing promotions.<br>

### **Total Amount**

* What it is: The final amount the customer paid for the order, including all items, taxes, and charges, after any discounts.
* How it's calculated: Sub-total Amount + Total Taxes + Charges - Discount
* Why it's useful: This is the full amount the customer was charged.<br>

### Merchant Total

* What it is: The amount your restaurant is expected to receive from the order, after aggregator discounts but before aggregator commissions.
* How it's calculated: Sub-total Amount + Charges + Merchant Taxes - Merchant Discount
* Why it's useful: This is a key figure for understanding your gross revenue from each order before aggregator fees.<br>

### Sub-total Amount

* What it is: The total price of the items in the order before any discounts, taxes, or extra charges are added.
* How it's calculated: This is typically the sum of (Quantity × Unit Price) for all items. (You would usually find individual item quantities and prices in a separate 'Item-wise Transaction Report'.)
* Why it's useful: Shows the raw value of the food/items sold.<br>

### Discount

* What it is: The total amount of all discounts applied to the order.
* How it's calculated: This is the sum of Aggregator Discount + Merchant Discount.
* Why it's useful: Helps you see the overall impact of promotions.<br>

### Aggregator Discount

* What it is: The part of the discount that was funded by the online platform (aggregator).
* Why it's useful: Helps you understand who is covering the cost of promotions.<br>

### Merchant Discount

* What it is: The part of the discount that was funded by your restaurant.
* Why it's useful: Directly shows the cost of your own promotions.<br>

### Merchant Taxes

* What it is: Taxes that your restaurant is responsible for collecting and remitting.
* Why it's useful: For your tax reconciliation.<br>

### **Total Taxes**

* What it is: The full amount of all taxes applied to the order.
* Why it's useful: Provides a complete overview of taxes on the order.<br>

### Charges

* What it is: Any extra fees added to the order (e.g., delivery charges if you collect them, packaging fees).
* Why it's useful: Helps you understand additional revenue streams or costs passed to the customer.<br>

### Wallet credit amount

* What it is: The amount of the order paid using wallet credits (e.g., Swiggy Money, Zomato Wallet).
* Why it's useful: For payment reconciliation, especially with aggregator-specific wallet systems.

***

## **Customer & Store Details**

These fields provide information about the customer and your store location. Please note that customer details are suggested to the information passed by DSP. Most of the DSP/Aggregators do not share the customer details. Data might be dummy.<br>

### Customer Name

* What it is: The name of the customer who placed the order.
* Why it's useful: For customer service and understanding your customer base.<br>

### Customer ID

* What it is: A unique code for the customer on the online platform.
* Why it's useful: Helps track repeat customers (though often masked by aggregators for privacy).<br>

### Store Name

* What it is: The name of your restaurant location that fulfilled this order.
* Why it's useful: Essential for businesses with multiple locations to track performance per outlet.<br>

### Store ID

* What it is: A unique internal code for your store location.
* Why it's useful: For internal tracking of your multi-location operations.<br>

### Store ref ID

* What it is: The unique identifier for your store on the external ordering platform.
* Why it's useful: For cross-referencing your store details with the aggregator.<br>

### City

* What it is: The city where the order was placed or delivered.
* Why it's useful: For geographical sales analysis.

***

## **Fulfillment Details**

These fields explain how the order reached the customer.

### Fulfillment mode

* What it is: How the order was completed (e.g., "delivery", "pickup", "dine-in").
* Why it's useful: Helps you understand how customers prefer to receive their orders.<br>

### Delivery Type

* What it is: Specifies who handled the delivery (e.g., "Partner" for the aggregator's delivery fleet, "Self" for your own delivery staff).
* Why it's useful: Crucial for managing your delivery logistics and costs.

***

This "Order Transactions Report" is a powerful report for gaining insights into your online business. By understanding each field, you can make more informed decisions to grow your restaurant!

<br>


# Order Status Transitions Report

rider'sThe "Order Status Transitions Report" is a report for understanding the entire journey of every order. It's like a time-stamped log that helps you measure your operational efficiency, find bottlenecks, and understand the real reasons behind cancellations.

This guide explains each field in the report, helping you track an order's lifecycle and gain valuable insights into your business's performance.

## **Order Identification & Source**

These fields help you identify each order and where it came from.

### Order ID

* What it is: A unique number for each order in your system.
* Why it's useful: It's your main key for tracking and referencing specific orders for internal purposes and troubleshooting.

### Brand & Brand ID

* What it is: The name and unique internal code for your brand.
* Why it's useful: In a multi-brand operation, these fields are essential for segmenting your data and analyzing brand performance.

### Channel

* What it is: The specific online platform where the order was placed (e.g., "Zomato").
* Why it's useful: Shows you which platforms are generating your sales and how efficiently each channel performs.

### Store Name

* What it is: The name of your restaurant location that fulfilled the order.
* Why it's useful: Essential for businesses with multiple locations to track performance per outlet, especially for metrics like preparation time.

### Aggregator Order ID

* What it is: The unique order number provided by the online platform (aggregator).
* Why it's useful: This is crucial for cross-referencing orders with the aggregator's records if you need to talk to their support team.

### Fulfillment mode

* What it is: How the order was completed (e.g., "delivery," "pickup").
* Why it's useful: Helps you understand how customers prefer to receive their orders and segment your operational data based on fulfillment type.

## **Order Lifecycle & Timings**

These fields provide a clear timeline of key events, which are critical for measuring your operational efficiency.

### Order Creation Time

* What it is: The exact date and time the order was first created in your system.
* Why it's useful: This is the starting point for all other time-based metrics.

### Placed Time

* What it is: The time when the order was successfully placed on the aggregator's platform.
* Why it's useful: The time between "Order Creation Time" and "Placed Time" can reveal delays in order processing.

### Order Auto-Ack Time

* What it is: The time when the order was automatically acknowledged by your system.
* Why it's useful: This marks the beginning of the order's journey in your kitchen and is a key metric for measuring system automation.

### Order Ack Time

* What it is: The time a person manually acknowledged the order.
* Why it's useful: If used, this indicates how long it took for a human to review and accept an order.

### MFR Time

* What it is: The "Made For Rider" or "Made For Ready" time. This is the timestamp when the food was prepared and ready for pickup.
* Why it's useful: This is a crucial metric for measuring your kitchen's efficiency and how quickly your team can prepare an order.

### Dispatch Time

* What it is: The time the delivery rider picked up the order.
* Why it's useful: The time between "MFR Time" and "Dispatch Time" shows the rider wait time. A long wait time could indicate operational issues with the delivery partner.

### Order Completion Time

* What it is: The final timestamp when the order was marked as completed in your system.
* Why it's useful: This marks the end of the order's lifecycle and is used to calculate the total time taken for an order.

## **Cancellation Details**

These fields provide important information if an order was cancelled.

### Order Cancelled Time

* What it is: The specific date and time when the order was cancelled.
* Why it's useful: A value here indicates that the order did not complete successfully.

### Order Cancelled By

* What it is: Indicates who initiated the cancellation (e.g., "customer," "aggregator," "store").
* Why it's useful: This helps you understand the root cause of cancellations, which is crucial for reducing them in the future.

### Order Cancel Reason

* What it is: The reason provided for the cancellation.
* Why it's useful: Provides specific insights into why an order was cancelled, allowing you to address issues like long wait times or out-of-stock items.

This "Order Status Transitions Report" gives you a clear picture of how efficiently your business is running. By using these fields, you can pinpoint areas for improvement and ensure a smoother experience for your customers!


# Item-wise Order Transactions Report

The "Item-wise Order Transactions Report" is a powerful report that gives you a detailed look at every single item sold in your online orders. By understanding each column, you can unlock valuable insights to optimize your menu, track bestsellers, and improve your business.

This guide will walk you through each field, explaining its purpose and how you can use the data to make smarter business decisions.

***

## **Order and Item Identification**

These fields are your keys to tracking every transaction.

### Order ID

* What it is: A unique number for each order in your system. All items from the same order will share this ID.
* Why it's useful: This is your primary way to internally track and manage a specific order from start to finish.

### Order ref ID & Aggregator Order ID

* What it is: The unique order numbers assigned by the online platforms (like Swiggy or Zomato).
* Why it's useful: Use these IDs whenever you need to talk to the aggregator's support team about a specific order.

### Item ID & Item ref ID

* What it is: The unique codes for your specific menu item within your system and on the aggregator's platform.
* Why it's useful: These allow you to track the performance of individual products, identify bestsellers, and manage your inventory.

### Item Name

* What it is: The name of the product that was ordered by the customer.
* Why it's useful: Gives you a clear, at-a-glance view of what's being sold.

## **General Order Information**

These fields provide a high-level overview of the entire order.

### Brand & Brand ID

* What it is: The name and internal code of your brand.
* Why it's useful: If you have multiple brands, this helps you analyze performance for each one separately. (For single-brand reports, these may show as "None.")

### Channel

* What it is: The specific online platform where the order was placed (e.g., "zomato").
* Why it's useful: Helps you understand which platforms are driving the most sales for your restaurant.

### Order State

* What it is: The status of the order (e.g., "Completed," "Cancelled").
* Why it's useful: Essential for filtering your sales data to only see successfully completed orders.

### Store

* What it is: The name of your restaurant location that fulfilled the order.
* Why it's useful: Crucial for businesses with multiple locations to see which store is performing best.

### Order date-time

* What it is: The exact date and time the order was created.
* Why it's useful: Perfect for analyzing sales trends over time, like finding your busiest days or peak hours.

### City

* What it is: The city where the order was placed.
* Why it's useful: Helps you understand your sales by geographic location.

## **Financials and Item Details**

This is where you get into the numbers for each item.

### Quantity

* What it is: How many units of this specific item were ordered.
* Why it's useful: Allows you to calculate the subtotal for each item and see popular ordering patterns.

### Unit Price

* What it is: The base price of one unit of the item before any taxes or discounts.
* Why it's useful: Provides the foundation for all financial calculations.

### Total Taxes

* What it is: The total tax amount applied specifically to this item.
* Why it's useful: For tax reconciliation and understanding your tax liabilities.

### Total Charges

* What it is: Any extra fees applied to this item (e.g., packaging or customization charges).
* Why it's useful: Helps you track additional revenue from specific item charges.

### Total Price

* What it is: The final amount the customer paid for this single item, including discounts, taxes, and charges.
* Why it's useful: This is the bottom-line revenue you made from this item in the order.
* Total Price = Quantity × Unit Price + Total Taxes + Total Charges − Coupon Value

### Liability On

* What it is: This field indicates who is financially responsible for remitting a specific amount (like taxes).
* Why it's useful: It's a key detail for your accounting, confirming whether you or the aggregator are responsible for paying certain amounts to the government.

### Options & option\_ids

* What it is: The customizations or add-ons chosen by the customer (e.g., "extra cheese," "no onions") and their unique codes.
* Why it's useful: Gives you valuable insight into customer preferences and can help you create new menu items or promotions based on popular add-ons.

### Coupon applied & Coupon value

* What it is: The name and monetary value of any coupon applied to this item.
* Why it's useful: Helps you measure the direct cost and effectiveness of your promotions on a per-item basis.

This "Item-wise Order Transactions Report" is a powerful tool for gaining granular insights into your online business. By understanding each field, you can make more informed decisions to optimize your menu, promotions, and operations!


# Items Summary Across All Locations Report

The "Items Summary Across All Locations Report" is your go-to document! Unlike detailed transaction reports, this report gives you a high-level overview of your product performance, consolidating all the data from every location into one simple view.

This guide explains each field in the report, helping you quickly identify your top performers, understand their profitability, and make smarter decisions for your menu.

## **Item Identification**

These fields are how you identify each unique menu item in your report.

### Item ID

* What it is: The unique code for this specific menu item within your system.
* Why it's useful: This is your primary key for tracking the performance of each product. Use this ID for all internal analysis and menu management.

### Item Name

* What it is: The name of the product as it appears on your menu.
* Why it's useful: Provides a clear, human-readable name for each item, making it easy to identify bestsellers at a glance.

### Item ref ID

* What it is: The unique code for the item as it exists on the online platform (like Swiggy or Zomato).
* Why it's useful: This allows you to cross-reference the item with the aggregator's system for any reconciliation or catalog management tasks.

## **Consolidated Financials**

These fields provide a powerful summary of your financial performance for each item, aggregated from all your locations.

### Total Quantity

* What it is: The total number of units of this item sold across all orders and all locations during the report period.
* Why it's useful: This is your most important metric for sales volume. It immediately tells you which products are your most popular.

### Total Amount

* What it is: The total revenue generated by this item. This includes its base price, taxes, and any extra charges.
* Why it's useful: This number shows the overall financial contribution of each menu item to your business.

### Total Taxes

* What it is: The total amount of taxes collected from the sale of this item.
* Why it's useful: Essential for your accounting and tax reconciliation.

### Total Charges

* What it is: The total amount of any additional fees, like packaging or customization charges, that were applied to this item.
* Why it's useful: Helps you understand any extra revenue streams or costs associated with a product.

This "Items Summary Across All Locations Report" gives you a clear and consolidated view of your product performance. By using these fields, you can quickly identify your top-performing items and make strategic decisions for your menu and promotions!


# Option-wise Order Transactions Report

The "Option-wise Order Transactions Report" is a highly detailed report that gives you a breakdown of every single customization, add-on/Variant, and option chosen for each item in an online order.

By using this report, you can analyze customer preferences, track the performance of your add-ons/variant, and optimize your menu and pricing. This guide will help you gain granular insights into what your customers truly love and are willing to pay extra for.

***

## **General Order Information**

These fields provide the essential context for the entire order, just like in your other reports.

### Order ID

* What it is: The unique number for each order. All options and items belonging to the same order share this ID.
* Why it's useful: It's your primary key for finding all associated details for a specific order.

### Order date-time

* What it is: The exact date and time the order was placed.
* Why it's useful: Crucial for analyzing daily sales trends, finding peak ordering times, and managing preparation timelines.

### Order State

* What it is: The current status of the order (e.g., "Completed," "Cancelled").
* Why it's useful: Helps you filter out incomplete or cancelled orders for accurate sales analysis.

### Order Channel

* What it is: The online platform where the order was placed (e.g., "zomato").
* Why it's useful: Shows which platforms are driving your business and helps you compare performance across channels.

### Store ID & Store Name

* What it is: The unique code and name of the store that fulfilled the order.
* Why it's useful: This allows you to analyze sales and popular options for each of your restaurant locations.

## **Item Details**

These fields provide information about the main menu item that was customized.

### Item ID & Item Title

* What it is: The unique code and name of the main menu item (e.g., "Keema Pav (Mutton)").
* Why it's useful: This tells you which core product the customer is customizing.

### Item Quantity & Item Price

* What it is: The number of units of the main item ordered and its base price before any options were added.
* Why it's useful: This is the starting point for calculating the total cost of the item.

## **Option Details**

This is the most important section of the report, giving you the detailed breakdown of each customization.

### Option Ref ID & Option ID

* What it is: The unique code for the option on the aggregator's system and within your own system.
* Why it's useful: These allow you to track which individual customizations are the most popular and profitable.

### Option Title

* What it is: The name of the customization or add-on (e.g., "Mango Lassi (200 ML)," "1 PC Extra Bhatura," "No Achaar").
* Why it's useful: This clearly shows what the customer chose to add or modify.

### Option Price

* What it is: The cost of a single unit of the option.
* Why it's useful: Helps you understand which options generate additional revenue and which are simple modifications with no added cost.

### Option Quantity

* What it is: The number of units of this specific option that were selected.
* Why it's useful: Crucial for calculating the total cost of all options for an item.

### Option Group ID

* What it is: The unique code for the category of options this customization belongs to (e.g., a group for sauces, drinks, or spice levels).
* Why it's useful: Allows you to analyze which categories of options are the most popular with your customers.

This "Option-wise Order Transactions Report" is a treasure trove of information about your customers' preferences. By using these fields, you can make informed decisions to refine your menu and improve the customer experience!


# Menu Snapshot Across All Locations Report

The "Menu Snapshot Across All Locations Report" is an essential report for managing your menu. It provides a static, one-time view of all your menu items, showing their pricing, availability, and categorization across every one of your restaurant locations.

This guide explains each field in the report, giving you the clarity you need to ensure consistency and make informed decisions about your menu and pricing strategy.

## **Item Identification & Categorization**

These fields help you easily identify and organize each unique item on your menu.

### Item ID

* What it is: A unique code for this specific menu item in your internal system.
* Why it's useful: This is your primary key for tracking the item's details and performance across all platforms.

### Item Ref ID

* What it is: The unique code for the item as it exists on the online ordering platform (aggregator).
* Why it's useful: Allows you to quickly cross-reference the item with the aggregator's catalog for any updates or reconciliation.

### Item Title

* What it is: The name of the item as it appears on your menu.
* Why it's useful: Provides a clear, human-readable name for each item.

### Item Category

* What it is: The menu category the item belongs to (e.g., "Pizzas," "Tandoori Veg Starters").
* Why it's useful: Essential for organizing your menu and for analyzing which categories are most popular.

## **Pricing & Availability**

These fields provide crucial details about the item's cost and stock status.

### In-stock

* What it is: A simple indicator of whether the item is available for order. A value of "1" means it's in stock.
* Why it's useful: This helps you quickly see which items are active and ready for sale across your different stores.

### Price

* What it is: The base price of the item in your internal system.
* Why it's useful: This is your core pricing reference point for each item.

### Aggregator Price

* What it is: The price of the item as it is listed on the online ordering platform.
* Why it's useful: Allows you to compare your internal pricing with the prices that are displayed to customers on aggregator apps.

## **Store Details**

These fields connect each item to the specific store that offers it.

### Store ID & Store Ref ID

* What it is: The unique codes for your store location in your internal system and on the external ordering platform.
* Why it's useful: Essential for businesses with multiple locations to track menu items and pricing on a per-store basis.

### Store Name

* What it is: The name of your restaurant location that offers this menu item.
* Why it's useful: Provides a clear, human-readable name for each store.

### Brand Name

* What it is: The name of your brand that offers the item.
* Why it's useful: In a multi-brand operation, this field would be essential for segmenting your data by brand.

This "Menu Snapshot Across All Locations Report" is your go-to resource for a consolidated view of your menu. By using these fields, you can ensure consistency across all your locations, manage item availability, and maintain an effective pricing strategy.


# 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!


# Getting started

### What Is Meraki?

Meraki is UrbanPiper’s self-branded, commission-free online ordering platform for restaurants. It allows you to build and launch your own website and mobile app—complete with customizable menus, discounts, analytics, and marketing tools—without relying on third-party aggregators.

#### **Why choose Meraki?**

* **No commission fees**: Keep more revenue by owning the order flow.
* **Full brand control**: Tailor store design, menus, and customer experience under your own identity.&#x20;
* **Valuable customer insights**: Access customer and order data, enabling loyalty programs and marketing automation (email, SMS, social).


# Configuring a Custom Domain

Configuring your DNS records might sound technical, but it's a crucial step to ensure your customers can find your website at the correct address. \
\
This guide will walk you through the process of setting up your custom domain with a few commonly used domain providers.

### Steps to Configure

* **Log in to Atlas**
  * Go to the Atlas Dashboard and log in with your admin credentials.
* **Open Meraki Editor**
  * From the left menu, select **Meraki → Editor**.
* **Add a Custom Domain**
  * Navigate to the **Domain** section.
  * Click **Add Custom Domain**.
  * Enter your desired domain name (e.g., `order.yourbrand.com`).
* **Get DNS Records**

  * After entering the domain, Atlas will generate the required **DNS records**.

  <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FCqBo1ss4hJbg8WmGlKOa%2Fimage.png?alt=media&amp;token=bdac71f7-e542-421f-bb6b-9f44df7470d8" alt=""><figcaption></figcaption></figure>

  * Each record will include:
    * **Name**
    * **Type** (CNAME, A, etc.)
    * **Value**
* **Update Your DNS Provider**
  * Log in to your DNS provider’s portal (e.g., GoDaddy, NameCheap).
  * Add the DNS records exactly as shown in Atlas.
  * Save and apply the changes.
* **Verify Setup**
  * Return to Atlas → Domain section.
  * Once DNS records propagate (can take up to 24–48 hours), your domain will be verified and connected.

***

{% hint style="warning" %}

* Ensure you only add the records provided in Atlas.
* DNS propagation time varies depending on your provider.
  {% endhint %}

Please refer to your DNS provider's help portals for detailed steps on configuring the above records.\
\
[GoDaddy](https://www.godaddy.com/en-in/help/manage-dns-records-680)\
\
[NameCheap](https://www.godaddy.com/en-in/help/manage-dns-records-680)\
\
[Hostinger](https://support.hostinger.com/en/articles/4738777-how-to-manage-cname-records)<br>


# Configuring Payment Gateway

You can configure payment gateways on Meraki to enable online payments for your customers.\
\
Multiple payment methods, such as credit/debit cards, UPI, wallets, and COD, can be supported depending on the gateway

### Steps to Configure

* **Login to Atlas**
  * Go to the Atlas Dashboard and log in with your admin credentials.
* **Navigate to Payment Settings**
  * From the left-hand menu, select **Meraki → Payments**.
* **Add a Payment Gateway**

  * Click **Add Gateway**.
  * Select your preferred payment gateway from the list (e.g., Stripe, Razorpay, PayU, Paytm, etc.).

  <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FGSu4BKygsUiX2WukP4ul%2Fimage.png?alt=media&amp;token=4c9e3c2e-618d-4e82-b743-a3df91bb2386" alt=""><figcaption></figcaption></figure>
* **Enter Gateway Credentials**
  * Each gateway requires specific credentials (e.g., API Key, Secret Key, Merchant ID).
  * You can obtain these from your payment gateway provider’s dashboard.
  * Paste the credentials into the respective fields in Atlas.
* **Choose Payment Options**
  * Enable/disable the methods you want to accept:
    * **Online Payments** (UPI, cards, net banking, wallets)
    * **Cash on Delivery (COD)**
    * **Wallets or Loyalty Points** (if configured)
* **Save & Test Configuration**
  * Save your gateway settings.
  * Perform a **test transaction** to ensure the integration works correctly.

***

{% hint style="info" %}

### Notes

* Some gateways are **region-specific** (e.g., Stripe for international, Razorpay/PayU/Paytm for India).
* You can configure gateways **globally** for all outlets, or **per outlet** if needed.
* Ensure your payment provider account is in **live mode** (not test mode) before going live.
  {% endhint %}

### 📊 Regional Payment Gateway Mapping

| Payment Gateway  | India | MENA | KSA | UK | LATAM | USCAN |
| ---------------- | ----- | ---- | --- | -- | ----- | ----- |
| RAZORPAY         | ✅     | ❌    | ❌   | ❌  | ❌     | ❌     |
| PAYMENTOS        | ❌     | ✅    | ✅   | ❌  | ✅     | ✅     |
| PHONEPE          | ✅     | ❌    | ❌   | ❌  | ❌     | ❌     |
| INSTAMOJO        | ✅     | ❌    | ❌   | ❌  | ❌     | ❌     |
| PAYSTACK         | ❌     | ✅    | ✅   | ✅  | ❌     | ❌     |
| PAYTABS          | ❌     | ✅    | ✅   | ❌  | ❌     | ❌     |
| STRIPE           | ✅     | ✅    | ✅   | ✅  | ✅     | ✅     |
| PAYTMBLINK       | ✅     | ❌    | ❌   | ❌  | ❌     | ❌     |
| PAYTABS\_V2      | ❌     | ✅    | ✅   | ❌  | ❌     | ❌     |
| PAYULATINAMERICA | ❌     | ❌    | ❌   | ❌  | ✅     | ❌     |
| MERCADOPAGO      | ❌     | ❌    | ❌   | ❌  | ✅     | ❌     |
| FREEDOMPAY       | ❌     | ❌    | ❌   | ✅  | ❌     | ✅     |

\ <br>


# Google Maps

Google Maps is integrated into multiple parts of your Meraki website to provide location-based services.

***

### Where Google Maps is Used

* **Store Selection**
  * When a customer searches for a location, the system checks if a store is available within the selected radius and assigns it.
  * All available stores are also displayed on a map on the **Store Locator** page.
* **Adding or Updating Customer Address**
  * Customers can search for their address using **autocomplete**.
  * Alternatively, they can drag a pin on the map to select their exact location.
* **Order Success Page**
  * A **static map** is displayed on the order confirmation page.
  * This uses UrbanPiper’s internal Maps API key (not the merchant’s key).

***

### Prerequisites for Maps to Work

If you are using **your own Google Maps API key**, ensure the following APIs are enabled in your **Google Cloud Platform (GCP) project**:

* ✅ **Maps JavaScript API**
* ✅ **Places API**
* ✅ **Geocoding API**

> ⚠️ Without these APIs enabled, Maps-related functions on your website will not work.

***

### Troubleshooting Maps Issues

If Maps aren’t working on your website:

#### Step 1: Inspect the Website

* Go to your website’s Menu page.
* Right-click → **Inspect**.
* Open the **Network** tab.
* Type `maps` in the filter bar to view Maps-related requests.

#### Step 2: Test Store Selector

* Open the **Fulfilment Selector** (store selection popup).
* Search for a location.

#### Step 3: Check for Errors

Look at the network logs and identify common issues:

* **Service not enabled** → Errors mentioning “places not enabled” or “geocode not enabled.”
* **Referrer restrictions** → Errors mentioning “referrer” (your domain is missing in the GCP key’s allowed list).
* **Billing not enabled** → Errors mentioning “billing” (your GCP project billing setup is incomplete).

📌 Reference: [Google Maps API error messages](https://developers.google.com/maps/documentation/javascript/error-messages#api-not-activated-map-error)

***


# Configuring Banner Images

The banner **images** are large, prominent visuals displayed on your website or app to attract attention.\
\
They are commonly used for:

* 🔹 **Marketing & Promotions** — showcase offers, discounts, or new launches
* 🔹 **Branding** — display your brand’s vibe with logos, slogans, or themed visuals
* 🔹 **Navigation** — guide users to specific sections via sliders or clickable banners

***

### Common Traits of Banner Images

* Wide and horizontal format
* Can include **text overlays** (e.g., *“50% OFF”*, *“Order Now”*)
* Used on **homepages, category headers, sliders, carousels, or in email campaigns**

***

### How to Configure Banner Images in Atlas

* **Upload Image**
  * Go to **Atlas → Meraki → Gallery**.
  * Click **Upload Image**.
* **Assign for Web or App**
  * After uploading, click **Settings** for the image.
  * In the **Image Type** dropdown:
    * Select **Web Banner** or **Mobile Web Banner** for website banners.
    * Select **App Banner** for app banners.
* **Location Group Assignment (Optional)**
  * In **Image Settings → Location Group**, select a location group to display banners only for those outlets.
  * If no location group is selected → the banner will appear for **all locations by default**.
* **Add a Clickable Link (Markup)**

  * In **Markup field**, you can add HTML to hyperlink the banner image to a specific URL.

  **Example:**

  ```html
  <div style="display:inline-block; width:100%; padding:19px 105px 58px;">
    <a href="YOUR-WEBSITE-URL" 
       style="left:1%; position:absolute; top:1%; width:1000px; height:200px; padding-right:10px; padding-left:10px;">
    </a>
  </div>
  ```

  📌 Note:

  * Works only for **Web**.
  * For **App banners**, hyperlink requests must be submitted to the UrbanPiper Support Team.
  * No need to **publish the menu/site** after adding/editing banners.
  * Allow **\~5 minutes** for updates to reflect.

***

### Recommended Aspect Ratios

* **Web Banners** → 1.6:1 to 1.8:1
* **Mobile Banners** → 2:2


# Setting up Your Own Mask ID for SMS

This guide will help you configure and use a **custom Mask ID** for SMS communications (OTP, order updates, and marketing campaigns) on the UrbanPiper Meraki platform.

### Register & Approve SMS Templates on the DLT Portal

* Log in to your **DLT portal** (Vodafone, Jio, Airtel, etc.).
* Create all required **SMS templates** under your registered entity.
* Submit templates for approval.
* Once approved, note down:
  * **Template ID**
  * **PE ID (Principal Entity ID)**

📌 These details are provided by TRAI after approval.

### Complete the PE–TM Bonding

To link your entity with UrbanPiper’s SMS service provider (**Gupshup**):

* Log in to your DLT portal.
* Bond your **PE ID** (Principal Entity ID) with the following **Gupshup Telemarketer IDs**:

| Operator | Gupshup TM ID |
| -------- | ------------- |
| Vodafone | (provide ID)  |
| Jio      | (provide ID)  |
| Airtel   | (provide ID)  |

📌 This **PE–TM bond is mandatory** before templates can be whitelisted on Gupshup’s platform.

### Share Approved Templates with UrbanPiper Support

* Once bonding is complete, email **<support@urbanpiper.com>** with:
  * Your **PE ID**
  * List of all **approved templates** (with Template IDs)
* UrbanPiper Support will configure the templates in the backend.
* The team will initiate the whitelisting process with Gupshup.

### Gupshup Whitelisting

* UrbanPiper Support will coordinate with Gupshup to whitelist your templates.
* Once approved, your **custom Mask ID** will be active.
* You can now send all SMS (OTP, order updates, campaigns) via Meraki using your Mask ID.

### Important Reminders

* ✅ **PE–TM bonding is compulsory** before template whitelisting can begin.
* ✅ SMS content **must exactly match** the approved DLT template. Any mismatch can lead to **delivery failures**.
* ✅ Keep your **Template IDs and PE ID** safe — you’ll need them for support and future updates.


# Configuring Coupons

### 📖 Types of Coupons in Meraki

Meraki provides two types of discounts you can configure:

### Cash Discount

* Applies a fixed amount discount on the order subtotal.
* You can target specific customer groups using the Rules section.
* Note: Cash discounts cannot be applied to specific items — it apply to the total bill value before taxes and delivery.

A discount is applied as a percentage of the order subtotal or on specific items, with two action types:

**Item Specific**

* Apply a percentage discount on selected items or the entire order subtotal.
* You can choose which items this discount should apply to.

**Buy X Get Y (BXGY) Specific**

* Create Buy X, Get Y Free/Discounted offers.
* Requires two lists:
* Items to Check: Items the customer must purchase.
* Items to Discount: Items that will receive the discount after qualifying conditions are met.

### 📌 Mandatory Coupon Rules

While setting up any coupon type in Meraki, these rules must be configured:

* Redemption Code:
* Must be entered manually.
* If left blank when required, the coupon will not work.
* Date & Time Validation:
* Always set the start date and end date/time for your coupons.
* Bulk Coupons:
* If using bulk coupon generation, once generated, ensure you remove the Redemption Code field from the main coupon setup.
* Otherwise, if you enable the suggestion toggle the redemption will be visible on the Coupons list & it won’t apply.

### 📌 Common Use Cases & Configuration Scenarios

Below are some typical promotional setups you can create using Meraki Coupons:

#### 📍 BOGO (Buy One Get One Free) — Same Item

Example: Buy 1 Dosa, Get 1 Dosa free

| Parameter                   | Value |
| --------------------------- | ----- |
| Items to Check              | Dosa  |
| Items to Discount           | Dosa  |
| Number of Items to Check    | 1     |
| Number of Items to Discount | 1     |
| Max No of Discounts         | 1     |
| Coupon Value                | 100%  |

Note:\
If both items to check and to discount are the same and multiple items are in the cart (e.g., Dosa ₹200 and ₹150), the lower-priced item (₹150) will get the discount.

#### 📍 Buy X Get Y Free (Different Items)

Example: Buy Chicken Biryani, Get Gulab Jamun free

| Parameter                   | Value           |
| --------------------------- | --------------- |
| Items to Check              | Chicken Biryani |
| Items to Discount           | Gulab Jamun     |
| Number of Items to Check    | 2               |
| Number of Items to Discount | 2               |
| Max No of Discounts         | 2               |
| Coupon Value                | 100%            |

Note:\
The 100% discount will apply to the price of Gulab Jamun.

#### 📍 B3G2 (Buy 3 Get 2 Free — Different Items)

Example: Buy 3 Chicken Biryani, Get 1 Gulab Jamun and 1 Coke free

| Parameter                   | Value             |
| --------------------------- | ----------------- |
| Items to Check              | Chicken Biryani   |
| Items to Discount           | Gulab Jamun, Coke |
| Number of Items to Check    | 3                 |
| Number of Items to Discount | 2                 |
| Max No of Discounts         | 1                 |
| Coupon Value                | 100%              |

{% hint style="info" %}
Note:\
If multiple items are present, Gulab Jamun and Coke (e.g. ₹50 and ₹20) will be discounted, totaling ₹70.
{% endhint %}

### 📌 How to Set Coupon Value

* In both Item Specific and BXGY Specific coupon types, you can configure discount percentages as required (e.g., 10%, 20%, 50%, 100%).
* For BOGO and free item promotions, always set the Coupon Value to 100% for the desired discount items.

### 📌 Important Notes

* Cash Discount: Applies on the order subtotal only, not item-specific.
* Percentage Discounts: Can be applied to:
* The entire order subtotal
* Specific items, BXGY offers (Buy X, Get Y) configurations<br>


# Manage Campaigns

With UrbanPiper's Meraki platform, you have the tools to create powerful, personalized campaigns that truly connect with your customers. The Meraki suite allows you to send dynamic messages across multiple channels, helping you drive engagement, build loyalty, and grow your business.

### **The Power of Personalized Messages 🎯**

Meraki's dynamic messaging is the key to making your campaigns stand out. Instead of sending a generic blast, you can use placeholders to automatically insert customer-specific information, making every message feel personal and relevant.

Here are the placeholders you can use to create dynamic messages:

| Placeholder               | What it does                                         | Example                                                             |
| ------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------- |
| `{{user_name}}`           | Inserts the customer's first name.                   | "Hi **{{user\_name}}**, a surprise is waiting!" 👋                  |
| `{{user_points}}`         | Shows the customer's current loyalty points balance. | "You have **{{user\_points}}** points to redeem!" ✨                 |
| `{{user_wallet_balance}}` | Displays the customer's current wallet balance.      | "Your wallet has **{{user\_wallet\_balance}}** waiting for you." 💰 |
| `{{user_phone}}`          | Inserts the customer's phone number.                 | "Reach out to us at **{{user\_phone}}** if you have questions." 📞  |
| `{{user_email}}`          | Inserts the customer's email address.                | "Your confirmation has been sent to **{{user\_email}}**." 📧        |

### **Setting Up Your Campaigns ⚙️**

The Meraki platform supports a variety of campaign types, giving you the flexibility to reach your customers wherever they are.

### **📱 SMS Campaigns**

SMS campaigns are a direct and effective way to communicate with your customers. To ensure your messages are compliant and delivered correctly, a few steps are required to get started.

* **Register Your Templates on DLT:** Before sending any message, you must get your templates approved on a DLT portal (e.g., Vodafone, Jio, Airtel). Once approved, you will receive a **Template ID** and a **PE ID** (Principal Entity ID). Be sure to save these!
* **Bond Your Account:** On your DLT portal, you need to "bond" your PE ID with our SMS provider, Gupshup, by adding the following Telemarketer (TM) IDs to your account:
  * **GS Digital Technology Private Limited:** 1002407114627154
  * **Lotus Transforms Private Limited:** 1702157390412895696
  * **Gupshup Technology India Pvt. Ltd.:** 120210000037
* **Share with UrbanPiper:** Once your templates are approved and bonded, email your **Template ID** and **PE ID** to our support team. Our team will then work with Gupshup to get your templates whitelisted in our system.
* **Launch Your Campaign:** After whitelisting is complete, you can create and launch your personalized SMS campaigns directly from the Meraki platform!

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXctR3c8EYyZRD4nvhmdLHKn2qcdm7XheqoxJ7iZUgPFcrfKSfjET83O7VZOMZvUPl4baC74TCL-uzL54WcVlwNouBuyRvi8038JiMj6xNcFkYWp2nP2CPP3JiXyQpI6MRAtfdc?key=O82WMBT15h7YxbcFl1bvF-Uu" alt=""><figcaption></figcaption></figure>

### **📧 Email Campaigns**

Email campaigns give you the freedom to create visually rich and branded content. Follow these steps to ensure your emails are ready to send.

* **Design Your Email:** Your email content must be in **HTML format**. If you're using a design tool, simply export your final email as a single HTML file.
* **Host Your Images:** For images to appear correctly for all recipients, they must be hosted on a web server. The easiest way to do this is to upload your images via **Atlas** → **Meraki** → **Gallery** to get a public URL for each one.
* **Embed in Your HTML:** In your HTML file, embed your images using the public URLs you just generated. The `src` attribute for each image must point to this public link.
* **Send a Test Email:** Before sending to your entire list, **always** send a test email to yourself! This is a critical step to ensure your email looks correct and is delivered properly.<br>

```
Example HTML
<!DOCTYPE html>
<html>
<head>
<title>Campaign Image</title>
</head>
<body>
<img src="https://cdn.urbanpiper.com/media/gallery_images/2022/12/13/New_Logo.png" alt="Campaign Image">
</body>
</html>
```

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXebLbjZ9Qe5k3sNbNg9HJn2OouzIYBM9Hn1vUe1zSzHU0y8pQh2KCCss0QHfdU7iaajSMX5ctCWhhTEqXFCbH-DFVT4ElmH-AlK64LtXIwwT-7uyUYPB-UZazt4pLnMypKXNB_f?key=O82WMBT15h7YxbcFl1bvF-Uu" alt=""><figcaption></figcaption></figure>

### **🔔 App Push Notifications**

Push notifications are a fantastic way to engage with your most active and loyal customers who have your app installed. They are a direct line of communication that can instantly get your message across.

1. **Define Audience & Message:** Decide who you want to reach and what you want to tell them. Remember that notifications will only be received by users who are logged into your app.
2. **Create Your Campaign:** Create your push notification campaign directly within the Meraki platform, define your target audience, and set the message content.
3. **Launch:** You're ready to send a quick, impactful message to your app users!\ <br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FaKVcAYjb8ouMW5P7M6sG%2Fimage.png?alt=media&amp;token=455d598e-5e36-4df5-b318-f5aa377df7f5" alt=""><figcaption></figcaption></figure>