Process: Creating New SKUs in Shopify for Accurate Packiyo Sync
Purpose
This document defines the required steps for creating new products/SKUs in Shopify so that they sync correctly into Packiyo (WMS) on the first pull — with no manual re-linking or data cleanup required afterward.
Why This Matters (Root Cause)
Packiyo pulls in product data from Shopify at the time a product is first synced. If a product is created in Shopify without a SKU and/or barcode, and Packiyo pulls that product in that state, Packiyo creates its own product/variant record based on what it received — usually blank or auto-generated SKU fields.
The critical issue: if a SKU or barcode is added to the product in Shopify after that first pull, Packiyo does not automatically update or reconcile the existing record. The two systems fall out of sync — Shopify shows the correct SKU/barcode, but Packiyo still has the old (blank or incorrect) values tied to that variant. This leads to fulfillment errors, mis-picks, and inventory mismatches.
The fix: SKU and barcode must be entered correctly in Shopify before the product is available to be pulled into Packiyo — never added retroactively.
Roles & Responsibilities
Brand / Product Team Creates the product in Shopify, enters SKU + barcode for every variant before publishing
Ops / Integration Owner Confirms sync timing, monitors for any products pulled without SKU/barcode
Warehouse / Packiyo Admin Verifies incoming product data matches Shopify before enabling fulfillment
Step-by-Step: Creating a New Product/SKU in Shopify
1. Draft the product — do not publish yet
Create the product in Shopify as a Draft (not Active).
This prevents it from being picked up by any sync/import process while it's incomplete.
2. Build out all variants
Add every variant (size, color, etc.) the product will have.
Do not leave placeholder variants to "fill in later."
3. Enter SKU for every variant
Use your standard SKU naming convention (brand prefix + product code + variant code).
Every single variant must have a unique SKU — no blanks, no duplicates across products.
4. Enter Barcode for every variant
Enter the UPC/EAN/GTIN in the Barcode (ISBN, UPC, GTIN, etc.) field on each variant.
Confirm the barcode is the correct format/length for your standard (e.g., 12-digit UPC-A).
Do not use the SKU as a placeholder barcode — leave it blank rather than fake data if the real barcode isn't available yet (see "What If Barcode Isn't Available Yet" below).
5. Fill in remaining required fields
Weight/dimensions (used for shipping calculations in Packiyo)
Cost/price fields as needed for your reporting
6. QA the product before publishing
Run through the Pre-Sync QA Checklist below. Do not proceed to Step 7 until every item passes.
7. Publish / Activate the product
Only once SKU + barcode + all required fields are confirmed correct, set the product to Active.
This is the point at which the product becomes eligible for Packiyo to pull.
8. Confirm the Packiyo pull
After sync, check Packiyo to confirm the product/variant(s) appear with matching SKU and barcode.
Spot-check at least one unit's barcode by scanning it against the Packiyo record, if possible.
Pre-Sync QA Checklist
Before moving a product out of Draft status, confirm:
[ ] Every variant has a SKU entered
[ ] Every variant has a barcode entered
[ ] SKUs follow the standard naming convention and are not duplicated
[ ] Barcodes are valid format/length and not duplicated across products
[ ] No variant is missing weight/dimensions if required for fulfillment
[ ] Inventory tracking is correctly configured
[ ] Product has been reviewed by a second person (Ops or QA) before publishing
Rule of thumb: if it's not in Shopify correctly, it will not be correct in Packiyo. Fix it in Shopify first, always, before it syncs — not after.
What If the Barcode Isn't Available Yet?
Sometimes a barcode (e.g., UPC from a supplier) genuinely isn't available at product creation time. In that case:
Keep the product in Draft until the barcode is available. Do not publish/sync without it.
If the product must go live before the barcode is ready (rare, time-sensitive exception only):
Flag it to the Ops/Integration Owner explicitly.
Do NOT rely on adding the barcode in Shopify later and expecting it to sync — it won't update Packiyo automatically.
Instead, once the barcode is available, it must be manually updated directly in Packiyo as well as in Shopify, by whoever manages the Packiyo product records.
If a Product Was Already Pulled Without SKU/Barcode (Cleanup Procedure)
If you discover a product already went through this exact failure mode (created without SKU/barcode, pulled into Packiyo, then updated after the fact in Shopify only):
Identify the product/variant(s) affected in both Shopify and Packiyo.
Confirm the correct SKU and barcode values in Shopify (source of truth).
Manually update the corresponding product/variant record directly in Packiyo to match — this will not resolve itself via another sync.
Verify inventory counts still tie out correctly after the manual update (a mismatched SKU can sometimes cause split or duplicate inventory records).
Log the correction (product name, what was wrong, what was fixed) so there's a record of manual interventions.
Ongoing Governance
This process should apply to every brand/team creating products that flow into Packiyo, not just the one that had the issue.
Consider adding a hard gate: products cannot be set to Active in Shopify without SKU + barcode filled in (Shopify does not enforce this natively, so this is a process/training control, not a system control, unless a validation app is added).
Periodically audit newly created products against Packiyo to catch any that slipped through without SKU/barcode before the first pull.
Quick Reference (Print/Post for Product Teams)
Before you publish any new product in Shopify:
SKU on every variant ✅
Barcode on every variant ✅
QA checked by a second person ✅
Only then → set to Active
Never: publish first and add SKU/barcode later. Packiyo will not catch up on its own.