On this page
Before you start
e-tailize runs this check itself before an offer push to a Mirakl storefront and on the Stockhub warehouse flow. On the other channels the marketplace decides, and bol reports an invalid EAN back in its own upload report. Two rules have to hold.
The EAN is digits only, and it is 8, 12, 13 or 14 digits long. A letter, a space or a length of 11 fails.
The check digit adds up. e-tailize pads the number to 14 digits and runs the GS1 calculation over it, weighting the digits alternately by three and by one. The total has to be a multiple of ten.
Where e-tailize runs the check, an EAN that fails one of the two is not a marketplace turning you down. Your push never left e-tailize.
Steps
- Open the listing page and read the table of the failed push. Its columns "Ean", "Message", "Name" and "Value" tie every message to one product.
- Copy the number from the "Ean" column and look that product up on your products page.
- Open the product and go to the "Main product" tab. The "Ean" field can only be edited there, on a marketplace tab it is greyed out.
- Compare the number with the barcode on the product or with what your supplier sent. Count the digits first, then check the last one.
- Type the correct number in "Ean", click "Save product" and then "Save & close".
- Validate the product again.
- Run "List content", and then "List offers".
What happens next
With a number that passes, the product joins the push again and the marketplace takes over. It checks the barcode against the official register on its own side, so a number that gets through here can still come back refused there.
Common problems
"Invalid product id. Please make sure to supply a valid EAN."
This comes back from an offer push to a Mirakl storefront, and it is our check, not theirs. It runs over the whole batch before the first call goes out, so one bad EAN holds up every offer in that push.
"Missing GTIN/EAN."
The product has no EAN at all, and the "Name" column says "gtin". Fill the "Ean" field on the "Main product" tab. The same push reports "Missing sellerExternalReference (Sku/Reference)." for a product where neither the "SKU" nor a reference is filled.
"Reference or EAN is required."
Allegro validation on the field "Reference": the product arrives with neither. Often the EAN does exist on the product and is only not mapped for that tab, so check the mapping before you go looking for the number.
Part of your range never reaches Stockhub
The Stockhub connection reads the barcodes of a product and takes the first one that passes the check. Is there none, the product carries no EAN into that flow and stays behind, while the rest syncs normally.
The products came in from Shopify
Shopify has no EAN field. e-tailize reads the EAN from the barcode field in Shopify, so a barcode that is wrong there becomes a product with an EAN that does not pass here. A product with an empty barcode is skipped at import. See My Shopify import brings in nothing or only half my range.
FAQ
Why is my 11 digit number refused?
Because the check accepts 8, 12, 13 or 14 digits and nothing in between. A shorter code, such as an article number of your own, is not an EAN however well it works in your own system.
Does a valid EAN mean the marketplace accepts the product?
No. e-tailize checks the shape and the check digit, nothing more. Whether the number is registered to you is something each marketplace checks for itself.
I corrected one EAN and the push still fails
Usually another product in the same batch fails too. The table lists every one of them, so work through the whole list before you push again. Does every EAN in the table check out and the push keeps failing, then it is not your data. Ask our support team, with the EAN and the exact message from the table, so we can look at the push itself.
Related
Was this useful?