Updating Existing Marketplace Items

In the life cycle of a product, there are many reasons why a Partner may wish to edit or update work that is already for sale on the Marketplace. When it comes to requesting an update to existing marketplace items, follow these steps to have your item updated.

  CAUTION

When any Marketplace Item is sent back to Draft status, it is temporarily removed from the Marketplace and may be unavailable to those who have previously purchased it. If an item is unavailable for too long, purchasers may think they have been deleted and request a product refund.

To avoid unnecessary refunds of your products, please be mindful when making changes to Marketplace items. Have all of your changes ready and try to time re-submissions with the Product Approval Workflow.

What You Can Change Without Sending Items Back to Draft

You may live-edit the following properties of any active Roll20 Marketplace Item:
  • Title
  • Price
  • Cover Image
  • Carousel Images
  • Description text
  • Item Category
  • Item Tags
  • Bundle Discount Percentage
  • For Sale dropdown
  • Downloadable dropdown
  • Compendium Initials
  • Adding or Removing Art Assets
  • Art Asset Dimensions
  • Art Asset Names
  • Art Asset Tags

Changes will apply to previous and future purchases.

Changes that Require Sending Items Back to Draft

  • Token Marker Base Set
  • Adding/Removing Items from a Package or Dyanmic Bundle 
  • Secondary Filter Changes
  • Changes to the Game Content of Addons and Modules (see the section below for more details)

To send your Art Pack back to Draft, from the Active tab of the Item Management page, click the Send Back to Draft button next to your item.

An_Example_of_an_Actived_Art_Pack_Displayed_on_the_Active_Tab_of_a_Partner_s_Item_Management_Page.png

  Resubmission Notes

Resubmissions for approval must thoroughly describe all changes and updates made to your content in the "Notes for Roll20 Staff" box, or your item may not be re-approved.

A_Screenshot_of_the_Notes_Field_that_Appears_when_you_Submit_a_Draft_Item_for_Approval.png

Game Addons and Modules

Game Addons and Modules cannot be sent Back to Draft. You will need to work with Roll20 Staff to make any updates to the game content of an Addon or Module.  

Any changes to the product itself (Pages/Maps, Handouts, etc.) will necessitate a patch. Patching Addons and Modules can be a difficult process. It is critical that all Addons are double-checked once Approved prior to Activation to ensure they are ready to publish. Patch requests may take 2-5 days to complete.

To request a patch, submit a request through our webform and include the following:

  • A link to the active Marketplace item
  • A link to a new game that is set up with all requested updates/changes
    • We recommend using a game made from the Marketplace listing of the item, then applying all required changes to that one instead of the original game
    • Please be mindful that editing Page or Journal content may overwrite edits made in your customers' games when a patch is applied.
    • Create a new Handout Entry titled "Patch Notes" and include your change list in there. 
      • Please note that Journal entries added to a Patch game currently populate at the bottom of the Journal in alphabetical order and outside of any folders. You can instruct the user via the Patch Notes on ideal placement within the existing folder structure. If adding Journal entries and/or reorganizing folders was the main change, the patch process may take longer and require Dev assistance.
  • A thorough explanation of all changes made
    • This not only influences what is included as patch notes but also informs Marketplace Staff of the changes they are expected to see between the old and new game during the patch process. This helps with QA when creating the patch.

  Patches Cannot Remove Content

Patches cannot DELETE content retroactively from a customer's existing game. Only new games created with the patched Module or Addon will respect the removed content.  

Was this article helpful?
0 out of 0 found this helpful