Custom ERP Integration - Signalx Webflow Ecommerce Website Template

Some manufacturers run ERPs that don't fit the standard categories — built in-house, deeply customized commercial products, or vertical-specific platforms unique to their industry. The integration for these starts with structured discovery, not assumption.

When 'custom ERP' is the right description

Custom ERP integration applies in three specific situations:

In-house developed systems — manufacturers (typically large ones) who built their own ERP over time because no commercial product fit their specific manufacturing process. Examples exist in aerospace, defense, semiconductor, and specialized chemical operations.
Heavily customized commercial ERPs — companies that started with a commercial ERP (SAP, Oracle, JDE) but modified it so extensively over time that vendor-standard integration patterns no longer apply. The "S" in SAP no longer stands for "Standard" at these customers.
Vertical-specific platforms — ERPs built for narrow industries (specific verticals in process manufacturing, fashion-specific systems, niche food and beverage platforms) that aren't on standard integration vendor radars.

Why generic 'we integrate with anything' isn't enough

Custom ERP integration is where most vendor promises break down. The standard pitch is "we have a flexible integration framework — we can connect to anything." This is technically true and operationally insufficient. The integration framework doesn't know the customer's specific data model. Discovery work, mapping work, adapter development, and testing work all have to happen — and they take real time and effort.

The honest approach is structured discovery first, scope definition second, build third. Skipping discovery and going straight to build is how custom ERP integrations turn into 12-month projects.

Common integration mechanisms

Across the custom ERP integrations we've designed, four mechanisms cover most customer environments: direct database read access, API calls where the customer's ERP exposes them, scheduled SFTP delivery of flat-file extracts, and custom adapter development for environments where none of the standard mechanisms apply. The discovery phase identifies which combination is right for the specific environment.

The discovery phase

The first 3-4 weeks of a custom ERP integration are structured discovery, not coding:

Data model walkthrough — with the customer's IT team, documenting what entities exist, what they're called, what relationships exist between them. For in-house systems, this often surfaces undocumented decisions made years ago.
Data quality assessment — sampling key tables for completeness, consistency, and currency. Identifying tables where the data hasn't been maintained.
Access pattern definition — determining how Horizon will access the data. Options include direct database queries, API calls (if any exist), scheduled extracts, or custom adapter development.
Customization mapping — for heavily customized commercial ERPs, identifying which standard objects have been modified and how the modifications affect integration.
Scope confirmation — defining what data Horizon will read, what it will write back, and what the operational handoff between systems looks like.

The discovery deliverable is a written integration design document that both Horizon and the customer sign off on before build begins.

Adapter-based build approach

For custom ERPs, the integration is typically built as an adapter layer specific to that customer's environment:

Connection layer — handling authentication, network access, error handling specific to the customer's system
Translation layer — converting between the customer's data model and Horizon's standard planning entities
Scheduling layer — managing data refresh cadences appropriate to the customer's operational rhythm
Error handling and reconciliation — what happens when data is incomplete, late, or conflicting

The adapter is documented and handed to the customer's IT team for future maintenance. Customer-specific adapters are not magic — they're configuration code that the customer's team can understand and extend.

What custom ERP integration realistically takes

For a typical custom ERP integration with moderate complexity:

Weeks 1-4: Structured discovery as described above.
Weeks 4-10: Adapter build — connection, translation, scheduling, error handling.
Weeks 10-14: Data load and master data validation.
Weeks 14-20: Planning configuration, parallel run, validation.
Weeks 20-24: Cutover and stabilization.

The total is 20-24 weeks versus 8-12 weeks for pre-built connector ERPs. The added time is real and shouldn't be glossed over.

Working with the customer's IT team

Custom ERP integration is collaborative by nature. The customer's IT team holds the institutional knowledge of the data model, the business logic, and the operational constraints. The Horizon implementation team brings the planning data model, the integration patterns, and the discovery methodology. The two work together through discovery and adapter build, with the customer's team owning the system of record and Horizon owning the planning layer.