Dashboard customization
Dashboard Settings tunes what the dashboard shows: which stat cards appear, what alert thresholds fire, which products get pinned for quick-glance tracking, and whether the post-count summary email goes out.
Standard cards
Five cards can be turned on or off. Most stat cards show the headline number and a week-over-week (WoW) comparison.
| Card | Toggle | What it shows |
|---|---|---|
| Inventory cost | On/off | Total value of current inventory, computed from receipt costs (weighted average). |
| Spend · 7d | On/off | Money received over the last 7 days, with WoW comparison. Credits, shorts and returns reduce it. |
| Weekly waste | On/off | Total waste cost this week, with WoW comparison. |
| Units sold | On/off | Units sold over the last 7 complete days, with WoW comparison and a daily sparkline. Needs sales data. |
| Sales chart | On/off | A daily units-sold bar chart for the last 7 days, paired with the same weekday one year earlier once you have a year of history, or with your demand forecast on the Pro plan. Tap it to open the full Sales report on those days. |
Turn off any card you don't want the team distracted by. Numbers are still computed and available in reports.
The dashboard has no usage card. Consumption in dollars between two counts is in Reports → Food Cost → By product. See food cost.
Alert thresholds
Two numeric thresholds tune the underlying alert engines, regardless of which dashboard cards are visible.
Expiration date warning
How many days before expiration to surface a product on the dashboard. Default 7. Range 1–90.
Tighter (3 days) keeps the card minimal — only truly urgent items show up. Looser (14 days) gives the team more lead time but more clutter. See expiration alerts.
Price alert threshold
The percentage cost change on a receipt that triggers a price alert. Default 5%. Range 1–100.
Lower (2–3%) catches more drift but creates noise from rounding and small per-case variations. Higher (10%) catches only meaningful jumps. See price alerts.
Wholesale food prices swing more than the prices diners and shoppers pay. USDA's Food Price Outlook notes that producer price indexes, which follow farm and wholesale prices, are typically far more volatile than consumer price indexes.
Low stock, Needs attention, and Worth a look
Alerts on the dashboard split by urgency into two lists. Needs attention is what costs service or money if ignored this week: out or low stock, overdue deliveries, stockout risk, expiring lots, and critical inventory-health findings. Worth a look, just below it, is decisions with no deadline: supplier price moves, food-cost drift, warning-level health findings, and a stale sales feed. It only appears when there is something in it. Both lists dismiss the same way, and a row you haven't seen yet carries a dot and counts toward a N new badge on the list's heading — per user, cleared once you've had it on screen. On the Rinvy phone app, the app icon badge shows the same count for the kitchen you have open.
On an iPhone, the app icon badge shows only while Badges is on in the Rinvy app's notification settings. Apple's guide to changing notification settings on iPhone shows where that switch is.
For when a product counts as low and who gets the push, see low stock alerts.
The Low stock card and the Needs attention list react to what you've already ordered, so the dashboard reflects what's actually handled:
- On order quiets the signal. When a low-stock product is covered by a pending order, it drops out of the Low stock count and the Needs attention list — you've dealt with it.
- The Low stock card is a shortcut. Tapping it opens the order list in Order to par mode, pre-set to refill everything that's low. See order list overview.
- Overdue gets louder. If a placed order passes its expected delivery date unreceived, the item comes back as a red "Delivery overdue" row. See overdue deliveries.
- One row per product. A product surfaces under a single, most-actionable stock signal — overdue, then low stock, then stockout risk — never two rows for the same item.
Highlighted products
A custom section where you pin specific products you want tracked on the dashboard at a glance. Useful for high-value items, items with tight margins, or anything the team needs visibility on without opening the full inventory list.
Open Dashboard settings.
In Highlighted products, pick a product from the Product dropdown and tap Add.
Use the up and down arrows to reorder. The order here is the order shown on the dashboard.
- Remove any product whose card is no longer useful.
Rinvy sets no hard cap on highlighted products, but 3–6 is the sweet spot in practice. Beyond that the section starts taking over the dashboard.
Who gets the email summary after a count?
The kitchen's Owners and Managers get it when Inventory count summary is on. Staff and Viewers don't. When an inventory count session completes, the email recaps low-stock items, reorder recommendations, and counts that changed significantly since the previous session.
| Toggle | Effect |
|---|---|
| Inventory count summary | Enables the post-count email to owners and managers (requires canViewReports). |
Turn it off if your team already reviews the post-count screen in person and doesn't need the recap.
What's not in Dashboard Settings
A few things you might expect here but live elsewhere:
- Timezone, operating days, business-day cutoff — see kitchen settings.
- Push notification preferences — see push notifications. Per-user, not per-restaurant.
- Billing / plan — Kitchen Settings → Billing (Owner-only).
Common mistakes
Turning off the alert card to silence the alert
Hiding the price alerts card doesn't stop alerts firing — the threshold still triggers them, and they still push-notify (if configured) and surface in the attention list. Adjust the threshold instead.
Pinning too many highlighted products
Past 5–6, the section dominates the dashboard and stops being scannable. Pick the products that matter today; rotate as priorities change.
Forgetting that "Inventory cost" is at receipt cost, not retail value
The number is what you paid for what's on hand, not what it would sell for. The retail value would need menu prices and an assumed consumption rate — out of scope for the card.