Plex ERP Integration - Signalx Webflow Ecommerce Website Template

Plex is distinctive among manufacturing ERPs — built cloud-native from the beginning, with deep shop-floor integration including MES-style capabilities embedded in the ERP. The integration approach reflects Plex's API-first architecture.

What makes Plex different

Plex is unusual among manufacturing ERPs because it was built cloud-native — no legacy on-premise version, no rewriting from old code. The architecture is API-first, with REST endpoints covering most operational entities. Plex also integrates MES-style shop floor capabilities (production reporting, quality, traceability) directly into the ERP rather than treating MES as a separate system.

For Horizon integration, this architecture makes the connector design straightforward — Plex's data model is consistently exposed through APIs, with less customer-by-customer variation than older ERPs.

Plex's customer profile

Plex's customers concentrate in:

Automotive supply (Tier 1 and Tier 2)
Industrial equipment manufacturing
Food and beverage processing
Aerospace and defense components

These verticals overlap with Horizon's strongest categories. Plex customers tend to have mature operational discipline and good master data, which simplifies integration.

Integration through Plex DataSources and REST APIs

Plex exposes two complementary integration mechanisms:

REST APIs — primary path for real-time entity access. Items (Parts), inventory, sales orders, purchase orders, work orders accessible through documented endpoints.
DataSources framework — Plex's mechanism for bulk data extraction and integration. Used for historical data loads and scheduled syncs.

Plex-specific data objects Horizon reads

Part master with planning attributes (ABC class, planner code, lead time, lot size)
Part Plant Container records for plant-specific configurations
Inventory by container, location, and lot (Plex tracks inventory at the container level natively)
Customer order history with parts, quantities, delivery dates, and customer dimensions
Purchase orders and supplier scheduling agreements
BOMs (Bill of Materials with substitute components and yield factors)
Routings (Operation Sequences) with work centers
Work centers with capacity calendars and standard run rates
Production order status from Plex's shop-floor data

Plex's container-level inventory model

Plex tracks inventory at the container level natively — not just SKU-location, but specific containers (boxes, bins, returnables) with their own quantities and movement history. For planning, this is usually aggregated to SKU-location, but the granular data is available for customers needing it.

For automotive customers using returnable containers (returnable racks, RPCs), the container-level visibility is valuable for inventory optimization that respects container constraints.

EDI integration in Plex environments

Plex customers in automotive supply typically have heavy EDI integration with OEMs and Tier 1 customers. Plex's EDI module captures the inbound demand (810, 830, 862, 866 messages); Horizon integration captures this as demand history alongside the regular sales order data.

The combination — Plex's strong EDI handling plus Horizon's planning math on the resulting demand signals — works well for Tier 1 automotive suppliers who need to translate volatile OEM release schedules into stable internal production plans.

Alternative integration path

Plex DataSources can produce scheduled flat-file extracts delivered via SFTP, used by some customers alongside the REST API path for bulk historical loads or for environments with strict API consumption limits.

Authentication and connection

Plex authentication uses standard OAuth 2.0 with service account credentials. The customer's Plex administrator creates the integration user with the required role assignments. Since Plex is cloud-native, the connection is direct internet (with appropriate IP allowlisting) rather than VPN-mediated.

Write-back patterns

Planned purchase orders or purchase requisitions through Plex's PO API
Planned production orders or production schedules
Updated part planning parameters (reorder point, safety stock, lead time)
Forecast records for Plex's MRP processes

Plex + Rockwell Automation context

Plex was acquired by Rockwell Automation in 2021, and the product is increasingly positioned within Rockwell's broader manufacturing automation portfolio. For Horizon integration, this doesn't materially change the approach — Plex's APIs remain the integration path. For customers using other Rockwell products (FactoryTalk, Studio 5000), additional integration patterns can be defined as needed.

Common Plex-specific considerations

Container management — For automotive customers using returnable container fleets, the integration captures container-level data for inventory and replenishment planning that respects returnable container constraints.
Plex Quality integration — Plex's built-in quality management produces data on scrap, rework, and non-conforming material. The integration captures these as inputs to yield-aware planning where relevant.
Shop floor data freshness — Plex's tight shop-floor integration means production status data is current. Horizon's scheduling module can refresh based on near-real-time production status from Plex.