Feed File Info

Selling on Amazon Listings and Variations
,
1

Just spent about an hour with a person (who is here in the US) about getting the product ID Feed Category corrected.

I don’t sell electronics, shoe laces, candles…etc…or backgrounds.

What she had me do was to go into the Catalog and download the spreadsheet as if I was creating a totally new item (as opposed to updating an existing item).

She said there’s a slight difference on how the backend treats the two files.

She completed the file for me while we were on the phone and it’s uploading now. AND if the ASIN is part of a variation, she said I’d have to do the entire family.

AND she didn’t recommend that in one FAMILY that there be several product feed type ID’s (like I use table runners, placemats, and tablecloths because my family is based on pattern – like White Lily Flowers and all the sizes show up).

We’ll see how this goes.

I have about 25 that need to be fixed. And if this works, I’ll know what to do.

3 Likes
2

:open_mouth: Very interesting, deserved a call out IMO. So often, we try to touch the least amount of breakable things and do an update versus new feed.

1 Like
3

she still used PARTIAL update – but to get to the template, it was “create a new item”…

So there’s something in the coding behind the scenes.

3 Likes
4

Reporting back – it didn’t work. So I’m hanging tight to see what they say before I spend tons of time trying to fix the other ones.

Iris

4 Likes
5

So chatted this time, last time was a phone call, and the agent said she’d update it.

So gotta give it over night again and see right?

I asked her if I needed to open individual cases for the 25 or so (out of 700) and she said to do about 5 per case.

SO If this works – maybe I have an avenue to a solution.???

2 Likes
6

The newer templates have more fields, but I’m not aware of anything else. that could depend though on how old your template was and how it was generated.

Correct. As much as we might like to think these are variations, they really aren’t. they are different items with the same pattern.

I would really see this Type as being a “Collection” type instead of “Variation.”

3 Likes
7

The template was about a week old. I have learned to kinda start fresh because Amazon changes them too often.

Collection is another good word.

3 Likes
8

I wouldn’t phrase it that way. It is “THE” word if you are putting “runners, placemats, and tablecloths” into a Relationship.

Your items are not “variations” because they are the same pattern, in the technical sense, and could be considered violations by Amazon.

Yes, they can be in a “Relationship”, just not a “Variation Relationship.” It needs to be a “Collection Relationship.” I’m hoping that is allowed for you in Handmade (I’m still on coffee #1 but I believe that’s where these are going)

Not sure if “Collection” shows up in the template, but it is in the XML.

<xsd:element name="Type">
	<xsd:simpleType>
		<xsd:restriction base="xsd:string">
						<xsd:enumeration value="Variation"/>
						<xsd:enumeration value="DisplaySet"/>
						<xsd:enumeration value="Collection"/>
						<xsd:enumeration value="Accessory"/>
						....
2 Likes
9

Related Question …

Bracelet … same style/type (all start with the same blank) with different design stamped on top …

Variation or Collection?

2 Likes
10

Ok, now you have me confused.

@wadeorcas tagging because I respect you know alot about handmade.

These are not hadmade at all, so I can’t (and won’t) use handmade.

And I don’t think over in handmade would work. Trying to understand what you’re saying

2 Likes
11

Variation is my repsonse.

I’d then use either the “StyleName” or “PatterName” Theme.

Under “Home”, in reference to Parentage.

<xsd:element minOccurs="0" name="Parentage">
            <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                    <xsd:enumeration value="collection-parent"/>
                    <xsd:enumeration value="variation-parent"/>
                    <xsd:enumeration value="base-product"/>
                    <xsd:enumeration value="parent"/>
                    <xsd:enumeration value="child"/>
3 Likes
12

My comments apply to wherever. I believe “Home” is the primary here.

There are limits within the Templates when compared to being able to submit XML files through the SP-API backend.

3 Likes
13

Thank you for the complement. I am definitely not one to give flat file advice as most of what I have learned has been from your advice. Hope you get it figured out.

2 Likes
14

Nail, meet hammer.

That particular distinction, stretching back to the years before the MWS-API was haltingly eventually migrated to the SP-API, goes far to explain why your self-taught skills in manipulating XML schema to advantage remain in broad demand.

2 Likes
15

@wadecross… I remember in handmade that folks would talk about putting together options in one listing with sets of jewelry. And that’s what I was hoping you would remember.

For example, there’s a necklace that has a particular stone, with matching bracelot, dangle earings, stud earings, and ring. Those are actually different feed ID’s – or categories – yet based on the stone, they all match. So you put them together into one listing to catch the eye of the customer to all the matching options available. And/OR one choice could be “necklace and bracelot” together priced slightly less than if purchased separately. Remember how people would ask “necklace with 5 stone options” Or put the stone as the thing that makes them all match (necklace, ring, bracelot, earings)? In handmade, we could do that with the customization option.

2 Likes
16

Trying to understand…

Just downloaded my category listing report to see if the one item got corrected and YES, it did. So whew…

but back to what you’re trying to teach me.

This is what I see in the Category Listings report:

Screenshot (1308)
Screenshot (1308)907×248 19.4 KB

Those are my choices for the relationship type under tablerunner product feed ID.

And a few lines down for an item that’s a tablecloth:

Screenshot (1309)
Screenshot (1309)922×273 23.6 KB

I use XML templates provided by Amazon – and used to convert them to .csv files (and sometimes still have to?)

I do have I think 2 products left that are stuck in home for a product feed type ID – along with many others that are totally wrong (candle, tray, music).

SP-API?

3 Likes
17

All I can say is with Jewelry, this is possible with Handmade Products>Jewelry>Jewelry Sets in the “manual create a listing wizard”

2
21728×741 111 KB

I do it with variations thru the wizard. I have a ring band that I offer different set gemstones so I assume you could do similar with table linens. Just not sure about in flat file and I think you are referring to a marketside listings. It looks like Handmade categories are limited for your product anyway and I don’t have any advice for marketside listings. Not any help here. :man_shrugging:

2 Likes
18

The parallel example would be the gem stone offered in different items (necklace, ring, bracelot, earrings). Not the ring band with different gem stones. But since jewelry has “sets” … table linens does not have “sets” to lump them all together.

3 Likes
19

@Image am I remembering correctly that you use feeds, on your Handmade side? :thinking:

1 Like
20

@Papy, this isn’t really a handmade situation for what it’s worth. These are all marketplace items and not handmade.

3 Likes