erp api fees, erp api access, erp data ownership, erp contract, distributor software
ERP API fees and data ownership: four questions to ask
November 13, 2026
Four written questions to put to an ERP vendor before you sign: API fees, data export, custom features and exit costs, with what vendors actually publish.
Executive summary
The feature list tells you what the software can do. The contract tells you what you are allowed to do with it.
ERP API fees are one of four things to get in writing before signing: what API access costs and whether it is metered, who owns your data and how you export it, who owns a feature you paid for, and what leaving costs. Most vendors I checked do not publish these terms, so the written answer is your protection.
I run ToolSwift, which connects online stores to ERPs, so I depend on that access too. That is why I am writing this one. On November 11, 2026 I read what NetSuite, Intuit and ECI publish about API access, plus third-party pages on Epicor, DMSi and Paladin, to see what vendors actually state. Where a vendor's own page blocked me, I say so below. The pages that say anything about fees are rare. This is not legal advice; have your own lawyer read the contract.
Which four questions decide what your store can do?
Four questions decide it, and each one is cheap to ask before you sign and expensive to ask after.
- What does API or file access cost, and is it metered?
- Who owns my data, and can I export all of it in a usable form?
- If I pay you to build a feature, what happens to it?
- What does leaving cost, and how long do I have?
Online ordering, contractor pricing and live stock all depend on the ERP handing data over on demand. If that handover is slow, capped or priced per call, the store above it inherits the limit. The vendor of the store can be excellent and still be stuck. Lumber yard software in 2026 explains why most dealers keep the ERP and add the store on top, which makes these terms matter more.
What does API or file access cost, and is it metered?
Ask for the fee for every route in the contract (API, file export, database access) and whether any of them has a cap, a meter or a permission step. A number on paper is a good answer. "We will work that out at the time" is a bad one.
Three vendors show the range. Oracle's NetSuite documentation says concurrent API requests are limited by service tier: a base limit of 5 for Standard, 15 for Premium and 20 for Enterprise and Ultimate on new contracts as of June 2020. Each SuiteCloud Plus license adds 10. Oracle also states that these licenses "aren't included in any service tier" and must be bought, up to 1 for Standard, 3 for Premium, 6 for Enterprise and 12 for Ultimate. Its own example: an Ultimate account with five licenses can run 70 concurrent requests. The page publishes no price for the license. That is a cap you can raise, for a fee you have to ask about.
Intuit changed the rules for apps that connect to QuickBooks. Its July 28, 2025 press release describes "access to APIs at no charge and variable API fees," plus a flat monthly program fee set by developer tier (Builder, Silver, Gold and Platinum). The release gives no dollar amounts. The fee lands on the app vendor first. Whether it reaches you is a question for your connector's contract.
For Epicor's Prophet 21, the third-party grader Supergood, which sells API services (page verified November 2026) says there is no public developer portal or sandbox, and the API reference sits on each customer's own middleware server. For Eagle, it says the API is licensed and requested through Epicor account management or a certified reseller, with no self-serve path. An integration agency, iWeb, says a BisTrack integration "may use the licensed API for reads and writes," and a comment on its page advises that the integration contract name the release, deployment model and licensed API capability. Saberis, which publishes an Agility connection page, tells Agility customers to "contact your DMSi Agility representative to set up the API connection."
For ECI Spruce I found no published API terms. ECI's own eCommerce page claims that direct connectivity with Spruce ERP lets you "avoid costly API integrations," which is a vendor claim, not a price. For Paladin, Supergood says Paladin Support must enable API access store by store; Paladin's own knowledge base blocked my read, so I quote no fee.
The pattern is that access is a negotiation, not a price list. One dealer told me that every time they ask their platform for something, it costs more. Another dealer told me they were frustrated by a monthly fee plus a percentage of transactions on a platform they used. Ask whether any percentage, per-call or per-connection charge exists anywhere in the chain, including the store vendor's side.
Who owns your data, and can you export it in a usable form?
Your data should stay yours, and you should be able to take all of it in a format a person can open. Ask for both promises in the contract, with the export format named (CSV, a database backup, an API pull) and the price of the export.
This is where I hit a wall. Oracle's NetSuite hosting policy and Epicor's customer agreement pages returned access errors to my automated reads, and I did not work around that. So I quote no ownership or export clause from either. If you cannot open the terms before signing, ask the rep for the exact clause and the exact version in writing.
Good looks like a named format and a timeline: "full export of customers, items, price levels, open orders and history, delivered as files within a stated number of days." Bad looks like a screenshot, a PDF report, or "your data is always yours" with no mechanism. Test it before you sign. Ask for a sample export of your own item file and customer list, and open it.
What happens to a feature you paid your vendor to build?
Ask who owns custom work, whether the vendor may ship it to other customers, and whether you get a credit if it does. Only a clause counts. A smile does not.
One dealer told me that an enhancement they paid their ERP vendor to build was later released to everyone. Nothing about that is unusual or necessarily unfair. Vendors build products, and a feature one customer funds can become a feature all customers get. The problem is learning it afterward. If you want exclusivity for a year, a discount on future licenses, or a credit when it ships to others, it has to be priced and written before the work starts.
The same logic covers requests that never get built. Ask how requests are prioritized, whether paying moves you up, and whether you get a refund if the date slips. No vendor can promise a roadmap. A vendor can state in writing what happens when it misses one.
What does leaving cost, and how long do you have?
Ask for the exit in numbers: notice period, the days you keep access after the contract ends, the export fee, and whether the API stays on while you migrate. Expect a short list with a day count. "We would never hold your data hostage" is not an answer.
Regulators have started to set a floor in some places. The EU Data Act has applied since September 12, 2025 and, according to the European Commission, removes switching charges, including data egress charges, from January 12, 2027. Until then, providers may charge their costs for switching and egress. It is written for EU customers of cloud services, so ask your lawyer whether it reaches you. It is still a useful yardstick: if a regulator thinks the cost of taking your data out should be zero, a vendor charging for it should be able to explain why.
Where software cannot help
No store, connector or middleware removes an ERP vendor's contract terms. If the vendor meters reads, a faster storefront still pays per read. If the vendor will not export your items, the best catalog tool in the world works from what you can get out.
That is the limit of everything I sell, and I would rather you know it first. The safest sequence is the contract questions, then the integration, then the store. The feature list can wait.
Where ToolSwift fits
I run ToolSwift, so weigh this section accordingly. ToolSwift connects to sixteen named ERP and accounting systems, including Epicor, ECI, DMSi, Paladin, QuickBooks and NetSuite, and builds connectors for systems not on that list; our team does the setup. The connection runs through your ERP's own access, so every question above applies to you as our customer too, and I would rather you ask them before a demo than after. On our side the pricing is flat: $399 a month for the first store, no transaction fees, month to month with 30 days notice. The integrations page lists every system we connect to, and BisTrack and Eagle integration routes shows how the store and ERP split the work. If you want to check an ERP's access terms against a real connection, book a demo and bring the answers you collected.
Sources
All pages read on November 11, 2026 unless noted.
Related in ToolSwift
Connected to the systems you already run
Sixteen ERP and accounting connections, and our team does the setup.