Find a provider for restaurant or café automation in Uzbekistan: floor service, checkout, kitchen, stock control and team training.
End-to-end business automation across Uzbekistan: software, hardware, implementation and support. Offices in Tashkent and Samarkand.
Clients and projects
Tasks: Store automation, Chain management
Services: Consulting and design, Software implementation
r_keeper implementation for restaurants and cafés.
Tasks: Restaurant automation, Retail equipment
Services: Consulting and design, Software implementation
iiko implementation for restaurant businesses.
Tasks: Restaurant automation
Services: Software implementation, Integrations
Restaurant, hotel and leisure automation. The offer lists r_keeper, Shelter and Game Keeper, equipment, training and service.
Tasks: Restaurant automation, Retail equipment
Services: Software implementation, Hardware selection and supply
An r_keeper integrator in Uzbekistan. The public offer includes StoreHouse and restaurant system modules.
Tasks: Restaurant automation, Retail equipment
Services: Software implementation
iiko implementation, training and support. The website describes POS, kitchen, inventory, management accounting and delivery.
Tasks: Restaurant automation, Inventory and warehouse
Services: Software implementation
A cloud POS system for shops, cafés and restaurants: sales, inventory, reports and staff management.
Tasks: Store automation, Restaurant automation
A delivery platform for owned sales channels, couriers, CRM and analytics. An r_keeper integration is not POS implementation.
Tasks: Restaurant automation, Chain management
A restaurant platform with a Tashkent office: POS, kitchen displays, back office and chain management.
Tasks: Restaurant automation, Chain management
A Samarkand-based POS and equipment offer for shops and food service. Confirm the specific software and implementation scope.
Tasks: Store automation, Restaurant automation
Services: Hardware selection and supply
The company portfolio helps prepare supplier questions. Agree the task-specific solution and modules separately; this table does not attribute every category function to each product.
| Provider | Role | Company portfolio | Catalogue score |
|---|---|---|---|
| 1Soft Business Group | Integrator | r_keeper, StoreHouse | 10/10 |
| 2BUSOFT | Integrator | r_keeper, StoreHouse | 5/10 |
| 3Zetta | Integrator | iiko / iikoCloud | 5/10 |
| 4Vades Smart Technologies | Integrator | r_keeper, Shelter PRO / Shelter, Game Keeper | 5/10 |
| 5Variant Soft Group | Integrator | r_keeper, StoreHouse | 5/10 |
| 6Veda Vector | Integrator | iiko / iikoCloud | 5/10 |
| 7Paloma365 | Software provider | Paloma365 | 5/10 |
| 8Delever | Software provider | Delever | 5/10 |
| 9Clopos | Software provider | Clopos | 5/10 |
| 10U-POS | Integrator | Confirm the solution scope | 3/10 |
Orders, POS and kitchen workflows for restaurants and chains.
Food inventory and cost accounting for food service.
Request a working demonstration using your products and data. Confirm versions, compatibility, licence scope, integration responsibilities and support terms.
SBG: software, hardware, implementation, training and support in Uzbekistan.
Start with the task your team needs to solve at the location. Prepare the menu, staff roles and kitchen routing. For stock control, check ingredients, units of measure and recipe cards separately. Schedule launch around shifts and training: waiters, cashiers, managers and stock staff should understand their part before the venue changes to the new system.
A restaurant order moves from waiter or cashier to kitchen, payment and ingredient write-off. A polished sales screen is not enough: check handovers between stations and the connection between menu and stock records. Cafés, table-service venues and quick-service restaurants need different workflows even on the same software platform. Ask each candidate to walk through this workflow and define responsibility boundaries before agreeing the project.
A restaurant order moves from waiter or cashier to kitchen, payment and ingredient write-off. A polished sales screen is not enough: check handovers between stations and the connection between menu and stock records. Cafés, table-service venues and quick-service restaurants need different workflows even on the same software platform.
Give this workflow to the team and ask for inputs, a responsible person and a success criterion. The answer should describe delivery at your location.
For a restaurant, price floor, checkout and kitchen workstations separately from the stock module. Menu and recipe-card migration should also have an explicit delivery scope.
Request separate estimate items for licences, hardware, configuration, data exchange, training and recurring fees. Cost and timing are agreed for the actual project; there is no universal fixed price here.
Soft Business Group’s solution selection for this task includes: r_keeper, StoreHouse.
Open the product pages and provider profile, then confirm the required configuration, integrations and delivery scope. A product in the portfolio does not mean every module is included in each implementation.
For acceptance, test an order amendment, item cancellation and split bill where the venue needs them. Check kitchen routing, payment and shift closure. Accept the stock-control scope separately by tracing how a sale changes inventory. Put required workflows in the specification and confirm module availability with the integrator.
Give this workflow to the team and ask for inputs, a responsible person and a success criterion. The answer should describe delivery at your location.
Prepare the menu, staff roles and kitchen routing. For stock control, check ingredients, units of measure and recipe cards separately. Schedule launch around shifts and training: waiters, cashiers, managers and stock staff should understand their part before the venue changes to the new system.
Confirm on-site and remote delivery, support hours, contact channels and data-exchange responsibilities. A city office and the ability to deliver in another region are different arrangements and should be recorded separately.
