Guide: Bleep
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
 |
|
|---|---|
| Location | ✅ Stores |
| Order Type | ❌ Not Supported |
| Revenue Center | ❌ Not Supported |
| Product Item | ✅ Products |
| Product Category | ✅ Groups |
| Product Division | ✅ Departments |
| Tender Type | ✅ Payment Methods |
| Employee | ✅ Users |
| Customer | ❌ Not Supported |
| Discount (Names) | ✅ Discounts |
| TicketItemDiscounts (Amounts) | ✅ Item Discounts |
| TicketDiscounts (Amounts) | ❌ Not Supported |
| Guest Count | 🚸 Guests — counted on sales transactions, but not on payment-only records |
| Transaction Length | ✅ First to last item sold on the transaction |
| KDS Bump Time | ❌ Not Supported |
| Ticket Voids | ❌ Not Supported |
| Ticket Item Voids | ❌ Not Supported |
| Table | ❌ Not Supported |
| Service Charge | ❌ Not Supported |
| Tips | ✅ Gratuity |
| Modifiers | ❌ Not Supported |
| Price | ✅ |
| Menu Item Visibility | ❌ Not Supported |
| Menu Item Size | ❌ Not Supported |
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 1 hour |
| Data retrieved on each poll | Today and yesterday |
| Historical data | All data from the start date you provide when connecting Bleep |
How Do I Compare Bleep Data to Data in Tenzo?
Compare against your Bleep sales reporting for the same date range and store. Net and gross sales, item quantities, discounts and payments by method should all reconcile.
Two things to know when figures differ. Bleep can report a payment with no matching sales transaction; Tenzo still records the payment so your payment totals stay complete, but those records carry no guest count, so guest numbers read slightly low where it happens. Order types, revenue centres and table numbers are not part of the feed, so sales cannot be broken down by them.