Supplier.csv + Import template.xlsx
Files remain in the desktop app and their schema is inspected before execution.
Short answer: Choose source and output fields, headers, and order, then save the mapping as a reusable recipe.
Files remain in the desktop app and their schema is inspected before execution.
The final output comes from the same reviewed preview result.
Map the supplier export to our import template. Keep SKU as text and rename Unit Cost to unit_price.
You can add more conditions. Each message updates the active plan instead of creating an unrelated result.
Confirm files, sheets, schema, and workbook features that need preservation.
The planner selects constrained actions from the current instruction, schema, and approved samples.
Edit steps and inspect Result, Diff, Issues, and the effect of each action.
Create a new file by default; source replacement requires a verified backup.
select_columnsrename_columnscast_typereorder_columnsColumn references and parameters validate against the current schema; a plan that cannot compile safely does not execute.
No. Transformation runs locally. The planner receives only the current instruction, schema, and small samples you approve.
Excel is not required to process supported CSV and XLSX files. You can use Excel or another compatible app to open the finished result.
Tablyra asks for clarification or creates an Issue instead of guessing a field or silently running a high-risk operation.
Yes. Additional messages update the same validated plan and local preview until you choose to save the final output.
Download the desktop app, open an Excel or CSV file locally, and build a reviewable result through conversation.