PROPOSED PROJECT
Menu Updates & Publishing
Update prices, item details, and serving times across your website and delivery menu. Preview changes, get approval, and check that both menus updated correctly.
One change.
Both menus checked.
A café manager requests that Garden Bowl, item F-021, change from ₱320 to ₱340 and become available only from 11:00 to 15:00 in Asia/Manila. The website and delivery menu must show the same approved values. The example keeps the release pending and also shows what the team would see if one destination failed.
WHAT IS USUALLY DONE
A text or vision model can turn a manager’s note into a proposed menu update. Getting that update safely into multiple systems still requires item matching, field validation, approval, scheduling, and recovery when a channel fails.
WHAT SOVRUN CAN DO FOR YOU
Sovrun would connect one approved menu to two places where it appears, such as your website and delivery app. AI turns a request into suggested changes. The system checks item codes, prices, and times before a manager reviews the before-and-after preview. Only approved changes are published. It records whether each update worked and provides a way to restore the last approved menu if something goes wrong.
Preview the update
before it reaches a guest.
Connect one approved menu to the website and delivery app. A manager sees both previews alongside a record of the changes.
Ready to review.
- Website
- Preview ready
- Delivery
- Preview ready
- Previous version
- v17 retained
- Approver
- Pending
How we’d make it happen.
Prepare the change
Read the request, match the exact item, and check the values and time zone. Ask for missing or unclear information instead of guessing.
Approve both previews
Show the current and proposed values in both menu layouts. Save exactly which version the manager approved.
Publish and check
Apply the approved changes at the right time and record whether each menu updated. Check unclear results before retrying or restoring the previous values.
Where AI helps
AI reads requests from typed notes or photos. We test it on unclear numbers and similar dish names. Separate software checks control prices, schedules, and publishing; AI cannot publish changes on its own.
What people approve
A manager approves the item match, each changed field, and the effective schedule. Unreadable values stay unresolved. The operations owner decides how to recover from a partial release.
What we’d need to start
- Approved menu, item codes, and earlier versions
- Access to the two menu systems and their update tools
- People who approve changes, time zones, serving times, and a plan for failed updates
How we’d test it
Test unclear prices, wrong item codes, serving-time changes, slow responses, repeated update requests, and updates that work on only one menu. Check the actual published values and recovery steps before live use.
Prepared for Food & beverage. We would agree on the work after reviewing your brief, materials, and requirements.
This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.
