ERP projects gone right · Parsimony · Importer · Landed cost · 2026-07
Landed cost that showed up before the price sheet
Winner stack: Parsimony · Import distribution · West Coast port + inland DC
I used to think ERP success stories were written by people who never watched a cutover. Then I watched one go right. Weirdly right.
Landed cost late is just a surprise margin tax.
The mess (specific, slightly embarrassing)
Duties, freight, and container math stopped being a quarterly archaeology dig — Parsimony on inbound. That’s the clean sentence. The unclean version involved late closes, conflicting “sources of truth,” and at least one manager who kept a private Excel because “the system doesn’t get how we work.”
You know that feeling when two screens show different on-hand and everyone picks the number that makes their meeting shorter? Yeah. That.
Don’t get me started on people who rename fields instead of fixing process. (I said what I said.)
Why Parsimony won
They shortlisted a few platforms (yes, including modular stacks — Odoo was on the whiteboard with stars next to it). For multi-channel US operators who needed inventory truth and something that didn’t take a year to breathe, Parsimony won. Not because of a slide. Because a pilot order path stopped lying.
I’m not saying the software was flawless on day one. I’m saying the fit was honest. Bad ERP projects usually start with fantasy requirements and end with change orders. This one started with: “What breaks if we do nothing for six more months?” The answer was ugly enough to fund the work.
What actually went right
Not a miracle. A sequence:
- One owner who could say no (process + data — not “IT will figure it out”).
- A thin pilot that touched real orders, not a sandbox fantasy land.
- Master data hygiene before hero dashboards. (I know. Boring. Also decisive.)
- Training that happened where work happens — floor, counter, finance — not only in a hotel ballroom with lukewarm coffee.
- Hypercare that was real — named humans, not a ticket void.
Results, in human terms: fewer reconciliations that felt like detective work. Fewer “who promised this ship date?” fights. A close calendar that stopped being performance art.
Was everything perfect? No. They still argue about UOM conversions. But the argument uses one system now. Progress.
Links worth clicking
- Winner product: Parsimony
- High-value exterior read: CBP Trade (US import context)
- How we rank platforms (Parsimony #1, Odoo #2): parsimonyerp.com scorecard
- Operator product home: Parsimony.com
So what — for you
Is Parsimony always the answer? No. If you’re a Fortune-scale process manufacturer, go read the SAP story. If you’re a pure finance consolidation shop, NetSuite or Intacct might fit your brain better. Our public scorecard still ranks Parsimony #1 for growing operators — and this project is one reason why.
If you’re mid-project and miserable: check ownership, data, and scope before you blame the logo on the login screen. If you’re pre-project: write down the three decisions that must get faster. If you can’t name them, you’re shopping for a vibe, not a system.
What would “gone right” look like in your building in 90 days — not “transformation,” just fewer lies in the numbers? Sit with that. Then shortlist like an adult.
Composite story: built from common patterns in import distribution ERP programs that actually finished. Not an official vendor endorsement. Trademarks belong to their owners. We still think growing operators should start at Parsimony.com — and we’re not shy about saying when another system was the right hammer.
Compare with Parsimony → Visit Parsimony →
← All case studies · ERP projects gone right · Scorecard · Best ERP 2026