Marketplaces reject listings that don't carry a valid, unique product identifier. Amazon wants a GTIN or an approved GTIN-exemption; eBay, Google Shopping, Walmart and Noon each enforce their own GTIN/UPC/EAN rules; and the same physical product often needs a different SKU or channel-specific ID on every store. In stock Odoo, product.template/product.product give you a single barcode field and a default_code (internal reference) — one slot for one code. There is no place to hold a UPC and an EAN and an ASIN and an ISBN at once, no check-digit validation, no cross-product uniqueness guard, and no way to say "this SKU is what we list on eBay, that ASIN is what Amazon assigned." Catalog managers end up tracking all of this in spreadsheets, and a single transposed digit becomes a suppressed listing.

We build a dedicated identifier layer on top of your product catalog. The core is a gs1.identifier model (a models.Model linked by Many2one to product.product) that stores each identifier as its own typed row — GTIN-8/12/13/14, UPC-A, EAN-13, ISBN, ASIN, MPN and free-form channel IDs — with a type selection field and a value char. A @api.constrains hook runs GS1 check-digit validation (the modulo-10 algorithm) on GTIN/UPC/EAN/ISBN values and rejects a bad digit at save time, and a SQL unique constraint plus a @api.constrains uniqueness scan stops the same GTIN being attached to two different products. A second marketplace.sku model maps each product to a (marketplace, sku, external_id) tuple so Amazon ASINs, eBay item IDs and per-channel SKUs live in structured rows, not notes.

On top of the data model we build the working surfaces: a notebook page on the product form (XML/OWL views) listing all identifiers and marketplace mappings inline; a Boolean GTIN-exemption flag with a brand-registry note field for products legitimately sold without a GTIN; ir.model.access.csv rules plus record rules so catalog editors can maintain identifiers while read-only roles only view them; and bulk import/export via a mapped Odoo Import template and an optional QWeb/XLSX export for channel feeds. Because everything is real Odoo data, your existing integrations reach it over standard XML-RPC/JSON-RPC — an Amazon or Google feed job can read search_read on gs1.identifier and marketplace.sku with no scraping. The module targets Odoo 17.0, 18.0 and 19.0 and works on Community and Enterprise (identifiers are core-model extensions, so no Enterprise-only dependency).

This is build-to-order: ECOSIRE develops, installs and supports the module for your specific catalog and channel mix — it is not an existing apps.odoo.com download. We start with a short scoping call to confirm which identifier types and marketplaces you sell on, your uniqueness and exemption rules, and how your feeds consume the data. Typical delivery is one working week from confirmed scope, delivered as installable source you own, validated on a staging database against your real catalog before go-live.