From the field
Notes on the problems that actually sink Epicor projects — written from inside implementations.
Short reads from the field
Notes on the problems that actually sink Epicor projects — written from inside implementations, not from a marketing calendar. Deeper guides are on the way.
Why Epicor implementations fail before go-live
Most failures are not software failures. They come from unclear ownership, weak testing, missing data, and poor process readiness — all fixable months before cutover if someone is watching for them.
MRP setup that actually plans
MRP output is only as good as part settings, lead times, buyers, methods, warehouses, and demand signals. Bad parameters produce suggestions nobody trusts — and then nobody uses MRP at all.
MES labor reporting explained
Useful labor data depends on how you structure employees, resource groups, job labor, indirect codes, and corrections. Get the structure wrong and payroll visibility goes with it.
Finance testing in Kinetic
AP, AR, GL, bank reconciliation, job costing, cost of sales, and month-end close must be tested with real scenarios before go-live — reconciling after cutover is ten times the work.
BPM vs. Epicor Functions
BPMs react to events in the flow; Functions are callable, reusable logic. Choosing the wrong one creates automation that is hard to test, hard to upgrade, and hard to hand over.
Connecting CAD to Kinetic
ETO shops win or lose on the engineering handoff. Automating method and BOM creation from SolidWorks through CADLink removes the retyping step where most costing errors are born.