Does Sana Commerce integrate with Epicor? No.

Two supporting checks, both negative. There is no Sana listing in the Acumatica Marketplace, which carries roughly 130 solutions including several competing third-party B2B storefronts. And Epicor's ISV Solution Gallery listed 27 solutions when we enumerated it; no ecommerce storefront of any brand appears, and the gallery has no ecommerce category at all.

Sana describes itself as a certified SAP and Microsoft partner. The supported list follows that shape exactly.

It means there is no Sana-built, Sana-supported connector for Epicor or Acumatica. It does not mean the following, and the difference matters if you are about to make a decision.

• It does not mean Epicor or Acumatica has ruled Sana out. Neither vendor has published any statement about Sana in either direction. What exists is absence from listings, which is silence rather than a position, and it should not be read as one.
• It does not mean nobody will sell you something adjacent. At least one middleware vendor publishes a page titled for exactly this pairing. Its own wording is conditional: the solution "can involve pre-built integrations with Epicor or, with the use of the Web Service Connector tool, create custom integrations." We are not going to tell you a connector does or does not exist behind that, because we do not know. What we can tell you is what the page itself does not carry: no version matrix, no connector documentation, no named customer, and no certification claim from any of the three vendors. Its own footer lists sibling pages built from the same text with the product names swapped. Ask for those four things before you treat it as a product.
• It does not mean Sana's own "custom ERP connections" feature is a route in. That feature exists to route Sana's subsystems through separate web services, or across multiple ERPs Sana already supports. Sana's own documentation calls that scenario very complex, and it is not a way to reach an unsupported ERP.

One loose end we will flag rather than pretend to understand: the connection list carries a bare entry labelled "SOAP" with no documentation, no example and no described behaviour anywhere in Sana's published help. If somebody offers it to you as the answer, ask them to document it.

Sana's connector is not middleware sitting between two systems. Sana states that the Sana Commerce Cloud add-on runs within the ERP, uses the ERP's business logic, and that all basket calculations are done by the ERP. Each connector is therefore code written in that ERP's own extension technology and shipped through that vendor's packaging channel: ABAP Objects for SAP, an AL extension on Microsoft AppSource for Business Central, a codeunit web service for NAV.

Now apply that to Epicor, and the reason the answer has stayed no becomes obvious. "Epicor" is not one ERP. Epicor's own product index lists ten, and they are not variants of one system. Prophet 21 extends through an SDK and DynaChange on a .NET and SQL Server stack. Kinetic extends through low-code Application Studio, Epicor Functions and the UD Service Designer. They share almost nothing.

So a Sana connector "for Epicor" would really mean a Sana connector for one of those codebases, built against that product's own extension model, with its own installation guide, its own release train and its own supported-versions page, then maintained on a standing update obligation forever. That is a new product line rather than a connector, and it is why this is a different kind of absence from a feature nobody has got round to. That last sentence is our reading, not something Sana states.

Sana publishes no roadmap statement either committing to or ruling out further ERP vendors. We looked. If you are deciding whether to hold off, that is the honest position: there is nothing to wait on, and nothing that says there is not.

One data point worth more than a roadmap, because it tells you how this vendor behaves. Support is per product, not per vendor, even inside the families Sana is certified for. Sana supported Microsoft Dynamics GP for roughly a decade. Development on that connector stopped in Q2 2023, and support ended on 31 December 2025, with Sana's stated reason being Microsoft's own sunset of GP. GP is no longer a connection type in the product.

Read that as an Epicor or Acumatica buyer and it cuts both ways. It shows a supported list is a snapshot rather than a guarantee. It also shows that when Sana adds or drops an ERP, it moves with that ERP vendor's own lifecycle, which is a rational trigger and not a whim. Our full breakdown of the supported list is on Sana Commerce ERP integration.

Before anything else: which one? Epicor's own index lists ten ERPs, including BisTrack, CMS, Eagle, Eclipse, iScala, Kinetic, LumberTrack, Propello, Prophet 21 and Scheduling+. Prophet 21, which Epicor calls the only ERP designed by distributors for distributors, is the one most people mean when they type "Epicor ecommerce" with a B2B storefront in mind. Eclipse serves an almost identical set of wholesale verticals. Kinetic is the manufacturing ERP that used to be sold under the Epicor ERP name. Your commerce answer differs by product.

Your first-party option is Epicor Commerce, which Epicor describes as powered by Magento and states is built on Magento Community Edition, the edition Adobe now ships as Magento Open Source. It supports four ERPs, and Epicor's own tier table says so in one row: seamless integration with Kinetic, Prophet 21, BisTrack or Eclipse. It comes in three tiers, all marked SaaS only.

One distinction is worth knowing before you conclude that already having Epicor Commerce answers your question. Epicor describes the entry tier as a B2B online customer self-service portal, and its own comparison column for that tier reads "No Front End or SEO / Self-Service / Quotes Only". If somebody has told you that you are covered, check which tier.

The genuinely useful part, and the reason this section exists, is that Epicor documents which features work on which ERP, in its own words, and the asymmetry is not what most people assume.

• Prophet 21 only: buyer-specific and job contract pricing, described as using configured job contracts from Prophet 21 in Epicor Commerce "without duplicating or recreating". If contract pricing is why you went shopping for a Sana-style ERP-integrated storefront, that is a real Prophet 21 advantage on the incumbent product. The phrase "without duplicating or recreating" also tells you what the normal alternative involves.
• Kinetic only: Dealer Portal, CPQ integration for custom quotes and orders, and user-defined attributes from the ERP.
• Kinetic, Prophet 21 and BisTrack: multicurrency.

One sequencing constraint to check early: Epicor states the latest Epicor Commerce version is verified with ERP versions currently in active support, and defines active support as up to two years from general availability. An older Prophet 21 build may need an ERP upgrade first.

Two things you were probably not shown.

Epicor now sells a second storefront. It acquired KYKLO in June 2024, and KYKLO Commerce is listed today as a separate product from Epicor Commerce, positioned around built-in product content maintained by application engineers and a content data pool of over seven million SKUs. Its page names no ERP at all, and Epicor's acquisition release says the KYKLO product information management can be integrated with any e-commerce platform, so that content layer is deliberately platform agnostic. If somebody is pitching you "Epicor ecommerce", ask which of the two.

And Epicor does publish and support third-party storefront integrations, just not for the distribution ERPs. Its integration index lists BigCommerce under integrations for retail, and its Propello connectivity page documents a BigCommerce integration that syncs inventory and customer data and books completed orders. Under integrations for distributors the only ecommerce entries are Epicor Commerce and Ariba and SAP OCI punchout. So if you have been told Epicor does not do third-party ecommerce, that is not right. What is true is that Epicor lists no third-party storefront for Prophet 21, and has published nothing endorsing, certifying, prohibiting or discouraging one. That is silence, not a position, and we draw no conclusion from it.

Your answer is shorter and better. Sana does not connect to Acumatica and there is no Sana listing in the Acumatica Marketplace. But the thing you were actually looking for, an ERP-integrated storefront where the ERP is the source of truth, already exists from your own ERP vendor.

Acumatica groups Amazon, Shopify with Shopify POS, and BigCommerce as its native commerce connectors. The BigCommerce one is Acumatica-built product code rather than third-party middleware: Acumatica names it its native BigCommerce connector, documents it on its own help site, carries it as a line item in its Licensing Guide, and teaches it in its own Open University course.

Two naming notes, because a lot of the web is stale on both. The edition is now Retail Edition, previously marketed as Commerce Edition. And the Marketplace listing will confuse you: it is titled "eCommerce Platform for Acumatica", badged as fulfilled by Acumatica, and names its publisher as Commerce, formerly BigCommerce.

Three things to check before you assume you are covered.

• The licence. Acumatica's datasheet says integration to BigCommerce is built into Retail Edition with no additional software to purchase. That is a claim about software, not about cost. In the Licensing Guide the BigCommerce, Shopify and Amazon integrations carry the same marker as optional modules such as Project Accounting, while Financials and Order Management carry a different one. The guide prints no legend, so we are reading those by comparison across editions and we are telling you that rather than presenting it as settled. Check your own order form.
• Storefront count. The datasheet says you can connect as many stores as you operate. The documentation says the number is limited by your licence, and that over the limit the system silently processes only the stores within it, sorted alphabetically, without an error. Budget per storefront.
• Version. If you are a B2B distributor, native BigCommerce B2B Edition company sync arrived in Acumatica 2026 R1, listed as available March 2026. Confirm your build, and ask your reseller for references specifically on B2B company sync rather than on the connector generally.

On architecture, it does what a Sana buyer wants, with one honest caveat. Acumatica is master for catalogue, price and availability, and the documentation states the direction of synchronisation is predefined and cannot be changed for those entities. Synchronisation can be scheduled, real time or manual. The flip side is that storefront-side merchandising edits to price or catalogue will not flow back, and that prices are synchronised into BigCommerce rather than fetched from the ERP at page render. Sana's own comparison writing concedes the ownership point, describing pre-built integrations with Acumatica as built and maintained by the ERP provider themselves.

If you would rather evaluate third-party B2B storefronts anyway, Acumatica's marketplace is the shortlist to use.

We build BigCommerce storefronts with ERP integrations, so treat the following as an interested party being careful rather than a neutral one. We have tried to mark the line between what is established and what is not.

Acumatica to BigCommerce is established, and the connector is not ours. It is Acumatica's product, it ships with Retail Edition, and it has a current Open University course. For an Acumatica shop the storefront question is largely a configuration, mapping and storefront-build project rather than an integration build. Our scope would be the storefront, the configuration and the data mapping. The work that actually eats time: confirming the edition and connector line on your order form, confirming the release if B2B company sync is required, mapping BigCommerce payment methods to Acumatica ones since unmapped methods produce no prepayment document, setting the order date and time zone, and deciding scheduled versus real time per entity.

Prophet 21 to BigCommerce is not turnkey, and we are not going to pretend otherwise. There is no first-party Epicor connector and no first-party BigCommerce connector for Prophet 21. What exists is a populated third-party market of integration products and services engagements. We would scope this alongside one of those vendors rather than claim a turnkey capability, and we would want discovery before any fixed price.

The hard part is worth stating plainly, because it is the thing that decides the project:

One planning point that outranks everything above. Epicor has scheduled Prophet 21's final on-premises feature release as 2028.1, tentatively May 2028, with sustaining support beginning 1 July 2029, and states that future innovation moves exclusively to the Epicor Cloud. Any storefront integration commissioned now will outlive on-premises Prophet 21. Design for the cloud constraints, meaning API-only writes, no direct SQL and discretionary throttling, even if you are on-premises today, or you will pay for the integration twice.

Questions to take into any Prophet 21 vendor call. Which API families do you use for pricing versus order entry? Does your integration read the order back from the ERP and reconcile it, or does it trust the write call's status? How do you handle multi-unit-of-measure, where the selling unit and the pricing unit differ? Have you shipped this on Epicor-hosted Prophet 21, where there is no direct SQL? When was your connector last updated, and against which release? And one procurement item: confirm in writing with Epicor that your licence covers the Prophet 21 API before you sign anything.