--- title: "Epicor Vision to Shopify Integration" url: https://www.uncap.com/integration/epicor-vision author: "Denis Dyli" published: 2026-09-27 updated: 2026-09-27 summary: "Vision is Epicor's ERP for parts distribution. Epicor does not publish API or integration documentation for Vision. What Epicor does publish, and what an integration should actually be built around, is the catalog layer. Epicor Catalog for Automotive is a documented product with a documented API, and for an automotive WD it is arguably more important than the ERP connection." --- # Epicor Vision to Shopify Integration > Vision is Epicor's ERP for parts distribution. Epicor does not publish API or integration documentation for Vision. What Epicor does publish, and what an integration should actually be built around, is the catalog layer. Epicor Catalog for Automotive is a documented product with a documented API, and for an automotive WD it is arguably more important than the ERP connection. If you are a warehouse distributor running Vision, your online question is narrow and hard: can a jobber or an installer find the right part for a specific vehicle, see their price, and order it, without calling your counter. Every word of that sentence is a separate engineering problem. ## The honest starting point Epicor does not publish API or integration documentation for Vision. We checked. Epicor's integration technology page talks about OpenAPI and Swagger, REST and OData, and says every function available in the client UI is equally available as a service or API. Vision is not mentioned anywhere on it. Every public REST specification we could find is for Kinetic. There is no Vision developer portal, no Swagger spec and no endpoint reference. That is worth saying out loud because it explains something a WD might otherwise find confusing: why you cannot assess this project yourself from public material, and why quotes for it vary so much. What Epicor does publish, and what an integration should actually be built around, is the catalog layer. ## The catalog is the integration surface Epicor Catalog for Automotive is a documented product with a documented API, and for an automotive WD it is arguably more important than the ERP connection. Epicor describes it as ACES compliant data in English and Spanish, covering more than 17 million part numbers and SKUs and more than 1.4 billion vehicle applications, with lookup by make, model and trim, by VIN, and by license plate. It handles aftermarket to aftermarket and OE to aftermarket cross-references. Epicor names an Epicor Catalog API for creating custom websites and applications, and states that Epicor Vision customers can view pricing, availability and custom data fields. Read that last part again, because it is the whole architecture. The documented path for a Vision distributor building a storefront runs through the catalog, with Vision data surfacing inside it, rather than through a Vision API that does not publicly exist. Epicor Parts Network sits alongside as the aftermarket trading partner network for real-time supplier inventory, and Epicor describes it as optimized for Vision among other products. ## Fitment, and why the standards version matters The catalog question is really a data standards question, and getting the vocabulary right is how a WD knows whether you have done this before. ACES is the Auto Care Association's standard for managing and communicating product fitment data, built on the Vehicle Configuration Database, and it is what carries year, make, model and engine as machine-readable data. PIES is its companion, covering product attributes, descriptions, pricing and media. Fitment and product content are two different standards, and conflating them is a common tell. The current versions are ACES 5.0 and PIES 8.0, released in April 2026. For a storefront this means the fitment experience is only as good as the data behind it, and the provenance question is a real one: whose ACES data, maintained by whom, refreshed how often. Nobody on the results page for this topic addresses it. [Uncap Garage](https://www.uncap.com/products/garage) is our shipped product for vehicle fitment on Shopify, built on ACES and PIES, letting a shopper build a garage of year, make, model and engine and keep it across visits, with the catalog filtered to what fits. It is for automotive parts merchants specifically, which is exactly this audience. ## Three things a parts storefront has to get right **Price tiers.** A WD does not have one price. Jobber, installer and retail are different, national accounts are different again, and a logged-in buyer must see theirs and only theirs. This is the most common reason a parts site loses trade customers: they see a number that is not their number and they stop trusting it. **Core charges.** A core charge is added at sale and reversed when the old unit comes back. On a counter that is routine. In a cart it is a line item that behaves unlike anything else in ecommerce: it is a deposit, it appears on the order, and it has to reconcile against a return that may arrive weeks later. We looked at every page competing for this topic and not one explains how a core charge behaves in an online cart. It is the single clearest gap. **Interchange and supersession.** A buyer searching your competitor's part number should find yours. A part that has been superseded should route to its replacement rather than to a dead page. Both are catalog functions rather than storefront functions, and both are what the Epicor catalog cross-reference capability exists to do. ## Proof, and a naming distinction that matters Uncap built [E3 Spark Plugs](https://www.uncap.com/work/e3sparkplugs), a global B2B automotive site with a cross-reference application that lets buyers search competitor SKUs, a year, make and model tool, Shopify Markets, and group pricing for dealers. Cross-reference search is the closest published analog to the interchange capability a WD needs, which makes it the most relevant proof we have for this page. [Scooterworks](https://www.uncap.com/work/scooterworks) adds year, make and model search plus shoppable diagrams, which is fitment user experience proven in production, though in powersports rather than automotive WD distribution. One distinction we will make explicitly rather than let it blur. Uncap's [Kooks](https://www.uncap.com/work/kooks) build is real ACES fitment proof, and the ERP behind it is **Infor VISUAL**, not Epicor Vision. Two different products from two different vendors with confusingly similar names. Kooks evidences fitment work, not Vision work, and anyone who reads carefully deserves to be told that by us rather than to catch it. ## Where the two systems line up Vision customer accounts become Shopify companies, with ship-to locations and buyer logins, so a jobber signs into their own tier and their own history. Parts become products with fitment from ACES and product content from PIES, with interchange and supersession handled in the catalog layer rather than approximated on the storefront. Availability comes by distribution center and by store, because a jobber cares about what can reach them today. Pricing resolves to the logged-in account's tier, including national account arrangements where they apply. Core charges appear correctly on the order and reconcile against core returns. An order reaches Vision with the account, the ship-to and the reference attached. [Uncap Connect](https://www.uncap.com/products/connect) keeps pricing, inventory, customer data and orders current in both directions, built for B2B so customer-specific pricing, terms and tax behave correctly. ## What we build A discovery pass establishing the actual integration mechanism against your Vision instance and your catalog subscription, before anything is priced as fixed scope. Fitment search built on ACES and PIES through Uncap Garage, with the data provenance question answered rather than assumed. Interchange and cross-reference search so a buyer arriving with a competitor's part number lands on yours. Price tiers for jobber, installer, retail and national accounts, resolved for the logged-in buyer. Core charges that behave correctly in the cart, on the order and against the return. Availability by distribution center and store, with order write-back to Vision. ## Industries that run Vision Auto Parts and Aftermarket, where ACES and PIES fitment decides whether the right part reaches the right vehicle. Vision is one of several Epicor products we connect to Shopify. The [Epicor integration overview](https://www.uncap.com/integration/epicor) covers Prophet 21, Kinetic and the rest. ## Ready to talk Bring your Vision version, which Epicor catalog products you subscribe to, your price tier structure, and how core charges work in your business today. That last one decides more of the cart design than anything else on the list. Book a strategy session, or start with a [Blueprint](https://www.uncap.com/blueprint), the paid discovery engagement that establishes the integration mechanism, the fitment data model and the phased plan before development begins. ## Frequently asked questions ### Does Epicor Vision have an API? Epicor does not publish API or integration documentation for Vision. Its integration technology page describes OpenAPI, Swagger, REST and OData but never mentions Vision, and every public REST specification we could find covers Kinetic instead. There is no Vision developer portal or endpoint reference. This is why a WD cannot self-assess this project from public material, and why the documented path runs through the catalog layer. ### If there is no Vision API, how does the storefront get data? Through the documented catalog surface. Epicor Catalog for Automotive has a named Epicor Catalog API for building custom websites and applications, and Epicor states that Vision customers can view pricing, availability and custom data fields through it. Epicor Parts Network sits alongside for real-time supplier inventory and is described as optimized for Vision. The exact mechanism for your instance is a discovery task. ### What are ACES and PIES, and does the version matter? ACES is the Auto Care Association standard for product fitment data, built on the Vehicle Configuration Database, carrying year, make, model and engine as machine-readable data. PIES is the companion standard for product attributes, descriptions, pricing and media. They are different standards for different things. The current versions are ACES 5.0 and PIES 8.0, released April 2026, and running current versions matters because fitment accuracy is the whole experience. ### How do core charges work in an online cart? They have to be modeled as what they are: a deposit added at sale that reverses when the old unit is returned, appearing on the order and reconciling against a return that may arrive much later. It is routine at a counter and unusual in ecommerce, which is why it needs designing rather than assuming. No page competing for this topic explains it, which is a reasonable signal about how often it gets handled properly. ### Can a buyer search using a competitor's part number? Yes, and for a WD it is close to essential. Interchange and cross-reference is a catalog function, and Epicor's automotive catalog covers aftermarket to aftermarket and OE to aftermarket cross-references. Uncap has built exactly this in production for a global automotive brand, where buyers search competitor SKUs and land on the right part. ### How do jobber, installer and retail pricing tiers work? The logged-in account sees its tier and nothing else, including national account arrangements where they apply. Getting this wrong is the most common reason trade buyers abandon a parts site, because a buyer who sees a price that is not theirs assumes the whole site is unreliable. ### Is Uncap's Kooks project proof of Epicor Vision experience? No, and we would rather say so. Kooks runs **Infor VISUAL**, a different product from a different vendor with a confusingly similar name. Kooks is genuine proof of ACES fitment work at production scale. The closest published proof for the interchange and cross-reference capability a WD needs is the E3 Spark Plugs build. ### How long does an Epicor Vision Shopify integration take? The catalog and fitment work usually outweighs the ERP connection, and the absence of published Vision integration documentation means discovery carries more weight than it would on Kinetic or Prophet 21. The Blueprint engagement establishes the mechanism and the data model before anyone commits to a date.