How do core concepts map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
Location |
✅ Restaurant |
Vendor |
✅ Vendor |
Category |
✅ Category |
Item |
✅ Items |
Purchases |
✅ Purchases |
Actual Usage |
❌ NOT SUPPORTED |
Theoretical Usage |
❌ NOT SUPPORTED |
Waste |
❌ NOT SUPPORTED |
Stock Counts |
❌ NOT SUPPORTED |
Menu Items |
❌ NOT SUPPORTED |
Menu Item Costs (for Menu Profitability) |
❌ NOT SUPPORTED |
Data Ingestion
Real-time optionally available? |
❌ NOT SUPPORTED |
Default polling frequency |
Daily |
Data retrieved on each poll |
Last 90 days |
Historical data |
Since you started using Margin Edge |
How do I connect this data to Tenzo?
MarginEdge can be connected directly inside of the Tenzo app; you will need to generate an API key from within Margin Edge as outlined here.
You will also need to input:
- a start date from which to pull data
- a setting to indicate whether you wish other charges to be spread proportionally across categories, or assigned to a new category. If all categories are set to "book proportionally" here you should set this to one (https://help.marginedge.com/hc/en-us/articles/1500005085382-Handling-Taxes-Delivery-and-other-Miscellaneous-Charges)
If you have an Enterprise Account, you can talk to your Customer Success Manager, who will connect this for you.
How do I compare Margin Edge data to data in Tenzo?
You can compare the Purchases number in Tenzo to the Orders report found here:
Category and Item level reporting in Tenzo can be compared by viewing the Category Report or Purchase Report in Margin Edge.
Note: this number in the Purchases report in Margin Edge does not include other charges (e.g., delivery, tax etc.) - so you'll need to remove them as they show in Tenzo. They may also be some missing items compared to the Orders report.
Exceptions
- Tenzo does not include the Bar/Garnish category, as this is a sub category of Produce. To match with the Produce category total in Margin Edge you will need to add the Produce and Bar/Garnish totals together.
#integrations
Comments
0 comments
Article is closed for comments.