Importing and exporting provide a fast, reliable way to set up and manage product data across the app. The workflow supports bulk creation and updates using standardized templates, processes in the background with email status notifications, and maintains alignment across sales channels through consistent identifiers and publishing settings.
Retailers, brands, and fulfillment partners benefit from fewer manual edits, faster catalog changes, and reduced error rates.
Common use cases:
Bulk management to create or update many products at once
Data migration from other systems or new integrations
Backup and recovery with downloadable CSVs
Bulk updates without editing each product
Template-based setup for consistent formatting
Exporting Products
Use export to back up data or prepare a working file for bulk updates.
What you can export
Products: All products or a filtered subset; choose which properties to include
Bundled products: Parent bundles, component SKUs, and component quantities
Product channel options: Channel-specific SKUs and IDs, inventory buffers, and sync status
How to export
Go to Products.
(Optional) Apply filters to narrow the catalog you want to export.
-
Select Export, then choose one:
Export Products
Export Bundled Products
Export Product Channel Options
Select the properties (rows and columns) to include.
Enter the email address for delivery.
Check your email for the CSV file.
Tips
Use the exported CSV as a starting template for updates.
Channel options export is helpful to audit publishing, IDs, and buffers across sales channels.
Importing Products
Use import to create products in bulk or update existing ones.
Templates you can download
Products template: All accepted columns with example data; required fields are SKU and Name. See the Pipe17 API Product model for field descriptions.
Bundled products template: Define bundle SKUs, component SKUs, and quantities.
Product channel options template: Set channel-specific SKUs and IDs, inventory buffers, and publishing preferences.
How to import
Go to Products and select Import CSV.
Download the appropriate template (Products, Bundled products, or Product channel options).
-
Prepare your CSV:
New products require SKU and Name.
For updates, include SKU and only the columns you want to change.
Use lowercase for keyword values unless specified otherwise (for example,
bundleItemuses a capital I).-
Row and field controls:
Skip an entire row: put
//at the beginning of the SKU cell.Keep an existing value: leave the cell empty.
Set a value to blank: enter
//as the cell value.
Upload your CSV file.
-
Choose duplicate handling (radio buttons):
Overwrite existing products: update matching SKUs with the values in your file. Blank cells leave existing values unchanged;
//clears a value.Skip and don’t overwrite existing products: create new SKUs only; rows with existing SKUs are ignored.
Review the preview and resolve any issues.
Add recipient email addresses for the status notification.
Select Import. The job runs in the background and a results email is sent when it’s complete.
Blank columns are ignored during import; existing data is preserved.
Large imports process in the background so you can keep working.
Best Practices
Export first to get a clean, app-formatted starting file.
Validate formatting before upload to avoid errors (column names, data types, lowercase keywords).
Limit scope by filtering before export so your working file stays manageable.
Use the right template for the job (Products, Bundled, or Channel options).
Keep a backup of your latest export before making broad changes.
Troubleshooting
“Some products didn’t import.”
Confirm your CSV follows the downloaded template exactly.
Make sure each new product row includes SKU and Name.
Recheck keyword values are lowercase where required.
“Bundle relationships didn’t appear.”
Use the Bundled products template.
Verify parent bundle SKU, component SKUs, and quantities are present and correct.
Ensure the special value
bundleItemuses a capital I when required.
“Fields didn’t change after import.”
For updates, include SKU and the columns you want to change.
Remember: blank columns are ignored. To clear a value, enter
//.
“Duplicate SKU errors or unexpected overwrites.”
Review your duplicate handling choice (Overwrite vs Skip).
If testing, try a small sample file first.
“Channel data looks wrong across marketplaces.”
Use the Product channel options export to audit SKUs, external IDs, buffers, and sync status.
Update with the Product channel options template to correct mappings in bulk.
Need Help?
If you need additional assistance:
Use Ask Pippen, our AI agent, located at the top of the app page.
Submit a support request with as much relevant detail as possible. Learn how to submit a request.
For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments