Suggestions go through your account, separately from support requests. They are recorded, and an accepted one becomes a roadmap entry you can follow.
#How many you get
Feature requests are limited, per product, by the license you hold for it. That is deliberate: each request takes real reading and discussion on our side, and a limit keeps that time for the requests people care about most.
| License | Feature requests, per product |
|---|---|
| Direct, Premium | 3 for the first activation, and 3 more for every additional activation you buy |
| Direct, Agency | 10 |
| Envato (Regular) | none |
A few details before you count:
The allowance is per product and per account. If you hold two licenses for the same theme, their allowances add up. A license for a different theme has its own separate count.
Buying an activation raises a Premium allowance by three, on the same license, so a Premium license covering four sites carries twelve requests for that product.
Sending a request spends it, and the outcome does not give it back. A suggestion that ships does not refund the slot, and neither does one that is declined. The exception is a suggestion we cancel before it is ever published, since you got nothing for it. Deleting your own suggestion frees the slot too.
An Envato license does not include feature requests.
An Envato sale returns a fraction of its price to us after marketplace fees, so this channel is open to customers who bought directly. It is one of several things a Regular license leaves out, and the full list is worth reading once if you are deciding where to buy. An upgrade opens the channel, along with everything else on that list.
#What we promise, and what we do not
A submitted suggestion does not commit us to anything.
No approval, no date, and no promise that an accepted idea ships exactly as described. A suggestion is not an order. We do read every one, and a good share of the theme's features grew out of them, so write to us: this section only sets expectations.
#Three channels, and this is one of them
- Support
Something is broken, or a documented feature does not behave as documented. It needs an active support window, and the support terms say what that window covers.
- A feature request
Something missing that would serve everybody using the theme. This page.
- Custom work
Something you need for your own site, whether or not anybody else would want it. Quoted and paid separately.
#What this channel is for
Ideas that are useful to everyone using the theme.
A wish specific to one site is custom work, with its own channel and its own terms.
#What a good request looks like
Ask one question: would somebody else, running the same product for a completely different purpose, want this too? If yes, it belongs here. If the answer depends on your particular content, your niche or your client, it is custom work.
A strong request names one capability, says who it serves, and says what you are doing now instead.
Add a "load more" option to post listings, so a listing can extend in place instead of paginating. Useful on any site with long listings. Right now I have to choose between numbered pages and showing everything at once, and neither suits a long archive.
That is three sentences. It asks for one thing, the need is clear, the current workaround is named, and anybody reading it can picture the setting.
A weak request describes your site instead of the product.
Add a field to the post card for my supplier's product code, shown under the title.
One site in one niche needs this. For everybody else it is an empty field cluttering the interface. Requests of this shape are usually better solved with a filter or a hook, or as custom work.
A request that gets declined immediately is a wall of generated text.
Do not send us an AI generated audit of the theme.
A thirty point list produced by asking a model to "analyze this WordPress theme and suggest improvements" is rejected on sight. The problem is that nobody stands behind the output. The model has not run the theme, has not read the settings panel, does not know which of its thirty points already ship, and is confidently wrong about several of them. Reading one costs a person an hour and produces nothing.
One request in your own words, about something you wanted while using the product, is worth more than the whole list. If a model helped you word it, that is fine, as long as the need is yours.
#Check it yourself first
Who else would use this?
Can the existing settings already do it?
Is this actually a problem rather than a suggestion? Then it is a bug report.
The third question matters. A bug sent as a feature request waits in the wrong queue, spends an allowance it should not, and is written differently.
#What happens next
An accepted suggestion becomes a roadmap entry with a status you can follow. When it ships, it appears in the changelog, and its documentation section is updated.
That cycle is why a suggestion does not disappear into an inbox.
#Common questions
How many feature requests do I have left?
The form tells you when you open it. It counts per product, so the number for one theme says nothing about another.
I have an Envato license. What are my options?
Vote on the public roadmap, which is open to everybody and is read like any other input. Beyond that, upgrading your license opens the channel along with automatic updates, every integration and every demo where an Envato license gets only the ones marked available to Envato, and priority support.
Can I see other people's suggestions?
Accepted ones appear on the public roadmap, where some entries carry votes you can add yours to.
Do I need a support window to send one?
No. A feature request is not a support request, so it does not draw on the support window. The allowance above is separate and is decided by your license tier.
How long until something is implemented?
A roadmap entry carries a rough period, not a date, and that period is intent, not a commitment.
My idea was declined. Can I ask why?
Yes. The usual reason is scope: it serves one site, not the product. In that case there is often a way to get the result with existing settings or a hook.
Does a declined suggestion give my slot back?
No. Sending it is what spends it, because the reading and the answer already happened. A suggestion we cancel before publishing does not count, and one you delete yourself is returned.
Can I pay to have my feature built?
That is custom work, a separate conversation with its own terms, and a perfectly good route.
I am unsure which channel to use
Something broken goes to support, something missing goes here, and something you need for one site goes to custom work. When it is ambiguous, send it to support and it will be pointed to the right place.
#Still stuck
Open a support ticket and say what you tried and where it stopped. Your product, your domain, a screenshot and the exact message you saw are usually enough to settle it in one reply.
Last updated
