Pos application.

Maybe create a pos application for android and ios that supports also bluetooth scanners ? And casher screens ?

Improve Cash Payment Details, Rounding, and Change Across the Entire System and Its Apps

The Idea: Standardize and complete cash payment details across all order pages and printed and electronic receipts, clearly showing the cash received and change due to the customer, with configurable cash rounding based on the currency. Key Features: Payment Details: Display the payment method, order total, actual cash received, change due to the customer, and any outstanding amount owed by the customer. Cash Rounding: Provide a configurable setting to round the final cash payment total to the nearest denomination in circulation, such as the nearest 5 cents. Show the rounding adjustment and final total, and apply rounding only to cash payments. Automatic Change Calculation: Calculate change using the cash received and the total after rounding. For example: order total 6.05 dollars, cash received 10.00 dollars, and change due 3.95 dollars. Clear Labels: Use separate labels for “Cash Received” and “Change Due,” and correct the current “Payment change” label to avoid confusion. Accurate Payment Status: Distinguish between the amount the customer indicates they will pay with and the cash actually received. Update the status to “Paid” once full payment collection is confirmed. System-Wide Coverage: Apply the same information and calculations across the backend, frontend, POS, and all connected apps and add-ons, including the customer’s order page and all receipts and invoices. This improvement is essential to ensure clear and accurate cash transactions.

Payment Gateways

Is it possible to add payment gateways for the South African market? Payfast - Overall, the Best Payment Gateway in South Africa Ozow - Best Payment Gateway for Instant EFTs Zapper - Best Choice for QR Code Payments SnapScan - Trusted by Over 60'000 Merchants in SA Peach Payments - Accepts Local and International Cards PayGate - Strong for enterprise and custom integrations Viva wallet Payment Any one of these will work. We have a market for it but there’s a lack of how they can pay. Currently everything is running manual which makes it harder and very inconvenient.

Custom map drawing for shop availability.

If its possible for the shop not only to be able to set how many kilometers he is available for orders but also to be able to draw at the map lines and make his own custom availability map

Integrate Google Translate into the Karenderia System

I suggest adding an ON/OFF option to enable or disable automatic translation using Google Translate code, allowing the system's Frontend and Backend interfaces to be easily translated into multiple languages. Since the Karenderia System includes many Apps & Add-ons, this feature should support all parts of the system, including Customer, Merchant, Driver, and other applications, rather than being limited to the website and administration panels. Suggested Features: Enable or disable Google Translate from the Admin Panel. Support automatic translation into multiple languages. Allow users to select their preferred language from the interface. Support Right-to-Left (RTL) languages, such as Arabic. Preserve the existing manual translation system without affecting its functionality. Implement this feature across all Karenderia Apps & Add-ons, not just the Backend and Frontend. This feature should preferably be integrated into the Core System.

Home Kitchen as a Business Type

I suggest expanding the registration options in Karenderia to include individuals who prepare and sell homemade food without needing to own a physical restaurant. 1. Business Type Add an option during merchant registration to select the business type: Restaurant Home Kitchen 2. Available Services Home Kitchen owners can use the existing services already available in the system, such as: Pickup Delivery Dine-in Takeout They can select one or multiple services depending on their business needs and local regulations. 3. Customer App Add a Home Kitchens category to allow customers to discover home-based food businesses and order from them. 4. Privacy and Verification Provide an option to protect the home address and support verification of any required permits according to local regulations. 5. Integration with the Existing System All menu management, order management, and service options already exist in Karenderia. Therefore, this suggestion does not require a new application or a separate paid add-on. It simply requires adding Home Kitchen as a new business type during merchant registration and integrating it with the existing features. Goal: Expand Karenderia to support home-based food businesses, attract more merchants and customers, and make better use of the existing system without unnecessary complexity or duplicated functionality.

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 🥰

Screens for menus and screen touch pricebook for entrance

As a shop i have all my items placed at catalogs. Woudnt be great to be able to upload iteractive screen menus for the top of the cashier and have a touch screen that i have my menu on a touch screen at the entrance of my shop that the customers can check prices ?

Advanced Inventory & Supplier Management

A complete inventory and supplier management system, fully integrated with Karenderia Multi Restaurant System and POS. The goal is to improve the existing Inventory Management and Suppliers features, allowing restaurant owners to efficiently manage stock levels, ingredients, purchases, suppliers, and inventory costs directly from the main admin and merchant panels. The system should automatically track inventory movements based on restaurant orders, purchases, and stock adjustments, reducing manual work and improving inventory accuracy. Proposed Features View and manage all inventory items and ingredients. Add, edit, and organize inventory items by categories and units. Track current stock levels in real time. Automatically deduct ingredient quantities when customer orders are completed. Link menu items and product variations to their required ingredients. Create and manage recipes with ingredient quantities. Set minimum stock levels and receive low-stock alerts. Track ingredient expiration dates and receive expiry notifications. View inventory movement and adjustment history. Manually adjust stock quantities with recorded reasons. Manage multiple suppliers and their contact information. Link inventory items to one or multiple suppliers. Create and manage purchase orders directly from the system. Track purchase order status, including pending, received, and cancelled orders. Automatically update inventory quantities when supplier deliveries are received. Record supplier invoices, purchase costs, and payment status. Track supplier payment history and outstanding balances. Compare supplier prices for the same ingredients. Monitor ingredient costs and calculate menu item food costs. Generate inventory valuation, stock usage, and purchasing reports. Manage inventory separately for each restaurant or branch. Transfer stock between restaurant branches. Assign inventory management permissions to authorized staff. Real-time synchronization with Karenderia POS, restaurant orders, and reporting modules. Example Workflow Restaurant receives ingredients from supplier → Staff records delivery → Inventory quantities are updated → Customer places an order → Order is processed → Required ingredients are automatically deducted → Stock reaches minimum level → Restaurant receives low-stock notification → Manager creates a new purchase order → Supplier delivers products → Stock is replenished. Goal The goal is to provide restaurant owners with a complete and reliable inventory and supplier management solution without requiring separate applications or excessive manual inventory tracking. Vote for this request if you would like to see advanced Inventory & Supplier Management features developed and integrated directly into Karenderia.

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.

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.

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,

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

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

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

Location-Based QR Code Ordering

I suggest expanding the QR Ordering feature so that each QR Code can be linked to a fixed, predefined location, not only to a table. For example, QR Codes could be assigned to locations such as: Food Court Barber Shop Grocery Store Pharmacy Parking Area near Gate A Parking Area near Gate B Each QR Code would be registered in the system with its specific location name. When a customer scans the QR Code, the system automatically identifies the location linked to that code. For example, if a customer scans the QR Code inside the Barber Shop, the restaurant will immediately know that the order came from the Barber Shop. If the customer scans a QR Code in the Food Court or in the Parking Area near Gate A, the restaurant will know exactly where the customer is waiting. Once the order is ready, restaurant staff can deliver it directly to the location linked to that QR Code. Workflow: Scan QR → Detect Registered Location → Place Order → Prepare Order → Deliver to QR Location This makes each QR Code a predefined ordering and delivery point inside the mall, food court, or nearby surrounding areas. Note: A similar QR-based ordering concept has been offered by Square and has been used in Australia for many years.

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.

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.

Multi-Level Franchise Management System

I suggest adding a multi-level Franchise Management System to the platform to support structured geographic expansion. The system should support: Country → State / Province → City → Area Each Franchise should have its own account, assigned territory, contract period, status, permissions, and financial settings. Main features: Assign restaurants and merchants to the Franchise responsible for their territory. Support Exclusive or Non-Exclusive territories. Set Franchise fees, renewal fees, and revenue-sharing percentages. Set targets such as merchant count or sales volume. Provide dashboards and reports for each Franchise. Track performance, contracts, commissions, and financial entitlements. Allow the Super Admin to fully manage all Franchise levels, territories, and accounts. Goal: To allow the platform to expand through an organized Franchise structure with clear territories, permissions, contracts, financial distribution, and performance management.