Guides · 1688 → Shopping

Do 1688 Products Need GTIN for Google Shopping?

Short answer: not always—but you must not invent barcodes. For many 1688-sourced private-label or unbranded offers, a compliant “no GTIN” path plus a real brand is safer than fake codes that look “fixed” in a report.

Why 1688 SKUs rarely have real GTINs

1688 listings are built for domestic wholesale. Many factories never assigned a global trade item number (UPC / EAN / GTIN) to each SKU. After import to Shopify, Google Shopping still asks about identifiers.

That gap is one reason 1688 → Merchant Center feels harder than branded Western catalogs.

What Google generally expects

Rules change and depend on category / country—always check current Merchant Center help. In practice for import sellers:

• If you have a real GTIN, use it.
• If you do not, say identifiers do not exist—and still provide a coherent brand.
• Do not paste random 12–13 digit numbers to silence warnings.

Should you “generate” GTIN for 1688 products?

No. Generated or borrowed barcodes create misrepresentation and account risk. Tools that auto-fill fake GTINs to make a checker green are solving the wrong problem.

AdFeed’s stance: never invent GTINs. Prefer a Google-ready no-ID path when you lack real codes.

What to do instead (Google-ready checklist)

1. Confirm the brand you sell under (not the factory name by default)— brand guide.
2. Keep titles and variants clean so offers are understandable.
3. Use compliant identifier handling when GTIN is missing.
4. Publish a synced Shopping feed URL—not a one-off patched XML.
5. If already disapproved, run the account vs feed diagnostic.

Google-ready vs Google-approved

Fixing identifiers helps readiness. It does not guarantee ads will be approved. Policy, landing pages, and account history still matter.