Epicor Kinetic historical data: what manufacturing records matter?

What do Epicor Kinetic job and quality histories show?

Epicor Kinetic links jobs, operations, material issues, quality inspections, nonconformance reports and engineering changes into one manufacturing record. For a manufacturer or distributor with 50+ full-time employees at peak (contractors excluded), that chain shows how a customer order became a job, what went wrong on the shop floor, and how the problem was resolved.

This page is for CFOs at manufacturers and for Epicor partners. It describes records at a metadata level. Partners never export, upload or describe the underlying records.

Which Epicor records carry the most workflow context?

Free-text notes on nonconformance and corrective action are the richest layer, since they describe causes in plain language.

What stays out of an introduction?

Manufacturing records often contain material that belongs to someone else. Be clear about the boundary.

• Customer-owned specifications and drawings. If the customer supplied the design, the company probably cannot license it without consent.
• Controlled or regulated content. Defense and government work can carry handling restrictions; see government contractors and what can be licensed.
• Personal data. Operator names, employee IDs and contact fields need de-identification and redaction rules agreed before any work begins.
• Supplier confidential terms. Pricing agreements may bar disclosure.

A company can still qualify when these are excluded, because job and quality histories can often be described without the restricted attachments. SourceX and the company decide scope during the inventory.

The 4-layer Epicor depth test

Ask the CFO or plant controller four things, one per layer.

1. Transactions: how many years of closed jobs and orders sit in the live system?
2. Quality: are nonconformance and corrective actions recorded here, or on paper and spreadsheets?
3. Engineering: are change approvals tracked in Epicor or in a separate PLM?
4. Context: where do emails, shared-drive procedures and support tickets live relative to the ERP?

A company with strong answers on layers one and two and several other systems is closer to the 10-15+ systems seen at stronger candidates. Compare approaches in the Acumatica and SAP Business One briefs.

How far back does the history go, and what about exports?

Approvals routed through Epicor business process management (BPM) workflows leave a decision trail alongside job records, and distribution customers on Prophet 21, Epicor's distribution product, face the same questions about order and purchasing history. Typically history reaches back to go-live of the current platform and any migrated legacy data. Epicor customers may have moved between versions, cloud and on-premises, or consolidated sites, which can change what remains. Keep the question practical: is there a named person who can run exports, and do older job records still exist? Only quote vendor limits if you hold vendor documentation.

When is a good moment to raise it?

Does this apply to franchise or distribution models too?

Distribution businesses on Epicor share the order and purchasing records described above; the wholesale distribution page gives the industry view. Franchise systems are different, because franchisee data raises its own boundary questions, covered in the franchisor brief.

What does the path from plant controller to SourceX look like?

1. A controller or CFO answers the four depth-test questions in a short call.
2. The sponsor (owner, CEO, CFO or authorized representative) decides whether to explore a license, using your referral link or the referral form.
3. SourceX qualifies the company, and the controller or ERP administrator helps compile the inventory of Epicor modules, quality tools and other systems.
4. Customer-owned drawings and controlled content are scoped out before price and terms are agreed.
5. The company signs only if the terms work for it, and the partner reward follows once SourceX receives payment.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is not deducted from what the company receives. Epicor partners and advisers should check their own rules on referral fees and disclosure, and read the program terms. ERP consultants may also find the ERP consultant page useful.

What should a partner say to a plant controller?

Keep it short and factual. Mention that some manufacturers license historical operating records to AI developers, that the company keeps ownership and approves scope and price, and that nothing is shared without a signed agreement. Then ask only about the four layers above. Avoid asking for job numbers, part names, customer names or quality findings, since those are the confidential details a partner should never see. If the controller is interested, the next conversation is between the sponsor and SourceX, not with you.

Next step

Choose one Epicor customer that has completed a recent upgrade or has a quality system with years of closed corrective actions. Run it through the company fit checker, then register as a partner and introduce it. The who qualifies page lists the baseline.