Guide: Flipdish

How do core concepts map to Tenzo?

Flipdish is an online-ordering and delivery platform. Tenzo ingests Flipdish sales via the Flipdish API.

Key: ✅ Supported   🚸 Work in Progress   ❌ Not supported

Location	✅ Store
Order Type	✅ Dispatch type (e.g. delivery / collection)
Revenue Center	✅ Sales channel type
Product Item	✅ Menu Item
Product Category	✅ Menu Category
Tender Type	✅ Payment
TicketItemModifiers	✅ Modifiers
Discounts (Amounts)	✅ Sale discounts
Service Charge	✅ Charges (non-tip)
Tips	✅ Tip charges
Price	✅ Menu item unit price
Ticket Voids	✅ Only sales with status created or accepted are ingested; other statuses are excluded
Refunds	✅ Sale refunds, netted out of the ticket's revenue as a negative Refund line
Product Division	❌ Not supported
Employee	❌ Not supported
Customer	❌ Not supported
Guest Count	❌ Not supported
Table	❌ Not supported

How is tax handled?

Flipdish reports tax at the sale level rather than per line. Tenzo splits each sale's tax across its priced lines using a net factor (gross − discounts − tax) / (gross − discounts), so item- and modifier-level figures are shown net of tax and still reconcile to the sale total.

How do I connect this data to Tenzo?

Flipdish authenticates with OAuth client credentials. You will need an OAuth Client ID and Client Secret, which you can generate in your Flipdish portal (or request from Flipdish).

How do I compare Flipdish data to data in Tenzo?

Compare the net sales total for a store and date range in your Flipdish sales reports to the same period in Tenzo. Tenzo's figures exclude tax and only include sales with a created or accepted status, so use the equivalent net (tax-excluded) figure in Flipdish.

Tenzo's revenue is also net of refunds: a refunded amount appears as a negative Refund line against its ticket and reduces the total. If your Flipdish figure is gross of refunds, expect Tenzo to be lower by the refunded amount for that period.