If you sell with PrestaShop and you need to know where and how to add EAN codes to your products, this guide has you covered. You'll see where the EAN-13 field lives in each version of the back office, how to assign it at product and combination level, how to bulk-import it via CSV and how to export it to Google Shopping and marketplaces. And if you don't have the codes yet, we'll show you how to get official GS1 EAN codes in minutes.
In short
- The EAN-13 field is on the product page: in PrestaShop 1.7, 8.x and 9 you'll find it in the Quantities tab (or Combinations if the product has variants); in PrestaShop 1.6 it's in the Information tab.
- You don't need any paid module: support for EAN-13, UPC, ISBN and MPN barcodes is built into the PrestaShop core.
- Each combination has its own EAN-13: size M and size L of the same t-shirt need different codes, just like each simple product.
- For many products, import via CSV from Catalog > Import, mapping your column to the EAN13 field and formatting the codes as text to avoid Excel's scientific notation.
- The EAN is exported as GTIN to Google Shopping and marketplaces (Amazon, eBay, Carrefour); without a valid GTIN many products are rejected or penalised.
- Use official GS1 EAN codes: made-up ones fail on the check digit and recycled ones cause ownership problems. At EAN CODA you get them with a one-time payment, no annual fees, from €3.
PrestaShop is one of the most widely used open-source e-commerce platforms in Spain and Europe, and it includes native support for barcodes. That means you don't need any paid module to assign your EAN codes: the field comes built into every product page. If you'd first like a refresher on what an EAN is, there's a full explanation in what an EAN barcode is.
Buy my EAN codes — official GS1, from €3, one-time payment and no annual fees. You receive them by email in minutes, ready to paste into PrestaShop.
EAN-13, GTIN and the PrestaShop fields: what each one is
Before touching the back office it's worth clearing up the terminology, because PrestaShop handles several similar fields and they're easy to mix up:
| Field in PrestaShop | What it is | Format |
|---|---|---|
| EAN-13 (or JAN) | The standard barcode in Europe. It's the GTIN-13. | 13 digits |
| UPC | The standard barcode in North America. | 12 digits |
| Reference | Your internal code (SKU). You define it yourself; it's not a barcode. | Free |
| MPN | Manufacturer Part Number. Useful in some feeds, but it doesn't replace the EAN. | Free |
| ISBN | An identifier specific to books. | 13 digits |
The key point: GTIN is the generic term that covers both EAN and UPC. An EAN-13 is a GTIN-13 and a UPC-A is a GTIN-12. When a feed or a marketplace asks you for the "GTIN", it means your EAN-13. The reference is your internal SKU and should never go in the EAN field. It's worth knowing that the MPN field (Manufacturer Part Number) was added in PrestaShop 1.7.7; in earlier versions it didn't exist, which is why in older feeds you'll see that only EAN-13 and UPC were exported. If you get confused between the EAN-13 and the short 8-digit version, we explain the difference between EAN-13 and EAN-8 in another guide.
Where to enter the EAN in PrestaShop (step by step)
The exact location of the field has changed between versions, so be careful if you're following an old tutorial. In every version the path starts at Catalog > Products; what changes is the tab inside the page.
PrestaShop 1.7, 8.x and 9 (at product level)
- Log in to the back office and go to Catalog > Products.
- Open the page of the product you want to edit.
- For a simple product (no variants), open the Quantities tab. There, below the stock management, you'll find the identifiers block with the Reference, ISBN, EAN-13, UPC and, since 1.7.7, MPN fields.
- Enter your 13-digit code in the EAN-13 or JAN field. Right next to it you'll see the UPC field in case you also sell in North America.
- Save the changes.
Version note: in PrestaShop 1.7.0 to 1.7.6 these identifiers were inside the Details tab. From 1.7.7 onwards and in all 8.x and 9.x versions they were reorganised and live in the Quantities tab. The logic and the code format are identical; only the tab name changes.
PrestaShop 1.7, 8.x and 9 (at combination or variant level)
If the product has combinations (sizes, colours, formats), the EAN doesn't go in the general field but in each combination:
- On the product page, enable combination mode and open the Combinations tab.
- Expand the specific combination (for example, "T-shirt - Size M - Blue").
- Inside that combination you'll see its own Reference, EAN-13, UPC and ISBN fields. Enter the EAN-13 that corresponds to that variant.
- Repeat with each combination and save.
Remember that each combination has its own EAN-13: size M and size L of the same t-shirt are different products for a scanner and for a marketplace, so they need different codes. If a product has combinations, the combination's EAN takes priority over the product's general field when exporting the feed. A screenshot of the back office for your specific version will help you locate the field if you get lost among the tabs.
PrestaShop 1.6
In older versions the EAN-13 field is on the product page, inside the Information tab (or in the Combinations tab if you use variants, where each combination has its own EAN-13 field). The logic is the same; only the visual location of the field changes. The menu path is still Catalog > Products, as in the modern versions.
How to bulk-import EAN codes via CSV
If you have dozens or hundreds of products, entering EAN codes one by one is unworkable. PrestaShop allows bulk importing:
- Go to Catalog > Import (in some versions, inside Advanced Parameters or Products).
- Select the entity type Products (or Combinations if you're going to assign EAN codes to variants).
- Upload your CSV file. You need an identifying column (for example the reference or the product ID) and a column with the EAN-13.
- In the mapping step, match your codes column to PrestaShop's EAN13 field.
- Tick the option "Update existing products" and, in many versions, indicate that matching should be done by reference or by ID, if you only want to add the EAN without recreating the pages. Then launch the import.
Tip: do a test first with just a few rows. If the CSV uses the wrong separator (PrestaShop usually expects a semicolon) or the EAN comes through in scientific notation from Excel (the classic 8.41E+12), it will import incorrectly. Format the EAN column as text before exporting and, if you can, save the file in UTF-8 to avoid problems with accents in other fields.
What a valid EAN-13 looks like (with an example)
An EAN-13 is not just any sequence of 13 digits: it has a structure. Take an example of the form 84xxxxxxxxxx C, where the first digits are the GS1 prefix, the central block identifies the product and the last figure is the check digit.
- Prefix (the first digits): assigned by GS1. The 84x range corresponds to codes registered from Spain. That prefix sits inside the EAN-13; there is no separate format called "EAN-84", and the prefix only indicates where the code was registered, not where the product is made or sold.
- Product block: uniquely identifies your item.
- Check digit (the last figure): it's calculated mathematically from the previous 12 digits. It's what lets a scanner or a feed instantly detect whether the code has been mistyped or made up.
That's why an EAN has to be well formed: if you make it up, the check digit most likely won't add up and any validator will reject it. And even if it happened to add up by chance, you'd be using a number that belongs to another company.
How to export the EAN to Google Shopping and marketplaces from PrestaShop
Once the EAN is on the product page, the next step is getting it to your sales channels. PrestaShop doesn't generate the Google Shopping feed on its own: you need a feed module that reads the EAN-13 field and outputs it as the GTIN attribute.
- Google Shopping: install an export module (the official "Google & YouTube Shopping", PS Facebook/Google, or third-party modules like Doofinder, Beezup or ShoppingFeed). In the feed settings, map PrestaShop's EAN-13 field to Google's gtin attribute. If you sell branded products, also fill in brand and, where applicable, mpn: Google requires at least two of the three identifiers. The feed is published as XML or connected via API to Merchant Center.
- Marketplaces: when syncing with Amazon, eBay or Carrefour through their module or a connector (such as Lengow, ShoppingFeed or the marketplace's native connector), the GTIN is used to create the listing or match it to a product already in the catalogue. On Amazon the EAN-13 goes in the product ID field with type "EAN". You'll find the details in our guides on barcodes for Amazon and barcode for eBay.
- Check the mapping: before uploading your whole catalogue, export a few references and verify in the XML or in the connector that the GTIN comes out filled in and with 13 digits. It's the most common silent error: the EAN is on the product page but the feed doesn't map it. It's key for your barcode for Google Shopping: without a valid GTIN, many products are rejected in Merchant Center with warnings like "Invalid GTIN" or "Incorrect product identifiers".
What the EAN is for in PrestaShop
- Feeds and comparison sites: export modules use the EAN to identify each product and avoid duplicates across channels.
- Marketplaces: the GTIN matches your product to the Amazon, eBay or Carrefour catalogue, or creates a new listing if it doesn't exist.
- Inventory and POS: with a real EAN you can manage stock with barcode scanners and connect your PrestaShop to a physical point of sale.
Common mistakes (and how to avoid them)
- Making up the number: as we saw, the check digit gives away invented codes and the feed rejects them instantly.
- Repeating the same EAN on several products: every reference and every combination needs a unique code. Duplicates cause "GTIN already in use" errors or products merged by mistake.
- Confusing reference with EAN: your internal SKU goes in the Reference field, not in EAN-13. The MPN and the ISBN don't replace the EAN either.
- Putting the EAN only on the product and not on the combinations: if you use variants, the product's general field is ignored in the feed and you export combinations without a GTIN. Fill in every combination.
- EAN in scientific notation: when importing from Excel, a code like 8.41E+12 comes in truncated. Format the column as text.
- Not mapping the field in the feed module: having the EAN on the product page isn't enough; you have to map it to the export module's gtin attribute.
- Unofficial codes: "recycled" EAN packs or codes of dubious origin end up causing ownership problems on the stricter marketplaces. Use legitimate GS1 codes.
Buy my EAN codes — official GS1, one-time payment, no annual fees and delivery in minutes.
Do you use more than one platform?
The same EAN-13 works in any system: it's a global identifier, not tied to PrestaShop. If you also run another store, if you use Shopify, check out this guide to place the codes on that platform. A single EAN per product works at the same time in PrestaShop, in your feeds and on every marketplace.
Frequently asked questions
Where exactly is the EAN-13 field in PrestaShop 8?
In PrestaShop 8 (and also from 1.7.7 onwards and in 9) the EAN-13 field is on the product page, inside the Quantities tab, in the identifiers block next to Reference, ISBN, UPC and MPN. If the product has combinations, each variant's EAN-13 is entered in the Combinations tab, inside each combination.
Is the EAN mandatory in PrestaShop?
PrestaShop doesn't force you to fill in the field to save the product, so technically it's optional. But in practice it's essential: the moment you export to Google Shopping or any marketplace, the EAN (GTIN) stops being optional and products without one are rejected or penalised.
Can I make up an EAN?
No. Even if you enter 13 random digits, the check digit will almost never add up and the code will be invalid. And even if it did add up, you'd be using a number that belongs to another company, which causes conflicts on marketplaces. You need legitimately assigned codes.
Do I need an EAN for each combination or size?
Yes. Each variant (size, colour, format) is a different product for a scanner and for a marketplace, so it needs its own EAN-13. A t-shirt in sizes S, M and L requires three different codes, and each one is entered in its combination inside the Combinations tab.
How do you export the EAN-13 to Google Shopping from PrestaShop?
You need a feed module (the official Google & YouTube Shopping one or a third-party one). In its settings, map PrestaShop's EAN-13 field to Google's gtin attribute and also fill in the brand. The module generates the XML or connects via API to Merchant Center; verify that the GTIN comes out filled in before uploading your whole catalogue.
Does the same EAN work for Amazon and for PrestaShop?
Yes. The EAN-13 identifies the product, not the platform. The same code you enter in the EAN-13 field in PrestaShop is the one you'll use on Amazon, eBay, Google Shopping or your physical POS.
How do I import many EAN codes at once in PrestaShop?
From Catalog > Import, choosing the Products or Combinations entity, uploading a CSV with an identifying column and an EAN column, and mapping the latter to the EAN13 field. Tick "Update existing products" so you don't recreate the pages, and format the EAN codes as text to avoid Excel's scientific notation.
Where do I get official EAN codes without paying annual fees?
With EAN CODA. We assign you official EAN codes from the GS1 database with a one-time payment, no renewals or annual fees, and we deliver them by email in minutes, ready to paste into the EAN-13 fields in PrestaShop.
Get your EAN codes for PrestaShop
With EAN CODA you get official GS1 EAN codes from €3, one-time payment and no annual fees, ready to paste into the EAN-13 fields of your PrestaShop and importable via CSV if you have many products. We're a reseller of legitimate GS1 codes: a faster and cheaper alternative to registering on your own, and you get them in minutes.