Location Setup

The following use case describes how to set up a location to consume menu data. Typical scenarios may include a new unit added to a chain, virtual stores, or ghost kitchens.

Use Case

ASSUMPTIONS

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

PRE-CONDITIONS

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

TRIGGER

BASIC COURSE OF EVENTS

• The restaurant is onboarding for the first time or a new location is added to an existing chain restaurant.

• The user creates a new location. • The user adds address, working hours, order channels to the location. • The user adds GPS coordinates for the location. • The user adds KML file for delivery zone (optional). • The use maps the internal location id to subscriber location ID. • The user publishes the location to the subscribers.

POST-CONDITIONS • The location is available on the subscriber for ordering.

EXCEPTION PATH

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

ALTERNATIVE PATHS • The user can also go directly to each subscriber and manually add locations.

Message Flows

User

User

1: createLocation() 2. setWorkingHours() 3: setOrderChannels() 4: setGPSLocation() 5: setDeliveryZone() 6: mapSubscriberLocation() 7: publishLocation()

1: createLocation() 2. setWorkingHours() 3: setOrderChannels() 4: setGPSLocation() 5: setDeliveryZone() 6: mapSubscriberLocation() 7: publishLocation()

LOCATION SETUP

: menuPublisher

8: newLocation() : menuSubscriber

: menuPublisher : menuSubscriber