Bug in FileExchange?

[dollybeauty]

@Anonymous

Trying to get a handle on the Product catalog, via FileExchange.

Submitted upload file - Ref # 842183054 (58 actions)

The upload results file is showing 'Success' for all but a couple of Actions.The message attached to each item says - RECOMMENDED_FIELD_VALUE_MISSING|RECOMMENDED_FIELD_VALUE_MISSING|RECOMMENDED_FIELD_VALUE_MISSING

The report does not give the member any clue what is missing (I am assuming that recomended item specifics for that item's category may be the issue[?]).

When I rerun the Add unique identifiers download report, only 2 items were actually updated.

Any advice?

Side issue...Every manual upload I did today, tells me the file has already been submitted in the last 24 hours. Resubmitting works, but these files are first run files. My auto uploaded files do not have this issue.

Thanks!

[dollybeauty]

@Anonymous

Side issue 2.

In my first attempt of the above task, I had a column in the csv file, labeled SKU. It is not a FileExchange reserved word, yet FileExchange did pick up on it.

It caused the first file to give the following error (on each item) - "Error - Could not find an active item for the given SKU number. A valid ItemID or SKU number is required.|10018199|"

(My internal sku is not the same as my eBay CustomLabel number.)

Does FileExchange now key on (instead of ignoring), columns labeled SKU? Are there other reserved words? Maybe the item fields of the API?

[Anonymous · Accepted solution]

---

@dollybeauty wrote:

@Anonymous

Trying to get a handle on the Product catalog, via FileExchange.

Submitted upload file - Ref # 842183054 (58 actions)

The upload results file is showing 'Success' for all but a couple of Actions.The message attached to each item says - RECOMMENDED_FIELD_VALUE_MISSING|RECOMMENDED_FIELD_VALUE_MISSING|RECOMMENDED_FIELD_VALUE_MISSING

The report does not give the member any clue what is missing (I am assuming that recomended item specifics for that item's category may be the issue[?]).

When I rerun the Add unique identifiers download report, only 2 items were actually updated.

Any advice?

Side issue...Every manual upload I did today, tells me the file has already been submitted in the last 24 hours. Resubmitting works, but these files are first run files. My auto uploaded files do not have this issue.

Thanks!

---

Hi @dollybeauty,

The column that you're referencing is the "code" column. This will show a message like the one you saw when eBay has listing guidance to offer you. The specific details are listed in the "Message" column just to the right of it. An example of the values you might see in the Message column is this:

Optimize your price or listing details|
Same day or 1-day handling time along with free shipping improves your chances to qualify for Fast 'N Free, and increase your sales by up to 11%.|
Offer up to a 1-day handling time to get Top Rated Plus benefits, which include 10% final value fee discounts, Top Rated Plus seal, and a boost in Best Match

 
The Add Unique Identifiers download is great at updating EANs UPCs or ISBNs, but if you are trying to update Brand or MPN you will need to go about it in another way.

Product:UPC, Product:EAN, and Product:ISBN will all add those product identifiers to your listings whether or not a match in the eBay catalog is found. Product:Brand and Product:MPN work differently.

When Brand+MPN are used together, we check the eBay catalog to see if there is a match in the catalog based on the Brand + MPN combination, but if there is no match the values are not added to your listing.  Brand and MPN don't have their own product identifier field like UPC does, and since they exist in the item specifics section of listings, you would need to revise item specifics to update those values. 

In general, I recommend using the Bulk Edit and Relist tool to update item specifics in bulk. Revising item specifics through File Exchange can be more difficult if you have added a lot of custom item specifics to your listings, while it makes no difference when revising through the Bulk Edit and Revise tool.

Did you change the file name each time you were uploading the file?

[Anonymous]

---

@dollybeauty wrote:

@Anonymous

Side issue 2.

In my first attempt of the above task, I had a column in the csv file, labeled SKU. It is not a FileExchange reserved word, yet FileExchange did pick up on it.

It caused the first file to give the following error (on each item) - "Error - Could not find an active item for the given SKU number. A valid ItemID or SKU number is required.|10018199|"

(My internal sku is not the same as my eBay CustomLabel number.)

Does FileExchange now key on (instead of ignoring), columns labeled SKU? Are there other reserved words? Maybe the item fields of the API?

---

That's really interesting. I hadn't seen that behavior from File Exchange before. 

Yes, File Exchange can react to most columns that have a match in the relevant Trading API call. I wouldn't normally expect that error to occur unless you had ReviseFixedPriceItem as the action, as this API call offers the ability to manage inventory by SKU instead of by ItemID, while the Revise action does not. It's possible something has changed.

File Exchange will still ignore any fields that don't match those in the Trading API calls that it uses (AddItem, ReviseItem, EndItem) and you might find some that work but haven't been added to our File Exchange user guide yet.

 
Here's an example of some column names that could be mapped by File Exchange from developer.ebay.com

[dollybeauty]

"Did you change the file name each time you were uploading the file?" I use a list of stock filenames, z1-z9, to make common changes and upload to FE. I do not do this each day.

On that day, I had not used those filenames within the last 24 hours, or even a couple of days. I should have, and will if the issue repeats, used a filename that I never use.

Since the issue no longer exists, nevermind (lol).

Thanks for your response!

[dollybeauty]

Thanks for this info!

[dollybeauty]

Interesting info about Brand+MPN. That clears up that issue.