Why Your ERP Is Bad at Shipment Tracking (and That's Fine)
Building shipment visibility into your ERP sounds efficient. In practice, it means slow development, stale data, and a tracking experience your customers will never use. Standalone tools exist for a reason.
The "just build it in the ERP" instinct
Every manufacturer hits this moment. You need shipment tracking. Someone on your team says: "Why don't we just build it in Epicor? We already have the data. We'll create some BAQs, add a dashboard, and we're done."
It sounds efficient. One system, one codebase, one team to maintain it. In practice, it almost always goes sideways.
Three reasons ERP-built tracking fails
First, ERPs are optimized for transactions, not real-time visualization. Epicor Kinetic stores pack slips, tracking numbers, and shipping dates in relational tables. Turning that data into an interactive map with live carrier status requires a fundamentally different architecture. Dashboards and BAQs can display tabular data. They cannot render a 3D globe with AIS vessel positions.
Second, the development timeline is brutal. Custom Epicor development means BAQ design, dashboard layout, custom function testing, and deployment through your Epicor change management process. Six months of developer time to build something that a purpose-built tool delivers out of the box.
Third, your customer cannot use it. Even if you build a tracking dashboard in Epicor, it lives inside your ERP. Your customer does not have an Epicor login. You would need to build a separate web portal, which is now a second application to maintain.
What ERPs are good at (and should keep doing)
ERPs are transaction systems. They excel at recording what happened: this order was placed, this job was scheduled, this pack slip was created, this carrier was assigned. That data is the source of truth for your business.
The mistake is asking the ERP to also be the presentation layer for that data. Your ERP should store and manage shipment records. A separate tool should present them to your customers in a format they can actually use.
The standalone tool advantage
Standalone tracking tools like FreightPane read from your ERP and add the layers an ERP cannot provide: interactive maps, real-time carrier integration, customer-facing portals, and mobile-friendly share links. The ERP remains the system of record. The tracking tool is the window into that data.
The API connection between the two is thin and read-only. FreightPane queries Epicor's REST API on every page load. No sync jobs. No data warehouse. No middleware. If Epicor is updated, FreightPane reflects the change on the next request.
The total cost comparison
Custom Epicor dashboard development: 3-6 months of developer time, $50K-$150K in consulting fees, ongoing maintenance burden, and a result that only your internal team can see.
FreightPane: $499/month, live in minutes, customer-facing by default, maintained and updated by a dedicated team. The decision is not close.
Let your ERP do ERP things
Epicor Kinetic is an excellent manufacturing ERP. It should keep doing what it does well: managing orders, jobs, schedules, and shipping records. Shipment visibility is a different product category with different requirements. The right answer is a thin API connection between the two, not building one inside the other.