New Marketplace feature creates a more direct way to push missing apps and product gaps into view

Sitecore just opened up Marketplace idea submission and voting to the wider community.

That's a small product update on paper, but it could matter if you've been watching the Marketplace and wondering why some obvious gaps keep hanging around. Sitecore is now giving Cloud Portal organization team members a direct way to suggest apps and push useful ideas up the list.

It's not a roadmap commitment, but it is a clearer feedback loop than the usual "tell your account team and hope for the best" approach.

What changed

Sitecore says Marketplace users can now:

• Submit new app ideas
• Browse existing ideas
• Upvote ideas they want to see built
• Search and sort ideas they want to see built
• Share idea links with others

There are a few practical limits:

• Each team member gets 1 vote per idea
• Each organization can submit up to 50 ideas
• Ideas can only be edited or deleted before they get their first upvote

Why this matters

This gives customers and partners a more visible way to signal demand.

That matters because the Marketplace only gets better if the missing pieces are easy to spot and easy to prioritize. A public-ish idea and voting flow won't magically fix that, but it should make it easier for Sitecore and partners to see what people actually want instead of guessing.

It also creates a bit more pressure for good ideas to rise on merit.

Who should care

A few groups should pay attention here:

• Sitecore customers that keep hitting the same product gaps and want a cleaner way to raise them
• Internal platform owners who want to influence what shows up in Marketplace
• Partners looking for signals about what customers would actually buy or install
• Teams already using Cloud Portal and Marketplace as part of their regular workflow

If your team has been keeping a private wishlist of missing connectors, utilities, governance tools, or admin helpers, this is the sort of update worth using.

Practical watch-outs

A few things stand out from the changelog:

• The 50 idea cap is per organization, so teams should probably avoid dumping every half-formed thought into it
• Once an idea gets its first upvote, you lose the ability to edit or delete it, so wording matters
• Voting is limited to one upvote per team member per idea, which helps a bit, but it still favours organizations that are organized enough to rally around their asks

In other words, treat submissions like product proposals, not rough notes.

My take

This is a sensible addition. It doesn't guarantee the right apps get built, and it doesn't tell us how heavily Sitecore or partners will actually lean on the signal. But it does reduce friction, and that's usually the first thing you want from feedback tooling.

If you work in the Sitecore ecosystem, the practical move is simple: submit the gaps that keep costing your team time, then upvote ideas that would genuinely make operations easier.