Home › Merge Guides › WooCommerce + BigCommerce › Cost of Goods Sold Tracking walkthrough
The Best Way to Merge WooCommerce and BigCommerce Data for Cost of Goods Sold Tracking
If you're doing cost of goods sold tracking 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 WooCommerce file first. The first time you see this file shape, you map each of its columns to your target list.
- Import the BigCommerce 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 cost of goods sold tracking.
What actually goes wrong if you do this by hand
WooCommerce gives you an Order Date in whatever format your WordPress site's locale is set to, while BigCommerce gives you an Order Date column that includes a full timestamp — line those up manually across a few hundred rows and it's easy to miscount a week. On top of that, WooCommerce's export column layout depends on which export plugin generated the CSV, so two WooCommerce stores can produce different headers entirely, and BigCommerce's many optional columns are exported blank depending on store configuration, which can throw off auto-mapping by header position. Individually those are minor quirks; combined into one spreadsheet by hand, they're where most reconciliation errors for cost of goods sold tracking actually come from.
Why it matters for cost of goods sold tracking
Calculating cost of goods sold across channels requires item-level data lined up the same way regardless of where it sold.
Just want the quick column-difference reference instead? See the short version.