Skip to main content

Understanding Rejections and Update Requests

When your data recipient reviews the data you submit in SKULaunch, they may ask you to change specific fields or complete new ones before the item can be approved.

S
Written by SKULaunch Support
Updated over 4 months ago

What these statuses mean

Rejected

A specific attribute you submitted has been reviewed and rejected by the data recipient.
This means:

  • The value you entered is not acceptable

  • The format or unit may be incorrect

  • The value conflicts with other data or documentation

  • The attribute needs to be corrected before approval

Rejected always refers to an attribute that the data recipient is not able to accept as submitted.

Update Requested

The data recipient requires you to complete a new attribute or update an existing attribute you have not submitted yet.

Typical reasons:

  • A new attribute was introduced for the product family

  • A required field was never filled

  • Data recipient needs additional information before they can approve the product

Update Requested usually refers to data you have not yet submitted or fields that were not completed originally.

Where to see what needs changing

  • Rejected fields are flagged and labelled clearly

  • Update Requested fields are highlighted so you can easily see what must be added or updated

  • Comments from the data recipient appear at the attribute level explaining what is required

If you are in a bulk edit view, the same flags appear on each attribute that needs attention.

How to fix the issue

For a rejected attribute:

  1. Open the item

  2. Review the comment explaining why the value was rejected

  3. Update the value

  4. Save

  5. Submit for review

For an update request:

  1. Open the highlighted attribute

  2. Enter the missing or updated value

  3. Save

  4. Submit for review

If you need clarification, reply directly in the comment thread for that attribute.

How re-submission works

After saving the correction or update:

  • The status moves to Update Submitted

  • Data recipient is notified

  • They review the new value

  • If acceptable, the item proceeds to Approved

  • If not, the attribute may be rejected again or a further update may be requested

Did this answer your question?