Plex and Cin7 integration

What moves between them

The main flow runs from Plex to Cin7. Purchase orders and supplier invoices from Plex map into Cin7 purchases at the ORDER and INVOICE stages, aligned by supplier and part number. Supplier records sync from Plex into Cin7 supplier master data. Sales orders created in Cin7 flow back to Plex customer records and sales orders so Plex production can track demand by customer. The chart of accounts is aligned in both directions so invoice GL mappings reference valid Cin7 accounts. Both systems require polling since Plex has no webhooks and Cin7 webhooks are optional; ml-connector polls both on a schedule tied to your procurement and sales cycle.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Plex side it presents OAuth2 client credentials, refreshing the Bearer token when a call returns 401, and implements exponential backoff on HTTP 429 since Plex rate limits are not publicly documented. On the Cin7 side it presents the custom API key headers on every request. ml-connector detects duplicate purchase orders and invoices by matching external reference fields since Plex REST API does not document Idempotency-Key support, and uses Cin7's Approach field to stage purchases correctly through procure-to-pay. Since Plex SOAP DataSources are customer-specific and available procedures vary per Plex configuration, ml-connector polls REST endpoints where possible and falls back to DataSources only if REST lacks the needed entity. Suppliers are matched by name or code, and parts are matched by Plex part number against Cin7 product SKU. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized discrete manufacturer uses Plex for production planning and procurement, and Cin7 Core for distributed inventory and fulfillment across multiple warehouses. Before the integration, the procurement team exported purchase orders from Plex weekly, re-entered line items into Cin7, and then manually matched supplier invoices to purchase orders to avoid duplicate payments. Sales orders were entered separately in Cin7, and Plex had no visibility of customer demand, forcing production to guess at job sequencing. With Plex and Cin7 connected, each purchase order flows into Cin7 on creation, invoices post automatically, and sales orders from Cin7 populate Plex demand signals. The procurement team no longer re-keys purchase data, and production can plan to actual customer orders.

What you can do

• •Sync Plex purchase orders, releases, and supplier invoices into Cin7 purchases at the correct procure-to-pay stage.
• •Map Plex suppliers and parts to Cin7 suppliers and products by code, keeping both systems aligned.
• •Flow Cin7 sales orders back to Plex customer records and sales order master data.
• •Authenticate Plex with OAuth2 client credentials and Cin7 with custom API key headers, with exponential backoff on rate limits.
• •Poll both Plex and Cin7 on a schedule tied to your procurement cycle, with full deduplication and audit trail on every record.

Questions

Which direction does data move between Plex and Cin7 Core?

The main flow is Plex into Cin7. Purchase orders, releases, and invoices move from Plex into Cin7 purchases, while suppliers and parts are aligned between both systems. Sales orders created in Cin7 flow back to Plex customer records and sales orders so Plex can see customer demand for production planning.

How does the integration handle Plex's OAuth2 and Cin7's custom API key headers?

ml-connector stores both credential sets encrypted and presents each on every request. Plex credentials are refreshed when a call returns 401, and Cin7 API keys are presented as custom headers. Both systems are polled on a schedule since neither offers full webhook coverage that ml-connector can reliably use.

How does the integration match suppliers, parts, and purchase orders across the two systems?

Suppliers are matched by name or code from Plex to Cin7 suppliers. Parts are matched by Plex part number to Cin7 product SKU. Purchase orders and invoices are deduplicated by external reference field since Plex REST does not document Idempotency-Key support. Cin7's Approach field (ORDER, INVOICE, RECEIVE) ensures each purchase is staged correctly through procure-to-pay.