Task catalogue
See all SellStar tasks.
Use it when a supplier file has different field names or order than your import template.
Use it when a file has different column names, a different field order or needs mapping before import.
| Step | Description |
|---|---|
| 1 | Load the data source: a file, export, URL or system data. |
| 2 | Set keys, columns, rules and the expected output scope. |
| 3 | Preview the result and save the output for the next step. |
A table with columns matched to the target format and a lower risk of a broken import.
Use a file, import, update or export from daily work and see how SellStar turns input data into a controlled result.
Use this workflow when operational data has to move from a supplier file, export, spreadsheet or integration into a checked result for import, reporting, translation, update or automation.
The goal is not just to generate a file. The goal is a checked result: a clean import, an export for another system, a report, a translated catalogue or a reusable automation.
Yes. The best test is a real CSV, XML, spreadsheet, export or supplier file from your current workflow.
Yes. The workflow is designed around preview and verification before export, import or automation.
If the same operation repeats, it can usually be saved as a repeatable workflow or implemented as a service.
Continue through the connected SellStar page.
Continue through the connected SellStar page.
Continue through the connected SellStar page.