Acumatica's marketplace lists prebuilt connectors for common pairings, Shopify, Amazon, Salesforce, HubSpot, and others, built mostly by Acumatica's partner network rather than Acumatica itself. Coverage is real but uneven: a construction business running Procore, a distributor needing EDI with retail trading partners, or anyone on a less common platform usually finds the marketplace stops short of what they actually need.
The named integrations that show up most in what businesses actually search for include HubSpot and Salesforce on the CRM side, Magento, BigCommerce, and Amazon for e-commerce, and Procore for construction and project management. Each exists because enough demand justified a partner building and maintaining it.
EDI sits apart from all of that. It's not a single connector but a whole separate integration pattern, exchanging structured documents, purchase orders, invoices, advance ship notices, with retail and distribution trading partners who require it as a condition of doing business, usually through a dedicated EDI provider rather than Acumatica's own marketplace listings.
Industry-specific tools are the most common gap: a construction business running Procore, or any specialized platform outside the mainstream e-commerce and CRM names, often finds no listed connector exists at all, marketplace or otherwise.
EDI compliance is the second: a retail trading partner's specific document format and transmission requirements rarely match generically across providers, so even where an EDI connection exists, getting it to actually satisfy a specific partner's requirements is its own build.
For a construction business running both, we build the sync that keeps project costs, change orders, or billing data moving between Procore and Acumatica without someone re-entering the same numbers in both systems.
When a retail or distribution trading partner requires EDI, we build the connection that generates and transmits the required documents directly out of Acumatica, formatted to that partner's own specification.
A platform, a trading partner, an industry tool with no listed connector: tell us what it is, and we'll scope what's buildable.
Tell us what it is, an industry tool, an EDI trading partner, a platform with no listed connector, and we'll scope whether it's a quick build or something bigger. And if the marketplace already covers your actual gap, that's fine too, we'll tell you that honestly instead of building something you don't need.
Let's talk →Yes, there's a marketplace connector for the common scenario, and for anything more specific to how your business uses both systems, a custom build against Acumatica's and Salesforce's APIs covers the rest.
Connectors exist for both from Acumatica's partner network, though coverage of specific fields and workflows varies by provider, which is usually where custom work picks up the difference.
Not built in natively. EDI with Acumatica typically goes through a dedicated EDI provider or a custom integration against Acumatica's API, built to match each trading partner's specific document requirements.
Some partner-built connectors exist for common scenarios, but coverage of specific project cost and billing workflows often needs custom work on top, especially for a construction business with its own particular process.
Not through a native marketplace connector. A restaurant or retail business that needs delivery platform data synced with Acumatica would need that built custom against both systems' APIs.