The short version
- A pricing page answers the questions a company wants asked - direct contact with support or sales, before paying, surfaces the ones it doesn't volunteer as readily.
- Five specific questions worth asking directly: what happens to my data if I cancel, is there a cap I'll hit as I grow, what does support actually cover, can I get a straight answer about refund terms, and what's genuinely not included.
- A vague, deflecting answer to any of these is itself useful information - a company confident in its own terms typically answers plainly and specifically, not evasively.
- None of this requires an adversarial tone - these are reasonable, ordinary questions a genuinely confident company should be entirely comfortable answering directly.
- Written answers, not just a verbal or chat assurance, are worth requesting where a specific answer materially affects the purchase decision.
Why direct contact reveals what a pricing page doesn't
Checked 27 September 2026: a company's own pricing page is written to answer the questions that page's own author wanted asked, in the order and framing that presents the offer most favourably - not dishonestly, necessarily, but naturally incomplete in the specific way any company's own marketing material tends to be. Direct contact with support or sales, before paying, is the practical way to surface the details a pricing page doesn't volunteer as readily, and a genuinely honest company should have no difficulty answering any of the questions below plainly.
"What happens to my data if I cancel or my payment lapses?"
Our piece on what happens when you stop paying a subscription tool covers why this matters directly - a specific, clear answer about data retention and export options after cancellation is worth getting before paying, not discovered only once a lapse actually happens. A vague answer here, or one that avoids the specific question asked, is itself worth noting.
"Is there a cap I'll realistically hit as my shop grows, and what happens then?"
Our piece on what a listing cap actually costs you as a shop grows covers why this specific question matters beyond simply reading the published tiers - asking directly what happens at the exact moment a cap is crossed, and whether that transition is automatic or requires a seller's own active upgrade, gets a specific answer a pricing page's own tier table doesn't always spell out in full.
"What does support actually cover, and at what response time?"
A specific, concrete answer - genuine response time expectations, and whether support is included at every tier or reserved for a higher-priced plan - is worth getting directly rather than assumed from a generic "support included" line on a pricing page. This is precisely the kind of detail our piece on the real total cost of ownership flags as easy to underestimate when comparing headline prices alone.
"Can I get your refund policy's exact wording, in writing?"
Our piece on comparing every major eBay dropshipping tool's refund policy covers why the specific wording matters more than the general existence of a guarantee - asking directly for the exact terms, in writing, rather than a verbal or chat-based assurance, gives a seller something concrete to refer back to if a dispute over the policy's actual meaning ever arises later.
"What does this tool genuinely not do that I might assume it does?"
This is the single most revealing question on the list, and the one a company's own marketing is least likely to answer unprompted. Our piece on the honest limits of Sellhelm shows what a genuinely honest answer to this question looks like when a company chooses to publish it proactively - asking it directly of any company tests whether it will offer the same honesty when asked, rather than only when it chooses to volunteer it.
What a genuinely honest answer sounds like, versus an evasive one
A company confident in its own terms typically answers each of these questions specifically and plainly, often pointing directly to a specific page or written policy rather than a vague verbal reassurance. An evasive answer - redirecting to a different question, offering only general reassurance without specifics, or declining to put an answer in writing when reasonably asked - is itself useful, real information about how that company is likely to behave once a seller has already paid and a genuine dispute or question arises later.
A sixth question worth asking, specifically about longevity
Beyond the five core questions, a further one worth asking any company, in a genuinely non-adversarial way: how long has this specific product existed in its current form, and has pricing or the feature set changed significantly recently? This isn't about penalising a genuinely newer company - a young, well-run product can be an excellent choice - it's about understanding what's actually being bought: a mature, settled offering, or one still actively finding its own shape, which changes what a seller should reasonably expect in terms of stability over the following year.
A seventh question worth adding: what happens if the company itself stops trading?
A genuinely useful, if slightly uncomfortable, question worth asking directly: what happens to a customer's own data, listings and access if the company behind the tool ever shuts down or is acquired by another business. For a server-hosted tool specifically, this is a real, non-hypothetical risk worth a direct answer, since a customer's entire operation depends on that company's own servers continuing to run - a genuinely honest company should have at least a general, considered answer to this, even if the honest answer is simply that no specific contingency plan currently exists. For a locally-run program, the same question has a different, generally reassuring answer worth confirming directly too: whether the software continues working on a customer's own machine even without ongoing contact from the company, since that structural difference matters considerably if the company itself were ever to disappear.
Why none of this needs to feel confrontational
It's worth stating plainly that asking these five or six questions doesn't require an adversarial or suspicious tone - they're entirely ordinary, reasonable questions any seller is entitled to ask before committing real money, and a company worth doing business with should welcome them as a sign of a seller doing proper, sensible due diligence rather than treat them as an unwelcome challenge. A defensive or irritated reaction to reasonable, plainly-asked questions is, in itself, a further piece of the same useful signal this whole piece is built around gathering.
Why it's worth actually saving the answers somewhere, not just reading them once
Once a company's answers have been received, saving them somewhere they can genuinely be found again later - a simple email folder or a saved document, rather than trusted to memory - is worth the small, extra effort, since the value of these answers is not just in the moment of deciding whether to buy, but in having something concrete to point back to if a genuine dispute about what was promised ever arises months or years later. A written answer that was never actually saved anywhere is, in practice, not much more useful than a verbal one once enough time has passed for the specific details to have been forgotten.
When to actually ask, and why earlier is better than during a decision deadline
These questions are worth asking well before a purchase decision feels urgent, rather than squeezed into the final moments of a limited-time offer or a trial period about to expire - a company's own support team, and the seller asking them, both tend to give more considered, complete answers away from that specific kind of time pressure. Asking early also leaves genuine room to walk away calmly if an answer turns out to be unsatisfying, without the sunk-cost pull of a countdown clock already running making that walk-away decision feel harder than it actually needs to be. A company genuinely confident in its own answers has little reason to rush a prospective customer past this kind of check, and a company that actively discourages taking the time to ask these questions properly first is, in itself, worth noticing as a signal.
The specific legal assumption worth checking, not just asking about
Many buyers assume, reasonably given how often it applies to ordinary online shopping, that any purchase made online carries an automatic 14-day right to cancel for any reason. It is worth knowing this is not actually guaranteed here: the UK's own Consumer Contracts Regulations 2013 define a "consumer" specifically as an individual acting for purposes wholly or mainly outside their own trade, business, craft or profession - and a sole trader buying a dropshipping tool specifically to run their own eBay business is, for that specific purchase, acting for their trade, not outside it. This means the statutory 14-day cooling-off right most people assume applies to any online purchase may not actually cover a business tool bought for business use at all, regardless of what applies to an ordinary consumer purchase made the same afternoon. This is exactly why questions four and one above matter as much as they do: whatever specific refund or cancellation right actually exists here is very likely coming from the company's own chosen policy, not from a backstop statutory right a seller might otherwise assume protects them regardless of what any specific company decides to offer.
A worked example
A seller emails a shortlisted company's support team all five questions directly before purchasing. The response addresses data retention specifically, quotes the exact cap and upgrade mechanism from the pricing page, states support response times plainly, links directly to the written refund policy, and - notably - proactively names two things the tool genuinely doesn't do rather than deflecting the question. This specific, direct, complete response is itself a strong, positive signal about the company's own transparency, independent of anything the pricing page alone could have shown - exactly the kind of direct evidence worth gathering before, not after, paying real money to a company a seller is about to depend on for their own livelihood.
Questions people ask
Why ask a company directly instead of just reading its pricing page?
A pricing page answers what a company chooses to volunteer. Direct contact surfaces the specific details - data retention, support levels, genuine limits - that pages don't always spell out.
What is the single most revealing question to ask a software company?
What the tool genuinely doesn’t do that a buyer might assume it does - a company’s willingness to answer this specifically and honestly says a lot about its overall transparency.
Should I get a refund policy in writing rather than a verbal answer?
Yes, where the answer materially affects the purchase decision - a written answer gives something concrete to refer back to if a dispute over its meaning arises later.
What does an evasive answer to these questions actually tell you?
It's genuinely useful information in itself - a company reluctant to answer plainly before a purchase is a real signal worth weighing alongside the price itself.