---
title: CSF Race: Epicor Vision and Katana Integration Case Study
url: https://dataautomation.com/case-studies/csf-race/
description: CSF Race connected Epicor Vision and Katana around receipts, component dependencies and outsourced work, translating operator knowledge into precise...
---

[← All case studies](https://dataautomation.com/case-studies/) CSF Race

# Turning legacy ERP complexity into defined manufacturing workflows.

CSF Race connected Epicor Vision and Katana around receipts, component dependencies and outsourced work, translating operator knowledge into precise integration rules.

ERP integration Process discovery Inventory automation Receipt handling Exception analysis

**Manufacturing dependencies represented across systems** Implementation outcome

## Client

CSF Race

## Engagement

ERP and manufacturing integration

## Systems and workflows

- [Epicor Vision](https://dataautomation.com/fishbowl-epicor-migration/)
- [Katana](https://dataautomation.com/katana/)

Orders and purchase receipts -> Component and inventory adjustments -> Outsourced production workflows

## The challenge

CSF's integration had to connect manufacturing and inventory processes across a legacy ERP and a modern production platform. Receipts, component dependencies and outside processing needed consistent treatment across both systems.

An apparently simple status update could have inventory or accounting consequences. The implementation needed to reflect the actual operating process and preserve the meaning of each transaction.

## The implementation

### Map the transactions and their dependencies

DataAutomation worked with CSF's team to map purchase-order receipts, sales demand, component adjustments and outsourced conversions. The configuration separates inventory synchronization, order flows, purchase-order handling and receipt-driven component adjustments.

### Match automation to real inventory behavior

DataAutomation investigated how each system represented inventory changes and translated the client's operating requirements into consistent integration rules. This kept cross-system updates aligned with the work being performed.

### Resolve ambiguous status and exception rules

The implementation distinguished production, fulfillment and financial status changes so each triggered the appropriate action. Exceptions and conflicting data were surfaced for resolution rather than silently interpreted.

## What changed

CSF gained cross-system workflows for manufacturing processes that depended on more than a matching SKU. Receipts, component adjustments and outsourced work were connected according to the business's actual operating rules.

The implementation made critical distinctions explicit. Inventory deductions followed the client's process, order completion retained its operational meaning, and conflicting component rules were surfaced for resolution rather than silently applied.

## The scope of the engagement

Engineering for legacy systems where a small field or status difference can change inventory and accounting behavior.

Business outcomes and timelines reported by DataAutomation.

[PreviousField Trip Snacks](https://dataautomation.com/case-studies/field-trip-snacks/) [All case studies](https://dataautomation.com/case-studies/) [NextNuleaf](https://dataautomation.com/case-studies/nuleaf/)

## Audited every year.

Deloitte and Amazon SP-API audits in 2026. PwC and Amazon SP-API in 2025. Shadow AI was involved in 43% of the breaches [IBM studied for its 2026 report](https://www.ibm.com/reports/data-breach); we keep your data out of it. And if something we run goes wrong, we own the fix.

[See the latest AI incidents](https://dataautomation.com/ai-security/) [See our audits](https://dataautomation.com/audits/)

## Bring us the complicated part.

[See what changed for our clients ->](https://dataautomation.com/case-studies/)

[Book a free call](https://meet.dataautomation.com/meet-with-dataautomation) [Describe your setup](https://dataautomation.com/#describe)
