SnapDabba Admin Panel Operations Manual

Food Delivery + Tiffin Subscription + Fitness Super App

1. Admin Panel At A Glance

SnapDabba admin is the control center for four connected operations: on-demand food orders, tiffin subscriptions, restaurant or kitchen management, and the new Fitness Super App layer. The same panel also manages payments, riders, customer accounts, promotions, reports, and system configuration.

Dashboard gives management a fast view of orders, restaurants, deliverymen, revenue, and operational alerts.

POS is used when staff need to create an order manually on behalf of a customer.

Subscription (Tiffin) manages meal plans, delivery slots, and subscription customers.

Fitness Super App controls wellness goals, meal plans, gyms, dietitians, combo plans, leads, and the Healthy Mode experience.

Business Settings and System Settings control branding, payments, notifications, policies, and app behavior.

Recommended working order for a normal day is: Dashboard -> Orders -> Subscription (Tiffin) -> Restaurants -> Foods -> Deliverymen -> Promotions -> Reports -> Settings only when configuration changes are required.

2. Access, Login, and Demo Environment

Login

Open https://masteradmin.snapdabba.in/login/admin.

Enter the admin email and password assigned to your team.

Complete the captcha shown on the login page.

After login, confirm the left sidebar and the dashboard cards load correctly.

Use the profile menu at the top-right to log out when the shift is complete.

Current demo data loaded

Demo delivery zone is DLF Phase 3, Gurugram with a 5 KM coverage radius.

Demo kitchens are SnapDabba Kitchen - U Block, SnapDabba Kitchen - Nathupur, and SnapDabba Kitchen - Cyber City.

Seeded plan prices are 1 Day Trial INR 199, 7 Days INR 1249, 15 Days INR 2399, and 30 Days INR 4599.

Sample subscription foods include Veg Power Thali, Paneer Millet Lunch Box, Jain Comfort Dabba, Chicken Brown Rice Bowl, and Non-Veg Muscle Gain Thali.

Reloading demo data

If the demo panel needs to be reset, use the SnapDabba seeder command from the Laravel project root.

3. Sidebar Menu Map

4. Daily Operations Workflow

Opening shift checklist

Log in and check Dashboard for pending orders, scheduled orders, failed payments, and refund requests.

Open Subscription (Tiffin) and review active subscriptions, today's lunch orders, today's dinner orders, and any paused or overdue accounts.

Confirm at least one kitchen branch and one rider are active in the DLF Phase 3 zone.

Check banner, coupon, or notification campaigns only if a marketing push is planned that day.

Mid-shift operations

Move standard food orders through pending -> accepted -> processing -> out for delivery -> delivered.

Use Subscription Orders to confirm tiffin meal generation and rider assignment.

If support receives a phone order, create it through POS instead of manually inserting records elsewhere.

Watch rider and kitchen load before enabling new offers or same-day campaigns.

End-of-day routine

Review undelivered, cancelled, failed, and refund-related orders.

Check rider cash collection and any restaurant or deliveryman disbursement tasks.

Review reports if management needs daily revenue, order, or subscription summaries.

Log out after saving any settings or catalog changes.

5. Dashboard, Search, and Global Navigation

The dashboard is your command center. Use it to spot spikes in pending orders, revenue changes, customer growth, and restaurant performance before diving into individual modules.

The top search bar helps jump across panel pages more quickly.

Use badges and counters beside menu items to understand backlog volume.

Most list screens support search, date filters, status filters, and export options.

If a page looks stale after a large data import or after seeding, refresh the browser once before assuming the save failed.

6. Order Management

Order list screens

Open Sidebar -> Order Management -> Orders. Each order status has a dedicated filtered page, including All, Scheduled, Pending, Accepted, Processing, Food On The Way, Delivered, Canceled, Failed, Refunded, Dine In, and Offline Payments.

Use the search bar to search by order ID, customer, or related data.

Use export to download the current filtered list.

Use the eye icon to open the order detail page.

Use the restaurant name link to jump to the branch record directly.

How to process a normal food order

Open the Pending Orders screen and click the eye icon for the target order.

Verify customer details, restaurant, items, payment mode, delivery address, and any add-ons or notes.

If the order is valid, move it to Accepted.

When the kitchen starts work, move it to Processing.

When handed to a rider, move it to Food On The Way or the equivalent dispatch status.

Mark Delivered only after rider confirmation or system proof is available.

Payment checks inside orders

Paid orders show a paid payment status and can be fulfilled normally.

COD orders should only be marked settled after cash collection is confirmed.

Offline payment orders need manual verification against the uploaded proof or finance confirmation.

Failed digital payments should not be pushed into fulfilment until resolved.

Refunds and problem orders

Use Sidebar -> Order Management -> Order Refunds or the Refunded / Refund Request screens to review refund cases.

Check item issue, customer complaint, delivery failure, or duplicate payment reason before approving.

When in doubt, confirm with both customer support and the restaurant side before refunding a delivered order.

7. POS: Creating Orders Manually

Use Sidebar -> POS when support or front-desk staff need to create an order on behalf of a customer.

Select the delivery zone first. In the demo environment, use DLF Phase 3 - 5 KM Delivery Zone.

Select the restaurant or kitchen branch.

Use the category and product area to search or browse items.

Open the item quick view if you need to choose variations or add-ons.

Add items to the cart, then choose the customer and the delivery address if it is a delivery order.

Select the order type: Take Away or Home Delivery.

Choose the payment method and place the order.

If no zone is selected, restaurant and product data may not populate correctly.

If the customer has no saved address, add or select an address before placing a delivery order.

Use POS for real manual orders only. Do not use it for mass demo-data creation.

8. Subscription (Tiffin) Management

The SnapDabba tiffin module sits in Sidebar -> Subscription (Tiffin). It is separate from one-time orders, but still uses the main customer, restaurant, rider, and payment ecosystem.

What the page contains

KPI cards for subscription revenue, active subscribers, and plan counts.

Plan Management for 1 Day Trial, 7 Days, 15 Days, and 30 Days.

Delivery Slots for Lunch and Dinner windows.

Subscription Management table with customer, restaurant, plan, remaining credits, and status.

Managing plans

Open the Plan Management form.

Enter plan name, duration in days, number of credits, and price.

Enable Veg and Non-Veg availability according to the plan design.

Save the plan and confirm it appears in the list table.

Current demo plans use credit-based pricing: 1 Day Trial INR 199, 7 Days INR 1249, 15 Days INR 2399, and 30 Days INR 4599.

Managing delivery slots

Lunch is seeded as 12:00 PM to 3:00 PM.

Dinner is seeded as 7:00 PM to 10:00 PM.

Cutoff time is 11:00 PM in the demo setup.

Use slot editing when operations want to change delivery windows without changing the plan itself.

Working with subscriptions

Active means the customer still has usable credits and the subscription can generate delivery orders.

Paused means deliveries are blocked for the selected period.

Cancelled means the plan is no longer serving deliveries.

Completed or expired means credits or duration are finished.

Open the subscription record from the list screen.

Review customer, restaurant, slot, plan, credits, and delivery log.

Use manual actions for pause, resume, cancel, or extend when support approves the change.

Check generated subscription orders to confirm daily order generation is working.

9. Restaurants, Kitchens, and Zones

Restaurants in SnapDabba

For SnapDabba operations, restaurants can also represent your own kitchens or micro-branches. In the demo setup, the restaurant list is used as the kitchen branch directory.

SnapDabba Kitchen - U Block

SnapDabba Kitchen - Nathupur

SnapDabba Kitchen - Cyber City

Adding or editing a kitchen branch

Go to Sidebar -> Restaurant Management -> Restaurants -> Add Restaurant.

Create the vendor profile if needed, then fill the restaurant or kitchen details.

Assign the correct zone, address, phone, email, timings, and order model.

Enable delivery, take away, food section, and subscription support where required.

Save and confirm the branch appears in the restaurant list.

Use the restaurant list to suspend or reactivate a branch during maintenance.

Use cuisine only if you want the customer-side restaurant discovery to filter by cuisine.

Bulk import and export are useful only when a large catalog or many branches are being migrated.

Delivery zone management

Open Sidebar -> Restaurant Management -> Zone Setup to create or edit delivery areas.

The current demo zone is DLF Phase 3, Gurugram with a 5 KM radius.

Zone settings control shipping charge, minimum charge, COD limit, and restaurant-rider coverage.

A restaurant or rider outside the intended zone can break customer-side availability and dispatch logic.

10. Food Catalog Management

Categories and subcategories

Open Sidebar -> Food Management -> Categories -> Category to create top-level groups.

Use Sub Category when a parent category needs finer segmentation.

Only create categories that customers or operators actually use; too many categories make search harder.

Add-ons

Use Sidebar -> Food Management -> Addons to create optional extras such as Protein Salad, Buttermilk, or Boiled Eggs.

Add-ons are charged separately from the main item price.

Use add-ons for extras. Use variations when the item itself changes in size or option structure.

Creating or editing a food item

Open Sidebar -> Food Management -> Foods -> Add New or open an item from the list for editing.

Select the restaurant or kitchen branch, category, and subcategory.

Enter name, descriptions, price, tax, discount, image, and availability fields.

Set Food Type as Veg or Non-Veg.

Select relevant add-ons if the item supports extras.

Save and verify the item appears in the food list.

Single Order and Subscription Meal mode

Single Order remains the normal food-delivery flow and stays enabled for standard ordering.

Subscription Meal is a separate checkbox used for tiffin-ready items.

When Subscription Meal is enabled, fill Subscription Meal Price carefully.

Use realistic subscription base pricing so the app can calculate 1 day, 7 day, 15 day, and 30 day plan display correctly.

Nutrition, allergy, halal, and food metadata

Nutrition can be used to mark protein, healthy, diet, or similar tags.

Allergy Ingredients should be filled for items containing common triggers.

Use the Halal toggle only when the kitchen and sourcing actually support it.

These fields help both customer communication and future wellness filtering.

How to edit size, variation, and option pricing

Food sizes are managed through the Food Variations area inside the food form.

Open the item in edit mode.

Scroll to the Food Variations section.

Create a Variation Name such as Size, Bread Choice, Protein Portion, or Spice Level.

Choose Variation Selection Type: Single when the customer can choose only one option, or Multi when multiple options are allowed.

Set minimum and maximum selection counts when Multi is used.

Add option rows with Option Name, Option Price, and Total Stock.

Save the item and test the option from POS or the customer app.

Use variations for structural choices inside the item.

Use add-ons for optional extras that do not redefine the main item.

If an option is removed, re-check stock and price logic before saving.

11. Promotions, Coupons, Banners, and Notifications

Coupons

Use Sidebar -> Promotions Management -> Coupons to create discount codes.

Coupon form supports title, multilingual title fields, code, coupon type, date range, total uses, customer limit, minimum purchase, maximum discount, and amount or percentage setup.

Use restaurant-linked or zone-linked coupons only when operations want limited campaigns.

After saving, verify the coupon appears in the coupon list and search finds it by title or code.

Banners and promotional placements

Banners are used for customer app or web hero placements.

Promotional Banners and Advertisement screens are used for more specific placements or campaigns.

Always verify the target restaurant, item, or page link before enabling a banner.

Push Notification page

Use Push Notification for one-time promotional or operational pushes.

Target the correct audience and write a short, action-oriented title and message.

Do not rely on push alone for critical payment or order events; system notifications should also be configured.

Notification channels and messages

Open Sidebar -> System Settings -> Notification Channels to control how notifications are delivered.

The screen has separate tabs for Admin, Restaurant, Customers, and Deliveryman.

Each notification topic can be toggled across Push, Email, and SMS.

If a channel is disabled for a specific topic, that user type will not receive that event by that channel.

Open Notification Messages to control message content and routing rules.

Email templates

Open Sidebar -> Business Settings -> Email Template.

User, admin, and restaurant templates exist for core order, refund, and SnapDabba subscription events.

Edit copy, branding, and email logos carefully, then send a test before using in production.

12. Customers, Wallet, Loyalty, and Riders

Customer management

Customer List shows registered users and gives access to the customer profile.

Wallet -> Add Fund lets support add or correct stored balance.

Wallet -> Bonus is useful for promotional credits or operational recovery.

Loyalty Point Report shows retention-related earning and usage patterns.

Subscribed Emails stores marketing opt-ins.

Deliveryman management

Create vehicle categories first if the rider fleet needs segmentation.

Create shifts if rider scheduling is managed centrally.

Use Deliveryman -> Add New Deliveryman to onboard a rider manually.

Use Deliveryman List to activate, suspend, review, or inspect current order load.

Use Bonus and Incentive pages for payout adjustments and incentive workflows.

Assign riders to the correct zone so they can receive relevant orders.

Drivers should only see delivery data, not customer medical or private health details.

13. Payments, Refunds, Disbursement, and Reports

Payment setup

Open Sidebar -> Business Settings -> Business Setup -> Payment Setup.

Cash On Delivery controls COD availability.

Digital Payment controls online payment methods.

Offline Payment is used when customers submit proof manually.

Partial Payment methods can be enabled only when the underlying payment methods are enabled.

Collect cash and withdrawals

Collect Cash helps reconcile cash from restaurants or riders where applicable.

Restaurant Withdraws and DeliveryMan Payments are used for payout requests and settlement workflows.

Withdraw Method defines the payout channels available to partners.

Reports to review regularly

Most report screens support date filtering and export. Always set the date range before drawing conclusions from totals.

Cross-check report totals against order and payment screens when reconciling abnormal spikes.

14. Business Settings and System Settings

Business Setup tabs

Logo and favicon

Open Sidebar -> Business Settings -> Business Setup -> Business Settings tab.

Update the business logo in the Basic Information section.

Upload the website favicon in the same business setup area.

Save information and hard refresh the browser if the old icon is cached.

Notification, email, SMS, and Firebase

Email configuration lives in the mail settings and email template area.

SMS Module and Firebase OTP are available under 3rd Party and Configurations.

Firebase Notification setup is used for push delivery in the apps.

Notification Channels decide who receives what. Notification Messages decide what the message says.

Other settings operators should know

App & Web Settings controls application behavior and display rules.

Login Setup controls login page behavior and verification options.

Invoice Setup controls invoice branding and invoice logo behavior.

Pages & Social Media controls Terms, Privacy Policy, About Us, Refund Policy, Shipping Policy, Cancellation Policy, and social links.

Analytics Script is where marketing or analytics tags are installed.

Page Meta Data is used for SEO-related titles and descriptions.

Landing Page Settings controls admin or React landing content where enabled.

15. Fitness Super App Module

Open Sidebar -> Fitness Super App. This is the admin control center for the Healthy Mode and wellness ecosystem layered on top of SnapDabba.

Use Settings when the customer app Healthy Mode layout or featured widgets need to change.

Use Meal Plans and Goals when catalog or wellness positioning changes.

Keep fitness data separate from rider-facing operational data; medical and progress details should remain role-controlled.

16. QA Checklist For The Admin Team

Daily smoke test

Login works and captcha appears correctly.

Dashboard cards load without blank widgets.

Orders list, Subscription Orders list, and Restaurants list open successfully.

Eye button opens order details.

At least one customer, one rider, and one subscription record are visible.

Catalog test

Create or edit one food item successfully.

Variation changes save correctly.

Subscription Meal toggle and Subscription Meal Price save correctly.

Category, addon, and coupon search work correctly.

Notifications and settings test

Notification Channels toggles save successfully.

Push Notification page opens and submits without validation errors.

Logo and favicon uploads appear after cache refresh.

Payment settings save without demo-mode restrictions.

Subscription test

Plan Management creates or edits plans correctly.

Delivery slots save and remain visible after refresh.

A subscription detail page opens and manual pause or resume actions work.

Generated subscription orders are visible for active plans.

17. Common Issues And Troubleshooting

Order detail does not open: inspect the order item payload and confirm food_details includes proper food references. The seeded demo data already includes this fix.

Logo or favicon looks broken: verify the business setup upload, confirm storage paths are live, clear application cache, and hard refresh the browser.

Settings page says demo save is disabled: confirm the environment is running in live mode, not demo mode.

Subscription item does not appear in app checkout: verify Subscription Meal is enabled and Subscription Meal Price is filled on the food item.

Push notification not received: check Firebase configuration, notification channels, and the target user type toggles.

Empty order or restaurant list: reset filters, confirm zone-linked data exists, and reload demo data if needed.

Search appears broken: clear existing query parameters and try the exact order ID, coupon code, or customer phone.

18. Pages Reviewed While Preparing This Manual

The following areas were checked directly from the current SnapDabba admin structure while building this guide.

Sidebar navigation structure

Orders list and order detail entry flow

POS screen

Subscription (Tiffin) page

Fitness Super App page and tabs

Food create and edit forms

Food variation editor

Coupon form and coupon list

Business Settings main tabs

Notification Channels page

Live demo data seeder and seeded entities

19. Final Operating Advice

Keep the admin panel clean, predictable, and boring in the good way: only create data you intend to use, document every pricing change, verify subscription items before they go live, and treat settings changes as controlled operations. The smoother the admin workflows are, the better the customer, kitchen, and rider experience becomes across the whole SnapDabba system.