Case · Distribution · Beverage distributor with three channels

The owner found out a channel had dropped 14% when the month closed. Now he finds out the next day.

A database that pulls in the ERP, the order app and the logistics spreadsheet every two hours. Eight rules check the data every day at 8am and send a WhatsApp alert to whoever needs it.

Sample data This case is built with sample data until the client's written permission exists. Real numbers get published with name, period and method.

30 → 1

days between the event and the alert

How it was measured Documented by how often the system runs; the monthly report used to get built between the 3rd and 5th of the following month. June–August 2026.

The context

Neuquén · 48 people · three channels: wholesale, convenience stores and the order app · ERP, app and logistics spreadsheet.

Integrated with ERP · order app · logistics spreadsheet · WhatsApp.

The capability Automatic reports with alerts

  1. 01

    What nobody knew

    Nothing, until the month closed. And at close, two people gave two different sales figures, because one subtracted credit notes and the other didn't.

    What was looked at, and what wasn't

    An Excel sheet that administration built every Thursday, six hours of work, with data from the ERP, the app and the logistics spreadsheet. It got looked at on Friday, and it told you what had happened up to Wednesday.

  2. 02

    What showed up when we looked

    In the first month with daily rules, three things showed up that the weekly report wouldn't have caught in time. A customer that accounts for 7% of sales cut their weekly order in half; the salesperson called the next day, found out they'd gotten an offer from a competitor, and matched it. A price list got loaded wrong in the app, with one product at 40% of its price: the alert arrived at 8am the next morning, with 90 orders placed instead of 1,400. And the wholesale channel had been dropping 3% a week for five weeks straight, and nobody had noticed because no single week stood out on its own.

  3. 03

    What decision changed

    All three alerts led to action the same day. And for the first time, someone wrote down what “net sales” means: one single definition, credit notes subtracted, for everyone. Deviations detected: 7 a month, 5 with action taken. Sources: from 4 to 1. The six hours on Thursday, as a result, no longer exist.

  4. 04

    What we built

    A database that pulls in the ERP, the order app and the logistics spreadsheet, every two hours. Every number has a written definition. On top of that, eight rules check the data every day at 8am and send a WhatsApp alert to whoever needs it: the salesperson if it's their customer, logistics if it's a delivery, the owner if it's a channel. At 8:30 the owner gets a one-screen summary. What to do with each alert is decided by the person who gets it.

    How it works

    How it works The ERP, every two hours The order app The logistics spreadsheet The system Gathers, defines, alerts Gathers Defines Alerts Eight rules, every day at 8am. One single definition of “net sales”. WhatsApp alert to whoever needs it The one-screen summary, at 8:30 What to do with each alert is decided by the person who gets it.
  5. 05

    How it's measured from here on

    Alerts a month and % with action taken, sources up to date (days with every source refreshed). The owner looks at it at 8:30.

written permission from the client: name, number, period, quote

Let's talk

Are we the right fit for your company?

Tell us what's going on and we'll tell you frankly whether we can help, and how.

  • We reply within 24 business hours
  • The first conversation is free
  • We come prepared: you leave with three concrete things for this quarter, whether you continue with us or not.

Rather write?

We use your data only to reply. We don't share it or add you to any list unless you ask.