SKU mapping walkthrough

Your Design Flex export carries catalog SKUs and prices. If your shop uses its own internal product numbers or pricing, a SKU mapping translates them automatically on every conversion — one shared database your whole team draws from, instead of price sheets passed around.

1. 1Export your QuickBooks Item List (or prepare a CSV of SKU → item/price).
2. 2Open SKU Mappings in the Studio.
3. 3Upload the CSV or add entries by hand.
4. 4Done — every future conversion applies them.

The CSV importer handles quoted fields and embedded commas, and flags duplicates with the exact row numbers from your file.

Exact, case-insensitive, or normalized — normalized (lowercase, whitespace ignored) is the forgiving default that handles most real-world files.

Every conversion's mapping report lists exactly which SKUs matched and which didn't. Unmatched items post under their file values and are clearly flagged — add them to your mapping as you meet them.

When you edit a product number or price during a run review, KitchenAPI captures the change as a suggestion. Accept it on the Suggestions tab and it becomes a permanent mapping — the correction you made once applies automatically forever.