Eatable

Different Requirements Across Delivery Platforms

Every delivery service runs on different APIs with its own set of rules. For businesses managing multiple platforms, that gap turns routine menu updates into a repeated manual effort.

Solution

We built a unified system that talks to major providers in the region and handles their differences under the hood. For a backend, our developers used NestJS with TypeScript to map and normalize provider-specific APIs, so businesses can manage everything from one place without touching each platform separately.

‍

Shift from Internal Tool to SaaS Product

EaTable built this tool for their own needs, and it worked. But when outside businesses wanted in, the foundation was not built to carry more than one partner.

Solution

Our team redesigned the core architecture. Thanks to a modular backend with PostgreSQL and TypeORM, the system could support multiple accounts, roles, and configurations without major rework each time a new client comes on board.

‍

Complex Menu Structures Across Businesses

Every business structures its menu differently. A single rigid system could not accommodate that variety without forcing businesses to change how they operate or sacrifice flexibility in the process.

Solution

We built a flexible menu management system that adapts to different structures. The backend supports nested items, modifiers, and pricing logic. At the same time, it keeps data consistent and stable across integrations, even for complex catalogs.