How are PLUs managed for different service modes?

Same PLU for both in-restaurant and delivery service modes. Different pricing is managed through definitionSequence.

• definitionSequence = 1 is in-store.

• definitionSequence = 2 is delivery.

Not all items have both definitions (e.g. some items aren’t sold in delivery).

How do we distinguish service modes?

• Use definitionSequence

• Do not use different revenue centers – this means multiple configurations.

How do we send the table order number for table service orders?

Sugar tax – is it added as surcharge to the product (included in priceSequence)?

E.g. Classic Coca-cola

Bottle deposit (Pfand)

Does it have a separate PLU?

Does Oracle require a separate PLU for each fee?

Are the following fees supported: bag fee, service fee, delivery fee?

FireOrder webhook. Does Symphony support ’suspended’ orders? That is, orders sent with fireOrderInSeconds=null which need to get fired at a later time.

For pre-ordering outside opening hours – does Oracle support pricing & committing orders outside restaurant opening hours?

E.g.: An order is priced and committed, at 6:00 AM. The order is set with the attribute fireOrderInSeconds = null to wait for an explicit FIRE_ORDER webhook at a later time to be sent to kitchen. While the restaurant opens at 9:00 AM.

Can orders be canceled in the POS?

If so, how does Simphony notify our system of canceled orders? Is there a Webhook?

Do we need to pass any information for fiscal integrations to work?

Is this standard across markets?

E.g. in BK MX in the commit call we need to send the following information:

"extensions": [
{
"displayName": "DocumentId",
"appName": "Harmonized",
"dataName": "DocumentId",
"dataType": "strings",
"data": "1",
"options": []
},
{
"displayName": "DocumentType",
"appName": "Harmony",
"dataName": "DocumentType",
"dataType": "strings",
"data": "01",
"options": []
}

This information always stays the same as it’s needed for the fiscal integration to work.