Epicor Integration FAQs: manufacturing & distribution ERP, every channel connected

The InfiPlex Epicor integration connects your Epicor Kinetic or Prophet 21 ERP to the InfiPlex Inventory & Order Management System — and through it, to 130+ marketplaces, shopping carts, and retail EDI trading partners. Orders from every connected channel push into Epicor as sales orders, shipments you make in Epicor flow back out as tracking to each channel, and Epicor inventory levels sync everywhere in real time.

Yes — InfiPlex connects to both Epicor Kinetic (Epicor's manufacturing-focused ERP) and Epicor Prophet 21 (Epicor's distribution-focused ERP), with our team mapping the connection to whichever product line your business runs.

Our team configures the connection directly with you and your Epicor administrator during onboarding — there's no per-channel connector to buy and no development work required on your end. We handle the account link, then map your items, warehouses, and order fields together.

Your InfiPlex OMS site is provisioned within 1–2 business days of sign-up, and marketplace connections come up in the usual 1–3 day window. The Epicor side is scoped with you during onboarding — ERP integrations take longer than a marketplace connection because item, warehouse, and workflow mapping deserve care.

No — InfiPlex is a no-code integration, and our USA-based team performs the configuration with you. You don't need in-house development resources dedicated to maintaining the connection.

InfiPlex pulls orders from your connected channels approximately every 15 minutes (faster if needed) and pushes them into Epicor as sales orders with line items, customer details, and shipping selections mapped to your fields.

Yes — fulfill the sales order in Epicor as you normally would, and InfiPlex pulls the shipping information from Epicor and syncs the tracking number back to the originating marketplace automatically.

Automatically, regardless of where fulfillment happened. If you ship in Epicor, InfiPlex pulls the shipment and posts tracking to the channel; if you ship in the InfiPlex OMS or through a connected 3PL, the same confirmation flows to both the marketplace and Epicor.

Yes — InfiPlex handles retail EDI connections (Target DVS, Costco, Home Depot, and any EDI trading partner) and pushes those orders into Epicor alongside your marketplace orders, often with significant EDI VAN cost savings.

Yes — routing rules decide per order whether fulfillment happens in Epicor, in your own warehouse through the OMS, or at a connected 3PL/WMS via the 3PL Connector.

InfiPlex pulls inventory levels from Epicor and distributes them to every connected channel in real time, so Amazon, Walmart, Shopify, and the rest all reflect what Epicor says is available.

Yes — you can map multiple Epicor warehouse or plant locations to the corresponding locations on your channels, or total inventory across locations and send a single combined quantity per SKU.

Yes — buffers apply per channel in InfiPlex, so you can hold back safety stock on a fast-moving marketplace while exposing full Epicor availability to your own webstore.

Continuously — InfiPlex pulls orders roughly every 15 minutes and pushes inventory adjustments back to every channel in real time as they occur.

Standard stocked-item inventory sync works out of the box; make-to-order or highly configured product flows are scoped individually during onboarding, since these often need custom handling regardless of which OMS or ecommerce layer sits on top.

Custom development multiplies cost and maintenance burden: each channel needs its own code, testing, and ongoing upkeep as marketplace APIs change. InfiPlex is one connection that carries every channel — adding Walmart or TikTok Shop later is a configuration step, not a new development project — and Growth packages even include InfiPlex building new marketplace APIs at no additional cost.

Yes — Growth Pro includes Amazon Multi-Channel Fulfillment, FBA Inbound, Vendor Central Direct Fulfillment, and Vendor Central Retail, all flowing through the same Epicor rail.

InfiPlex supports QuickBooks Online today and Epicor on Growth Pro, so you can run the OMS through the migration: channels stay connected to InfiPlex while the ERP behind them changes.

Yes — the 3PL Connector program lets a 3PL connect each client's channels and systems, including Epicor where a client runs it, with each client in its own Site Area.

Yes — wholesale orders from the InfiPlex B2B eCommerce Portal or the Faire marketplace push into Epicor as sales orders just like retail channels, drawing on the same inventory.

Structurally the same — one OMS connection carrying every sales channel into the ERP as sales orders, with inventory syncing back out. Which ERP you use depends entirely on your business; InfiPlex adapts the field mapping to whichever system is your source of truth.

Epicor and other ERP connections are included with Growth Pro at $999.99/month — which also carries up to 100,000 SKUs, 10,000 included monthly orders ($0.05 per additional order), 4 new marketplace API integrations per year, the Marketplace Repricer, PIM, and the full Amazon channel set. Details are on the Pricing page.

The Epicor integration is part of Growth Pro rather than a per-channel license, and ERP configuration is scoped with you during onboarding so there are no surprises.

Manufacturing and distribution operations running Epicor typically clear Growth Pro's threshold on volume alone, and retiring custom-built or point-connector marketplace integrations usually covers a meaningful share of the cost.

Growth packages carry a 3-month minimum commitment and Partner packages a 12-month term. Given that ERP integrations are meant to run for years, most Epicor customers care less about the commitment than about the mapping being right.

InfiPlex's connection works with Epicor's core order and inventory data structures; our team confirms any industry-edition-specific field mapping considerations during onboarding for your specific Epicor deployment.