Listing on Amazon: attaching to what exists, creating what does not
Two completely different operations wear the same name. Sending the wrong one is most of why Amazon listing fails.
Half your catalogue will not list. The errors mention product IDs not matching brand records, or attributes you have never heard of, and none of them say what to actually change.
Amazon’s catalogue is shared. When you list, you are usually not creating a product — you are adding your offer to a product that already exists, created by someone else, possibly years ago. Occasionally you are genuinely creating something new.
These are different operations with different rules, and conflating them produces the great majority of confusing rejections.
Attaching: send less, not more
Adding your offer to an existing product means sending your price, your quantity and your condition. That is all.
The instinct is to send everything you know — the title, the description, the bullet points — on the reasonable theory that more data is better. It is not. Product attributes in an offer-only submission are rejected, because you are not the owner of that catalogue entry and Amazon will not let you rewrite it through the back door.
So an attach body carries no product attributes at all. It is a much smaller message than people expect, and shrinking it is often the entire fix.
Creating: send far more than feels reasonable
Creating a genuinely new product is the opposite problem. Amazon requires a schema of attributes specific to the product type, and it is not a short list — typically fifteen to twenty-five required fields, different for footwear than for kitchenware than for electronics.
There is no universal set. Each product type has to be satisfied on its own terms, and a submission missing one required attribute is rejected with a message about that attribute rather than about the twelve you got right.
The error that means something other than it says
The most misleading rejection in the set: “the product ID does not match the brand records”. It reads as a barcode problem, so people go and check their barcodes, and the barcodes are fine.
It usually means the brand is wrong — specifically, that the brand has been submitted as something generic. Amazon will not accept a real barcode attached to a placeholder brand. The fix is the brand field, and no amount of barcode checking will find it.
Barcodes are not always yours
A trap worth knowing before you rely on barcode matching. Some legitimate brands’ barcodes are already occupied on Amazon by other sellers’ listings — not fraud exactly, but a listing created against a code that was not theirs to use.
Match by barcode against one of those and your stock flows into a listing you do not control. For affected brands, barcode matching must be verified rather than trusted, which is the opposite of the usual advice and is correct here.
Suppression is separate from listing
A listing can be accepted and still not be shown. Footwear is the common case: a size submitted in the wrong format is accepted at upload and suppressed afterwards, so the listing exists, reports as active, and sells nothing.
Reading suppression is a different query from reading listing status, and a catalogue that looks fully listed can be substantially invisible. Check both.
What Qwikr does about all this
It sends the right shape of message for the operation, matches on barcode with verification rather than assumption, and snapshots the account before it is permitted to write anything. What it will not do is guess at required attributes to get a submission accepted — a product created with invented specifications is worse than one that failed to list, because it sells and then gets returned.
Stop reconciling stock by hand
One catalogue, six channels, one stock figure that stays right.