Restaurant Portal with iiko/R_Keeper Integration

Many restaurants lose up to 30% of potential orders by relying solely on aggregators. We offer development of a portal that not only attracts customers but also becomes a full-fledged order management and loyalty tool. Over 7+ years, we have completed over 50 projects for restaurants serving up to 2,000 guests daily. Get a free project estimate by contacting us.

Why a Restaurant Website Is More Than a Business Card

A restaurant website is a marketing tool and entry point for online ordering and table reservations. It competes with aggregators (Yandex.Eda, Delivery Club), so it must offer what they cannot: atmosphere, story, branded promotions. An own portal is 2× more effective for repeat sales because you pay no commission and can personalize offers. Commission savings can reach 300,000 rubles per year for an average-turnover restaurant. A Harvard Business Review study shows that an own sales channel increases customer LTV by 40%.

Functional Blocks

• Interactive Menu: interactive menu with filters by category, dietary restrictions (vegan, gluten-free), allergens. Each dish: photo, composition, nutritional info, price. Mobile version is critical – up to 60% of customers order via smartphone, often through a QR code on the table. Page load under 2 seconds due to SSR on Next.js.
• Online Reservation: select date, time, number of guests. Basic availability check against set table limits. Confirmation via email/SMS. Integration with iiko/R_Keeper via API to sync with actual hall occupancy. This reduces staff workload by 30%.
• Delivery/Pickup: own ordering without aggregator. Choose items → address → online payment (YooKassa) → courier tracking. Delivery zones as geopolygons with minimum amounts and times. Load testing shows the portal handles up to 50 simultaneous orders without failures.
• Promotions and Loyalty Program: bonus points for orders, special offers on specific days (business lunch, happy hour). Increases average check by 15–20% (average 200 rubles).

How Our Restaurant Portal with iiko Integration Speeds Up Order Processing

Integration with POS software is key to automation. Via REST API, we sync the menu (prices, composition, stop-list) in real time. When a waiter marks an item as unavailable in the POS, it automatically hides on the site. Orders from the site go directly to the kitchen printer or KDS. This eliminates errors and speeds up preparation: time from order to kitchen drops to 30 seconds (40% faster than manual entry). Comparison: manual order entry takes 50 seconds on average, our automated flow takes 30 seconds.

Technology stack of the portal:

CMS for Menu

The restaurant administrator must update the menu without a developer: add a dish, change price, mark out of stock. We use the headless CMS Strapi with a simple drag-and-drop panel. All changes apply instantly without reloading the site. CMS documentation is included in deliverables.

Work Process

1. Analytics: study business processes, connect to POS for test API. Identify bottlenecks – e.g., staff downtime due to manual order entry.
2. Design: create a prototype – menu, reservation, delivery. Consider scenarios: dine-in, delivery, pickup.
3. Development: stack Next.js + Laravel, TypeScript. Implement SSR for fast initial response. Use Repository pattern for database work.
4. Integration: configure iiko API, sync menu and transmit orders. Test on test environment before launch.
5. Testing: load testing (up to 1000 concurrent users), browser and mobile compatibility, Core Web Vitals check.
6. Deployment and Training: deploy on Vercel or your own hosting, train staff (up to 2 hours).

Timelines (Approximate)

Basic site with menu, reservation, and gallery – 2–3 weeks. Extended version with delivery, iiko integration, and loyalty program – 6–10 weeks. Cost is calculated individually after a brief. Request a consultation to get exact timelines for your project.

What’s Included

• Source code and API documentation.
• CMS access with instructions.
• Staff training (up to 2 hours).
• 3-month warranty support.
• Hosting and further optimization recommendations.

Contact us for a project estimate. Get a consultation on portal architecture and potential savings on aggregator commissions.

Development of Corporate Portals and Internal Systems

We specialize in developing corporate portals — CRM, ERP, LMS, and Intranet. Each project starts not with landing page layout, but with how business rules will be embedded into the architecture: who sees which data, how 1C and accounting systems sync, how 500 contacts turn into 500,000 without performance degradation. Over 7 years, we have delivered over 40 portals for companies with 50 to 5000 employees. We will evaluate your project in two business days — just contact us.

A public website can be launched without detailed design — iteratively improved based on feedback. With a corporate portal, this approach does not work: the cost of fixing architectural decisions after launch for 200 users is incomparably higher. Therefore, we spend 70% of our time on analysis and prototyping, and write code only after the role matrix and integration scheme are approved.

Three areas where bad decisions are often made: access rights model, performance on large data, and real-time updates.

How to build a role model for 30 departments?

Access rights model. "A manager sees only their own clients, a department head sees the entire department, a director sees the whole company, but financial data is visible only to the CFO and above." This is not three roles — it's a matrix of roles, permissions, organizational units, and record ownership. Implementing it with if ($user->role === 'manager') in controllers will make the code unmaintainable after six months.

The correct approach: Spatie Laravel Permission for basic role model + Policy classes for object-level permission (can('view', $deal) checks not only the role but also ownership). For complex hierarchical structures — ABAC (Attribute-Based Access Control) instead of RBAC.

Performance on large data. CRM with 500,000 contacts, filtering by 10 fields, sorting by activity — a naive implementation yields 15-second queries. Composite indexes, denormalization of aggregates (last_activity_at on the record itself instead of MAX over related table), Elasticsearch for full-text search on contacts.

Real-time updates. Multiple employees working on the same document or task. Without WebSocket — constant setInterval with polling every 5 seconds, extra server load, update delays. Laravel Broadcasting + Pusher/Soketi or a custom WebSocket server on Node.js — for notifications and real-time changes.

CRM Systems

Typical set: contacts, companies, deals, activities, sales funnel, reports. Technically straightforward. The complexity lies in the details.

Pipeline with custom stages. Every company wants its own funnel. Stages must be configurable without deployment. Table pipeline_stages with position, color, is_final, probability — and drag-and-drop for reordering on UI (React DnD or dnd-kit).

Change history. Who and when changed a deal status, reassigned a responsible person, added a note. Audit log via Observer or spatie/laravel-activitylog. On UI — timeline with filtering by activity type.

Email integration. IMAP/SMTP for connecting corporate mailbox, automatic linking of incoming emails to contacts by email address. This works reliably only with proper handling of bounces, spam, auto-replies — filtering is required.

Why is ERP not about code but about data?

ERP is when CRM, warehouse, production, accounting, and HR are unified into a single system. Full ERP from scratch is rare (usually integrating with existing systems), but modular systems for specific businesses are common.

Key principle: financial operations must be immutable. Not UPDATE orders SET status = 'cancelled' — but creating a new record order_cancellations with a reference to the original order. This is the immutable ledger principle, which simplifies auditing and reconciliation.

Integration with 1C is almost always part of an ERP project. Two-way synchronization: from 1C to portal (directories, balances, prices) and from portal to 1C (orders, documents). RabbitMQ as an event bus between systems is more reliable than direct HTTP interaction — if 1C is unavailable, messages wait in the queue.

How are LMS structured: learning platforms?

Learning Management System — courses, modules, lessons, tests, certificates, user progress.

Video content is the most demanding part of an LMS. Storing video on your own server and serving via Nginx is a bad idea: expensive, slow, no adaptive bitrate. Correct approach: upload to S3/Cloudflare R2, transcode via AWS Elemental MediaConvert or Mux, HLS playlist for adaptive streaming via Video.js or Plyr.

Viewing progress — periodic sending of watch_position from the frontend (every 10–30 seconds), storage in Redis with periodic synchronization to PostgreSQL. Do not save every second to the database — it will kill performance.

SCORM compatibility — if integration with corporate training materials is needed. Separate module, there are ready libraries (scorm-again).

Intranet and HR Portals

Corporate intranet: news, documents, organizational structure, HR processes (vacations, requests, KPIs).

Organizational structure in the database is a hierarchical structure. Adjacency list (parent_id on each record) is simple to implement but slow for recursive queries. Nested Sets or Closure Table are faster for reading hierarchies, more complex for changes. In PostgreSQL — recursive CTEs (WITH RECURSIVE) with adjacency list — a balance between simplicity and performance.

Document and request approval — workflow engine. Simple linear approvals (employee → manager → HR → accountant) can be done without a special engine. Non-linear (parallel branches, conditional transitions, delegation) — consider ready solutions: Temporal.io for workflow orchestration or a custom state machine based on the state-machine pattern.

What is included in the work

When ordering a corporate portal development, you receive:

• Architectural documentation (ER diagrams, integration scheme, role matrix)
• Full code in a Git repository with CI/CD
• Access to infrastructure (hosting, databases, storage)
• Training for administrators and key users (2–3 sessions)
• Warranty support for 3 months after launch

Our design principles rely on official Laravel documentation on authorization (Policies) and recommendations for working with queues.

Technical Stack for Portals

Timeline Estimates

The cost is calculated individually after a detailed analysis of requirements and role model. To get a preliminary estimate, contact us — we will analyze your task and offer an optimal turnkey solution.