Files and input data
CSV/XML editing, XML to CSV conversion, file merging and matching data by SKU, EAN, ID or another key.
Task catalogue
E-commerce tasks in SellStar
Choose a task by the result you need: a prepared file, product import, price update, order export, translation or automation.
Task categories
Product catalogue
Prepare imports, exports, bulk changes, feeds and product data for the next operational step.
Prices and stock
Match price lists and availability data to the catalogue and review changes before using them in a system.
Orders and reports
CSV exports, order cleanup and data preparation for accounting, warehouse work or analytics.
Translations and content
Translate files, product catalogues and e-commerce content while preserving data structure.
Automations and integrations
Recurring imports, exports, reports and updates based on files, URLs, FTP or integration profiles.
Common tasks
| Task | When to use it | Link |
|---|---|---|
| CSV/XML editing | A file needs cleanup before import, reporting or automation. | File editing |
| XML to CSV conversion | A supplier or system gives XML and the next process needs CSV. | XML conversion |
| Data joining | Several files, price lists, stock files or descriptions need one output. | Join by key |
| Product import | A supplier catalogue or export needs preparation for a sales system. | Product import |
| Product export | Products need to go to reporting, migration, comparison or a partner. | Product export |
| Bulk product editing | A larger catalogue needs many field changes without row-by-row work. | Bulk editing |
| Price updates | A new price list needs to match products by SKU, EAN, ID or another key. | Price updates |
| Stock updates | Supplier, warehouse or system availability needs to match the catalogue. | Stock updates |
| Order export | Orders need to go to reporting, accounting, warehouse work or analytics. | Order export |
| File translation | A file, catalogue or e-commerce content needs to keep its structure after translation. | Translation |
| Automations | The same import, export or update returns regularly. | Automations |
Tasks by system
If the workflow is tied to a specific system, start from its page. If the starting point is a supplier file, CSV/XML export or feed, file tasks are often the better entry point.
Base
Products, prices, stock, orders and exports in the Base context.
WooCommerce
Imports, exports, updates and store data work for WooCommerce.
PrestaShop
Products, price lists, stock, orders and operational PrestaShop files.
Shoper
Imports, exports, updates and Shoper data cleanup.
IdoSell
File, export, catalogue, price, stock and order workflows for IdoSell.
Selly
File, export, import, price list and reporting workflows for Selly.
How to choose
I have a file
Start with CSV/XML when you have a wholesaler file, store export, feed or several sheets to merge.
I have a system
Start with the system when you know the workflow concerns Base, WooCommerce, PrestaShop, Shoper, IdoSell or Selly.
I have a recurring process
Start with automations when the same import, export, report or update returns on a schedule.
Test SellStar on a real task
Use a file, import, update or export from daily work and see how input data turns into a controlled result.