The SKU [ 2V-D363-5ORY] is a variation Parent in one or more marketplaces and a variation Child in another marketplace(s). A SKU needs to have the same Parentage in all marketplaces. Please resubmit the SKU with the correct ‘Parentage’ to ensure it is consistent across all marketplaces.
This is the parent sku that’s been since this product variation group has existed. Not sure how to fix since international listings were auto-generated, but maybe create an entirely new parent?
my issue is that the listings on international markets of F’d, where the parent is it’s own non-functional listing and all the children are flying solo. Was automated that way. so i’m thinking a new parent sku might be the fix, but never sure if I lose anything when jumping to brand new parents.
If set up correctly, a parent should never be able to become a child … so a big on that. the only time I’ve seen it is when a parent was set up wrong to start.
Anyway as to …
I would say yes, and when you do use only the very basic required data. No pricing, quantity or offer listing type data.
Also, there’s nothing to lose by creating a new parent. Reviews are locked to the children.
It happened when I agreed to be listed in other marketplaces. Instead of carrying over the structures, they brought them over piecemeal, breaking everything up into a parentless listing with a parent with no purpose.
I noticed but didn’t think it was a big issue at the time.
do another flat file, give the parent a unique sku, refer to that sku in the children, and have pretty much no other information (save for gtin and such)
And have them all Partial Update except I guess the parent?
minor follow up: and would tha tupdate international market too?
got greedy and tried to have the new parent and the children calling to the new parent in the same spreadsheet. got the same wild error that the new parent was both a child and parent in other markets.
So changed the sku again, submitted the parent independently, waited, then did partial update on the 3 children calling to the new parent sku.
I’ve noticed that my multimarketplace file is not properly updating pages properly even when set to UPDATE. I tried uploading this file to different marketplaces but got the following alert:
“You have uploaded your multi-marketplace inventory file in a different region than the one you downloaded it from. Please make sure that your marketplace selection is correct and if it is, download a new file for this marketplace.”
So am I going to need to have a flat file for every product for every region?
Didn’t create. It rejected the first row (the new parent) and took the partial updates from the children.
I cut the parent row, put into a new excel, gave it yet another sku, and added no problem.
This was the processing error:
The SKU [ wooflinen-leash-parent] is a variation Parent in one or more marketplaces and a variation Child in another marketplace(s). A SKU needs to have the same Parentage in all marketplaces. Please resubmit the SKU with the correct ‘Parentage’ to ensure it is consistent across all marketplaces. You can read more about Parent/Child relationships at: Amazon
That sku never existed before in its life.
Then the children got the error that the Parent sku doesn’t exist, since the first row was rejected for already existing. which made sense.
I’ve always preferred using Marketplace Specific templates in the past … In fact, I’ve never used anything else.
Ahh, I was always using the US +3 but it seems worthless in its ability to update listings properly other than the US.
I guess my day today is going to be the whole CTRL+C CTRL+V day.