Food and beverage. Menus that move with the day.
Control menu, daypart and branch content across every ordering screen.
Food and beverage content changes by the hour and by the branch: breakfast becomes lunch, an item runs out, one location closes early. Teams also need the same offer to read correctly in Arabic and English, and to stop being shown once it is no longer true.
Menus that move with the day.
One change, end to end.
Illustrative interface content. It shows what the platform supports, not a restaurant configuration.
What makes it hard.
Dayparts and sold-out items
Breakfast, lunch and late-night menus turn over several times a day, and an item that sells out has to stop being promoted before the next order is placed.
Branch-level differences
Opening hours, pickup availability, delivery radius and local offers can differ branch by branch, so a single national message is usually wrong somewhere.
Ramadan and weekend trading
Iftar and suhoor windows, Thursday and Friday peaks and holiday hours compress the time available to prepare, approve and retire content.
Four things a team could build.
Switch the menu by daypart
A coffee chain could show a different home card for breakfast, afternoon and late hours. Dynamic Blocks would return the eligible approved variant for the daypart supplied by the ordering app, without a release for every menu change.
Dynamic BlocksSeparate pickup and delivery
A restaurant group could distinguish pickup customers at one branch from delivery customers in the same city, using order attributes it supplies. Audiences would make different content eligible for each configured group.
AudiencesRun an iftar offer window
A restaurant group could schedule an iftar offer that opens and closes on exact times during Ramadan. Campaigns would control timing, branch eligibility, priority and the approved content shown, and stop serving once the window ends.
CampaignsPublish menus in Arabic and English
A Saudi chain could maintain Arabic and English wording for the same item description and allergen note. Localization would return the approved variant for the locale supplied by the application, with configured fallback behaviour.
LocalizationWhat does the work.
Dynamic Blocks
It lets the chain change menu and promotion cards for a daypart or a branch without releasing new application copy.
Audiences
It separates branch, channel and order-history groups using attributes and events supplied by the chain.
Campaigns
It controls trading windows, branch eligibility, priority and the approval workflow behind each offer.
Localization
It manages approved Arabic and English item, allergen and offer wording with RTL support and locale-specific publishing.
Residency, certification and integration.
Data residency. Today ContentFlow runs as a single deployment on infrastructure located in Riyadh, Saudi Arabia, so production content and end-user data are processed in the Kingdom; that is a property of how we are currently deployed rather than a control the product enforces, encrypted backups and some third-party processors are handled outside the Kingdom, and an in-Kingdom-only arrangement is something we agree in writing on an Enterprise plan rather than something this page can promise.
Certifications. Our controls are built around the requirements of the Saudi PDPL. Backups are encrypted with AES-256 and restore-tested. HTTPS is enforced across the site. SOC 2 Type II and ISO 27001 are planned.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.
One engineering integration up front. After that your team publishes content changes without a new app build and without a new app store submission.
What teams ask.
Can the menu card change without an app release?
Yes, once the placement is integrated. Approved content can be updated remotely while the ordering application keeps control of rendering, and of the menu and price data itself.
Can content differ from one branch to another?
Yes, where the application supplies the branch. Audience rules and campaign eligibility evaluate the attributes and events the chain sends, so branch-level targeting depends on that data being provided.
Does ContentFlow hold our menu, prices or allergen records?
No. Items, prices, stock and allergen records stay in your systems of record. ContentFlow manages the approved content shown around them, and the application supplies the context that decides which approved content is eligible.
Five sectors, one platform.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.