...
Rolling out Deliverect in restaurants that are still using Oracle;
Rolling out Deliverect in restaurants that do not support delivery.
Market-Specific Requirements
...
| Note |
|---|
Preliminary section, will require more detail after Discovery Session (05th Nov) |
When guests place a delivery order via the Guest App, the RBI Platform will use the Partners API to inject the order contents into Oracle POS. This requires translation of Parter API payloads into the corresponding Oracle payload, which will be accomplished by using Khumbu.
...
| Warning |
|---|
Clarification of menu requirements needed. |
...
Content Team is setting PLU as following:
Sanity > Vendor config field
Toshiba-Loyaltyuses for Toshiba POS, Tillster, Smoothr and Acrelec is reading the PLU from (Kiosk);Sanity > Vendor config field
Toshiba-LoyaltyPartnerused for Oracle POS;
Loyalty integration: all vendors changed the integration to “supportingPos”: “toshibaLoyalty”.
Technical Requirements
As today, SIDES is managing 1P Delivery orders and SIDES does not have Order Injection on Toshiba POS.
Scenario As-Is
Scenario Transition period (Transition time SIDES > Deliverect)
In order to accommodate Deliverect in the same flow as SIDES, our Platform needs to develop a routing logic to direct incoming delivery orders under SIDES and Deliverect at the same time until SIDES be decommissioned.
...
Scenario TO BE (Fully transitioned SIDES > Deliverect)
After fully onboarded Oracle restaurants
Phase | Description |
|---|---|
1 | Enable RBI <> Oracle ordering integration
|
2 | Enable Deliverect integration in 1 store:
|
3 | The transition from SIDES to Oracle-Deliverect in all restaurants
|
4 | SIDES decommissioned
|
Key Stakeholders
Timelines
...
Potential Risks
Dependencies
...