Every phase, what we do, what you do, and how many of your people's hours it costs. No surprises in week six.
Two of these are the numbers every vendor dodges. They belong here because you are going to ask anyway, and you should be able to compare us against everyone else on the shortlist.
Single site, standard configuration, on the happy path. Complex lot or allergen rules can extend that — scoped during Discovery once we see your operation.
This requires the full focus of your implementation staff for the duration of the program. Concentrated in the discovery and training weeks, not spread thinly across every one.
A Warehouse Manager, an IT contact, and an executive sponsor — the minimum named contacts we need from you for the project.
The Acumatica connection is already built and version-pinned. Nobody is writing a connector for you. How it connects.
Each phase says what WMSi does, what you do, and what you hold in your hand when it ends. If a phase cannot produce its deliverable, the date moves and we say so at the time.
WMSi does: a discovery call on your buildings, shifts, item count, and what breaks today. Produces a fixed written scope and quote against the published rates.
You do: get us your Acumatica instance details and one hour of your operations lead.
You leave this phase with: a fixed price and a dated go-live target. Nothing has been signed yet.
WMSi does: walks your warehouse (remote by default, on-site when mutually agreed). Maps your real receiving, putaway, picking and counting flows onto the system. Documents your location naming, your zones, your ABC velocity picture and your exceptions.
You do: time from your operations lead and one supervisor per shift, scoped during Discovery. Show us the workarounds — especially the ones you are embarrassed about. Those are the ones that break go-lives.
You leave this phase with: a written configuration design that you sign off on.
WMSi does: stands up your dedicated VM. Configures the OAuth Connected Application against your Acumatica instance, then works through the build in order: Warehouse Structure (location master, zone configuration, putaway strategy, product separation rules, LP settings), Inbound (receiving configuration, multi-user session setup, over-receive controls, LP label design), Inventory Management (replenishment thresholds and hot lane setup, cycle count scheduling and variance approval, quality hold SLA thresholds), Outbound (picking configuration, packing method and carton master, carrier credentials and rate configuration, the Acumatica transmission trigger), Specialized Workflows (kitting and manufacturing, for customers who need them), and the Platform Layer (security and permissions, notifications, Salesboard, Warehouse Intelligence dashboards).
You do: answer questions and approve decisions — the time this takes is scoped during Discovery. This is our heaviest phase and your lightest.
You leave this phase with: a working system running on your own data, in a test instance.
WMSi does: validates item master, unit-of-measure and location data against what the floor actually looks like. Builds your label templates in the designer — pallet tags, LP labels, pick labels, shipping labels.
You do: time here is scoped during Discovery, and this is the phase where your project can slip. We need current location data and an item master that matches the rack. If fifteen years of drift live in your data, this phase is where it surfaces.
You leave this phase with: labels printing on your own printers, off your own data.
WMSi does: trains supervisors first, then operators — on your devices, remote by default, with on-site available when mutually agreed. The screens are built to be learned by doing, so this is shorter than you expect.
You do: time per operator and per supervisor — scoped during Discovery based on your headcount and shift structure. Every scanning person attends.
You leave this phase with: supervisors who can train the next hire without calling us.
WMSi does: supports you closely — remote by default, with on-site available when mutually agreed — from the first receipt of the first shift. This is a hard cutover: we do not run your old process and the new system in parallel. Watchpost monitoring is live before the first scan, not after.
You do: run your warehouse. Pick your cutover day deliberately — a lighter day of the week, and not month-end.
You leave this phase with: every receipt, pick, count and shipment posting to Acumatica in real time.
WMSi does: daily check-ins for the first two weeks, then weekly check-ins through week four, before moving to the standard support relationship. Watchpost keeps reporting continuously, with no agent installed on anything of yours.
You do: tell us what is annoying. Week-three complaints are configuration tuning, and tuning is included.
You leave this phase with: a support relationship with the people who built your configuration — not a ticket queue that has never seen your warehouse.
Data is where WMS projects slip, at every vendor, including this one. We tell you in week one exactly what we need and we chase it. If it is not there by the date we agree on together in week one, the go-live date moves — and we say so at the time, rather than in week six.
| Task | WMSi | You |
|---|---|---|
| Acumatica connection and OAuth setup | Owns it | Approve the Connected Application |
| VM provisioning, hosting, backups, DR | Owns it | — |
| Location, zone and putaway configuration | Owns it | Sign off the design |
| Item master and location data quality | Validate and flag | Own and fix |
| Label template design | Owns it — and then you can change them yourself | — |
| RF scanners and printers | Advise on compatibility | Buy and network |
| Wi-Fi coverage in the racks | Flag the gaps we find | Own and fix |
| Operator training | Owns it | Get everyone in the room |
| Go-live floor support | Owns it | Run the warehouse |
| Ongoing support after go-live | Owns it | Email us |
Data and Wi-Fi. No WMS vendor can fix a dead spot over aisle 14 from a laptop, and none of them will tell you that before you sign. We are telling you now, on a public page, before you have spoken to anyone.
Hardware and third-party accounts sit on your side of the line for the same reason: scanners, PrintNode and your carrier accounts are never included in any tier, and we would rather you own them outright than have them locked inside a WMS contract.
The team that built your configuration answers your calls. There is no tier-one queue reading a script, and no ticket that has to be explained from scratch.
We monitor your installation continuously, with no agent to install. We often see a problem before you call. How Watchpost works.
8am – 6pm CT, Monday – Friday. Floor-down response target: reachable for emergencies. Everything else: same business day.
Threshold changes, new label templates, new locations — that is configuration, not a change request, and it is not billed.
If you came to us through an Acumatica VAR, none of this changes. Your VAR stays the Acumatica relationship. WMSi implements the WMS and takes the WMS calls. You do not sit between two vendors pointing at each other.
Where we have not published a specific commitment — disaster-recovery posture, liability terms — that is deliberate, and we tell you where the real answer lives instead of guessing.
Sometimes. A single site with clean data, one shift and no lot tracking is the fast case. We will tell you which case you are in on the discovery call, not after you sign.
Three things, in order: item and location data that does not match the rack, Wi-Fi that does not reach the top of the racking, and a go-live scheduled on month-end. All three are visible in week one, and we name them in week one.
All phases are conducted remotely unless on-site is mutually agreed. When on-site work is agreed, travel is available and billed independently. This keeps the price predictable and lets us staff your project with the right team regardless of location.
Hard cutover — the standard approach for WMS-to-Acumatica implementations. We do not run your old process alongside the new system; reconciling two sources of truth creates more risk than it removes.
Cutover is designed to happen between shifts, so the intent is no. The exact cutover approach and timing are confirmed during Discovery, based on your operation.
Every customer gets a dedicated VM rather than a row in a shared tenant — that part is settled and it is how the product is built. Here is the rest of what a procurement team needs: your VM runs on dedicated cloud infrastructure, US-based, with nightly encrypted backups retained for 30 days. Disaster-recovery posture and liability terms are addressed in the Master Services Agreement — bring your procurement or legal team into the conversation and we will walk through both in detail before you sign.
Zebra devices are recommended for mobile scanning and label printing. Most Android devices running Chrome are compatible. "Will this run on the guns I already own?" is one of the first questions a warehouse manager asks, and it deserves a device and OS answer rather than a conversation.
That is a good time to do this, not a bad one. You are already changing process and your data is already being cleaned. We coordinate with your VAR's Acumatica timeline rather than competing with it.
No. It is a separate one-time fee, published per tier: $10,000 on Rampart, $14,000 on Bastion, $20,000 on Stronghold, $28,000 on Fortress. Sentinel replaces it with the $1,500 Kickstart Package, which is a deliberately narrower scope — one 90-minute walkthrough call, no data migration, no custom label design. The full rate card.
Implementation work past 90 days from contract execution is billed at $175 an hour, and a project that has been dormant for two consecutive flagged months carries a $2,500 restart fee. Both are published on the pricing page, because a fee you only discover when it is charged is not a fee, it is a surprise.
One call gets you a fixed scope, a fixed price against the published rates, and a go-live date you can put in front of your board.