Overview

Sellers who rely on automated XML feed uploads may encounter Amazon’s Error 5005, an authentication failure that stops the feed from being processed. The error appears when the merchant identifier embedded in the XML file does not match the login credentials supplied in the HTTP request header. Fixing the mismatch is critical because a rejected feed halts catalog, inventory, or pricing updates, directly affecting a seller’s ability to stay competitive on the marketplace.

Key Points

• Authentication mismatch — The error is triggered when the merchant token in the XML header differs from the username/password used in the HTTP header.
• Token format — Merchant identifiers follow a pattern such as M_ACMEINC_012345 and are unique to each seller account.
• Credential consistency — The HTTP header must carry the exact Seller Central login (email/username and password) that the account owner uses to sign in.
• Automatic token generation — Amazon creates the merchant token when the seller account is first registered; it cannot be edited manually.
• Common trigger — Managing several Amazon accounts or using outdated integration settings often leads to the token‑credential mismatch.

How Error 5005 Occurs

1. XML payload includes merchant token — The feed’s XML header contains a <MerchantIdentifier> element, for example <MerchantIdentifier>M_MYSHOP_987654</MerchantIdentifier>.
2. HTTP request carries login credentials — The same submission sends an HTTP header with Authorization: Basic <base64‑encoded‑username:password>, where the username is the seller’s login email.
3. Amazon validates both values — Amazon’s gateway checks that the token in step 1 belongs to the account identified by the credentials in step 2. If the token belongs to a different account or is mistyped, the system returns Error 5005 and rejects the feed.

Context: Before vs. After