Limited Time Offer

The following use case describes a potential implementation of a limited time offer (LTO), which is essentially a temporary menu item, temporary price, or other aspect of a saleable item.

Use Case

ASSUMPTIONS

• The menu publisher has the ability to connect to all subscribers through an API or menu subscribers are able to listen for updates.

PRE-CONDITIONS

TRIGGER

• The menu publishing system must be online and connected to the subscribers to share menu updates, or the menu subscribers are able to reach out earlier and download the changes to local cache.

• The restaurant is running a temporary promotion like LTO or happy hour.

BASIC COURSE OF EVENTS

• The user identifies an item for a LTO. • The user uses the menu publisher to set the start date, time and end date and time. • If the offer is recurring by day of week or time day, the user adds those conditions. • The user selects brand/location/store where this change will apply. • The menu publisher updates the item availability to all subscribers. • The item(s) become visible at the designated start date and time, and is hidden at the designated end date and time.

POST-CONDITIONS

• If the LTO is recurring, the item automatically becomes visible or hidden based on date and time range.

EXCEPTION PATH

• The menu publisher is not able to connect to subscribers or subscribers are not able to reach the publisher because they are offline.

ALTERNATIVE PATHS

• The menu publisher can replace the full menu at all subscribers if it is not able to update individual items on the menu. The user can also go directly to each subscriber menu and manually add and remove the items from the menu.

Message Flows

User

1: createLTO() 2: addTimeDetails() 3: mapLTOToBrandsAndSites() : menuPublisher

4: updateItem() : menuSubscriber

User

1: createLTO() 2: addTimeDetails() 3: mapLTOToBrandsAndSites() : menuPublisher : menuSubscriber