Cordiant
Cordiant turns menus, discovery, and ordering into one natural-language experience — built to drive more direct revenue. A Simphony-native commerce platform for restaurants and restaurant groups.
Your restaurant website is a brochure. Every commerce moment leaks to a third party.
A guest lands on your restaurant's site to look at the menu, read about the chef, see the room. Then they leave — to OpenTable to book, to DoorDash to order, to Tock for a tasting, to a phone call for a private dining enquiry. Every commerce moment happens on someone else's surface, under someone else's brand, against someone else's take rate. Your system of record is Simphony. The commerce is everywhere else.
This is not a UX problem. It is a surface problem. The website was built to describe the restaurant. It was never built to run the commerce the restaurant actually does. Decouple the surface from the vendor stack behind it, put Simphony at the centre, and the leakage collapses.
Cordiant Restaurant Commerce replaces the brochure-style restaurant website with a single conversational commerce surface that transacts directly against Simphony. Menus, reservations, ordering, private dining, gift cards, and follow-up — one dialog, one brand, one commerce engine.
Guests don't browse a menu PDF, and then jump to a third-party ordering app. They ask for what they want — by dish, by dietary restriction, by mood, by occasion — and the right items render in the same surface, ready to add to a check that lives in Simphony. This unified stream — cards, conversation, and cart composed into one continuous scroll — is Cordiant's second patent-pending invention, not a UX choice.
Reservations, pre-orders, gift cards, and takeout all transact through your commerce engine — not through someone else's marketplace. The guest is yours. The check is yours. The cover charge, the loyalty, the repeat visit — all yours.
Every menu read, every item added, every reservation booked, every gift card issued is a live call against Simphony. No cached menu that drifts from the POS. No reservation that lives outside the kitchen's view. Your system of record never disagrees with your guest's surface.
A guest enquires about a wedding rehearsal, a corporate off-site, a Sunday anniversary. The conversation captures party size, date flexibility, dietary needs, budget, and occasion — and hands the structured enquiry to your events lead with everything already gathered. No forms, no back-and-forth.
Every response — including every AI-generated recommendation from your menu and wine list — renders in your restaurant's brand. Tone, typography, imagery, layout. Inherited from a theme defined once and applied across every surface the guest touches.
Deploys inside your brand's OCI tenant. No cross-cloud hop between the commerce surface and the POS. Under your existing security posture. No new SaaS vendor in the data path. No guest data leaves your tenant. No marketplace intermediary reading your order flow.
A restaurant group gets one platform across every concept — the steakhouse, the seafood house, the neighbourhood bistro. Each renders in its own brand, shares the commerce engine and the architecture, and consolidates data at the group level where the CFO actually wants it.
WCAG compliance is built into the foundation. Every screen, every workflow, every AI-generated response inherits accessibility structurally — not remediated after launch.
We built guest commerce for luxury hotels on Opera Cloud — a live reference deployment on the Oracle Hospitality Integration Platform sandbox. Three years of refinement on the most demanding commerce surface in hospitality.
The restaurant layer was always part of that stack. Guests at a hotel don't think in terms of "room system" and "dining system" — they ask about a table at Nobu in the same conversation they extend their stay, and the platform executes both. That restaurant layer has now been packaged into a dedicated platform for Simphony restaurants — available to restaurant groups and standalone restaurants who don't need the rooms side of the stack.
You get the same three-layer architecture, the same patent-pending conversational-plus-deterministic execution model, the same brand-by-architecture rendering. Sized to a restaurant group's scale, priced for a restaurant group's margin, deployed against Simphony as the system of record.
A restaurant commerce surface is the cleanest possible embodiment of Cordiant's second patent-pending invention — unified visual stream commerce, filed by Dennis Paul, Co-Founder and CEO. Four properties of the restaurant journey make the fit near-exact:
A single restaurant has fifty to three hundred items. A restaurant group is typically under two thousand five hundred across venues. The full catalog — with live inventory, live pricing, live modifiers — fits into every conversation. No retrieval layer, no vector store, no embedding drift. The model reasons against the whole menu.
Discovery, choice, modification, reservation, check, and confirmation compose into a single vertical stream. No search page. No results page. No separate cart page. No separate confirmation page. Commerce happens in place. The guest never leaves the conversation.
Sixty to seventy percent of restaurant traffic is mobile. Typing searches on a phone is where the existing restaurant web loses its guests. A stream that responds to plain language — something light, dining in thirty minutes, for two — removes the search box entirely and replaces it with the conversation the guest would have with a maître d'.
A restaurant already maintains its menu as a live, structured artifact inside Simphony — the catalog is not an abstraction produced for the commerce surface, it is the kitchen's source of truth. The conversation reads the same menu the line cook is plating from. No second catalog. No data-modelling exercise to turn inventory into a shoppable taxonomy. The restaurant is the rare commerce category where the product database was already built, by operators, for themselves.
Every interaction runs the same split — an intelligent conversational surface on top, deterministic application code underneath, executing against Simphony.
"Table for four Saturday at 7:30 — my partner is gluten-free."
The platform checks Simphony availability, offers the closest times, confirms the booking, and attaches the dietary note to the cover record. The kitchen sees the gluten-free flag when the guest walks in. No separate reservation app. No data that has to be reconciled back to the POS the next morning.
"Something lighter than the tasting — maybe the sea bass, and a glass of whatever the sommelier would pick."
The platform reads the live menu from Simphony, synthesises a pairing from the wine list and the chef's notes, renders the dish and the glass in a branded card with the prices, and on confirm opens a tab in Simphony with the items already attached. The check lives in your POS from the moment the guest says yes.
"We're booking our daughter's engagement dinner — about 18 people, a Saturday in October, she's allergic to shellfish."
The platform captures the party size, the date flexibility, the dietary restrictions, the occasion, and the guest's contact details — and hands the events lead a pre-structured enquiry with everything already gathered. The next conversation is a real proposal, not a form-filling exchange.
"I want to send $500 to my parents for their anniversary — they come every year around this time."
The platform identifies the guest from their history, issues the gift card through your commerce engine, attaches a note, and notifies the property so the team can acknowledge the occasion when the parents arrive. Direct, personal, and reconciled into the same system that runs the rest of the night.
Cordiant Restaurant Commerce runs on the same patent-pending three-layer architecture as Cordiant Hotel Commerce. The conversational surface is intelligent. The transaction engine is deterministic. The split is structural.
The surface interprets what the guest wants, synthesises responses from your menu, wine list, chef's notes, and property knowledge, and decides which action to offer next. That layer is AI. The engine beneath it writes reservations, opens tabs, commits orders, issues gift cards, and records every action in the audit trail. That layer is deterministic application software, executing against Simphony through the same role-based access your restaurant already governs.
The AI cannot hallucinate an order. It cannot add a menu item that isn't on the menu. It cannot commit a reservation outside your service policy. Because the AI is not the thing executing those actions. This is why Cordiant clears security and compliance review where agent-first restaurant pilots stall.
Adoption is a configuration exercise against a platform that already works. The first restaurant in a group reaches production in six to eight weeks — brand theme, Simphony integration, identity federation, commerce engine, menu and knowledge ingestion, and payment rails, all configured against a platform that already works. Subsequent restaurants compress to two to four weeks because the group-level foundation is already live.
Cordiant Restaurant Commerce deploys inside your brand's OCI tenant, under your existing security and compliance posture. No cross-cloud hop between the commerce surface and the POS. No new SaaS vendor in the data path. No guest data leaves your tenant. Identity federates through OCI IAM. LLM inference runs against the model provider you govern, under your data-residency and model-governance rules.
Two operating modes. One architecture. Self-operated: your technology team runs the platform, with Cordiant Group Support covering architecture, upgrades, and issue triage. Cordiant-operated: Cordiant runs the platform inside your tenant under an ops contract, with audited access and no data leaving your cloud. Tenant ownership, identity federation, and the trust posture are identical in both modes. Only the operator changes.
The same predictable structure as Cordiant Hotel Commerce, sized for restaurant-group scale and margin. Predictable line items. No revenue share. No per-transaction metering. No marketplace take rate. Commercial patterns your CFO already understands from POS, reservation, and loyalty contracts.
A thirty- to forty-five-minute briefing with Cordiant leadership. We will walk the architecture, show the conversational commerce surface handling live reservations, ordering, and private dining flows, and propose a first-restaurant pilot scoped to your group.
Schedule a Briefing