Food & Hospitality · 2026

One Menu Source, Every Surface

A rebuilt site plus a self-serve menu system for a Seychelles café — one place to edit the menu, and it updates the website, the printed menu, the in-store TV boards, and the social posts.

Quick answer

What did Seypro build for American Deli? One CMS drives the web menu, print, TV boards, and social. Live at adcsey.com (opens in new tab). Stack: Next.js, React, TypeScript, Tailwind CSS, Drizzle ORM, Neon Postgres. Part of our Website Design and Software Development practice.

American Deli — built by Seypro
In production · American Deli
Live
Rebuilt site at adcsey.com
1 CMS
Drives web, print, TV boards & social
Staff-run
Menu managed in-house, no developer
WhatsApp
Direct ordering, no platform fees

The brief.

American Deli was running an ageing site and managing its menu the way most small restaurants do — a designer for the printed menu, someone else for the screens, a separate effort for social, and a developer needed for any website change. Prices drifted out of sync across surfaces, and nothing could be updated quickly. The brief: rebuild the site and give the team one place to manage the menu that keeps every customer-facing surface in step.

How we built it.

We rebuilt the public site on Next.js and put a role-gated menu CMS behind it, backed by a single Postgres database that acts as the one source of truth for the menu. Staff edit categories, items, per-size prices, and daily specials themselves — no developer in the loop. The same data then feeds a built-in design studio that generates the printed A5 menu, the in-store TV boards, and branded social graphics, so a price change made once shows up everywhere. Ordering runs through a WhatsApp cart, and the team can publish a menu item or the day's special straight to Facebook from the studio.

One source of truth

The menu lives in one database. Everything customer-facing reads from it, so the team edits once and every surface follows. No more reconciling the website against the printed menu against the screens.

What the one CMS drives

  • The public website menu at adcsey.com
  • A print-ready A5 menu generated in-browser (save-as-PDF)
  • In-store TV boards — portrait and landscape — a screen opens directly
  • Branded social graphics for menu items and the daily special
  • Per-size (S/M/L) pricing, daily specials, and 86 / sold-out toggles

Staff-managed, role-gated

The team manages the menu themselves through a role-gated admin — an owner account with full access including social publishing, and staff accounts limited to menus, boards, and print. Every change is written to an append-only audit log. The client owns the code and the data; there are no recurring software fees to keep it running.

Ordering and social

Customers build an order and send it straight to the café over WhatsApp — no ordering platform fees, no third-party middleman. From the same studio, the team can push a menu item or the day's special to the restaurant's Facebook page in a couple of clicks.

A small café now runs the kind of menu operation a chain would — edit once, and the website, the printed menu, the screens on the wall, and the social post all stay in sync. Managed entirely by the team, with no developer in the loop.

Stack

Next.jsReactTypeScriptTailwind CSSDrizzle ORMNeon Postgresbetter-authVercelVercel BlobMeta Graph API

Services behind this build

Building something this serious?

This is the work we do. Tell us what you need.