SKU Mappings (Crosswalks)

Your Design Flex export carries catalog product codes and catalog pricing. Most shops sell under their own internal product numbers and their own pricing strategy. A SKU mapping translates both, automatically, on every conversion — your Cyncly output goes in, your internal product numbers and your prices come out. It's one shared database for your whole team: update a price or a product number once, and every designer's next conversion uses it. No more price sheets passed around.

1. 1Go to SKU Mappings.
2. 2Create a new mapping or open an existing one.
3. 3Add entries that match a source value (the code from your Design Flex file) to the value you want in the output.

SKU mappings are applied per field, under Operations in your pipeline's mapping:

1. 1Open your pipeline's mapping and select the field you want translated — for example, the item name or the unit price.
2. 2Under Operations, add a lookup against your SKU mapping list.
3. 3KitchenAPI then scans each row for a value that matches an entry in your mapping — and when it finds one, it replaces that field with your internal product number or price. Repeat for each field you want translated (most shops map the product number field and the price field).

It's all optional. And if a row has no match in the mapping, no changes are made to that row — it converts exactly as it came in.

When someone edits a product number or a price during a run review (see Running a Conversion), KitchenAPI captures that change as a suggestion. Open the Suggestions tab on the SKU Mappings page to see them — accept a suggestion and it becomes a permanent mapping entry, applied automatically on every future run. One edit, captured forever.