Release notes when we ship. Field notes when a warehouse teaches us something.
Supported: Acumatica's latest version
This strip is the honest signal on this page. It says what we support today whether or not we wrote anything this month.
Where inventory lands after receiving affects everything that comes after — pick efficiency, lot traceability, allergen safety, and space utilization. WMSi uses a configurable hybrid strategy system to make that decision consistently and automatically.
WMSi receives live data from Acumatica via push notifications the moment records change. Here's the architecture behind that sync — and why it's more reliable than polling.
When multiple workers assemble kits simultaneously, knowing which station produced what matters. WMSi tracks assembly contribution at the station level — a capability Acumatica's Assembly Orders have no native concept of.
Acumatica requires a completed Assembly Order before finished kits enter inventory — which doesn't work when floor space limits how much you can assemble at once. Here's how WMSi solves it.
WMS Intelligence maintains its own bin-level location system alongside Acumatica's zone model. Here's why that separation exists and what it means for your warehouse operations.
Eight notes, each about one decision in the software and the failure it exists to prevent. Every one of them is checkable in a twenty-minute demo.
ExternalRefA network blip during a receipt post is not rare, and the naive fix — retry — is how a receipt becomes two receipts and a week disappears into the GL. Every document WMSi posts carries an identifier tied to the WMSi record, so a retry is recognised as the same document instead of creating a second one. A WMSi-side guard also checks sync status before the network call is made at all, so a record already marked synced will not repost however the task was triggered.
Real-time sync is the happy path. Every thirty minutes WMSi queries Acumatica directly for records in stale or ambiguous states — documents posted but never confirmed, POs closed in Acumatica without a matching webhook, sync statuses that diverged on an upstream error — and flags anything that does not agree in the manager portal. A webhook-only integration cannot tell you about the webhook it never received, which is the failure that matters.
Most WMS receiving assumes a single receiver working a PO start to finish. Docks do not work that way: two people split a forty-pallet truck, one gets pulled to a hot order, and the paperwork gets reconciled at 4pm by a supervisor with a clipboard and a good memory. WMSi gives every receiver their own session against the same PO, each seeing the others' progress live, and posts one receipt to Acumatica when the work closes — never two.
When several benches work a shared component pool, Acumatica has no native way to say which bench built what. WMSi tracks each station independently, and a transfer covering work from several stations distributes the Assembly Order across each contributing station session. The attribution exists in the ERP record afterwards instead of in someone's recollection of the shift.
Adding a field to a pallet tag is normally a ticket: someone writes ZPL, someone tests it, and three weeks later the label has the customer's part number on it. WMSi's label designer is a canvas — drag text, barcodes and QR codes, bind live fields with a token, preview exactly what prints. Changing a label becomes a manager's afternoon rather than a release.
Every WMSi customer runs on a dedicated virtual machine — own database, own queues, own workers. Not a schema in a shared database, not a tenant row beside somebody else's inventory. It costs more to run and it is a one-sentence answer to the isolation question a CFO's auditor will ask. Operator, region and backup posture: dedicated cloud infrastructure · US-based · nightly encrypted backups with 30-day retention.
Pick flow state lives in the database, not in a browser session. A crash, a reboot, a dead battery or a swap onto a different device resumes at the exact step it stopped on, with the same tote and the same remaining lines. The picker walks back to the aisle, not back to the start.
Acumatica only: no NetSuite, no Dynamics, no Sage, no ERP-agnostic roadmap. We do not sell the ERP, and we do not sell direct — every deployment is contracted through an Acumatica VAR. Voice-directed picking is on the roadmap but not built yet, so it is not available today, on any timeline we will quote you. A gap found in the demo is a scoping conversation; the same gap found in week six is somebody's problem, so we would rather publish the list.
Field notes are published in full on this page. There are no separate article pages here, so nothing links to a post that has not been written.
Twenty minutes, real workflow, real Acumatica sync. No slides.