Software marketplaceDEMOSOFT / SELECTION GUIDE
Choosing restaurant ordering and food delivery software
Compare Kebapche and GetFood using their documented workflows, modules, integrations and licence prices.
Publisher: DemoSoft / FALCOSOFT ITS LTD · Updated:
Questions to clarify first
- How will restaurants, menus and ordering options be presented?
- Who receives and processes orders, and how are statuses tracked?
- How will delivery, opening hours, payments and notifications be configured?
- What hosting and support will a live deployment require?
Compare purpose and pricing
This guide uses DemoSoft’s current product descriptions. Prices exclude VAT; review the full details, demo and licence for your chosen product.
| Product | Purpose | Pricing and status |
|---|---|---|
| Kebapche · Restaurant Ordering SystemSoftware system | A single-kitchen ordering store based on kebapche.bg, with meal bundles and zone-based delivery. |
|
| GetFood · Food Delivery SystemSoftware system | A multi-restaurant food ordering and delivery platform with customer, restaurant, courier and admin roles. |
|
Features, integrations and limits by product
Kebapche · Restaurant Ordering System
Modules
- Menu — 10 bundles, variants and an ayran choice.
- Ordering — quantity, cart, fees and a prepayment workflow.
- Kitchen and delivery — states, courier assignment and administration.
Integrations
- Configure the producer, business details, menus, allergens, hours and service coverage.
- The live model uses card prepayment and needs your own Stripe account, keys and validated webhook.
- Agree kitchen, courier, SMS and fiscal interfaces before activation.
Scope and limitations
Payment is confirmed locally as DEMO-SIMULATED. No request reaches Stripe and no delivery occurs. Prices and contacts are examples; settings and external integrations are locked.
Details, demo and terms →GetFood · Food Delivery System
Modules
- Catalogue — restaurants, menus, variants and extras.
- Checkout — cart, delivery, service fee and total.
- Operations — acceptance, preparation, courier assignment and status history.
Integrations
- Configure restaurants, menus, service zones, hours, roles and fees for deployment.
- Live payments require your own provider account, keys, webhook and status reconciliation.
- Courier APIs, SMS, email and fiscal/ERP connections require separate agreement and activation; they are not automatically included.
Scope and limitations
4 fictional restaurants and 12 dishes. Orders are simulated and contact details are forced to fixture values. No real payment, SMS or delivery; system settings are locked.
Details, demo and terms →Before deployment
Confirm the selected licence, installation environment, external services and required data rights. Test the workflows that matter to your project. See the FAQ or contact [email protected] for available options and the installation service.