What came in, what went out, and how much of it your team had to touch. Counted, week against week.
The owner's version of this is short. The day's numbers sit where a spare minute finds them, the limits Rocoto works inside are written in one place in plain sentences, and once a month a report arrives with what the year has been doing to your customer list.
Every order passes six checks before it leaves: quantity, money, amount, catalogue, question and change.
The day's line says how many passed all six and how many stopped — «279 of 288» — and the ones that stopped come forward with the reason. That number is where you watch the review load fall.
Customers who are falling away, products they stopped ordering from you, and where your sales concentrate.
It comes out of the same history Rocoto read to learn your business, and it arrives as a document you can read on paper.
Included in the month
The report
Your accounts, your product mix and who is going quiet.
See it
Twelve months of what that account buys, the week they buy in, their tarifa, and every order they have placed.
It is the page a rep opens before a call, and it is the history the month's report reads.
The day's orders leave as a file your team already knows how to open. Your ERP is touched by whoever already maintains it — Rocoto brings the file, the spec and the key.
Each one has a page saying how data goes into it today, checked against its maker's own site.
Rocoto
GitHub