Enhancement Request (option API vs. CSV) - NetSuite "X" Category to Amazon "X" Category Add/Update

The "Add/Update" CSV template from Amazon is problematic for Updates (only update - not add) to Product Detail Fields based on Modified Date from the Saved Search provided by the initial export.

Case:

• When we purchase a product, and all data entry is completed first in NetSuite so the item can be sold on our website via Celigo, we determine if the vendor allows us to sell it on Amazon.
• If the vendor states we cannot sell it on Amazon, no further data entry is required for listing it on our website.
• If the vendor states we can sell it on Amazon, then the following occurs:
• Copy/Paste the UPC into Amazon to determine if the listing is already created and if an available ASIN can be used.
• If yes, we add our listing to our Amazon Product Catalog using this ASIN and add the identifier of SKU (productID in NetSuite) to sync products via that field.
• Also, if the item already has an ASIN, then the "Product Description" field MUST be present - otherwise, the listing will not work as it is a required field when building it on Amazon.
• If no Amazon listing exists, we go through the Amazon process of building that item which must include the "Product Description" for it to complete and saved. Then it generates the ASIN we and others can use to sell.
• Once the ASIN is created or found - we put that into a field in NetSuite so the sync can occur and map to the correct product.
• We can only modify ASIN (once created by us) since we started the ASIN.
• This is the same for a vendor or other merchant who creates the ASIN
• We cannot modify someone else's "Product Description," nor can we overwrite it since we are not the original creator of the ASIN.
• Hence the "suggested" field determination. It is not required since it is often impossible to modify that field, as noted above.

On the initial creation of a Product on Amazon, "Add" - this process works fine if the listing has never existed on Amazon using this Flow. When a manufacturer or brand owner is propagating new products into the Amazon ecosystem and those products are also available for merchants to sell on Amazon - we run into a problem. The authority to modify during this Flow is an "Update" function similar to Inventory.

In many instances, the merchant may have changed a field that isn't even used in the Flow, triggering this flow. e.g., Inventory Adjustment, adding an internal custom field for traceability purposes, making a Purchase Order, adding it to Amazon via the eTail Channel, etc. It has no direct bearing on the fields "required" by Amazon - yet this flow is triggered and hence generates errors for those required fields, which may not be authorized for change due to authority.

A suggestion for Enhancement is this: Look at the modified fields and proceed accordingly. If none of the "required" fields have been changed, skip it.