We see it before you do.
Every WMSi installation runs a monitoring layer that watches services, backups, sync status and data integrity around the clock, and reports back to us. Nothing to install. Nothing for your team to check.
Nothing in a warehouse fails all at once.
Disk trending the wrong way. A backup that ran late. An Acumatica sync error accumulating quietly. We find those before they become the reason a shift stops.
The usual model is the opposite of that: the WMS is fine until a supervisor calls to say nothing is posting, and the vendor starts looking at 9am for something that started at 2am. By then the receipt is a day late reaching the ERP and someone is reconstructing a shift from paper.
Watchpost exists so that the first person who knows is us.
Signals that mean something to a warehouse, not to a dashboard.
Every one of these is a thing that stops a shift if nobody catches it early.
Service health
The application, the workers and the queues behind them. A worker that stops consuming is a scanner that stops responding twenty minutes later.
Backups
Whether the backup ran, and whether it ran on time. A backup that quietly started failing is only discovered on the day you need it, unless something is watching.
Acumatica sync status
Posts that left WMSi and were never confirmed by Acumatica, and errors accumulating on the outbound path. This is the signal that matters most, because it is the one your ERP silently disagrees with you about.
Webhook delivery
Whether Acumatica's push notifications are still arriving. A webhook that stops firing looks exactly like a quiet day until someone receives against a PO that isn't there.
Reconciliation drift
The reconciliation pass runs every thirty minutes and flags records in stale or ambiguous states. Watchpost watches the flags, so drift is a ticket rather than an audit finding.
Data integrity, disk and printers
Storage trending the wrong way, integrity checks on the installation's own database, and printer status — because a pack bench with a dead label printer is a stopped line.
Watchpost reports on the installation. It is not a quality system and it does not inspect inventory — it tells us the software, the sync and the hardware around them are healthy.
Built in. No separate agent to install.
Every WMSi customer runs on a dedicated VM — their own database, their own workers, no shared tenant. Outpost, the piece of Watchpost that runs on your VM, is not a separate product installed alongside WMSi; it is part of the same codebase, running inside that installation and reporting back to Watchpost. There is no third-party agent, nothing extra to deploy on your network, nothing for your IT team to approve, and nothing to keep updated on a fleet of scanners.
It also means monitoring is live before the first scan rather than after the first incident. On the day of go-live, the installation is already being watched.
- Is it installed?
- Yes — as part of WMSi itself. Outpost, Watchpost's on-VM component, is a module inside the same application your team already runs on your dedicated VM, not a separate product you deploy alongside it.
- A separate agent on your network
- No. No agent, no collector, no scanner-side software beyond WMSi itself.
- Where each half runs
- Outpost runs inside your own WMSi installation, on your dedicated VM. It reports to Watchpost, which runs on WMSi's own dedicated cloud infrastructure, US-based.
- What Outpost transmits to Watchpost
- Infrastructure health signals only — never warehouse operational data. Specifically: service status for the WMS, Celery worker and Celery beat processes; disk and memory usage percentages; database size; the timestamp of the last WAL-G backup; Redis connectivity; the last Celery beat run time; the WMS version tag and commit hash; deduplicated error fingerprints from WARNING-and-above log events; and settings-change audit events from the last 24 hours. No inventory, order, customer or pricing data is included.
- When it starts
- Before go-live. Monitoring is live before the first receipt of the first shift, not after the first incident.
"We're already watching" is only worth something if you can invoke it.
A monitoring promise with no hours and no response target is a liability, not an asset. Here is where ours stands today.
- Support hours
- 8am – 6pm CT, Monday – Friday
- Floor-down response target
- Reachable for emergencies outside business hours
- Everything else
- Same business day
- Support contact
- [email protected]
- Escalation path
- Email [email protected] — Watchpost monitoring provides proactive alerting before most issues require a call
Support hours, response target and escalation path above are real commitments, not placeholders. There is no support phone line — support runs by email, and Watchpost's continuous monitoring means most floor-down issues are caught and addressed before a call would even be needed.
What is not blank: your support contact is the person who configured your warehouse. There is no tier-one queue reading a script, and no handoff between the team that built your configuration and the team that responds when you write in.
The answer to "whose phone rings at 6am."
When you deploy WMSi for a client, Watchpost is part of what you are delivering. Your client's WMS is monitored continuously by the vendor that wrote it, with no agent installed on their network and nothing added to your own support queue.
Most of the time we open the ticket before your client notices. That is the whole point of putting it on this page.
Four things you can verify in a demo or a contract.
One VM per customer
Your data on infrastructure nobody else shares — not a row in a shared tenant, not a schema in someone else's database.
Pinned to a named Acumatica release
Built and tested against Acumatica's latest version. OAuth 2.0 Connected Application, real-time webhooks, ExternalRef idempotency on every post, and a reconciliation pass every thirty minutes.
Built by an operator
Rich and his team spent seven years implementing WMS across food and beverage, auto parts, apparel, chemical, heavy fabrication and floral before writing a line of this code.
Watched, not waited on
Watchpost monitors every installation with no agent to install. Most of the time we open the ticket before you'd need to call. Support hours 8am – 6pm CT, Monday – Friday · Response target Same business day.
Ask us what we would have seen.
Twenty minutes, live scanner, real Acumatica sync. Bring the failure your last WMS never warned you about and we will show you where it would have surfaced.