Order Transactions Report: Your Guide to Online Sales Data
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.
1. 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.
2. 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.
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.
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.
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.
3. 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.
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.
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.
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.
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.
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.
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.
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.
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.
Merchant Taxes:
What it is: Taxes that your restaurant is responsible for collecting and remitting.
Why it's useful: For your tax reconciliation.
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.
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.
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.
4. 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.
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.
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).
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.
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.
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.
City:
What it is: The city where the order was placed or delivered.
Why it's useful: For geographical sales analysis.
5. 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.
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!
Last updated
Was this helpful?