Customer SKU mapping template for QuickBooks distributors
The single biggest time-saver in distributor PO processing is a clean cross-reference between your customers' part numbers and your QuickBooks SKUs. This is the template we built our cross-reference tooling around. Yours to use, free, no signup, no email capture.
sku-mapping-template.csv
4 columns, 10 example rows. Opens in Excel, Numbers, or Google Sheets.
What's in it
Four columns. Boring on purpose:
The notes column is the most underrated. That's where you capture the "why" — why this part number, what customer-specific quirk, what changed in March 2025. The notes become institutional memory the next operator can read.
Why this matters
A typical distributor PO has 10 to 25 lines. Each line forces an inside-sales rep to play translator between the customer's part number convention and the QuickBooks catalog. Without a cross-reference, every translation is a fresh puzzle: 30 seconds of "what is DM78123?" multiplied by 15 lines multiplied by 30 POs a day.
With a cross-reference, the same line is a lookup. Two seconds instead of thirty. Across a year of PO volume, that single CSV file is worth roughly 80 to 200 hours of inside-sales time depending on your scale.
If you've never built one: this Saturday is the highest-leverage time to start. Pull your top 50 customers from QuickBooks. Open one of their recent POs. Fill in 20 rows. Repeat next Saturday for the next 50 customers. By the end of the month you have a cross-reference covering 80% of your PO volume.
How to use it (without SideQuest)
The CSV works as a standalone reference. Keep it open in a second monitor while you process POs. Sort by customer_id, find the customer, scan their rows for the part numbers on the incoming PO. Two seconds per line.
If you have a team, host it in Google Sheets or Airtable so everyone reads the same source of truth. Version the file weekly so you can roll back if someone edits incorrectly.
How to use it with SideQuest
SideQuest reads this CSV directly. After install, point the connector at the file with one prompt to Claude Desktop: "load my cross-reference from sku-mapping-template.csv." From then on every incoming PO line gets matched automatically against the cross-reference before falling back to fuzzy matching. The match rate goes from "maybe 60% on a new customer" to "98%+ on any customer in your CSV."
Free tier (20 POs/month) is enough to test the workflow. See pricing.
Common questions
"What if my customer changes their part numbers?" Add a new row with the new part number. Leave the old one too — POs in flight will still reference it. Use the notes column to record when the customer transitioned. The pricing on the example template shows how we track this for the "GLOBEX-CORP" row.
"My customer uses 10 different formats for the same part." Add 10 rows, one per format, all pointing at the same internal_sku. The mapping is many-to-one on purpose.
"What if I don't have the customer's part number — they just write the description?" Skip the customer_part field for those rows. SideQuest falls back to description-based fuzzy matching with confidence scoring, and humans approve anything below the threshold.
"Do I have to use SideQuest to benefit from this?" No. The CSV is useful on its own. We built it because we needed it for our connector. The format is portable.