r/ERP • u/Wings4Mercury • 6m ago
Question Deacom ECI - worth considering?
Curious to hear real-world experiences with Deacom (ECI) — is it worth considering as a replacement for an old Dynamics GP setup that's been running a heavily customized catchweight/lot-tracking add-in (yarn/textile-adjacent, sold by weight but purchased by count, pallet-level actual vs. nominal quantities, lot/Batch traceability).
A few things I'd love input on:
- General take — anyone running it day-to-day? What's good, what's painful? How's ease of use for regular users vs. admins/configurators?
- Catchweight/lot handling — is dual quantity (nominal vs. actual) and lot/sub-lot tracking genuinely native, or does it still need bolt-ons/customization to get real reconciliation and weight-based costing?
- Specific-lot costing — can Deacom pin an individual lot/batch to its own original receipt cost and keep it from blending with other lots, especially through transfers? (FIFO Actual is mentioned in their materials, but not clear if it's true specific-cost persistence.)
- Landed cost — does Deacom have a real landed cost workflow (freight/duty/customs allocation by weight, value, etc.) that updates lot-level cost, or is this something you had to build/customize?
- Customization — how do you actually tailor Deacom to specific business logic? Native configuration/scripting, or does it need third-party dev work?
- Reporting — what's the reporting story? Is built-in reporting sufficient, or do most shops end up bolting on Power BI / Crystal / something else?
- Cost — how is pricing structured (per-user, per-transaction volume, flat license + modules)? What did implementation run (cost + duration, and how much was configuration vs. custom dev)? And what's the ongoing recurring cost — monthly/annual license or subscription fees?
Appreciate any first-hand experience, good or bad.