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.
Log in to comment and vote
Comments12
foodclick
Oct 3
Hello Basti, the concept is definitely interesting, especially if the goal is to turn KMRS into a Super App. But personally, I’m not very interested in having all these different services running within the same database and core system.
My main concern would be scalability and database performance. As the number of merchants and transactions grows, having restaurants, grocery, pharmacy, hotels, bookings, services, etc. all sharing the same database could make the system very heavy and complex. It will be a disaster when the database become heavy.
I would prefer a more scalable architecture where merchant data is properly isolated, ideally with the infrastructure/database being scalable on a per-merchant basis. That would make it much easier to handle thousands of merchants without one merchant’s data or traffic affecting the performance of others.
So rather than adding more and more service types, I’d personally prefer focusing on making the existing core system extremely fast, lightweight, scalable, and properly optimized for large-scale usage.
The Super App idea is good, but I think the architecture and scalability should be considered carefully before going in that direction.
ceazar
Oct 4
this is just survey it will depends on how many would want it, about the issue with performance it will not matter it depends in the structure of the code how efficient is the query and how the table was created , remember the bank still using very old database but still its working :) with many customer.
foodclick
Oct 13
I understand your point. However, large legacy systems, such as banking and airline platforms, often continue using established architectures because migrating them is complex, expensive, and risky. Their continued operation does not necessarily mean the architecture is ideal for every new platform.
I agree that query optimization and proper database design are critical. However, for a Super App supporting multiple service types and potentially thousands of merchants, I believe scalability should be considered at the architectural level as well.
An architecture with isolated merchant databases and scalable infrastructure would provide better workload isolation and more flexibility to scale resources as the platform grows. This would give us greater confidence in supporting multiple services without one merchant's heavy workload unnecessarily affecting others.
Anyway, thank you for sharing your perspective. I understand that this is currently just a survey, and I appreciate the discussion.
ceazar
Oct 13
thanks mate yes for now its survey i will decide to create or not if many user wants it
foodclick
Oct 17
Thank you. I hope more users support this feature request. I believe a Super App architecture would open up many opportunities for Karenderia and make it more attractive to businesses looking for a scalable, multi-service platform. One question, if you adopt a multi-database architecture for the Super App, would the existing KMRS database structure need to be redesigned or restructured to support it properly?
Aydin_silver
Oct 5
Good idea. But for hotels and accomodation they use Amedus, or similar booking GDS softwares in order to get booking from booking platform as well as flight operators. So it will be very difficult to integrate to attract those merchants. I like the service module. If we could structure it well, it will work like charm. Also I don’t recommend it for supermarket because KMRS will be bloated and the server infrastructure need to established in industry standard. Supermarket operation is always superfast :-)
Ryan Pietersen
Oct 16
love this idea yes im trying to vibe code a plugin but if you can please
Magic Lamp
Oct 27
I believe the proposed Multi-Service / Super App Addon should be reconsidered, as most of the features and services mentioned in this proposal already exist in Kartero, which has not received any updates since 2020.
Instead of redeveloping these features and selling them as another paid add-on, I suggest updating and modernizing Kartero and integrating it directly with Karenderia, making better use of an existing product rather than reintroducing its functionality under a new name.
I also believe that the main priority now should be providing regular updates, fixing bugs, and improving all existing applications and add-ons, rather than continuously introducing more paid extensions.
There are already features that should have been included in the core system, such as Karenderia Menu Clone, Karenderia Thermal Printer, and Karenderia Location-Based Service Search Addon. However, these were released as separate paid add-ons, and we purchased them to support you and the continued development of the project. But our willingness to purchase these add-ons and support your work does not mean we agree with turning the entire system into a collection of paid extensions.
Likewise, New Website Frontend Add-on for Karenderia Multi Restaurant System should not be introduced as another paid product. Improving and modernizing the website's frontend, design, and functionality should be part of the natural development and ongoing improvement of the core system, rather than something existing customers must pay for separately.
We understand that you need to generate revenue, and we fully respect your right to make a profit. However, continuing down this path could gradually damage customer trust and raise concerns that Karenderia might eventually face the same fate as Kartero.
We also have practical ideas and strategies that could help you generate greater and more sustainable revenue without constantly introducing additional paid add-ons. If you are interested in our advice and consultation, simply say yes and tell us exactly what you want to achieve and what challenges you are facing. We can share well-thought-out plans and practical strategies to help you increase your revenue and build a more sustainable business.
Our goal is to see Karenderia succeed and continue growing while maintaining customer trust through regular updates, improvements, and long-term support for all existing products, rather than focusing on releasing more paid add-ons.
ceazar
Oct 27
Thanks for sharing your thoughts. We understand your concerns and appreciate your continued support.
However, developing new add-ons doesn't mean we're abandoning the core Karenderia system. We will continue improving and maintaining it while also exploring new features and products.
Major new features and standalone solutions require significant development and maintenance, which is why some are offered as optional paid add-ons.
We appreciate your suggestions, but we also need to balance customer requests, development resources, and the long-term sustainability of Karenderia.
Elperas Antonio
Nov 1
Very good idea, Basti! However, appointment-based service bookings need to be carefully considered, as they involve several complexities, such as multiple staff members, individual availability, multiple outlets, minimum service durations, buffer or rest times between appointments, and other scheduling factors. Managing all these variables requires quite a bit of planning and calculation.
I would suggest starting with the retail outlet module first, as it covers many common e-commerce requirements, such as multiple product categories, multiple products, product variations, upselling, cross-selling, and frequently bought-together products.
Unlike the food business, there is no need for a separate menu management system. Everything is structured around a product catalog, along with advanced inventory management. This makes retail a more straightforward starting point while allowing us to build a strong foundation that can be extended to other business types later.
Elperas Antonio
Nov 1
When selecting the Business Type as Retail, there should also be an option to select a specific Business Category, such as Grocery, Mobile Shop, Textiles, Car Accessories, Electronics, etc.
The reason is that different retail categories have different product requirements and features.
For example, in the Textile category, if a business sells trousers, there should be an option to add size variations (S, M, L, XL, etc.) and display a size chart to help customers choose the correct size.
Similarly, other categories may require their own specific product attributes, specifications, filters, and display options.
Therefore, selecting a Business Category under Retail would allow the system to dynamically enable relevant product features and configurations based on the type of products being sold, rather than using the same product setup for every retail business.
brettos napoleon
Nov 1
Count me in