Which ERPs Sana Commerce actually supports.

Sana's own ERP User Guide describes the product as an e-commerce solution for Microsoft Dynamics and SAP. Every connector Sana has ever documented belongs to one of those two families.

That distinction matters more than it looks. Most pages making this claim state it as an absolute and cannot back it. We would rather tell you exactly how far the evidence goes.

Product names below are Sana's documentation names, which differ from their marketing names. We have deliberately left out connector version numbers: Sana ships those on a roughly quarterly train, so any number printed here would be wrong within a quarter. ERP version support moves on a scale of years and is worth stating.

Supported

• Microsoft Dynamics 365 Business Central. Sana expects Business Central Cloud customers to be on the latest version, and updates the extension automatically through Microsoft AppSource when Microsoft performs a major upgrade. Version-specific extensions for on-premises go to partners through Sana's community site. Sana publishes no numbered supported-versions page for Business Central.
• Microsoft Dynamics 365 for Finance and Operations. Supported, and more actively than its absence from Sana's marketing would suggest. Since a December 2025 connector release Sana supports the three most recent Microsoft Finance and Operations versions, up from the latest version only, though it still tests against the single latest. Note that means three Microsoft versions, not three Sana connector versions, and Sana names no concrete version numbers.
• Microsoft Dynamics NAV. Documented for NAV 2009 R2 through NAV 2018, W1 and NA localizations only. Sana states that all other localizations should be merged by the partner from the W1 version.
• Microsoft Dynamics AX. Documented for AX 2012 R3 and AX 2012 R2 only, with the latest cumulative update. Lower AX versions require a paid downgrade or partner work.
• SAP ECC. Documented for SAP ECC 6.0 with EHP 6, 7 or 8. Sana states explicitly that versions below ECC 6.0, R/3 for example, are not supported.
• SAP S/4HANA. A separate connector from ECC, with its own release track. Sana's supported-versions table lists S/4HANA 1909, 2020, 2021, 2022 and 2023, plus an on-demand column for any-premise. The 2024 and 2025 releases are not listed, and Sana says nothing either way about them.
• SAP Business One, Service Layer only. Documented for 9.2, 9.3 and 10.0, with two named exclusions: 10.0 SP 2305 is not supported, and FP 2105 and FP 2108 are incompatible. Sana dropped DI Server support in favour of Service Layer, which is worth knowing if you are on an older integration.

Discontinued

• Microsoft Dynamics GP. End of life 31 December 2025. Four dates are worth keeping separate, because a single "support ended" hides the useful detail: feature and code development stopped in Q2 2023; Sana committed to showstopper support, explicitly including security issues, until 31 December 2025; that date has now passed; and Sana's stated reason is Microsoft's own sunset of GP, in tandem with it. GP no longer appears as a connection type in Sana Admin. More below.

Not on Sana's supported list

• Epicor. No Sana product page, connector, documentation set or release-notes track appears in Sana's published history, and Sana is not listed in Epicor's ISV channel. We go into the detail, including what a Prophet 21 or Acumatica shop should evaluate instead, on Sana Commerce and Epicor. Worth knowing separately: Epicor sells its own B2B storefront for Prophet 21, so the comparison a P21 distributor is actually making is usually Epicor's own commerce product against something else, not against Sana.
• Acumatica. Same evidence as Epicor, and no listing on the Acumatica marketplace.
• NetSuite. No Sana ERP connector exists. NetSuite does appear in Sana's documentation, but only as an e-procurement system on the buyer side of a punchout integration, meaning a NetSuite-using buyer punching out into a Sana webstore. That is not an ERP connector and it does not power a Sana store.
• Infor. No connector, page or release track. Every apparent hit in the archives turned out to be the word "information" in one language or another.
• Sage ERP, meaning Sage 200, Sage 300, Sage X3 and Sage Intacct. No connector for any Sage ERP product appears in Sana's current or archived documentation. Sana did ship a Sage Pay add-on in Sana Commerce 9.0, with its own installation guide, but Sage Pay was Sage's payment gateway, later Opayo, and not an ERP integration.
• Oracle, JD Edwards, SYSPRO, Odoo, SAP Business ByDesign and Microsoft Dynamics SL. None appears in Sana's current documentation, live integrations page, or archived marketing.

One thing not in any of those columns: Sana publishes no roadmap statement either committing to or ruling out further ERP vendors. If you are deciding whether to wait, there is nothing to wait on, and nothing saying there is not.

Most platforms integrate with an ERP through middleware sitting between two systems. Sana does something else, and it is the reason the supported list is seven products rather than seventy.

Sana states that the Sana Commerce Cloud add-on is built on top of and runs within the ERP system, that it uses the business logic of the ERP, and that all basket calculations are done by the ERP. The storefront is not reimplementing your pricing. It is calling yours.

That means each connector is written in the ERP's own extension technology and shipped through that ERP's own packaging channel:

• For SAP, ABAP Objects, service definitions and tables under Sana's registered namespace, installed with SAP's own Add-on Installation Tool.
• For Business Central, an AL extension published to Microsoft AppSource.
• For NAV, a Sana-authored codeunit exposed as a NAV web service endpoint.

The cost of that is recurring rather than one-time. Sana ships ERP add-ons on a roughly quarterly release train per connector, obliges standard customers to update the ERP connector at least every two years, and has had to re-target a connector when a vendor changed its API surface, which is what happened when SAP Business One moved from DI Server to Service Layer.

It also explains the version floors. Sana refuses ERP versions that lack the API infrastructure it needs: SAP below ECC 6.0 because it predates NetWeaver, and GP below 2015 because Service Based Architecture arrived in GP 2015.

Our reading, which Sana does not state: adding a new ERP is therefore a new product line rather than a connector. It means a native application inside another vendor's development stack, invoking that vendor's pricing and order-entry routines, distributed through their packaging and upgrade model, and re-targeted every time they change their integration surface. Nothing Sana publishes quantifies that cost. The closest they come is their GP end-of-life language about reassigning development resources to ERPs with an active lifecycle.

One honest caveat, because repeating vendor copy would be the easy thing here. Sana's architecture page says there is no need to export, import or synchronize anything, while Sana's own master data management page says master data, including products, categories, customers and shipping addresses, is held in the Sana Commerce Cloud database. Sana publishes nothing reconciling the two. The accurate version is live for volatile data such as price, stock and orders, and cached for master data. The architectural argument survives that correction intact.

GP is the only entry that has moved from the supported column to the discontinued one, and it is the most useful row on this page for anyone evaluating Sana, whatever ERP they run.

The sequence: feature and code development stopped in Q2 2023. Sana continued showstopper support, explicitly including security issues, until 31 December 2025. That date has passed. Sana's stated reason is Microsoft's own sunset of GP, and Sana moved several years ahead of it.

Two things follow that are worth carrying into any Sana decision.

A supported list is a snapshot, not a guarantee. GP was supported for roughly a decade. If your ERP is legacy, the question to ask Sana is not whether it is supported today but what their commitment looks like against your ERP vendor's own lifecycle, because that is the trigger they used.

Live documentation does not mean live support. Sana's GP documentation is still online, roughly a hundred and twenty pages of it, with no removal date and at least one banner still written in the future tense. A search result or a partner blog can look current and be describing a product that ended eight months ago. This is a trap we have watched people fall into, and it is why every claim on this page carries a verification date.

If you got here searching for Sana and your ERP, you were probably qualifying before booking a demo. The answer is no, and the useful part is why, because it tells you whether to wait.

It is structural, not a gap in the roadmap. A Sana connector for your ERP would be a native application inside your ERP's development stack, with its own installation guide, its own release train and its own supported-versions page. No such artifact exists for any ERP outside Microsoft Dynamics and SAP, in current or archived form. That is a different kind of absence from a feature nobody has got round to yet, and it will not change next quarter.

What we would actually think about in your position, briefly, because this is not the place for a pitch:

• Work out what the ERP-first model was buying you. Sana's pitch is that pricing, stock, credit and order entry are executed by the ERP rather than copied into a storefront database. If that is what attracted you, the question for any alternative is how close it gets to that, not which feature list is longer.
• Check whether your ERP vendor sells its own storefront first. Several do. Epicor sells a B2B storefront for Prophet 21, and for a distributor that is usually the incumbent option worth pricing before anything else, whether or not it wins.
• If you go the platform route, the seam is the project. A platform such as BigCommerce integrated to your ERP puts the pricing and availability contract back in your hands, which is more work and more control. We have written that up per ERP on the BigCommerce ERP integration side, and the same reasoning applies to an ERP we have not written a page for.

If you want a second opinion on which of those fits, we will give you a straight read. We build on Sana and on BigCommerce, so we are not defending a single answer.

Everything above describes Sana Commerce Cloud. If you are on the older Sana 9.x line, the ERP list is not what changed underneath you, the product lifecycle is.

There is no ERP that Sana 9.x supported and Sana Commerce Cloud does not. The intuitive answer, GP, is wrong: GP was a fully supported Sana Commerce Cloud connector with its own supported-versions page, and its end of life is a Cloud-side end of life.

What has changed is support for the 9.x line itself, and it depends on your exact release. Sana's support policy table puts 9.3.0 through 9.3.4 out of passive support on 26 September 2023. Version 9.3.5 remains in passive support until 31 December 2026, which is time and material and covers hotfixes for critical security issues and order-blocking bugs only.

If you are staying on 9.x past those dates, we cover that separately on Sana 9.3 support, including the honest limit on what anyone outside Sana can do. And if Business Central is where you are heading or already are, the detail is on Sana Commerce and Business Central.