Managing thousands of SKUs across multiple platforms can be challenging. To make product mapping faster and easier, Synder allows you to bulk upload your product mappings using a CSV file. This guide walks you through the process.
What is Bulk Product Mapping?
Bulk product mapping allows you to match your integration products/SKUs (like from Amazon, Shopify, Stripe, etc.) with your accounting products (in QuickBooks Online, QuickBooks Desktop, or Xero) by uploading a CSV file. This feature saves you time by eliminating the need to map each product manually.
Typical Scenario
An ecommerce brand sells the same hoodie on Shopify and Amazon with different SKUs/names:
- Shopify: HD-BLK-M, “Hoodie – Black / M”
- Amazon: AMZ-HOOD-BLK-M, “Blk Hoodie M”
Goal: In the Per Transaction mode, book every sale to one accounting item “Hoodie Black M” so revenue, COGS, and inventory stay accurate.
What they do: Download the CSV template and map both Shopify and Amazon identifiers to a single accounting item. Upload once. From now on, any order line with those SKUs/names will be posted to “Hoodie Black M” in the ledger without any manual fixes, clean reports.
How to Prepare Your File
- Download the Template
- Go to Settings → Product mapping.
- Click Upload a CSV file and download the CSV template provided.
- Fill Out the Template
The file must include the following two columns:- Accounting product name: the product name exactly as it appears in your accounting platform (QuickBooks Online, QuickBooks Desktop, Xero).
- Integration product name/SKU: the product name or/and SKU as it appears in your integration.
- Important:
- You can use commas to separate multiple integration product names and/or SKUs if you want to map to the same accounting product.
- Only CSV (.csv) files are accepted.
- Ensure no special or unsupported characters are in the file.
- Save the file in a CSV format
Uploading Your Product Mapping File
- Navigate to Settings → Product mapping.
- Click upload a CSV file.
- Upload your completed CSV (max 10MB).
- Click Map products to start the import.
- You’ll see a notification confirming the import has started.
What Happens Next?
- Processing time: Large files take longer.
- API call limits: Synder fetches products from your accounting system first. Very large imports may hit API limits—if you see a temporary failure, retry later.
- Future syncs: New mappings apply to transactions synced after the product mapping import.
- Past data: Previously posted transactions remain unchanged. If you want the history corrected, re-sync the affected period after updating mappings (or contact support for options).
Tips & Best Practices
- Overwrite behavior: If a mapping exists with the same accounting product name, your upload will overwrite it.
- Many SKUs → one item: Use commas to map several integration SKUs/names to a single accounting item.
- Large catalogs: If needed, split very large catalogs into smaller files to avoid API limits.
- Auto-match vs file: If your names already match, Synder auto-matches; use a file only to override or fix mismatches.
Troubleshooting
- “Unknown accounting product” → Ensure the Accounting product name matches your ledger exactly (spelling/case/spacing).
- “Invalid file/columns” → Use the provided template and keep both required headers.
- “Rate limit/API error” → Wait a bit and retry; large catalogs can temporarily hit your accounting platform’s API limits.
- Duplicates in CSV → The last occurrence wins; keep one clean row per accounting product.
For more information about Synder features, visit our Help Center or reach out to Synder Team via online support chat or email.
