6 results found
-
Reintroduce CLI commands (functionality) for Migrations
CLI commands for migrations have been removed from release 16 (see https://github.com/shopware/shopware/issues/10825) without proper replacement.
As a result it is currently not possible to migrate with a finer selection via the CLI. One has to select an entire data category (i.e. all products) to migrate, making it more difficult and time-consuming in larger shops to debug issues.
2 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Export orders with redeemed voucher codes
I would like to be able to use the export tool to export all voucher codes redeemed for an order as part of the order export.
8 votes -
Allow importing only gross or net price with automatic calculation of the other value
It is currently impossible to import only an updated net or gross price without also providing the other price. The calculation of the missing gross or net price does not take place during import.
If one value is empty in the CSV or not mapped in the profile, the price will not update. No error or indication is shown that it failed.
If both net and gross prices, as well as the price.DEFAULT.linked value, are supplied, both prices will be set exactly as provided, but the gross/net link will not trigger recalculation. This can lead to broken scenarios where tax…
4 votes -
Improve export of products - better handling of variant data
The current situation is, that inherited field stay empty when a product export is done. This makes it more difficult to exchange data with other software or just to use spreadsheets to gain special information.
It's a topic that currently needs a workaround for many customers. Perhaps it could be possible to create several export profiles: one for exchange and editing data just for Shopware and one for external exchange.
3 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Import / Export Profiles - technical names make identification more difficult
Since Shopware 6.7 (?) the import / export profiles use technical names. The customer's labelling has been totally erased, although it's still available in the translation table.
Of course the customer can now overwrite the new name default_product-copy-1762844593373 for duplicated profiles. But usually these profiles were marked like "Import prices manufacturer1", "Import prices manufacturer2" and so on.
Means the customer has to check all their profiles correct the technical name, which seems to be the same for any administration language. Please add the labeling again.2 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Add filters for Exports according to Shopware 5
Many customers miss the filter functionality they know from Shopware 5 especially because the AI features do not work reliably.
For example the export of orders is often needed for a year or two and the amount of data grows very quickly.8 votes
- Don't see your idea?