Multi-Service / Super App Addon

Transform Karenderia into a multi-service marketplace or Super App where different types of businesses and services can operate from one platform. Instead of supporting only restaurants and food delivery, this addon would allow the platform owner to create multiple service categories such as: 🍔 Food & Restaurant Delivery 🛒 Grocery & Supermarket 💊 Pharmacy & Medicine Delivery 🏨 Hotels & Accommodation 🧺 Laundry & Dry Cleaning 🔧 Home Services 💇 Beauty & Salon Services 🧹 Cleaning Services 🚗 Car Services 📅 Appointment & Service Booking 📦 Other Local Services Each service type could have its own suitable ordering or booking flow. For example, restaurants can use food ordering and delivery, hotels can use room reservations, while salons or service providers can use date and time-slot bookings. Possible Features Multiple service/business types in one platform Admin can create and manage service categories Merchants choose their business/service type during registration Different workflows depending on the service type Product-based ordering for food, grocery and pharmacy Appointment and time-slot booking for service businesses Hotel/accommodation reservation support Pickup, delivery and on-site service options Merchant-specific service settings Location-based merchant and service discovery Separate categories and filters for every service type Commission and subscription support Customer wallet, promotions, coupons and loyalty support One customer account for all available services One mobile app / website for accessing multiple services The goal is to make Karenderia suitable for building a Grab, Gojek, Careem or local Super App-style marketplace, where customers can access different products and services from a single application. 👍 Vote for this feature if you would like to use Karenderia for more than restaurants and food delivery.

Stripe Connect – Automated Merchant Payouts

A proposed KMRS add-on that integrates Stripe Connect to automate payment distribution between the platform and merchants. Instead of the admin manually calculating and sending merchant payouts, Stripe Connect would allow merchants to connect or create their Stripe account and receive their share of eligible online payments automatically. Proposed Features Merchant Stripe Connect onboarding Connect and manage merchant Stripe accounts Automatically calculate platform commission Automatically allocate the merchant's share of an order Support platform/service fees Track merchant payment and payout status View Stripe transaction details from the admin/merchant panel Handle refunds and payment adjustments Stripe webhook integration for payment and payout updates Admin controls for Stripe Connect settings Example Customer pays $100 → KMRS platform keeps its configured commission/fees → remaining eligible amount is allocated to the merchant through Stripe Connect. The goal is to reduce manual merchant settlements and make KMRS marketplace payments more automated. Vote for this add-on if you would like Stripe Connect support for automated merchant payments and payouts in Karenderia.

AI Voice Agent to handle phone orders?

I have a question. Would it be possible to add an AI Voice Agent to handle phone orders? The idea is for the AI agent to answer customer calls, take the complete order (items, quantities, customer details, delivery address, etc.), and then automatically send the order to our Karenderia Multiple Restaurant System, just as if the order had been placed through the app or website. This would allow us to fully automate phone orders without staff having to manually enter each order. Do you think this could be integrated with our current system? Thank you. Best regards,

Separate Operational Database for Each Merchant Using AWS RDS

Objective Implement a separate MySQL operational database for each merchant using Amazon RDS, while maintaining a central database for merchant accounts, subscriptions, authentication, and platform management. Reason for This Request KMRS is expanding beyond online ordering to support multiple order sources and restaurant applications, including: POS Flutter Waiter App Kitchen Display System (KDS) Self-service Kiosk QR Menu ordering Single Site Single App Main KMRS Customer App As more restaurants use these applications simultaneously, each merchant will generate increasing volumes of orders, order items, payment records, inventory updates, kitchen status changes, and other operational transactions. Keeping all merchants' operational data in one shared database could increase database contention, complicate maintenance, and make performance optimization more difficult as the platform grows. Requested Implementation Separate merchant databases: Automatically create an isolated MySQL operational database for each merchant on AWS RDS when their account is provisioned. Central merchant registry: Maintain a central database that maps each merchant account to its operational database and stores platform-level information. Automatic database routing: The application must securely identify the authenticated merchant and route requests to the correct database without affecting other merchants. Scalable AWS infrastructure: Initially, multiple merchant databases may share an RDS instance. The architecture must support moving high-volume merchants to separate RDS instances when required. Complete operational data isolation: Each merchant's orders, order items, products, inventory records, payments, tables, and other operational data must remain isolated from other merchants. Automated provisioning and maintenance: Implement automatic schema creation, database migrations, backups, recovery procedures, connection pooling, and monitoring. Compatibility with all KMRS applications: All supported ordering channels and restaurant applications must use the correct merchant database without changing the existing user experience. Why This Is Important Better scalability: The architecture can accommodate growing numbers of merchants and increasing transaction volumes. Performance management: Merchant workloads can be monitored and optimized individually, with the option to move busy merchants to dedicated RDS instances. Data isolation: Separate databases reduce the risk of accidental cross-merchant data access and simplify merchant-specific backup and recovery. Reliable restaurant operations: As POS, Waiter, KDS, Kiosk and online ordering generate transactions simultaneously, the database architecture can evolve to accommodate the workload. Easier maintenance: Individual merchant databases can be backed up, restored, migrated and maintained more independently. Long-term growth: The system can expand without requiring a complete redesign of the merchant database architecture. Expected Outcome KMRS should use a scalable multi-tenant architecture with a central platform database and separate operational databases for individual merchants. The solution should support automatic provisioning, secure database routing, reliable synchronization with the KMRS Loca

New Website Frontend Add-on for Karenderia Multi Restaurant System

We are planning to develop a brand-new Website Frontend Add-on for Karenderia Multi Restaurant System (KMRS), featuring a modern, responsive, and user-friendly design. This will be a separate add-on that provides a completely new customer-facing website experience while integrating with the existing KMRS backend. The goal is to deliver a faster, more modern, SEO-friendly, and fully responsive online food ordering website that works seamlessly across desktop, tablet, and mobile devices. Planned Features & Improvements - Modern UI/UX: A completely redesigned website with a clean, professional, and intuitive interface. - Responsive Design: Optimized browsing and ordering experience across desktop, tablet, and mobile devices. - Improved Performance: Faster page loading, smoother navigation, and optimized user interactions. - SEO-Friendly Architecture: Improved search engine visibility, metadata, and search engine indexing support. - Restaurant Discovery: Easily browse nearby restaurants, cuisines, categories, and popular dishes. - Advanced Search & Filters: Search restaurants and food items with improved filtering options. - Restaurant Profile Pages: Modern restaurant pages featuring menus, operating hours, ratings, and reviews. - Improved Menu Browsing: Enhanced food categories, item customization, add-ons, and product details. - Streamlined Cart & Checkout: Simplified ordering process with fewer steps. - Multiple Ordering Services: Support for delivery, pickup, and other services available in KMRS. - Order Tracking: View order progress and delivery updates. - Customer Accounts: Manage profiles, saved addresses, favorites, and order history. - Promotions & Discounts: Support for existing KMRS coupons, offers, and loyalty features. - Payment Integration: Compatibility with supported KMRS payment gateways. - Multilingual & Multi-Currency Support: Integration with existing KMRS language and currency settings where supported. Compatibility The new Website Frontend Add-on will integrate with the existing Karenderia Multi Restaurant System (KMRS) backend and APIs. Restaurant owners and administrators will continue managing their operations through the existing KMRS management panels. Important Note This will be a separate, newly developed Website Frontend Add-on, not a redesign or automatic replacement of the existing KMRS website frontend. The existing website will remain available independently. This feature is currently proposed for future development. Final functionality, availability, and release details will be announced later.

Multi-Device Offline LAN Sync for Flutter Waiter Apps and Kitchen Display App

The Goal When the internet drops, all devices (Flutter Waiter Apps and KDS App) must continue working and updating each other in real-time over the local Wi-Fi router without relying on the cloud. How It Should Work (The Architecture) The "Local Master Host": Designate one primary device on the local network (such as a primary terminal or dedicated local node) to run a lightweight local backend service to act as the Local Host Server. Local Data Routing: When a waiter places an order while offline, the Flutter Waiter App sends the order payload directly to this Local Host IP address over the local Wi-Fi. Waiter to KDS: The Local Host instantly routes that order JSON payload to the specific web-based KDS screens (PHP/JS/HTML) based on station routing rules (e.g., kitchen vs. bar). Two-Way Status Updates: When a chef clicks "Ready" on a web-based KDS screen, it sends an update back to the Local Host, which instantly pushes that status update over the LAN to refresh the Flutter Waiter App's local UI. Auto-Cloud Sync: The system must save all offline transactions in a local cache. The moment internet connectivity returns, the system automatically pushes all saved data back to the central Karenderia cloud database. The system must include an mDNS / Auto-Discovery feature so the Flutter Waiter apps and web KDS screens can automatically find the Local Host IP without manual configuration. It must use WebSockets for real-time, two-way communication between the Flutter frontend and web KDS terminals, alongside a clear visual sync status indicator (e.g., Green/Red Cloud) on all UIs showing the exact number of pending unsynced orders.

Live map with real-time driver tracking

Provide a dedicated delivery map showing the restaurant's active delivery staff and their orders. The restaurant should be able to see: Each driver's current location. Driver name and status. Number of active orders. Current delivery destinations. Order locations. Delivery routes. Nearby orders. Which drivers are already heading toward a particular area. Real-time Google Maps tracking would make it much easier for restaurants to monitor their delivery operations and decide which driver should receive a new order.

Sort location search results by current location

While searching, locations should be sorted based on the user's current location. Because the same location name from different cities may appear on top, sorting by current location would solve this.

New Flutter Customer Mobile App for Karenderia (Android & iOS)

We are planning to develop a brand-new Karenderia Customer Mobile App using Flutter for both Android and iOS. This will be a completely new application built from the ground up, rather than an update or conversion of the existing Quasar/Vue + Capacitor Customer App. The goal is to provide a modern, faster, smoother, and more reliable mobile ordering experience while maintaining compatibility with the existing Karenderia Multi Restaurant System (KMRS) backend. Planned Features & Improvements - Built with Flutter: A new mobile application developed specifically for Android and iOS. - Modern UI/UX: A completely redesigned interface with improved navigation and a better food ordering experience. - Optimized Performance: Faster loading, smoother animations, and more responsive navigation. - Restaurant Discovery: Browse nearby restaurants, explore menus, and search for favorite foods. - Food Ordering: Support for delivery, pickup, and other available ordering services. - Real-Time Order Tracking: Track order status and delivery progress. - Push Notifications: Receive order updates, promotions, and important notifications. - Location & Address Management: Improved GPS integration and delivery address selection. - Secure Checkout: Support for existing KMRS payment gateways and available payment methods. - Customer Accounts: Manage profiles, saved addresses, favorite restaurants, and order history. - Promotions & Rewards: Support for available coupons, discounts, and loyalty features. Compatibility The new Flutter Customer App will integrate with the existing Karenderia Multi Restaurant System (KMRS) backend and APIs. Important Note This will be a separate, newly developed Flutter application. The existing Customer Mobile App will remain a separate product. This feature is currently a proposal for future development. Final features, availability, and release details will be announced later.

Multi-Counter POS System

Develop the POS system to support multiple counters within the same restaurant, while restoring POS functionality in the Merchant App. Core Features: Create multiple POS counters such as Main Counter, Counter 2, Counter 3. Separate order screen for each Counter. Allow an order to start at one Counter and be completed or closed at another Counter. Keep a complete history of order movement between counters. Provide a Username / Password or PIN for each staff member. Record all orders and actions under the staff member who handled them. Reports by Counter and by Staff/User. Restore POS support in the Merchant App. Goal: Make the system suitable for restaurants operating multiple POS counters, with flexible order handling and clear tracking of each Counter and staff member.

KMRS Local Server for Offline Restaurant Operations

The Idea Develop a Windows-based KMRS Local Server Desktop App that acts as the central communication gateway between KMRS Cloud and all restaurant applications. Key features: Centralized Communication: All communication between KMRS Main (Cloud) and POS, Waiter App, KDS, Kiosk and other supported apps passes through the Local Server. Offline Operations: Continue accepting local orders, routing kitchen tickets and updating order statuses even when the internet is unavailable. Online Order Integration: Receive Cloud (KMRS Main) orders through the Local Server and deliver them to the appropriate local applications. Automatic Synchronization: Queue local transactions during outages and synchronize them with KMRS Main (Cloud) when connectivity returns. Centralized Administration: Provide a desktop dashboard for device management, system health, database monitoring, backups and synchronization status. Simplified Development: Implement shared offline capabilities once in the Local Server instead of independently building complete offline infrastructure into every application. Single Installer: Package the Local Server Engine and Admin Desktop into one easy-to-install Windows application. The server engine must keep running even when the administrator closes the dashboard. Otherwise, closing the window could interrupt restaurant operations. Expected benefit: A reliable offline-capable restaurant ecosystem with less duplicated development, centralized management and seamless synchronization with KMRS Cloud. Software installation Admin Interfaces

Advanced self delivery module for restaurants

Provide a complete self-delivery management system inside the Merchant App so restaurants using their own delivery staff (because third-party delivery commissions are high) can manage drivers and deliveries. Key freatures include Manage Drivers: Add delivery staff, set availability, and view their current status. Driver Workload: See how many active orders each driver has and view all assigned orders. Smart Assignment: Assign multiple orders to the same driver when deliveries are going to the same or nearby areas — even if the driver has already left and needs to return for another pickup. Live Map: View drivers, delivery locations, routes, and real-time locations using Google Maps. Order Tracking: See each driver's active orders, delivery status, and destination. COD Management: Track which driver collected each payment, total amount collected, and daily settlement. Daily Overview: A simple dashboard showing available drivers, active deliveries, driver workloads, and COD collections. This would help restaurants reduce delivery costs, better utilize their own drivers, and manage deliveries and payments efficiently.

Rating popup for recently delivered orders

After any order is successfully delivered, each time the customer opens the app, show a popup in the footer with an option to give a rating to recent orders directly.

Karenderia Waiter App

A dedicated mobile app for restaurant waiters and servers, fully integrated with Karenderia. The app would allow waiters to take and manage customer orders directly from an Android device while serving customers at their tables. Proposed Features Select restaurant table View table status and current orders Create new orders for a table Add additional items to an existing table order View menu items, categories, addons, and item options Send orders directly to the kitchen/KOT View and update order status Request or generate customer bill Accept/manage payments Print customer bills using a Bluetooth printer View table order history Multiple waiters can manage restaurant tables Real-time synchronization with Karenderia POS and restaurant orders Example Workflow Waiter selects table → Takes customer order → Sends order to kitchen → Customer adds more items if needed → Waiter requests bill → Payment → Print receipt → Close table The goal is to give restaurant staff a fast and simple way to manage dine-in customers without having to return to the main POS terminal for every order. Vote for this request if you would like to see a dedicated Karenderia Waiter App developed.

Karenderia Merchant App update

Hello please update the merchant app with advanced pos features available in admin panel and bring the same beautiful interface to the Merchant App, optimized for iPad and desktops. It would be amazing to have waiter selection before table selection, support for multiple POS terminals under the same merchant account, and offline support for order processing and KOT printing. Also, please support partial table occupancy. For example, if a table has 2 seats and only 1 guest is seated, the remaining seat should be available for another order at the same table. Keep up the amazing work and I really thank you this gentleman. You’re making this system more lovable with every update 🥰

Menu approval addon for KMRS merchant submissions

Hi basti, can you consider having a Menu Approval addon for KMRS. When ever metchant submit any items, addons, this need to be approved by portal owner or admin. If merchant changes exisitng menu or addons title, descriptions and images, this edits need to be approved by admin. Why I am telling this we provide free trial for merchant. Some people simply register as merchant and post irrelevant menu and photos that could make heigh serious legal issues for owners. Sometimes people put porn images, or restricted items like drugs. So every menu items should be strictly verified by admin before it goes to public. We can have a menu in admin panel like Verify Menu or similiar. Then we will see each submission with item title, merchant name, edit, approve, reject with reason etc. A seperate staff user can assign only for this Add a Menu Approval addon for KMRS so that whenever a merchant submits any items or addons, the portal owner or admin must approve them before they go public. If a merchant changes an existing menu or addons title, descriptions and images, these edits also need to be approved by admin. Reason: free trials are offered to merchants, and some people simply register as merchants and post irrelevant menus and photos that could create very serious legal issues for owners — sometimes porn images or restricted items like drugs. Every menu item should be strictly verified by admin before it goes to public. Suggested implementation: a menu in the admin panel like Verify Menu or similar, showing each submission with item title, merchant name, edit, approve, reject with reason etc., with a separate staff user assigned only for this.

Kiosk-style QR menu mode without table selection

Self service Kiosk-style Menu in the Smart Table Ordering Addon. Add a kiosk-style QR code menu without table selection to the Smart Table Ordering System, as an additional option called “Kiosk Menu” or “Food Court/Kiosk Mode” in the Smart QR Menu. In some restaurants, such as mall food courts, there are no fixed tables and customers can sit anywhere, so no staff serve the customer at the table. The flow should be: Scan the QR code from counter and browse the menu. Place an order without any table selection Choose to pay at the counter or make an online payment (optional). If the customer chooses to pay at the counter, the order should not be sent to the kitchen until payment is completed. Customer must visit the counter and say his Token number. Once payment is confirmed, the order is sent to the kitchen (If payment made online, order will go direct to kitchen.) The kitchen accepts the order and marks it as Ready when it is prepared. The customer receives a notification, or the customer-facing screen displays the order status. The customer collects the order and eats at their chosen table. There would be no staff serving the customer at the table. A similar idea is used in KFC self service kiosks, but here users would simply scan a QR code and order.

Admin can edit user information

bring back the options that admin can modify the customer informations

Cloud Kitchen Addon for Karenderia Multiple Restaurant System

Cloud Kitchen Addon for Karenderia Multiple Restaurant System Manage multiple restaurant brands from one centralized cloud kitchen! The Cloud Kitchen Addon allows restaurant owners and food businesses to operate multiple virtual restaurant brands from a single kitchen location using Karenderia Multiple Restaurant System (KMRS). Instead of managing each restaurant separately, cloud kitchen operators can streamline orders, menus, kitchen operations, deliveries, and staff management through one centralized dashboard. Key Features - Multiple Restaurant Brands – Create and manage multiple virtual restaurant brands under one cloud kitchen. - Centralized Order Management – Receive and manage orders from all connected brands in one dashboard. - Unified Kitchen Operations – Organize food preparation and kitchen workflows across multiple brands. - Brand-Specific Menus – Each brand can have its own categories, menu items, pricing, add-ons, and availability. - Centralized Delivery Management – Manage drivers, delivery zones, assignments, and delivery operations from one kitchen. - Shared Kitchen Location – All brands operate from the same kitchen address and location. - Flexible Business Settings – Configure brand-specific ordering services, taxes, and payment options where applicable. - Kitchen and Brand Availability – Control opening hours and temporarily pause operations at the kitchen or individual brand level. - Centralized Customer Management – View customers and their orders across connected brands. - POS Integration – Manage point-of-sale orders within the cloud kitchen environment. Who Is This For? Ideal for cloud kitchen operators, ghost kitchens, virtual restaurant businesses, food entrepreneurs, and restaurant owners who want to operate multiple food brands without managing separate physical restaurant locations. Help Us Shape This Addon! We are planning this addon for Karenderia Multiple Restaurant System (KMRS) and would love to hear your feedback. Would you like to see Cloud Kitchen support added to KMRS? Vote for this feature and share your suggestions in the comments. Your feedback will help us prioritize development and decide which features to include.

Allow admin to add/edit customer address