When Kurodyne requests changes, a new product stays a private draft until you fix it and resubmit. For an update, your published listing and current release stay in place while you work.
- On the Console's Products page, the Review column shows Changes requested. Choose Changes requested in the Status filter to see every affected product.
- Open the product in the Product Editor. The Changes requested summary above the form shows Feedback from Kurodyne with the changes to make.
- The Console's Diagnostics shows how many products have changes requested, and its Review products button opens them on the Products page.
- If Kurodyne emails you about the decision, the email repeats the feedback, and its Open Product Editor button opens the product.
Edit the fields the feedback names. The draft still holds everything you submitted, and your edits save automatically.
- To replace the package, choose or drop a new ZIP file in the Product Editor's Files section.
- Check each change against the listing standards.
- Address every item in Kurodyne's feedback. The summary keeps Changes requested until you resubmit, even when all required fields are complete.
- Open Review and fix any listed requirements. Select Submit for review, select the license authorization checkbox, and select Submit for review again.
The Product Editor shows In review, and the Review column on the Products page changes from Changes requested to In review. The product stays locked until review finishes. How does listing review work? explains what happens next.
Changes requested on an update leave your published listing and its current release in place. Buyers keep the current release until the update is approved.
- Changing the package, Key delivery, Delivered value, Delivered value name, Key value, Access requirements, or Private usage instructions creates an included update. Give it a new Release label and Release notes.
- A change to the listing alone reuses the current release, so leave the release label and notes empty.
- To go back to the published package, select Restore published package in the Files section.
- To start over, select Discard unpublished changes. It resets the draft to the published product and removes Kurodyne's feedback on these changes.
Which buyers receive product updates? explains what an update may change.
Only a product that has never been published can be rejected. The Product Editor shows Submission rejected with Kurodyne's feedback. Rejection is final, and the product stays read-only. You can delete it now. The Product Editor, Products page, and Console's Diagnostics show the automatic deletion date, after which Kurodyne deletes the product and its files.
To try again, create a new product. Contact Kurodyne support if you think the decision needs another look. If support upholds your appeal, you still create a new product.
If you can't resubmit, open Review and check the message above Submit for review:
- Missing requirements: Open Review and select each listed item to go to its field and fix it.
- Review limit: Wait for another of your products to finish review, then submit.
- Stripe payments: A product that has never been published needs active Stripe payments. Select View Stripe account in the Review section, complete what Stripe asks for, then submit.
- Required fields complete: Readiness checks the required fields. It doesn't confirm that you addressed Kurodyne's feedback. Make the requested changes before resubmitting.