A ready-made product saves weeks of work if it fits and costs you weeks if it does not. Most of the information you need is on the listing, if you know which parts to read.
Read the licence before the feature list
- How many projects or sites may use it?
- May you use it for client work, or only for your own?
- May you resell it, or include it in something you resell?
- Does the licence last forever, or only while a subscription runs?
If the listing is vague, ask the seller to state it in the order. Under our Buyer Terms, the licence described in the listing is the one you receive for ready-made products.
Look at the maintenance story
Software ages. Check whether the product states which versions of its framework it supports, how updates are delivered, and how long support is included. A template that has not been touched since the last major framework release may need work before it runs at all.
Check what is inside
Third-party code and assets keep their own licences. A trustworthy seller lists what is bundled. If the product handles user data, payments or logins, ask how secrets are managed and whether dependencies are kept current.
Test on something small first
Before deploying to production, install it in a scratch project and try the one feature you are buying it for. Downloaded and deployed products are generally not refundable, so the trial period is the only one you get. The conditions that do allow a refund are in the Refund and Cancellation Policy.
Plan for the seller disappearing
Ask whether you receive the source, not just access to a hosted service, and keep your own copy. For APIs, consider how much of your product depends on one provider and whether you could swap it.
Check the work-mode label
A product may be Human Built, AI Assisted, AI Generated with human verification, or Automated. None is better in general. Read the label alongside the licence and support terms, and see what we say about choosing between them.