UnilyticDigests, not a stream
One message listing the nine SKUs that need attention, rather than nine messages. Volume is what kills an alert channel, so the reports are built to summarise.
Stay in the loop
The right alert, in the right place.
Nobody wants another dashboard to remember to open. Build rules that send the digests you actually act on — low stock, excess stock, weekly growth, warehouse intake — to the people who act on them, on a schedule you choose. And the alerts that genuinely cannot wait are always on, whether you configured anything or not.
Email & SlackDaily or weeklyYour recipientsEssentials always on
Your rules, your recipients
Turn on only the updates you want.
A rule pairs a report with a schedule and a list of recipients. Send the low-stock digest to your planner every morning at eight, the weekly growth recap to a Slack channel on Monday, and the warehouse scan summary to your depot manager each evening. Times are set in your own timezone, some reports carry their own settings — a threshold, a cutoff — and any rule can be tested with a single send before you inflict it on the team. Recipients do not all need to be Unilytic users.
- Daily, weekly or on-event, at a time and timezone you set.
- Per-rule settings where a report has them, so a digest matches your thresholds.
- Send a test first, and pause everything at once when you need quiet.
Where your team already is
Email for the record, Slack for the moment.
Some things belong in an inbox where they can be forwarded and filed; some belong in the channel where the team is already talking. Both are supported, and a rule can use either. Every send is recorded in a delivery log, so when someone says they never got the digest, that is a question with an answer rather than a debate. Slack is available on Pro and Business.
- Email and Slack, chosen per rule.
- A delivery log showing what was sent, to whom, and when.
- A monthly allowance per plan, so costs stay predictable.
Designed to be read
Tuned so people keep opening them.
An alert everyone learns to ignore is worse than no alert, because it also teaches people to ignore the next one.
Essentials you cannot mute
A stalled Amazon sync, an authorisation that needs renewing, a failed payment — these are sent whether or not you built a rule, and they are never blocked by your monthly allowance.
Reminders with a deadline
Where Amazon has promised to reimburse a claim by a particular date, the claim reminder chases that date — because the whole value of the reminder is that it arrives before the window shuts.
Why this matters
The problems that cost the most are the ones nobody was looking at.
Inventory failures are rarely sudden. A SKU drifts down for eleven days before it goes out. An Amazon connection breaks and the dashboard just quietly stops changing. A reimbursement window closes while the claim sits on a list. Each of these is completely visible to anyone who happens to look on the right day — and the entire problem is that nobody does. A report that arrives on its own converts a thing you must remember to check into a thing that interrupts you only when it matters.
Checking becomes receiving
The digest arrives at the time you chose, to the people who can act on it.
Failures announce themselves
Sync and billing alerts are always on and exempt from the monthly allowance.
Delivery is verifiable
A log records every send, so 'I never got it' has an answer.
Common seller mistakes
- Relying on someone remembering to checkManual review works right up until a busy week, which is reliably the week something goes wrong.
- Alerting on every individual eventOne message per low SKU trains the team to filter the channel. Then the important one arrives and is filtered too.
- Sending every report to everybodyThe planner does not need warehouse intake and the depot does not need growth figures. Untargeted alerts are read by nobody in particular.
- Assuming a quiet dashboard means healthy dataA broken sync looks exactly like a calm week. Without an always-on alert, stale data is indistinguishable from good news.
Reference
What Unilytic can send you.
Scheduled reports are yours to configure. The always-on alerts report that something has broken, so they do not wait for a rule to exist.
Scroll the table sideways for the remaining columns.
| Report | Type | What it tells you |
|---|---|---|
| Low stock digest | Scheduled | SKUs below your days-of-cover threshold |
| Excess stock digest | Scheduled | SKUs above your excess threshold, ranked by cover |
| Weekly growth recap | Scheduled | Units sold, stock on hand, SKUs needing attention |
| Warehouse performance | Scheduled | Per-warehouse units on hand and SKU count |
| Warehouse scan summary | Scheduled | Return intake and claims still to file |
| Warehouse claim reminder | Scheduled | A postponed claim's reimburse-by date approaching |
| Amazon sync stalled | Always on | No successful sync for several days |
| Amazon reconnect required | Always on | Amazon stopped accepting the stored authorisation |
| First import finished | Always on | Your initial Amazon import completed |
| Billing & trial notices | Always on | Trial ending, payment failed, plan changed, receipts |
Questions
Alerts, answered.
Can I get a low-stock alert for my Amazon inventory?01
Yes. The low-stock digest lists every SKU below your configured days-of-cover threshold and can be sent daily or weekly, at a time you pick, to as many recipients as you like. There is a matching excess-stock digest for the opposite problem.
Does Unilytic support Slack?02
Yes, on Pro and Business. Any rule can deliver to Slack instead of email, so a weekly recap can land in the channel your team already uses. Email is available on every plan.
What can Unilytic email me about?03
Six scheduled reports — low stock, excess stock, weekly growth recap, warehouse performance, warehouse scan summary and warehouse claim reminders — plus always-on operational alerts covering a stalled Amazon sync, an authorisation that needs renewing, your first import completing, and billing or trial notices.
Will I get buried in notifications?04
The reports are digests rather than per-event messages, so nine low SKUs produce one email instead of nine. Every rule targets its own recipient list, each rule can be switched off individually, and there is a single control to pause everything at once.
How many emails do I get each month?05
Free includes 25 org-wide automated emails per month, Pro 200 and Business 500. Critical alerts — a stalled sync, an expired Amazon authorisation, billing notices — are exempt from that allowance, because those are exactly the messages that must never be suppressed.
Can I check whether an alert was actually delivered?06
Yes. A delivery log records each send with its recipients and time, and any rule can be test-sent before you enable it.
Explore more
Keep going.
Analytics
Back to all featuresSell-through analytics
The numbers behind the weekly recap and the low-stock digest.
See the trend PlanReplenishment & send list
The thresholds the low-stock and excess digests are measured against.
Set your thresholds TeamRoles & audit log
Send reports to people who never need a login of their own.
Bring the team inGet started
Stop checking. Start being told.
No card · Built for Amazon India · Email support from the founder.