Epicor to Shopify Integration

Epicor and Shopify can be connected through Epicor's own Epicor Storefront Connector, which Epicor says supports inventory, order, and shipment data flows; third-party apps on the Shopify App Store built for specific Epicor products such as Prophet 21 and Kinetic; an iPaaS platform; or an embedded Shopify app such as Uncap Connect. Which route fits depends on which Epicor product you run and how much account pricing, payment terms, credit, and branch inventory logic the integration has to carry.

If you are running Epicor, you already know what it can do. Epicor does not sell one ERP, it sells a range built for specific trades, and which one you run changes the integration more than most people expect. Prophet 21 handles wholesale distribution with customer-specific pricing, branch inventory and matrix logic. Kinetic runs discrete manufacturing from quote through job completion. Eclipse serves electrical, plumbing and PVF trade distribution. BisTrack and LumberTrack sit on opposite sides of the lumber trade. Vision runs automotive parts distribution and Eagle runs retail hardware. They share a vendor and very little else, which is why each has its own page below.

‍

Shopify Plus is a different kind of platform. It is built to sell: consumer-grade storefront performance, a full B2B wholesale infrastructure for buyer-specific pricing and purchase order workflows, POS for retail, and DTC for everything in between. Together, Epicor and Shopify Plus can run every channel in your business from a single connected platform.

The problem is the space between them.

Most Epicor Shopify setups rely on a scheduled middleware sync. Inventory updates every few hours. Pricing exports run overnight. Orders land in Epicor on a delay. For a distributor with branch inventory that moves throughout the day, or a manufacturer whose available stock shifts every time a work order closes, a four-hour sync window is four hours of potential oversells, pricing disputes, and orders that sit unacknowledged in a queue.

Here is what that looks like on a real Tuesday afternoon.

A plumbing distributor on P21 has a major contractor account that just renegotiated their pricing. The new rates are live in Epicor by 10am. The Shopify sync runs at midnight. The contractor logs into the portal at 2pm, sees the old price, and places a $55,000 order. Correcting it means a call from your inside sales team, a void in Epicor, and a buyer who now calls to verify pricing before every significant order.

A fabrication shop on Kinetic closes a production job at 3pm. Forty units move from WIP to finished goods. Shopify does not know until the next scheduled sync. Meanwhile, two wholesale accounts order against stock that has technically just become available, but because Shopify's count has not updated, they see zero. Those sales do not happen.

Neither of those is a technology problem. Both are sync-schedule problems.

The sync-schedule problem in one sentence: Epicor holds your live pricing, live inventory, and live credit limits. A middleware connector exports a snapshot of those values on a schedule. Every hour between runs is a window where buyers are working with data that Epicor has already moved past.

The obvious costs are easy to measure: hours spent correcting orders, pricing discrepancies that require intervention, backorders that could have been prevented with live inventory data. Less obvious is what it does to your buyer relationships.

Wholesale accounts are not forgiving about self-service failures. A buyer who orders at the wrong price and gets a correction call does not trust the portal after that. They route their next order through your rep instead. Then the one after that. The digital channel your team invested in to reduce inside sales workload ends up generating more of it, because every significant order gets a verification call first.

That is not an edge case. It is the natural behavior of buyers who have been burned.

There are three other costs that compound quietly in the background.

Credit and terms enforcement. Epicor knows which accounts are on credit hold, what payment terms each customer carries, and what their outstanding balance looks like. Shopify does not, unless the integration puts that data in front of the checkout layer. Without it, a buyer on a restricted account can place an order freely. Finance catches it after it ships.

Middleware ownership. When Epicor releases a version update or Shopify changes an API endpoint, someone has to keep the connection current. Epicor says it manages supported API and schema updates for its own Storefront Connector. A connector that runs through a third-party middleware platform carries a subscription that runs indefinitely, and when an update breaks it, the fix can land on your team. You are paying to run an integration and separately paying to maintain it.

The two-store problem. Distributors and manufacturers who sell to wholesale accounts and also run a DTC or retail channel often end up with two separate Shopify stores syncing back to the same Epicor instance. Two catalogs to maintain, two inventory pools to reconcile, two sets of pricing data to keep consistent. Unified commerce is not two stores. It is one Shopify Plus platform configured to serve every channel, connected once to Epicor.

Each Epicor product has different customers, a different data model, and a different integration surface. The integration scope (real-time inventory, pricing, orders, customer hierarchy) is the same for all of them. The way we build it depends on which product you are running.

Prophet 21 is Epicor's wholesale distribution ERP and the default across PVF, industrial and branch-and-counter distribution. It exposes data through the P21 Middleware, carrying Data Services on OData v4, Transaction API Services for validated writes, and Entity REST Services, with each customer's API reference hosted at their own middleware address rather than published. Release 2026.1 moved the backend to .NET 10 and added bulk data API capabilities.

Two things decide a P21 project. Contract pricing and special price agreements have to resolve live rather than as an exported file, and branch level availability has to be real enough to support will call. Epicor's announced end of on-premises feature development, with a final P21 feature release in 2028, also affects what order the work should be done in.

Epicor Prophet 21 Shopify integration in detail

Kinetic is Epicor's discrete manufacturing ERP, running jobs, bills of material, work orders and MRP. Epicor documents an open REST API for it where all Kinetic services, including business objects, processes, reports, BAQs and Epicor Functions, are reachable through REST endpoints with API keys and access scopes.

The piece that decides a Kinetic commerce project is availability. A quantity on hand is often not available to sell, because units may be committed to an open job or allocated to a work order, so the storefront number has to be calculated with that logic rather than pushed raw. Business Activity Queries are how that calculation is defined, and Epicor Functions are where custom server-side logic belongs so it survives upgrades.

Epicor Kinetic Shopify integration in detail

Eclipse runs trade distribution: electrical, plumbing, HVAC, PVF and industrial, with front counter, branches, contract pricing and job management. Epicor describes its API as an integration layer built on a .NET Core engine exposing secure REST endpoints for Eclipse data and business logic, which is a better foundation than several competing distribution ERPs offer.

There is a commercial detail worth knowing before budgeting. The API comes in two tiers, and while Product, Customer, Inventory and Priceline sit in the standard set, both Sales Order and Price Matrix are premium bundles licensed separately. Submitting orders from a storefront and resolving matrix pricing are therefore the two things that need licensing beyond the standard endpoints.

Epicor Eclipse Shopify integration in detail

BisTrack runs lumber and building materials dealers, covering yards, dispatch, delivery journeys, tally and job-level balances. Selling to a contractor who is standing on a site is a real opportunity and a demanding integration.

Epicor's BisTrack API page describes authenticated access, encrypted communication using Microsoft tooling, a Smart View Endpoint that extracts data using SQL queries, and the ability to create and update records programmatically, with named capability areas including web store connectivity and order and quote management. What that page does not state is the protocol: it says only that the API maintains data integrity "with standardized protocols." Epicor offers a BisTrack API eBook that it says covers developer tools and a "full endpoint overview and setup guidance," but we found no public developer documentation or API reference. That makes a discovery pass against your own instance the first real task rather than an optional preliminary, and it is worth asking any fixed-price quote how the mechanism was established.

Epicor BisTrack Shopify integration in detail

LumberTrack runs the supply side of wood products. Epicor sells it to hardwood and softwood sawmills, panel mills, value-added remanufacturers, and to distributors, wholesalers and brokers, tracking cost, species and grade from the log yard through the mill to the reload yard. It sits on the opposite side of the transaction from BisTrack, which serves the dealers buying from you.

Epicor publishes no API or integration documentation for LumberTrack, unlike BisTrack which has a dedicated API page. So a dealer portal project starts with discovery against your own instance. The capability worth building around is Available to Sell, which Epicor's own published customer story describes as a fully integrated module inside LumberTrack, and which is the number a dealer portal actually needs rather than raw on-hand.

Epicor LumberTrack Shopify integration in detail

Vision is Epicor's ERP for parts distribution, linking distribution centers, company-owned stores, independent jobbers, buying groups and service accounts across automotive, heavy duty and appliance parts.

Epicor does not publish API or integration documentation for Vision. What it does document, and what a storefront should be built around, is the catalog layer: Epicor Catalog for Automotive carries ACES compliant fitment data with lookup by make, model and trim, by VIN and by license plate, aftermarket and OE cross-references, and a named Epicor Catalog API, with Epicor stating that Vision customers can view pricing, availability and custom data fields through it.

The three things a parts storefront has to get right are price tiers for jobber, installer and retail, core charges that behave correctly in a cart, and interchange so a buyer arriving with a competitor's part number lands on yours.

Epicor Vision Shopify integration in detail

Eagle is Epicor's retail management system for hardware, home centers, farm and home, lawn and garden, paint and building centers. It is retail-led rather than wholesale-led, which makes it a different project from P21 or Kinetic: one store serving a walk-in customer at the counter and a contractor with a charge account, bids and a pickup truck.

Epicor does not publish a developer API for Eagle. The published integration surfaces are Epicor Integration Cloud, its iPaaS offering, and Epicor Data Fabric, so the integration architecture is the thing being scoped rather than a set of endpoints to call. The work that decides an Eagle project is store-level availability and the pickup workflow behind it, with charge account self-service alongside the retail experience.

Epicor Eagle Shopify integration in detail

The integration is a translation exercise. Epicor organizes your business data in an ERP structure. Shopify needs it in a commerce structure. Getting it right means knowing exactly how each Epicor concept maps to the right Shopify feature, and building the sync logic that keeps them aligned in real time. Here is how the key pieces connect.

Every customer record in Epicor, with their account number, credit status, and assigned terms, becomes a corresponding company account in Shopify. When a buyer logs in, Shopify already knows who they are and what they are allowed to do. Credit holds set in Epicor propagate to Shopify immediately. New accounts activated in Epicor show up in Shopify without any manual step.

A customer with four approved ship-to addresses in Epicor sees exactly those four addresses at Shopify checkout. Nothing more. When your team adds, updates, or removes a ship-to in Epicor, Shopify reflects it in real time. This matters most for distributors with multi-location accounts: a contractor buying for five job sites needs those sites available at checkout, matched precisely to what is in P21.

Individual contacts linked to a customer account in Epicor sync as Shopify company contacts. Each person gets their own portal login, scoped to their company's pricing, catalog, and purchasing rules. When someone leaves and is removed from Epicor, their Shopify access goes with them automatically.

This is where most Epicor Shopify integrations go wrong.

P21's buy matrix handles customer-specific prices that vary by product, quantity, and account tier. Kinetic's price schedules apply layered rules across product categories and customer groups. A connector that exports raw pricing data from Epicor and tries to replicate the logic in Shopify will break at every edge case.

Uncap resolves what Epicor would actually calculate for each account and each product, then writes that resolved price into a Shopify price list for that company. When pricing changes in Epicor, the Shopify price list updates immediately. Your buyers see the correct price. Not an approximation. Not a price that requires a correction call after the order goes through.

Net 30, net 60, net 90, or any custom term assigned to an account in Epicor applies at Shopify checkout without buyer input. The order that lands in Epicor carries those terms correctly. No mismatches between what a buyer agreed to and what the invoice shows.

Credit limit data from Epicor's customer records is live in Shopify's checkout layer. When a buyer tries to place an order that would push them over their limit, Shopify declines the transaction before it reaches Epicor. Finance does not discover the problem after the shipment leaves.

A purchase order submitted in Shopify creates an Epicor order in real time, with the correct account, ship-to address, line items, PO reference, and payment terms already populated. Your fulfillment team sees it immediately. No sync window. No re-entry.

Available stock in Epicor syncs to Shopify continuously. When a Shopify order is placed, inventory is committed in Epicor immediately. When a warehouse movement, receipt, or production job completion runs in Epicor, Shopify reflects the updated availability within seconds. For P21, this happens at the branch level. For Kinetic, available-to-sell accounts for production commitments.

Epicor Kinetic runs the back end for manufacturers who build to order rather than to stock. Job-specific inventory, BOM-driven pricing, and non-standard customer accounts do not map cleanly through a generic integration tool. Uncap Connect is a Shopify-embedded app built for that environment. It syncs job inventory, customer pricing, and order status between Epicor and Shopify inside the Shopify admin, with no middleware platform in the stack. $390 a month, one vendor. The chart below shows what the generic iPaaS alternative looks like by comparison.

Inventory quantities in Epicor sync to Shopify on an event-driven architecture, not a scheduled batch. An order placed in Shopify commits inventory in Epicor at that moment. A warehouse movement in Epicor updates Shopify within seconds. Branch-level inventory for P21 and production-aware available-to-sell for Kinetic are both supported.

Epicor's pricing logic (P21's buy matrix, Kinetic's price schedules, account-specific overrides, and volume breaks) is resolved per customer and per product before it reaches Shopify. Shopify price lists always reflect what Epicor would actually charge each account, updated in real time when pricing changes. No pricing corrections on submitted orders.

Company accounts, ship-to structures, and credit limits from Epicor map directly into Shopify's company account layer. Credit limits enforce at checkout. Payment terms apply automatically. Buyers cannot exceed their approved limit or check out against terms your finance team has not approved.

Orders placed in Shopify create Epicor orders in real time, with full line-item detail, customer account data, ship-to address, PO reference, and any custom field your Epicor order workflow requires. Fulfillment starts without waiting for a connector run. Supported for both P21 and Kinetic order entry workflows.

Wholesale accounts access Epicor-sourced contract pricing and their PO workflow behind Shopify's authentication layer. DTC buyers land on the same Shopify Plus instance at retail pricing. POS transactions hit the same Epicor inventory pool. All three channels generate Epicor orders immediately. One integration, one catalog, no reconciliation between stores.

Product master data, pricing, availability, and item attributes flow from Epicor into Shopify's product catalog continuously. High-SKU operations (distributors with tens of thousands of part numbers, manufacturers with complex part variants) stay synchronized without manual data entry. Epicor remains the item master. Shopify reflects it accurately.

The integration is the foundation.Once Epicor and Shopify Plus are connected in real time, Uncap Products drive what comes next. Uncap Quotes handles complex pricing and quote workflows without a separate CPQ tool. Uncap Portal gives trade accounts a self-serve home on Shopify: catalogs, pricing, reorders, invoices, and users, so buyers help themselves and reps stop fielding the same requests. Integration connects your systems.

‍

Shopify Platinum Partner for manufacturers, distributors, and retailers. Shopify's Platinum Partner designation is the highest designation Shopify awards. It means direct access to Shopify's product and engineering teams, which matters when an Epicor integration requires advanced Shopify Plus architecture decisions across wholesale, DTC, or POS channels. Uncap is a Shopify Platinum Partner, on Shopify since 2013, with 380+ storefronts launched on Shopify across manufacturing, distribution, and wholesale.

We know the difference between P21 and Kinetic. These are not interchangeable products. P21's buy matrix pricing, branch inventory model, and distribution-focused data structure require a different integration approach than Kinetic's production-aware inventory, job costing model, and BAQ-based API layer. When we scope your integration, you will not spend time educating us on how your Epicor instance works.

Pricing that resolves, not approximates. Getting pricing right in Epicor Shopify integrations is harder than it sounds. P21's buy matrix and Kinetic's price schedules involve layered logic that generic connectors simplify to the point of being wrong in real-world scenarios. We resolve Epicor's pricing output per customer and per product before it reaches Shopify. Every buyer sees exactly what Epicor would calculate for their account.

One integration, every channel. Your Epicor instance connects once. B2B wholesale, DTC, and retail all run from the same Shopify Plus platform. No daily reconciliation between two stores, no manual processes covering for a sync schedule that cannot keep up.

Disconnected systems do not announce what they are costing you. The pricing call your rep made this morning, the backorder that should not have happened, the buyer who stopped using the portal: those are the bill. A real-time Epicor to Shopify Plus connection eliminates them, across every channel you run.

Book a free integration assessment with Uncap. We will review your Epicor setup, whichever Epicor product you run, map out the full integration scope, and give you a clear picture of what your operation looks like when both platforms run as one. No pitch deck. No pressure. Just a practical plan built for your environment.