Do I need a clean file before starting?
No. SellStar is intended for real operational files, including files that need cleanup, mapping or matching before use.
Match new prices to products by SKU, EAN, ID or another key. SellStar helps prepare the data, preview the result and move it to the next operational step.
Use this task when prices change regularly, arrive from a supplier or need matching by SKU, EAN or ID.
| Step | What you do |
|---|---|
| 1 | Load the new price list or integration data. |
| 2 | Match products by SKU, EAN, ID or another key. |
| 3 | Review differences and prepare the price update. |
A controlled price update or review file showing changed and unmatched records.
The same workflow can often be reused for supplier files, CSV/XML exports and connected systems in the Shoper context.
If you want us to prepare the process for you, go to implementation services.
Use a file, import, update or export from daily work and see how SellStar turns input data into a controlled result.
Start with the file, export or integration data that your team already uses: supplier CSV/XML, a system export, a price list, a stock file or an order dataset. SellStar keeps the work tied to the source so the result can be checked before it is used in Shoper.
The task is built around matching fields, choosing keys such as SKU, EAN or ID, previewing differences and preparing a controlled output. When the same operation returns every week or month, it can become a repeatable workflow or an implementation service.
No. SellStar is intended for real operational files, including files that need cleanup, mapping or matching before use.
Often yes. The same source file can be used to prepare imports, exports or reports for other systems if the target format is defined.
Yes. Implementation services can cover supplier integration, automation setup and recurring reports based on SellStar workflows.
Continue through the connected SellStar page.
Continue through the connected SellStar page.
Continue through the connected SellStar page.