Import EAN UPC Barcodes DocumentationImport EAN UPC Barcodes Documentation
Buy Now
View Demo
  • Getting Started

    • Overview
    • Features
    • Installation
  • Setup & Configuration

    • General Settings
    • Destination Fields
  • Importing Barcodes

    • Preparing the CSV File
    • Sequential Pool
    • Importing Codes
    • Managing the Pool
  • Assigning Barcodes

    • Auto-Assignment
    • Bulk Assignment
  • Help & FAQ

    • FAQ & Troubleshooting
Buy Now
View Demo
  • Getting Started

    • Overview
    • Features
    • Installation
  • Setup & Configuration

    • General Settings
    • Destination Fields
  • Importing Barcodes

    • Preparing the CSV File
    • Sequential Pool
    • Importing Codes
    • Managing the Pool
  • Assigning Barcodes

    • Auto-Assignment
    • Bulk Assignment
  • Help & FAQ

    • FAQ & Troubleshooting
  • Getting Started

    • Overview
    • Features
    • Installation
  • Setup & Configuration

    • General Settings
    • Destination Fields
  • Importing Barcodes

    • Preparing the CSV File
    • Sequential Pool Deep Dive
    • Importing Codes
    • Managing the Pool
  • Assigning Barcodes

    • Auto-Assignment
    • Bulk Assignment
  • Help & FAQ

    • FAQ & Troubleshooting

Destination Fields

One of the most powerful features of the Import EAN UPC Barcodes plugin is its flexibility. It doesn't lock you into a single way of storing barcodes. Instead, you can choose exactly which database field the barcode is saved into, ensuring compatibility with your specific theme, POS system, or inventory management plugin.

You can configure this on the New Products & Settings tab under the Destination Field dropdown.

Available Destination Integrations

The plugin natively supports writing to the following fields:

WooCommerce Core

  • WooCommerce Barcode (Global GTIN): This is the default and recommended option. It writes to WooCommerce's native _global_unique_id meta key. Using this field ensures that WooCommerce's built-in digit validation and duplicate checks apply. This field is visible on the product's Inventory tab (and on each variation) and is automatically used by WooCommerce core for structured data and schema markup.
  • WooCommerce SKU: Writes the barcode directly into the standard WooCommerce SKU field.

Third-Party Plugins

If you use specialized inventory or Point-of-Sale (POS) plugins, you can map the barcodes directly to their required fields:

  • EAN for WooCommerce: Writes to _alg_ean
  • Product GTIN: Writes to _wpm_gtin_code
  • WooCommerce UPC, EAN, and ISBN: Writes to hwp_product_gtin
  • Germanized: Writes to GTIN (_ts_gtin) or MPN (_ts_mpn)
  • wePOS: Writes to _wepos_barcode
  • PayPal Zettle POS: Writes to _izettle_barcode
  • ATUM Inventory: Writes to Supplier SKU (_supplier_sku) or ATUM Barcode (_atum_barcode)

Custom Meta Keys

  • Any Custom Meta Key: If your theme or another plugin uses a proprietary field to store barcodes, you can select this option and type in the exact meta key string. The plugin will write the generated or imported barcodes directly into that custom meta key.

[!TIP] Developer Hook The entire destination map is filterable via the imp_ean_destination_fields hook. Developers can easily add custom integrations to the dropdown menu by hooking into this filter in their theme's functions.php file.

Prev
General Settings