SKU and Barcode Now Both Required in Product Imports
📦 What’s changed?
To improve data consistency across our platform, both SKU and barcode are now required for all imports involving products — regardless of which field is used as your unique identifier.
This includes:
- Product imports
- Bundle imports
- Receiving reports
🔁 Products with serial numbers imported are the only exception — they still require SKU only.
✅ Why this change?
Even if your account is configured to use barcode as the identifier (or vice versa), both fields are used behind the scenes across integrations, warehouse processes, and reporting. This update ensures clean, reliable data for fulfillment, inventory, and syncing.
🧪 Validation rules
Product SKU | Product Barcode | Result |
sku123 | (empty) | ❌ Invalid – barcode required |
(empty) | 123456789012 | ❌ Invalid – SKU required |
sku123 | 123456789012 | ✅ Valid – both fields present |
📥 What should you do?
- Make sure all product-related import files now include both SKU and barcode
- Use the latest import templates — if you’re unsure, contact our team.
If you have questions or need help updating your templates, reach out to your onboarding manager or open a support ticket through the app.