Home › Merge Guides › BigCommerce + Depop › QuickBooks Import walkthrough
The Best Way to Merge BigCommerce and Depop Data for QuickBooks Import
If you're doing quickbooks import by hand right now, here's the fastest path from "two exports" to "one usable sheet," and why the manual version keeps breaking.
Step by step
- Decide your target columns once. Most people settle on Date, Channel, Order ID, and Total — set that up in CSV Experts and you won't redo it.
- Import the BigCommerce file first. The first time you see this file shape, you map each of its columns to your target list.
- Import the Depop file the same way. Its columns get mapped once too — after that, every future file with this shape merges with no extra clicks.
- Check the merged totals. Dates and numbers are normalized automatically, so a European "24,00" and a US "24.00" both land as the same value.
- Export. CSV or Excel, ready for quickbooks import.
What actually goes wrong if you do this by hand
BigCommerce gives you an Order Date column that includes a full timestamp, while Depop gives you a transaction date column — line those up manually across a few hundred rows and it's easy to miscount a week. On top of that, BigCommerce's export many optional columns are exported blank depending on store configuration, which can throw off auto-mapping by header position, and Depop's like Poshmark, the export is minimal and mixes sold, refunded, and offer-related rows together. Individually those are minor quirks; combined into one spreadsheet by hand, they're where most reconciliation errors for quickbooks import actually come from.
Why it matters for quickbooks import
QuickBooks expects a consistent column layout for imported transactions — mismatched headers between channels usually mean manual cleanup before import.
Just want the quick column-difference reference instead? See the short version.