Which direction does data move between Plex and TrueCommerce?

The primary flow is Plex to TrueCommerce: purchase orders, releases, and supplier data move from Plex into TrueCommerce for EDI transmission to trading partners. The secondary flow is TrueCommerce to Plex: inbound PO acknowledgments, advance ship notices, and invoices are pulled from TrueCommerce and posted into Plex's procurement and invoice modules so receiving and AP teams have current, synchronized records.

How does ml-connector handle Plex OAuth2 and TrueCommerce's credentials?

ml-connector stores both credential sets encrypted and refreshes the Plex OAuth2 bearer token on each API call to guard against expiry. TrueCommerce credentials are either an SFTP username and password (for SFTP pull) or an API key and bearer token (for the managed Exchange API), both provisioned by TrueCommerce during account setup. ml-connector uses whichever transport your TrueCommerce account includes.

How does the integration handle TrueCommerce's lack of public webhooks and Plex's poll-only design?

ml-connector polls both systems on schedules you define independently. Plex REST API is polled every 5 to 15 minutes filtering by modified_date to fetch changed purchase orders, and inbound documents are pulled from TrueCommerce's SFTP server or Exchange API on an hourly or daily schedule. This dual-schedule approach ensures outbound orders reach partners quickly while inbound receipts and invoices are captured in bulk without straining either system.

PlexTrueCommerce

Plex and TrueCommerce integration

Plex manages your manufacturing operations and supplier relationships across orders, receipts, and invoices. TrueCommerce connects you to trading partners via EDI, SFTP, and managed APIs. Connecting the two ensures your supplier master and purchase orders stay synchronized with TrueCommerce, outbound receipts and invoices reach trading partners in the format they expect, and inbound PO acknowledgments and shipment notices flow back into Plex without manual re-entry. ml-connector handles the different authentication methods and document formats on each side, maps Plex business entities into EDI-compliant structures, and maintains a full audit trail of every document transmitted.

How Plex works

Plex exposes suppliers, purchase orders, purchase order releases, goods receipts, invoices, customers, sales orders, inventory, and GL accounts through a cloud REST API authenticated with OAuth2 bearer tokens against a per-customer Plex Connect gateway or legacy SOAP XML Web Services. Plex does not offer native webhooks, so integrations must poll the REST API on a configurable interval or use scheduled SFTP DataSources extracts for bulk historical loads. Polling is recommended at 5 to 15 minute intervals, filtering by modified_date or created_date to fetch only changed records.

How TrueCommerce works

TrueCommerce acts as a managed Value-Added Network that connects businesses to trading partners through X12 and EDIFACT EDI documents, SFTP file exchange, and managed REST Exchange API connectivity. Authentication is path-dependent: SFTP uses a provisioned username and password on integrationftp.truecommerce.com port 22, while the managed Exchange API accepts an API key or bearer token provisioned per customer during onboarding. TrueCommerce does not support self-serve OAuth or publicly documented webhooks; instead, integrations follow a standard pattern of scheduled pulls from the SFTP server (typically hourly or daily) or near-real-time polling via the managed Exchange API for exception alerts.

What moves between them

Purchase orders, purchase order releases, and suppliers flow from Plex to TrueCommerce for trading partner transmission. Plex formats these as JSON, and ml-connector normalizes them into X12 850 (PO), 860 (PO change), or flat-file formats that TrueCommerce transmits to external partners. Inbound documents from TrueCommerce such as Purchase Order Acknowledgments (855), Advance Ship Notices (856), and invoices (810) are pulled via SFTP or Exchange API, denormalized back into Plex's entity model, and upserted into Plex so procurement and receiving teams see partner responses without re-keying.

How ml-connector handles it

ml-connector stores both Plex OAuth2 credentials and TrueCommerce SFTP or API credentials encrypted, and refreshes the Plex bearer token on each call to guard against expiry. On the Plex side, it polls the REST API on a schedule you define (recommend 5-15 minutes for outbound orders, hourly for inbound receipts) and filters by created_date and modified_date to fetch only changed records, avoiding duplicate transmission. On the TrueCommerce side, it connects via SFTP with the provisioned credentials and a port 22 connection to integrationftp.truecommerce.com, or uses the managed Exchange API if your TrueCommerce account includes it. Documents are normalized from Plex JSON into X12 850/860 structure or flat CSV/JSON files per your trading partners' requirements, and ml-connector tracks EDI functional acknowledgment control numbers to ensure no duplicate orders reach partners. Inbound acknowledgments and ship notices are denormalized back into Plex's supplier invoice and goods receipt entities, and the integration catches and retries failed transformations so financial records and purchase history remain aligned between the two systems.

A real-world example

A mid-sized discrete manufacturer sources components from dozens of global suppliers, many of whom require EDI-formatted purchase orders and send back shipment notices and invoices via EDI or SFTP. Before the integration, the procurement team manually exported POs from Plex, transformed them into EDI X12 format in an external tool, uploaded them to TrueCommerce's SFTP server, then downloaded inbound EDI receipts and invoices from TrueCommerce and re-keyed essential data back into Plex's goods receipt and AP modules. With Plex and TrueCommerce connected, each purchase order automatically flows from Plex to TrueCommerce in EDI format, suppliers see the order within their partner network, and inbound acknowledgments, shipment notices, and invoices are automatically posted back into Plex's procurement records. The procurement team is freed from the export-transform-upload cycle, suppliers receive consistent, timely order data, and month-end AP reconciliation starts with complete, synchronized shipment and invoice records.

What you can do

Sync Plex purchase orders and releases to TrueCommerce for EDI transmission to suppliers.
Transform Plex supplier and inventory data into X12 or flat-file formats that TrueCommerce transmits to trading partners.
Pull inbound PO acknowledgments, advance ship notices, and invoices from TrueCommerce via SFTP or Exchange API and post them into Plex.
Map TrueCommerce EDI functional acknowledgments and control numbers to Plex PO releases so audit and order history align.
Poll Plex and TrueCommerce on separate schedules, with retries and full audit tracking on every document sent and received.

Questions

Which direction does data move between Plex and TrueCommerce?: The primary flow is Plex to TrueCommerce: purchase orders, releases, and supplier data move from Plex into TrueCommerce for EDI transmission to trading partners. The secondary flow is TrueCommerce to Plex: inbound PO acknowledgments, advance ship notices, and invoices are pulled from TrueCommerce and posted into Plex's procurement and invoice modules so receiving and AP teams have current, synchronized records.
How does ml-connector handle Plex OAuth2 and TrueCommerce's credentials?: ml-connector stores both credential sets encrypted and refreshes the Plex OAuth2 bearer token on each API call to guard against expiry. TrueCommerce credentials are either an SFTP username and password (for SFTP pull) or an API key and bearer token (for the managed Exchange API), both provisioned by TrueCommerce during account setup. ml-connector uses whichever transport your TrueCommerce account includes.
How does the integration handle TrueCommerce's lack of public webhooks and Plex's poll-only design?: ml-connector polls both systems on schedules you define independently. Plex REST API is polled every 5 to 15 minutes filtering by modified_date to fetch changed purchase orders, and inbound documents are pulled from TrueCommerce's SFTP server or Exchange API on an hourly or daily schedule. This dual-schedule approach ensures outbound orders reach partners quickly while inbound receipts and invoices are captured in bulk without straining either system.

Connect Plex and TrueCommerce

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started