Preparing a Product for Review

Every product you submit is reviewed by hand: what completes each section, what the review looks at and which gaps come back most often.

Overview

Submission is not automatic. Every product and every new release goes through the WISECP team's quality review and a baseline security assessment.

The readiness meter in the editor is a copy of the rule, not the rule itself. On submission the server counts the sections again and refuses anything incomplete.

Review is a quality gate, not a design audit. Most requests that come back concern what a buyer reads before purchasing rather than the product itself.

Prerequisites

Structure

A section is complete only when its own answer is. The table below says what completes each one.

Licensing is a step of its own and does not follow the price: a free product may require a check, and a paid one may ship without any. The highest supported WISECP version is not asked for — leaving it empty means there is no upper bound.

Walkthrough

Before you submit

1. Read the description as a buyer would: what the product does, who it suits, what it needs.
2. Take screenshots from the product's real screens; a cover image alone is not enough.
3. Write the compatibility range from versions you actually tested. The upper end is a gate: installations above it cannot download the package.
4. Leave the package for last, so the archive already carries the licensing you configured above it.

Submit

1. Tick the three confirmations in the review section.
2. Select Submit for Review. The product enters the queue and the editor becomes read-only.
3. You may withdraw it until a moderator picks it up; after that the decision is awaited.

After the decision

1. When changes are requested, the reason appears on the record. Correct what it names and send the product again.
2. An approved product goes live; every later update goes through its own release submission.
3. While live, description, artwork and price stay editable, and every section opens directly. A new package can still be uploaded from here, but sending it takes the card out of the catalogue until the decision comes back; a version number and a licence change normally travel with a release.

Reference

Example

A refused submission names each missing section. The reading below shows the three most common gaps.

Product identity  complete
Product pitch     missing   -> description 96 characters (120 required)
Pricing           missing   -> commercial model selected, no priced offer
Licensing         missing   -> check declared, test never passed
Compatibility     complete
Installation file missing   -> no package uploaded
Review            complete

The character count is measured on the text a visitor reads, after formatting tags are stripped. Empty paragraphs do not reach the threshold.

Pitfalls

Related Articles

• Publishing a Marketplace Product
• Marketplace Product Licensing
• Shipping a Marketplace Release
• Packaging a Module for Distribution
• Becoming a Certified Developer