Running a Conversion

1. 1Go to the Run tab and choose the pipeline you want to run.
2. 2Upload your Design Flex export. KitchenAPI reads the file and shows you the source data.
3. 3Choose the QuickBooks customer — pick an existing one, add a new one, or leave it to match/create from the file.
4. 4Optional: add a job-site ZIP (for destination tax) or a document reference number if your pipeline prompts for them.
5. 5Run.
6. 6If your pipeline has Review before posting turned on, the run pauses — check the lines, edit prices or quantities, remove or add items, then Approve (or Cancel, and nothing posts).
7. 7Confirm success — on the run screen, in History, or directly in QuickBooks via the link in the summary.

Prefer a second set of eyes? Turn on Review before posting and use it as an approval step: a designer starts the run, and a manager has 48 hours to review, edit, and approve before anything posts — if no one approves in time, the run is cancelled and nothing reaches QuickBooks.

After a conversion, KitchenAPI shows a summary:

• A preview of the output rows.
• Row provenance — how many line items came in versus how many rows went out, so you can confirm everything carried through.
• Mapping report — a detailed breakdown of how each source field was mapped, which items matched your QuickBooks Item List, and which were unmatched. You can download this report for your records or to share with your bookkeeper.
• Warnings, if any — for example, a field that couldn't be matched. Warnings don't stop your file from generating; they point you to anything worth reviewing.

Blank columns or mismatched fields mean a template or mapping needs adjusting. Mapping adjustments happen in the pipeline editor, not during a run — see Creating a Pipeline and Working with Templates.