Website templates are the most-refunded category in digital products, and almost always for the same reason: the buyer received exactly what was listed, and it was not what they assumed. The preview was a rendered image. The files were the real product. Those two things can differ enormously.
The Licence Decides What You Bought
Read this before anything else, because it is where the expensive mistakes live.
Single-use — one website, one domain. Using it for a second client is a breach.
Multi-use — several projects, usually capped.
Developer or extended — unlimited client projects. This is what agencies and freelancers actually need, and it is frequently a different, higher-priced tier.
Resale rights — you may sell the template itself. Rare and expensive.
End-product restrictions — some licences forbid use in anything sold as a product, which excludes SaaS entirely.
If you build a client site on a single-use licence, the problem surfaces when the client asks for the files. Ask the seller directly, in the deal chat, what the licence permits — and get the answer in writing before you confirm.
What "Included" Actually Means
Source or build output? For a coded template, you want the working source — the Sass or Tailwind config, the component files, the build setup. A folder of minified CSS is technically a website and practically unmaintainable.
Which framework, and which version? "React template" spans a static export and a Next.js app with server components. Ask for the exact stack and versions.
Are the demo images licensed to you? Usually not. Template previews are typically built with stock photography licensed to the author, replaced with placeholders in the delivered files. If the demo look depends on those images, you have a further purchase ahead.
Fonts. Same problem. A template designed around a commercial font ships without it.
Included plugins. WordPress templates often bundle premium plugins. Ask whether those licences transfer, or whether you are inheriting software that cannot receive updates.
Verifying Files Before You Confirm
The escrow window exists for this. On Escrozon funds are held in escrow while you check the delivery, so:
- Extract the archive and look at the folder structure. A tidy structure with a readme is a reasonable proxy for care taken.
- Open it locally. Static templates open directly; framework templates need an install and a dev server. If it will not run, you have found that out while funds are still held.
- Compare against the preview. Same layout, same sections, same components. Missing pages are the most common discrepancy.
- Check responsiveness yourself at phone, tablet and desktop widths.
- Test in more than one browser. Safari in particular breaks layouts that work everywhere else.
- Search for hard-coded URLs and keys. Templates sometimes ship pointing at the author's analytics or API endpoints.
- Read the licence file inside the archive, not just the listing text. If they disagree, raise it before confirming.
Red Flags
Refusal to use escrow. On a platform built around it, this is the whole answer.
Password-protected archives with no password. Sometimes a mistake, sometimes a stalling tactic while the clock runs.
A preview that is an image rather than a live demo. Ask for a working URL. Anyone selling a real template has one.
Delivered as a PDF or a video walkthrough. That is not a template.
Vague framework claims. "Modern responsive HTML5" describes nothing. Specifics are cheap for an honest seller.
A price far below the category. Nulled premium themes circulate widely, cannot receive security updates, and occasionally ship with injected code. If the price makes no sense, that is usually why.
For Sellers
Provide a live demo URL. Publish the exact stack with versions. State the licence tier plainly in the description. List explicitly what is not included — demo images, fonts, plugin licences — because that is where every dispute in this category starts. Sellers who disclose exclusions up front see fewer refund requests, not more.
Frequently Asked Questions
Can I use one template for two client sites? Only under a multi-use or developer licence. Single-use means one end product. Ask before buying, not after.
The template does not match the demo. Is that a valid dispute? Yes. Materially differing from the advertised product is exactly what escrow covers. Screenshot the demo and the delivered files side by side.
Do I get updates? Only if the seller says so. Many marketplace templates are sold as-is. If ongoing updates matter, confirm it in writing before confirming receipt.
What if it uses a paid plugin I do not own? Ask whether the licence transfers. Many do not. You may be able to run the template without that plugin, but confirm which features you lose.
Is a nulled theme really that risky? Yes. No security updates, and modified distributions have historically shipped with backdoors. Ask for a licence key and purchase receipt; if the seller cannot produce them, walk away.
