The 2026 ERP Buyer's Checklist: 20 Questions to Ask Every Vendor

Most ERP demos are built to answer the questions vendors want you to ask. Show the dashboard. Walk through the sales pipeline. Play the AI highlight reel. What they are not built to answer are the questions that actually determine whether you will be happy with the decision two years from now: what this costs at your real headcount, what happens to your data the day you want to leave, and whether the "AI" on slide fourteen is a shipped feature or just a slide.

This is a checklist of twenty questions organized around the five things that quietly decide most ERP outcomes: pricing, data portability, AI claims, support, and total cost of ownership. Ask them in order, in the room, and write down the answers. A vendor who has nothing to hide will not mind.

Pricing Transparency

Pricing is where ERP vendors do the most creative work, and where buyers get burned the most often. A published price list tells you something a "let's set up a call with our sales team" page does not: whether the vendor is confident enough in its own pricing to show it to a stranger.

1. Is your pricing published, or does it require a custom quote?

There is a real difference between a price that varies by scale and a price that is negotiated in a closed room. NetSuite does not publish a price list at all: pricing is negotiated deal by deal (ERP Research, "NetSuite Pricing 2026," https://www.erpresearch.com/pricing/oracle-netsuite), and Infor's plan costs are likewise only available by requesting a custom quote (The CFO Club, "Infor Pricing Tiers & Costs," https://thecfoclub.com/tools/infor-erp-pricing/). When a vendor prices this way, your number depends as much on your sales rep as it does on what you actually need. Published, flat pricing is checkable by anyone, including your CFO, before a single call happens.

2. What does implementation actually cost, separate from the license?

Ask for a number, not a range with an asterisk. Implementation, data migration, and configuration can end up costing more than the software license itself once consultants, custom fields, and data cleanup are added in. Ask the vendor to show you where that number comes from, and get it in writing before you sign anything for the software itself.

3. Are there per-module or per-feature add-on fees once we are live?

Some platforms price the base seat cheaply and then gate the modules you actually need, advanced reporting, a second warehouse, API access, behind per-module fees discovered after go-live. Ask for the complete list of what is included at your tier, not just the marketing page's summary.

4. Does the price change based on our industry, region, or company size, and if so, how?

If the answer involves a "custom enterprise agreement," ask what specifically about your business changes the calculation. A vague answer here usually means the real answer is "whatever the market will bear."

Data Portability and Lock-in

The data portability questions matter more the longer you plan to stay with a vendor, which is exactly why they get asked the least during a sales process. Nobody signs a contract planning to leave. But every ERP relationship eventually reaches a renewal, a pricing change, or a shift in business needs, and what happens at that point is decided by decisions made before you signed.

5. Can we export all of our data, in a usable format, at any time?

Not a partial export of a few standard reports. All of it: transactions, custom fields, attachments, historical records. Ask for a demo of the export function during the sales process, not a promise that it exists.

6. Is the platform open source, or fully proprietary?

This is not a purity test. It is a practical question about what happens if the vendor is acquired, changes direction, or shuts down a product line. An open source core means you, or a contractor of your choosing, can keep running the system independently of the vendor's continued existence. A closed, proprietary core means your operational continuity depends entirely on one company's roadmap.

7. What happens to our data and our access if we terminate the contract?

Get the exact terms: how long you retain read access after cancellation, and whether any of your data remains on their infrastructure with no path back to you. This should be a specific contract clause, not a verbal assurance.

8. Can we self-host, or are we permanently dependent on your cloud?

Even if you plan to run on managed cloud hosting for convenience, knowing whether self-hosting is a real, supported option changes your negotiating position for every renewal that follows.

AI Claims

Every ERP vendor now claims AI. Almost none of them will answer specific questions about how it actually works, because "AI-powered" has become a marketing modifier applied to features that existed unchanged five years ago. G2's 2026 report on ERP buyers advises looking past feature claims and evaluating AI "based on workflow impact, automation value, and decision support" (G2, "Best ERP Software in 2026: What 500+ Buyers Say About AI, Implementation, and Vendor Trust," https://learn.g2.com/tech-signals-best-erp-software-in-2026-g2-review-insights), but stops short of giving buyers concrete questions to ask. For more on spotting AI-washing, see our companion piece on telling real AI from marketing. The five questions below are the condensed version.

9. Show me one specific, named AI feature acting on live transactional data, not a reporting dashboard.

A chatbot that summarizes a report is not the same thing as a feature that scores a lead, flags a reconciliation mismatch, or reorders stock automatically. Ask to see the second kind, in a live system, not a scripted video.

10. If I removed this AI feature entirely, what would stop working?

This is the single best test for AI-washing. If the honest answer is "nothing, it's a nice-to-have summary," the AI is decorative. If the answer is "the reconciliation queue would stop clearing automatically" or "leads would stop getting scored," the AI is doing real work inside the product.

11. Is AI available across many modules, or confined to one bolted-on add-on?

A single AI chatbot layered on top of an otherwise unchanged ERP is a different product than AI embedded in the modules where the actual transactions happen: sales, inventory, accounting, HR. Ask for the specific list of modules where AI is live today, by name, not a roadmap slide of what is coming.

12. Is AI included in every tier, or gated entirely to the top, most expensive plan?

AI gated entirely behind the top tier is not automatically dishonest, building and running AI agents costs real money, but a vendor who cannot explain why it is priced that way, or who buries the gating in fine print, is treating AI as a monetization lever rather than a product decision they will defend out loud.

13. Whose infrastructure does the AI run on, and can I choose or switch the underlying model provider?

A vendor who cannot answer who controls the model or infrastructure behind their AI feature is usually running a thin wrapper around someone else's API with no real ownership of the workflow. Ask whether you are locked into one AI provider, and what happens if that provider changes pricing or shuts down.

Support and Implementation

The sales team that runs your demo is rarely the team you deal with a year in. Support quality and implementation reality separate vendors more than any feature comparison does.

14. What does support actually include at our tier, and what is the guaranteed response time?

"Email support" can mean a same-day reply or a five-business-day queue. Get the specific service level in writing, and ask what channel (email, chat, phone) is actually available, not just listed.

15. Who does the implementation: your own team, a certified partner network, or do we need to find our own consultant?

This changes both cost and accountability. If something goes wrong during migration, you want to know in advance whether the vendor owns that problem or whether you are managing a third party on your own.

16. Can we talk to a customer who has been live on this platform for at least a year?

Not a curated case study. A live reference call. If a vendor cannot produce one for a platform they claim has been in the market for years, treat that as information.

Total Cost of Ownership

The sticker price is rarely the real price. Total cost of ownership is what the decision actually costs across a multi-year horizon, and it is where most ERP budgets go wrong.

17. What is the all-in cost per user per month at our actual headcount, including implementation amortized over three years?

Ask the vendor to do this math with you, live, using your numbers. If they resist, do it yourself with the numbers they have given you for questions 1 through 4, or run them through our ROI calculator for the three-year number.

18. What is the cost of adding users, modules, or a new location later, not just today?

Growth is usually the point of buying ERP in the first place. Make sure the pricing model does not punish you for succeeding.

19. What does migrating away from this platform cost, in time and money, if we need to?

Nobody wants to plan their exit before they have started, but a rough answer here tells you how strong your negotiating position will be at every future renewal.

20. Are there mandatory annual price increases built into the contract?

Some vendors build automatic year-over-year increases into multi-year agreements. Ask directly, and get the percentage in writing if one exists.

How Yukti Answers a Few of These

We are not going to pretend Yukti has a perfect answer to all twenty questions, no vendor does, but a handful of these map directly onto decisions we have made and we would rather state them plainly than let a demo imply something broader.

On pricing (questions 1 through 3): our pricing is published, not negotiated. Enterprise is $9.99 per user per month billed monthly, $7.99 billed annually, and effectively $6.66 per user per month on a two year plan with the third year free. There is no per-module AI upsell hidden behind that number, and Community, our self-hosted, open source edition, is free forever with 50 or more core ERP modules and no user limit.

On data portability (questions 5 through 8): the Community edition is fully open source under LGPL-3.0, with complete source code access, so you are never dependent on us continuing to exist to keep running your own instance. Self-hosting is a real, supported path, not a hypothetical.

On the AI questions, we want to be direct rather than generous with ourselves. Our 14 AI agents, covering CRM, sales, inventory, accounting, HR, manufacturing, and more, are an Enterprise-tier feature, not part of the free Community plan, and we are not going to pretend otherwise. What we can say honestly: it is one flat-priced tier, not per-module add-ons; the price is published, not sales-gated; the agents sit inside the actual transactional modules, not behind a single generic chatbot; and the platform beneath the AI layer is fully open source and auditable. The AI itself is provider-agnostic, running on OpenAI, Anthropic, Google, or a local model through Ollama, switchable without rebuilding your workflows. That answers question 13, but it does not change the fact that AI is a paid feature, and any vendor, us included, who implies otherwise about their own product deserves the same skepticism this checklist applies everywhere else.

Ask these twenty questions of every vendor you evaluate, including us. The answers, and how comfortable a vendor is giving them out loud, will tell you more than any demo will. Want the side-by-side version against a specific vendor? Our comparison pages walk through it.