Updated August 21st, 2026

Items submitted to Wrapmarket are reviewed against the Quality Guidelines before publication. The purpose of review is to evaluate the submitted item and assign one of three outcomes: Published, Soft Rejected, or Hard Rejected.

The review process considers the item as a whole. The item submission may satisfy every required form field while still requiring changes to its design, functionality, presentation, live preview, or other customer-facing details.

The Quality Guidelines define the requirements and standards that apply to submissions. This page explains how review works and how to respond to a review decision.

Table of contents

Before submitting an item

Submit only after the item and its customer-facing materials are complete, accurate, and ready for customers. Read the complete Quality Guidelines and any other applicable marketplace policies.

Test the exact item, download package, and live preview being submitted, and correct known issues before submitting rather than relying on the review process to identify unfinished work.

The item submission process includes the following steps:

  • Complete the applicable item settings and disclosures.
  • Provide the listing details and attributes.
  • Upload the listing images and provide a live preview where applicable.
  • Upload the complete customer download package.

All required steps must be completed before the item can be submitted for review. Completion of the submission steps means that the required information has been provided. It does not mean the item will be published.

Do not submit a known incomplete item merely to reserve a place in the review queue or to obtain a list of work that remains to be completed.

Review may evaluate design quality, but it is not a design critique or product-development service. Reviewers may identify issues that prevent publication, but they are not responsible for establishing the item's creative direction, teaching design principles, or providing a step-by-step plan for completing or redesigning it.

What the review considers

The reviewer may examine any part of the item or submission that is relevant to customer readiness or marketplace policy. The reviewer may inspect selected parts of a large item rather than testing every page, file, component, configuration, device, or possible use case. Creators remain responsible for the complete item.

Review commonly considers:

  • Quality and customer readiness
    Whether the item is sufficiently complete, usable, refined, and professionally prepared for its purpose and category.
  • Functionality and technical preparation
    Whether the item works as represented and the customer download is usable and appropriately prepared.
  • Accuracy and consistency
    Whether the listing and customer-facing materials accurately and consistently represent the item and package.
  • Originality and policy compliance
    Whether the item reflects meaningful creator contribution and is aligned with applicable marketplace policies, such as the License Terms, Support Policy, and Refund & Exchange Policy.
  • Settings and disclosures
    Whether the information supplied with the submission accurately describes the item.
  • Overall customer experience
    Whether a reasonable customer will be able to understand, evaluate, and begin using the item.

These broad review areas do not replace or limit the requirements in the Quality Guidelines.

Possible review outcomes

Published

If the submitted item meets the applicable quality and policy requirements and is ready to be offered to customers, it is published. Publication does not transfer responsibility for the item to Wrapmarket. You remain responsible for its content, functionality, legality, accuracy, support, maintenance, and future releases.

Soft rejected

If the item requires correctable changes before it can be published, it is soft rejected. The creator receives the review decision and the concerns identified during that review. The item remains unpublished and available in the creator's dashboard for revision and resubmission.

After completing the requested changes, the creator must review the submission as a whole and resubmit it for re-evaluation. The new review may result in any of the three outcomes.

Hard rejected

If Wrapmarket is not requesting changes and does not want to publish the item, it is hard rejected. A hard rejection is not a request to revise and resubmit the same submission for re-evaluation.

An item may be hard rejected when it is substantially incomplete, too minimal for its represented purpose or category, does not meet the marketplace's quality level, presents unresolved rights or policy concerns, is misleading, or would require a fundamental redesign or redevelopment rather than a reasonable set of corrections.

An item may be functional, visually appealing, or potentially useful to customers and still be hard rejected if it lacks the originality, depth, refinement, or overall direction expected for new items.

When the concern is broad or foundational, it may not be possible or useful to provide a finite revision checklist. Whether a substantially reworked item may be submitted in the future will depend on the reason for the hard rejection and the extent of the changes made afterward.

Categories marked Soon

A category marked Soon is accepting submissions before its public launch. The category and its submitted items are not yet offered to customers, and accepting submissions does not guarantee a launch date.

These submissions follow the same quality requirements and review process as other items. If an item is otherwise ready for publication while its category remains Soon, publication is deferred and the item remains unpublished until the category launches.

Wrapmarket may re-evaluate the item before publication and request changes if its files, supported software, listing, presentation, or applicable marketplace requirements have changed while it was waiting. The creator is responsible for supplying a current, customer-ready submission when the category launches.

Responding to a soft rejection

A soft rejection email identifies concerns that must be addressed before the item can be re-evaluated. Depending on the condition of the submission, it may provide specific corrections, identify broader areas requiring work, or direct the creator to relevant sections of the Quality Guidelines.

It is not a complete checklist or restatement of every requirement that applies to the item.

The reviewer may request corrections for any applicable requirement in the Quality Guidelines or another issue that materially affects customer readiness, accuracy, functionality, usability, or marketplace policy.

Review the complete email before making changes. Some corrections may apply in more than one place.

For example, changing an item name may also require changes to the logo, listing, live preview, documentation, filenames, source comments, and package content. Correcting a compatibility claim may require changes to the attributes, description, documentation, live preview, and item itself.

When preparing a revised submission:

  • Address every requested change that applies to the item.
  • Apply the correction throughout the submission, not only to the specific example identified by the reviewer.
  • Test the revised item and package from a clean copy.
  • Confirm that the listing, live preview, screenshots, documentation, and package remain consistent.
  • Resubmit only after the revised version is complete.

If a request does not appear to apply, provide a clear explanation and any relevant supporting information. If you do not understand a request, ask for clarification. Do not silently ignore the request.

Additional review rounds

An item is re-evaluated after it is resubmitted following a soft rejection. It may then be published, soft rejected again, or hard rejected. Another soft rejection may occur when:

  • A prior request was not fully addressed.
  • A correction was made in one location but conflicting information remains elsewhere.
  • The revised package introduces a new issue.
  • An issue could not reasonably be evaluated until an earlier problem was corrected.
  • Further inspection identifies another material concern.

A prior soft rejection email should not be treated as a complete certification of every part of the submission. The creator is responsible for reviewing the entire item before each resubmission.

Applying prior review feedback

Creators are expected to apply generally relevant instructions from prior reviews when preparing future submissions. A correction should not be treated as applying only to the specific item or example in which it was first identified.

If the same issue appears in later submissions, the reviewer may identify it again or refer to prior guidance without repeating the complete explanation. Repeated failure to apply a clear and applicable requirement may be considered when determining whether another soft rejection is appropriate.

Each item is still evaluated as submitted, and prior feedback applies only when it is relevant to the new item.

Scope and judgment

Some requirements are objective, such as image dimensions, file formats, package limits, required fields, and valid URLs. Other decisions require judgment, including whether an item is sufficiently complete, original, usable, professionally presented, or differentiated for the marketplace.

Review decisions are based on the submission as it stands, its category, complexity, intended use, representations, and expected customer experience, together with the standards applied to new items at the time of review.

Publication of another item, including an older or similar item, does not establish that a new item will also be published.

Review is not an exhaustive audit

Wrapmarket review is not a complete code audit, security audit, accessibility audit, legal review, license audit, or test of every possible configuration.

Publication does not represent or guarantee that:

  • The item contains no bugs, vulnerabilities, or compatibility problems.
  • Every statement made by the creator has been independently verified.
  • Every included file or third-party license has been examined.
  • The item will work with unsupported software, environments, modifications, or integrations.
  • The item will continue to meet marketplace requirements after it is changed or updated.

You remain responsible for conducting the testing, rights review, and quality control appropriate for your item.

Creator communication

Messages sent by a creator about a review decision should remain focused on the item, the stated concerns, and any requested changes. Creators may provide relevant context, explain technical decisions, or point out information the reviewer may have missed. Disagreement with a requested change in a soft rejection does not remove the requirement to resolve the underlying concern. Where more than one solution is reasonable, the creator may propose an alternative that addresses the same customer or policy issue.