Vista Watch · the Operational Immunity model
Early access · limited cohortsKeep the control. Hand off the vigilance.
Celigo gives you ownership of the configuration. Vista Watch adds the operating layer: watching for specification drift and transaction failures, diagnosing what changed, surfacing the affected transactions with evidence, and carrying approved corrections through.
You keep the ownership and the visibility you bought. You stop being the one who has to notice. We call the model Operational Immunity, and it works the way an immune system works.
Vista Watch onboards in small cohorts so each operation gets the attention the first ninety days need. A HealthCheck baseline is how a cohort place gets held.
Read-only access · Governed · A human approves anything that matters
Vista Watch · the operating loop
It enters the loop two ways
Before it fails
Specification or configuration drift
After it fails
A failed or missing transaction
Detect
The change, or the transaction that did not land.
Diagnose
What changed, what it touches, and the evidence behind it.
Disposition
What it costs to leave alone, and the options worth considering.
You approveYour call
Nothing is changed until a person says so. Leaving it alone stays on the list of choices.
Fix and retest
The approved correction is carried through and proven.
Remember
The cure becomes a signature, and every brand under the Watch is checked against it.
Then it watches for that one everywhere, and the loop starts again.
Why error management fails
The worst errors are the ones you never see.
The platforms aren’t wrong. They were built a decade ago for companies with IT departments, where an error queue was something somebody was paid to watch. Most commerce brands don’t have that somebody. The controller is the somebody. The ops lead is the somebody. You are the somebody.
And the worst errors aren’t the ones in the queue. They’re the ones dismissed automatically because they looked like yesterday’s errors. Orders that never posted. Deposits that never tied out. Inventory that never came back after a return. Silent failures don’t nag you. They quietly bend your books until the day you stop trusting your own numbers.
So we built something different. Not better error management. The end of the error as a way of life.
The operating choice
Someone has to watch it. The question is who, and what it costs you to find out.
Handing the whole operation to a managed provider buys you someone to call and costs you the ability to see inside. Running it yourself on Celigo buys you the visibility and hands you the vigilance along with it. There is a third arrangement.
Traditional managed EDI
Someone else operates it. The configuration and the response time sit somewhere you cannot see, and the problems still surface on your desk.
Self-managed Celigo
Full ownership and full visibility. You also inherit the watching, the maintenance, and the repairs, because the platform does not operate the vigilance layer for you.
Celigo and Vista Watch
Ownership and visibility stay yours. Altura supplies the vigilance: proactive detection, diagnosis, disposition, and governed remediation you approve.
What the vigilance covers
The change that breaks it, and the transaction it broke.
Monitoring that only reports failures is always arriving late. The Watch works both sides of the moment.
Specification and configuration drift
A trading partner revises a document requirement. An admin changes a field. A channel updates its API. The Watch is looking for the change itself, so the break gets caught while it is still a change and not yet a failed order.
Failed and missing transactions
When something does fail, the Watch surfaces the affected transactions with the evidence behind them, including the ones that never raised an error at all. Then it carries the correction you approve through to done.
How it works
An immune system for your operation.
Issues get driven down until they stop mattering. Then the Watch keeps them from coming back, and catches the new ones your next channel, your next 3PL, your next admin change will introduce. Because they will. That’s not a flaw in your business. It’s why immunity has to be continuous.
It watches.
Vista Watch stands watch over your systems on a continuous, governed schedule. It is built to surface failures early, including the silent ones. Not just the errors the queue admits to.
It diagnoses.
Every issue gets evidence, a business impact in dollars and hours, and a cost to fix. You decide what's worth treating. Some things aren't, and we'll tell you that too.
It remembers.
Every issue we beat, anywhere, becomes a signature: what it looks like, what causes it, how it's cured. The Watch never has to learn the same lesson twice.
It protects everyone under it.
Every brand under the Watch is checked against the signature library. When something new appears at one, we check the rest for it and bring each affected brand the fix. A cure found once is a cure offered everywhere, at a fraction of what finding it again would cost.
Governed by design
Guardrails first. Always.
A watcher inside your business systems has to earn the right to be there. Vista Watch runs governed from the first minute, and the governance is not fine print. It is the design.
Read-only access
The Watch observes your systems through read-only access. It watches, evidences, and reports. It does not change your data or your configuration on its own.
A human approves anything that matters
Anything consequential, any fix, any write, any change to how your operation runs, is proposed to a person and approved by a person before it happens. Your system of record stays yours.
Your data, on your terms
Zero-retention AI options and local model options are available for client data. You choose the posture. The Watch works inside it, never around it.
The evidence standard
Evidence, impact, options. Then your call.
An alert that says something failed is noise. Vista Watch holds every issue to a higher standard before it ever reaches you.
The issue, in plain language
What broke, where, and what it touches. Written for an operator, not for a log file.
The evidence
The records behind the finding, so you can verify it yourself. Nothing reaches you that can't be shown.
The impact, in dollars
What the issue costs the business in dollars and hours if it keeps running, and what it would cost to fix.
Fix options you choose
Options with trade-offs, including the option to leave it alone. You decide what's worth treating. Then a person carries out exactly what you approved.
What immunity looks like
The brand that almost started over.
A multi-channel brand came to us worn down. Silent failures had bent their books for so long that re-implementing NetSuite from scratch was on the table. Not because the system was beyond saving, but because nobody had ever treated the disease.
The Watch’s diagnostic scan traced the symptoms back to root causes. Not alerts in an error queue. Causes, each with the evidence behind it and the cost of leaving it alone.
After remediation, the flows that had slowed to a crawl ran fast again. Orders in. Money tied out. And re-implementation came off the table, along with the cost, the disruption, and the year of the team’s life it would have consumed.
Their system wasn’t dying. It was sick. There’s a difference, and the difference is treatable.
Detected
Every issue the Watch finds is logged, evidenced, and tracked to resolution.
Fixed for good
Every cure becomes a signature that protects every brand under the Watch.
The running tallies will live here, drawn from the Watch itself, not from marketing.
Silence is the outcome.
Orders in. Money tied out. Close on time. An integration you never think about, still running in the environment you own. Cohorts are small and the first step is a HealthCheck baseline of what is actually happening in your account.
