My client and I both were having problems updating the product images in her store. Any time we try to replace the MAIN product image inventory item, we’d get the message:
The file you specified does not appear to be an image file.
Please make sure the file you specified is not missing or currupt and is a .jpg or .gif
In order to replace the main image for a product:
- Delete the main image.
- Wait a day. When I uploaded a new picture right away, it would always show the previous one. Waiting for the change queue to process seemed to correct this. The queue might take a few minutes or several hours. The blue “In Queue” number on the screen’s lower right shows the current queue.
- Upload the new image.
It’s possible that waiting for the queue to clear isn’t necessary, that the new image is stored and will get displayed correctly once the queue clears
I know what you’re thinking: you have to delete all the pictures, wait, and then re-upload them? you can’t just “replace” them like the screen implies?
I guess we’ll just call it a quirk.
Amazon SellerCentral – discrepancies in the category hierarchy
We are seeing discrepancies between the Categories & Pages / Category Pages hierarchy, and the one on Store Design / Merchandising & Layout / Site Design.
I would expect that adding new categories, renaming them, etc on the “Categories & Pages” would be reflected on the Merchandise page. So from a given category you could select the “Edit in Merchandising & Layout” link and be taken to to that page. But it doesn’t work that way.
For example, in our store, I go to the “Dental Products/XX Instruments” category and select the “edit” link, and the page loads the “Hand Instruments” page. So far I can’t find a way to edit (in Merchandise & Layout) the categories that actually exist on Categories & Pages.
I would also expect the hierarchy to be reflected in the “Browse Structure Directory” screen, accessible from Inventory/Manage Inventory/View & Edit/Page Assignment Tags. The hierarchy shown here for us is different than either of the other two hierarchies, and reflects the initial state of our (published, but not launched) store.
We’ve published multiple times, waited over a week, and watched the update queue finish processing. Still no luck. Help desk is looking into it.
I don’t think we’re doing anything too unusual, but we’ll see.