1 Support questions or comments

• 
  1 week ago
  Networkbek

  Great script, but some features are missing for a complete solution
  ​"The UI/UX of Kitchora looks clean and professional. However, to make it a top-tier product, I suggest adding the following features:
  ​Inventory & Recipe Management: Automatic stock deduction based on orders.
  ​SaaS Version: Multi-vendor/Multi-restaurant support would be a game-changer.
  Telegram Mini App (TMA) Compatibility: The script needs a native Telegram Bot API integration and User ID-based authentication for a seamless mobile experience.
  ​Loyalty System: Points or cashback for returning customers.
  ​Without stock management (Ingredients tracking), it’s hard to manage a real kitchen's cost efficiency. Hope to see these in future updates!
• View 6 more replies
• 
  1 week ago
  DoableTech Author

  Thank you for your valuable and detailed feedback — I really appreciate you taking the time to review Kitchora so thoroughly.
  
  I’m happy to clarify that most of the features you mentioned are already implemented and functional, including:
  
  Inventory & Ingredients Management
  Kitchora already includes an ingredients module with stock tracking, supplier management, and procurement. This allows kitchens to monitor inventory and manage costs effectively. Automatic stock deduction based on recipes is part of the planned enhancement layer and will be expanded further in upcoming updates.
  
  Loyalty System
  The system already supports points and coupons, enabling restaurants to reward returning customers and run loyalty campaigns.
  
  Regarding the remaining points:
  
  SaaS / Multi-Vendor Version
  You’re absolutely right — a full SaaS multi-restaurant marketplace version is not yet enabled. The current architecture, however, is already multi-branch and multi-kitchen, and was intentionally designed to be SaaS-ready. A dedicated SaaS version is planned as a future major release.
  
  Telegram Mini App (TMA) & Bot Integration
  Telegram native integration (Bot API + User ID authentication) is not included in the current release. This is a roadmap feature and will be introduced as an optional integration module in future updates.
  
  Kitchora is positioned as a production-ready restaurant management & POS system, with a strong and scalable foundation. Advanced SaaS and Telegram integrations are part of the long-term vision and will be delivered progressively without breaking existing installations.
  
  Thanks again for your constructive feedback — it genuinely helps shape the future updates of the product.
  
  Best regards,
  Alaa
• 
  5 days ago
  Networkbek

  Thank you for the detailed response. After reviewing the kit, I have a follow-up question regarding the multi-vendor functionality. Instead of using 'Airport Branch' or 'Downtown Branch,' can I replace them with different independent stores from my city?
  ​For instance, if I rename one branch to 'McDonald’s' and another to 'Burger King' to create a multi-vendor marketplace, would that work seamlessly or would it cause any technical issues? I'd appreciate your guidance on this
• 
  5 days ago
  DoableTech Author

  Great question, and I’m glad you brought this up because it’s an important distinction.
  
  In the current version, branches are designed to represent locations under the same brand, not fully independent vendors. So technically, you can rename branches to “McDonald’s” and “Burger King” and it will work from a UI and data perspective, but conceptually they will still be treated as branches of one main restaurant entity.
  
  That means:
  
  All branches share the same main owner/admin.
  
  Financial reports, settings, and some configurations are centralized.
  
  There is no full separation of vendors in terms of payouts, subscriptions, or ownership.
  
  So yes, it will work without technical errors, but it won’t behave like a true multi-vendor marketplace where:
  
  Each store has its own owner account.
  
  Each store has its own billing, subscription, and independent financial reports.
  
  Data is fully isolated per vendor.
  
  This is exactly what the planned SaaS / Multi-Vendor version will introduce:
  
  Each restaurant becomes an independent tenant.
  
  Separate dashboards, owners, and financials.
  
  Marketplace-style operation similar to Uber Eats, Talabat, etc.
  
  Optional central admin to manage and monitor all vendors.
  
  So to summarize:
  
  For demos or small internal setups → using branches as independent stores is fine.
  
  For a real multi-vendor marketplace → a dedicated SaaS architecture is required, which is on the roadmap.
  
  The current structure was intentionally built to make this transition smooth, so upgrading to a true multi-vendor version later will not require rewriting the core system.
• 
  5 days ago
  Networkbek

  Thank you for the clear explanation. I really appreciate the detailed breakdown. I am a big fan of the design and structure of this kit, which is why I’m keen on using it for my project.
  ​Since the official SaaS/Multi-vendor version is still on the roadmap, I am interested in exploring custom development to adapt the current version into a marketplace now. To be professional and transparent, I have a fixed budget of $400 allocated for these modifications at this stage.
  ​I wanted to ask if you could provide a solution for a core multi-vendor setup that fits within this budget. Furthermore, if you develop this custom update for me, you could also repackage it and sell it as a 'Multi-vendor Add-on' or a new version on Codester. This way, you can generate ongoing revenue from other buyers who are also looking for this feature.
  ​I believe there is a high demand for a multi-vendor version of your kit. Please let me know if you are open to this collaboration.
  ​Looking forward to hearing from you.
• 
  5 days ago
  DoableTech Author

  Thank you for your interest and for the great proposal. I really appreciate your confidence in Kitchora and your support for its future development.
  
  Yes, I’m open to this collaboration and I’m willing to accept your offer. We can work on a core multi-vendor setup that fits within your $400 budget as a first phase. This will focus on the essential features needed to convert the current system into a basic marketplace structure, such as:
  
  Separate vendor (restaurant) accounts
  
  Vendor-level data isolation
  
  Independent dashboards per vendor
  
  Basic financial separation
  
  Then, this can later be expanded into a full SaaS/Multi-vendor version.
  
  I also like your idea of repackaging this work as a “Multi-vendor Add-on” or a separate version for platforms like Codester. It’s a win-win situation where you get your marketplace solution, and I can make this feature available to other users as well.
  
  We can start by defining:
  
  The exact scope of the core multi-vendor features
  
  A clear delivery timeline
  
  The technical boundaries of this first phase
  
  Once we agree on these points, we can proceed smoothly and professionally.
  
  Looking forward to working with you on this.
• 
  5 days ago
  Networkbek

  Thank you for the clear explanation and for accepting the proposal. I am a big fan of Kitchora’s design, and I am excited to move forward with you on Phase 1.
  ​To make this system powerful for a global market and successful in my region, I would like to finalize the scope of Phase 1 with the following features:
  ​Multi-Vendor Core: Separate vendor accounts, data isolation, independent dashboards, and basic financial separation as we discussed.
  ​Telegram & WhatsApp Integration: Since Telegram is vital in my region and WhatsApp is dominant in global markets like India, integrating both for login/authentication will make this kit a huge bestseller on Codester.
  ​Multi-City Support (Admin Managed): I prefer a simple and effective approach where the Admin can add a list of cities. Users should be able to select their city upon visiting the site and see the restaurants available in that specific area.
  ​API-First Approach & Loyalty System: A solid API structure to support a future Mobile App, and a Loyalty Points (Bonus) system to keep customers engaged.
  ​Payment & Security:
  To be professional and transparent, I must share that I have had bad experiences in the past where I paid for custom work and the developers did not complete the project. I hope you understand my caution.
  ​For our mutual protection, I would like to split the $400 payment into 2 or 3 milestones. Additionally, I prefer to keep all transactions within Codester to ensure the process is secure and transparent for both of us.
  ​I am confident that by adding these features, you are creating a high-end SaaS Marketplace product that will generate massive sales for you on Codester in the future.
  ​Please let me know the estimated timeline for these features. I am ready to start as soon as we agree on these points.
• 
  4 days ago
  DoableTech Author

  Thank you for your detailed message and for your trust. I completely agree with your vision, and I believe the features you listed will make Kitchora a very strong and competitive SaaS Marketplace product.
  
  All the points you mentioned are clear and well-defined:
  
  The Multi-Vendor core features
  
  Telegram & WhatsApp authentication
  
  Multi-city support managed by Admin
  
  API-first structure with a Loyalty Points system
  
  Regarding payment and security, I fully understand your caution, and I respect your professional approach. Splitting the $400 into 2 or 3 milestones and keeping all transactions inside Codester is perfectly fine with me and ensures safety and transparency for both of us.
  
  For Phase 1, I suggest the following rough timeline:
  
  Planning & architecture: 2–3 days
  
  Multi-vendor core implementation: 7–10 days
  
  Telegram & WhatsApp integration: 4–6 days
  
  Multi-city support + Loyalty system + API setup: 4–6 days
  
  Total estimated time: approximately 2 to 3 weeks, depending on testing and refinements.
  
  Once we agree on:
  
  The exact milestone breakdown
  
  The final feature list for Phase 1
  
  We can start immediately.
  
  I’m excited about this collaboration and confident it will create a high-value product with strong market demand on Codester.
• 
  4 days ago
  Networkbek

  Thank you for the detailed timeline. I am very satisfied with your plan and the estimated duration. I agree to proceed with the project under the following Milestone Breakdown to ensure a smooth workflow:
  ​Milestone 1 ($150): Multi-vendor core implementation and Multi-city support (Admin-managed).
  ​Milestone 2 ($150): Telegram & WhatsApp authentication and the Loyalty Points (Bonus) system.
  ​Milestone 3 ($100): API structure setup, final testing, and project handover.
  ​I am happy to keep all these transactions within Codester as we discussed.
  ​Regarding the feature list, the points we have already covered (Multi-vendor, Social Auth, Multi-city, API, and Loyalty) are the final requirements for Phase 1.
  ​Please let me know how you would like to initiate the first milestone on Codester so we can get started immediately. I’m looking forward to a great result!
• 
  3 days ago
  DoableTech Author

  Thank you for confirming the milestone breakdown. Everything looks perfect and well-structured.
  
  I agree with the three milestones exactly as you outlined:
  
  Milestone 1 ($150): Multi-vendor core + Multi-city support
  
  Milestone 2 ($150): Telegram & WhatsApp authentication + Loyalty Points system
  
  Milestone 3 ($100): API setup + final testing + handover
  
  Keeping all payments inside Codester is completely fine and is the best option for both security and transparency.
  
  To initiate the first milestone, please create a custom job / custom offer on Codester with the Milestone 1 scope:
  “Multi-vendor core implementation and Multi-city support (Admin-managed)” for $150.
  
  Once it is created, send me the link and I will accept it immediately so we can start working without delay.
  
  I’m excited to begin this collaboration and confident we will deliver a strong and successful Phase 1.