Guide: COGS-Well
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
![]() |
![]() |
|---|---|
| Location | ✅ Sites |
| Vendor | ✅ Vendors |
| Category | ✅ Categories |
| Item | ✅ Items |
| Purchases | ✅ Receiving |
| Transfers | ❌ Not Supported |
| Actual Usage | ✅ Usage |
| Theoretical Usage | ✅ Sales Usage |
| Waste | ✅ Waste Usage |
| Menu Items | ✅ Menu Items |
| Menu Item Costs (for Menu Profitability) | ✅ Batch Cost |
| Stock counts | 🚸 Beginning and ending counts — received, but not reported separately |
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 20 minutes |
| Data retrieved on each poll | Everything sent since the previous poll |
| Historical data | All data COGS-Well has sent us since the integration was connected |
How Do I Connect This Data to Tenzo?
COGS-Well sends its inventory data to Tenzo, so there are no credentials for you to enter. Your Customer Success Manager arranges the feed and confirms when it is live.
If you have an Enterprise Account, you can talk to your Customer Success Manager, who will connect this for you.
How Do I Compare COGS-Well Data to Data in Tenzo?
Compare against your COGS-Well reporting for the same date range and site. Purchase totals, usage, waste and recipe costs should all reconcile.
Stock transfers between sites are not part of the feed, so a site's usage does not account for anything moved in or out. Menu item costs are recorded against the day they are received, so a recipe re-costed later does not change the cost already reported for earlier days.
