Plex and Adobe Commerce integration

What moves between them

Products and pricing flow from Plex into Adobe Commerce storefronts to keep catalogs and pricing current without manual editing. Purchase orders and supplier records from Plex are also available for B2B buyers in Adobe Commerce. Orders placed through Adobe Commerce storefronts are read back into Plex for manufacturing planning and fulfillment. Invoices and payments generated in either system are recorded to maintain financial alignment. This sync runs on a Plex poll interval (typically every 5 to 15 minutes) and is one-way or two-way depending on which entities the customer configures.

How ml-connector handles it

ml-connector stores both credential sets encrypted and polls Plex's REST API on your configured interval to detect new or modified products, pricing, and orders. It maps Plex product codes and GL accounts to Adobe Commerce product SKUs and custom attributes so catalogs stay in sync. For B2B flows, Plex purchase orders are written to Adobe Commerce's native PurchaseOrder and NegotiableQuote resources. When Adobe Commerce generates orders and invoices (either via webhook if 2.4.4+, or via polling if earlier versions), ml-connector reads them back into Plex, creates matching sales orders and invoices, and links them to the correct GL accounts for financial reconciliation. Plex rate-limit responses (HTTP 429) trigger exponential backoff, and every record carries a full audit trail so a failed downstream write can be retried without creating duplicates. ml-connector validates OAuth tokens before expiry and refreshes them proactively to avoid outages during long polling intervals.

A real-world example

A mid-sized discrete manufacturer in automotive supplies runs Plex ERP for production and finance, and operates two B2B Adobe Commerce storefronts for tier-1 suppliers and tier-2 aftermarket customers. Before integration, product catalog owners updated Plex pricing and availability nightly, and the e-commerce team manually pushed changes to Adobe Commerce by CSV export every morning, creating a 12 to 24-hour lag. Orders from the two storefronts were printed, re-entered into Plex, and the finance team reconciled invoices by hand at month-end. With Plex and Adobe Commerce connected, product pricing and availability sync every 15 minutes, so customers always see current information. Orders flow directly into Plex for manufacturing and fulfillment, and invoices are automatically recorded in the GL, eliminating re-entry and reducing month-end close by two days.

What you can do

• •Sync products, pricing, and availability from Plex into Adobe Commerce storefronts in real time on a configurable poll interval.
• •Make Plex purchase orders and supplier data available to B2B buyers through Adobe Commerce native PurchaseOrder and NegotiableQuote resources.
• •Read orders and invoices from Adobe Commerce back into Plex for manufacturing planning, fulfillment, and GL posting without manual re-entry.
• •Authenticate Plex with OAuth 2.0 client credentials and Adobe Commerce with OAuth 1.0a (PaaS) or OAuth 2.0 (SaaS), and validate webhook signatures where available.
• •Poll Plex with exponential backoff on rate limits, refresh tokens before expiry, and keep a full audit trail so failed syncs can be replayed without duplicating records.

Questions

Which direction does data move between Plex and Adobe Commerce?

Products, pricing, and suppliers flow from Plex into Adobe Commerce storefronts. Orders and invoices flow from Adobe Commerce back into Plex for manufacturing, fulfillment, and financial reconciliation. The sync is configurable per entity type, so you can choose one-way or two-way for each data class.

How does ml-connector handle Plex's polling-only model and lack of webhooks?

ml-connector polls Plex's REST API on your configured interval (typically every 5 to 15 minutes) and filters by modified_date to detect new or changed records. If Adobe Commerce is version 2.4.4 or later and has webhooks enabled, ml-connector can consume order and invoice events synchronously; for earlier versions, it also polls Adobe Commerce so you do not have to wait for the next Plex poll interval.

What happens if Plex or Adobe Commerce rate-limits the API calls?

ml-connector detects HTTP 429 rate-limit responses and backs off with exponential jitter, then retries after a delay. It also proactively refreshes OAuth tokens before expiry so outages during long polling windows are prevented. Every record carries audit data, so if a downstream write fails, it can be safely replayed.