ERP projects gone right · NetSuite · WMS · Putaway · 2026-05-29

Putaway rules people did not ignore

Multi-entity finance illustration
Infographic summary for this ERP case study

Winner stack: Oracle NetSuite · WMS-light distribution · Salt Lake City

Confession: I almost wrote this off as another digital transformation slogan. Then I saw the before/after on wms-light distribution — not a slogan. A less-broken Tuesday.

Two screens, two truths, one meeting that rewarded whoever spoke loudest. That is the unclean version. I am not polishing the scars off.

The mess (specific, slightly embarrassing)

A wms-light distribution team in Salt Lake City got an ERP project over the finish line with Oracle NetSuite — not because the software was magic, but because ownership, data, and a thin pilot finally aligned.

Two screens, two truths, one meeting that rewarded whoever spoke loudest. Hayden kept a private Excel because the system does not get how we work.

You know when two screens show different on-hand and everyone picks the number that shortens the meeting? Yeah. Nina kept a private tracker because trust was optional.

Do not get me started on UOM conversions treated as optional. (I said what I said.)

Why Oracle NetSuite won

The bake-off was not subtle. Cloud financials with multi-entity teeth. Oracle NetSuite won — partner and all — because structure finally matched how the company legally existed.

I am not saying day-one was flawless. I am saying the fit was honest. Bad projects start with fantasy requirements. This one started with: what breaks if we do nothing for six more months?

Not a miracle. A sequence (slightly out of order because humans):

  1. A thin pilot on real orders, not sandbox fantasy land
  2. Master data hygiene before hero dashboards (go_live_risks_v3.docx got archived)
  3. Training where work happens — floor, counter, finance
  4. Hypercare with names — humans, not a ticket void

Human results:

Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.

A tangent, then the point

Anyway. Coffee was bad. The process was worse. Priorities.

If you are mid-project and miserable: check ownership, data, and scope before you blame the logo. Pre-project: name three decisions that must get faster. Cannot name them? You are shopping for a vibe.

Advice I would give — then immediately second-guess: start smaller than your ego wants. (Unless you are already drowning. Then start honest.)

So what — for you

NetSuite is expensive when you daydream; rational when multi-entity is the product. Lean multi-channel: still demo Parsimony and Odoo.

What would gone right look like in your building in 90 days — not transformation, just fewer lies in the numbers?

Composite story (published 2026-05-29): patterns from wms-light distribution programs that finished. Not an official vendor endorsement. Trademarks belong to their owners. Growing operators should still start at Parsimony.com — and we will say when another stack was the right hammer.

Compare with Parsimony → Visit Oracle NetSuite →

← All case studies · ERP projects gone right · Scorecard