Success Is Not News
A system that tells you every time something worked trains you to ignore it — including the time it did not. Why confirmations of routine work should start switched off, and failures should never be quiet.
Connect an accounting integration and the first day is reassuring: “Vendor synced.” “Item synced.” “Purchase order synced.” By the end of the week there are two hundred of them. By the end of the month nobody opens them, and the one that said “Sync failed” sits unread between two hundred that said everything was fine.
The arithmetic of a confirmation
A confirmation’s value is the surprise it carries. If a sync succeeds ninety-nine times in a hundred, a success message carries almost none: it tells you what you already assumed. A failure message carries all of it. Send both through the same channel at the same volume and the reader’s attention is spent on the ninety-nine.
Where success belongs
Success is not worthless — it is just not news. It belongs somewhere you can look it up, not somewhere it interrupts you: the record itself, an integration status screen, a weekly digest. The test is whether anybody would do anything differently on receiving it. For a routine sync, nobody would.
Send it as an alert
- Something failed and will not retry on its own
- Somebody has to act before a deadline
- A number crossed a line you set
Keep it out of the inbox
- A routine job did what it always does
- The same event happens dozens of times a day
- The record already shows the result
How AWRA OpsHub sets it up
The QuickBooks sync is a one-way push: items, purchase orders and vendors go from AWRA OpsHub to QuickBooks, and a connected workspace syncs a vendor every time one is saved. In Settings → Notification preferences the three “sync succeeded” rows now start switched off. A workspace that wants them switches them on; nobody gets them by accident.
The failure rows start on, by email and as an in-app notice for the same people, with a link to the integration settings where the connection is checked and the sync run again.
Find your noisiest confirmation
Which automated email arrives most often?
Look at
Search the inbox for the last week.
Then
If it reports success, switch its row off.
When did someone last act on it?
Look at
Ask the person who receives it.
Then
Never: it is a log, not an alert.
Is its failure message a separate row?
Look at
Check the settings screen.
Then
Keep that one on, in two channels.
Verdict
Confirm by exception. Routine success belongs on the record and the status screen; failures belong in the inbox and the bell. A workspace that has heard nothing should be able to trust that nothing went wrong.
What AWRA OpsHub does today
- A one-way sync of items, purchase orders and vendors to QuickBooks
- Success confirmations for those syncs switched off by default, and switchable on
- Sync failures sent by email and as an in-app notice, with a link to the integration settings
More we can add to your workspace
- An integration status screen listing every sync and its result
- A weekly digest of successful syncs in place of individual confirmations
- Automatic retry of a failed sync with a single alert if the retry also fails
Where we point you to a specialist
- QuickBooks remains the book of record for what is posted there; reconciling it stays with your accountant.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsHear about the failures only
See which integrations AWRA OpsHub connects to and how each one reports.
See integrationsFrequently asked questions
Why am I getting a QuickBooks sync email for every vendor?
A connected workspace syncs a vendor to QuickBooks every time one is saved. The success confirmations for those syncs now start switched off, so they only arrive if your workspace turns them on.
Will I still hear when a QuickBooks sync fails?
Yes. Sync failures are on by default, sent by email and as an in-app notice to the same people, with a link to check the connection and run the sync again.
Should an ERP send success notifications at all?
Only when someone would act on them. For routine jobs that succeed almost every time, the result belongs on the record or a status screen, and only failures should interrupt anyone.
