What questions should I ask an ERP vendor before signing?

Questions to ask ERP vendors and implementation partners about fit, integrations, GST, data ownership, support and exit before a D2C brand signs a contract.

Anadoris Digital · · 4 min read

Business meeting
Photo: rawpixel.com / Unsplash (CC0)

ERP sales conversations tend to focus on features. The questions that decide whether a project succeeds are usually about fit, integrations, support and ownership. Asking them before you sign saves months of frustration after.

Use the questions below with both the software vendor and the implementation partner, if they are different companies. Ask for answers in writing where they affect cost or scope.

Fit with your processes

  • Can you run our real order-to-cash flow in a demo, using our SKUs and channels?
  • How does the system handle combos, multipacks and free gifts?
  • How does it handle purchase orders to a contract manufacturer where we supply packaging?
  • Does it track batch and expiry from receipt to dispatch and returns?
  • What do other D2C brands of our size typically customise, and why?
  • Which of our requirements would need a workaround or custom work?

Integrations

  • Which of our sales channels, couriers and payment gateways have ready connectors?
  • Who builds and maintains each connector: you, a partner or a third party?
  • How often does each connector sync, and what happens when a sync fails?
  • What does it cost to add a new channel later?
  • Is there a documented API we can use for our own integrations?

Integrations are where D2C projects most often slip. Ask to see each connector working with a real account, not only a description of it.

Indian compliance

  • How are GST invoices, credit notes and return data produced?
  • How does e-invoicing and e-way bill generation work, and through which provider?
  • Can we keep Tally, and how does the integration work?
  • Who updates the system when GST rules or formats change?

Cost and scope

  • What exactly is included in the licence or subscription, and what is extra?
  • How are users counted, and do warehouse staff need full licences?
  • What does implementation include: data migration, training, integrations, reports?
  • How are change requests priced once the project starts?
  • What ongoing costs should we expect after go-live?

Ask for a written scope that lists deliverables, assumptions and what is out of scope. Ambiguity at this stage almost always turns into extra cost later.

Support, data and exit

  • How do we raise support issues, and what response times are committed in the contract?
  • Who on your side knows our setup after go-live?
  • Where is our data hosted, and how is it backed up?
  • Can we export all our data in standard formats at any time?
  • What happens to our data if we end the contract?
  • Can we speak to two or three current customers similar to us?

How to read the answers

Vague answers are a signal. A vendor who says everything is possible, without showing it or naming a cost, is describing what software could do, not what you will get. Good partners are comfortable saying a requirement is a poor fit, or that they would suggest changing a process instead of customising.

Reference calls are worth the time. Ask references what went wrong, how the partner handled it and what they would do differently. Those answers tell you more than any demo.

Read the contract’s terms on data ownership, termination, price changes and support commitments carefully, and have someone qualified review it. Verbal assurances in sales meetings are not part of the contract.

Questions about the implementation team

  • Who exactly will work on our project, and what similar projects have they done?
  • Will the same people support us after go-live?
  • How do you run testing and training, and how much time do you need from our team?
  • What do you need from us, and by when, for the plan to hold?
  • How do you handle disagreements about scope during the project?

The people matter as much as the product. A strong team that understands D2C operations, marketplaces and Indian GST will catch problems early and suggest simpler approaches. A team learning your industry on your project will take longer and miss things. Ask to meet the actual consultants, not only the sales lead.

Ask also how the partner documents your setup. Clear notes on configuration, integrations and custom work make it possible to change partners later or bring support in-house if you need to.

Keep a simple record of every answer each vendor gives, in the same format. When you compare options a few weeks later, memory of who said what fades quickly, and a written scorecard keeps the decision grounded in evidence rather than the most recent or most persuasive meeting.

Where to start

  • Prepare a short pack: your SKU list sample, channels, a typical PO and a few real orders.
  • Send it to each shortlisted vendor before the demo.
  • Use the questions above as a scorecard during demos.
  • Ask for written scope and pricing based on what you saw.
  • Call references before signing.

If it helps, Anadoris Digital can sit in on vendor demos with you and help interpret the answers against your actual operation.

Related service: ERP Solutions · More on this topic: ERP Solutions articles

Common questions

Should I ask for a paid pilot before signing a full contract?

A short paid discovery or pilot can be worthwhile for larger projects. It lets you test fit, integrations and the partner’s working style with limited commitment. Agree clear goals and what happens to the work if you do not continue.

How many ERP vendors should I evaluate?

Two or three serious options is usually enough for a small brand. More than that spreads your team’s time thin and makes comparisons harder. Do a quick paper screen first, then run detailed demos with your own data for the shortlist.

What is the most overlooked question for ERP vendors?

How you get your data out. Founders rarely ask until they want to leave. Confirm that all data, including history, can be exported in standard formats at any time, and that the contract states what happens to it on termination.

Your next chapter

Let’s build what comes next.

A new website. A better system. A simpler way to work. Tell us where you want to begin.

Discuss your project