Understand Writeback results and usage

Writebacks are processed asynchronously. The review submission and Amazon's final result are separate stages.

#Find the final result

After you submit, Hopted queues the reviewed changes for Amazon. Writebacks submitted successfully confirms that stage; it does not confirm that every row was accepted.

Hopted emails the submitting admin when processing finishes, including successful and failed row counts. You can leave the spreadsheet while it is processing.

#Inspect errors and warnings

1. Add Last Writeback Issues to your sync if it is not already included.
2. Locate the affected product row. Double-click its issues cell to expand the details when needed.
3. Read the reported field, reason and marketplace. Correct the underlying value or Amazon requirement.
4. Review and submit only the rows or cells that need another attempt.

This column reflects the last Writeback and is cleared when a new Writeback starts. Keep the relevant details before another submission if you need them for support.

#Understand usage counts

Usage is based on product rows Amazon accepts successfully, rather than the number of edited cells. Several successful attribute changes in the same SKU row within one submission count as one successful row. Failed rows do not count. Submitting that row successfully again later counts again.

Open Settings → Usage for your current allowance and usage. Hopted checks access before submission and shows the next step if the batch needs more capacity.

If Amazon accepts the change but the public product page stays the same, see Troubleshoot Writeback results.