FILEHUB ANALYST GUIDES
How do I map SKUs when every system uses different codes?
A supplier SKU, your internal material number, and a retailer’s item number can all refer to the same product. Matching the codes directly will not work unless you maintain a cross-reference. Product descriptions are useful clues, not proof.
1. Build a cross-reference table
Store Source System, Source SKU, Official Product ID, Description, Pack Size, Unit of Measure and Approval Status. Add an effective date when identifiers change.
2. Match the product, not just the name
Check brand, flavor, size, case pack, unit and product status. A 12×200 g product is not automatically the same sellable unit as a 24×100 g product.
3. Review non-exact suggestions
Use product description similarity as a review queue. Never silently substitute different numeric SKUs or packaging sizes.
4. Apply verified mappings before analysis
Once SKU mapping is approved, sales by brand, category, supplier, promotion and manager become more reliable.
5. Export exceptions
Keep unmapped products visible. FileHub Analyst exports a separate Review Needed sheet so missing mappings do not silently disappear.
Frequently asked questions
Can two SKUs refer to the same product?
Yes, across systems, but the relationship must be verified and may depend on pack size.
Should I map descriptions automatically?
Only as suggestions for review. Numeric product IDs and variant attributes must be respected.
Prefer to do this without building the formulas?
Upload your Excel file to FileHub Analyst, select the columns and get a report. If your data needs mapping first, you can review matches before exporting.
Run your numbersClean and match dataMore Excel guides: Unique customers · Match names · Sales by region · Sales vs target · SKU mapping · FMCG reports