How do I prepare product data, SKUs, and barcodes?

Last updated: May 20, 2026

Quick answer

Use this article to prepare the product, SKU, UPC, and barcode data that Logentic needs before warehouse work starts.

Common use cases

  • Product owner: Clean missing, duplicate, or inconsistent SKUs before launch.
  • Warehouse lead: Confirm barcode values can be scanned during receiving, picking, packing, or counts.
  • Operations manager: Create a product file that can be reviewed before Shopify or WMS sync work.

When to use this

  • You are preparing products before onboarding or go-live.
  • Shopify product exports contain missing SKUs, missing barcodes, duplicate identifiers, or variant confusion.
  • The warehouse will scan UPCs, barcodes, or SKU labels.

When not to use this

  • You are already troubleshooting one live SKU mismatch.
  • You need bundle, item box, or inventory calculation rules confirmed.
  • You need a final Shopify inventory sync decision.

At a glance

What you are doingWhat you needGood resultContact us if
Preparing product identifiers for Logentic.Shopify product export, SKU rules, barcode/UPC source, variant logic, and owner approval.Every sellable variant has a reviewed SKU and scan value before warehouse work depends on it.Duplicate products, missing UPCs, archived SKUs, bundles, or mismatched Shopify variants could affect live fulfillment or inventory.

Before you start

  • Keep the original Shopify product export unchanged.
  • Confirm whether existing SKUs should be preserved or cleaned.
  • Confirm whether UPC/barcode values already exist or need assignment.
  • Decide who approves SKU and barcode changes.
  • Use Logentic Tools when you need a controlled cleanup workflow before importing or syncing.

Steps

  1. Export the product catalog from Shopify or prepare the product CSV approved for onboarding.
  2. Review sellable variants for missing SKUs.
  3. Review sellable variants for missing UPCs, barcodes, or scan values.
  4. Check for duplicate SKUs, duplicate barcodes, archived SKUs, and variant naming issues.
  5. Use SKU & UPC in Logentic Tools if identifiers need cleanup before launch.
  6. Export the cleaned product file or product master when the product owner approves it.
  7. In Logentic WMS, review Product Dashboard or product search after products are loaded.
  8. Check a few sample products across Shopify and Logentic before warehouse work starts.
  9. Contact us before launch if product values affect inventory, receiving, picking, packing, or Shopify sync.

What good looks like

Each sellable Shopify variant has the right SKU and scan value, and your team knows which product file is approved for warehouse and Logentic setup.

Common issues and next actions

If this happensWhat to do next
A SKU is missing or duplicated.Decide whether to preserve, rebuild, or correct SKUs in Logentic Tools before launch.
A barcode does not scan.Check the product file value, leading zeroes, label size, scanner, and whether the value belongs to the correct variant.
Shopify and Logentic show different product details.Compare the product, variant, SKU, and barcode. Contact us with both screenshots if the difference affects launch.
A product is archived but orders still exist.Confirm whether the SKU should be active, replaced, or excluded before live fulfillment.

Contact us when

Contact us when product identifiers affect live inventory, Shopify sync, duplicate variants, bundles, unknown UPCs, archived SKUs, receiving, picking, packing, or go-live confidence.

Contact options

Send us this information

  • Shopify product or variant link.
  • SKU and barcode/UPC value.
  • Product export row or screenshot.
  • Logentic product screenshot.
  • Expected SKU/barcode.
  • Actual SKU/barcode shown.

Related workflow

  1. Prepare Shopify product data.
  2. Clean SKUs and barcodes in Logentic Tools if needed.
  3. Review products in Logentic WMS before launch.

Useful links