- or
21 results found
-
Migration
During migration, it should be clear in the log where information is missing/null or cannot be found.
The migration log is very difficult to read for non-developers.
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration in app
It would be better if migration like system implemented for custom entities through app.
5 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Provide more migration profiles
As a merchant who wants to migrate to Shopware 6, I want a solution to minimise the effort of data migration from my current shop platform to Shopware 6.
Example areas:
- products
- categories
- custom products
- customer data
- order history
- content
- blog
- etc.3 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 24 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration: Correcting the multiple connection function
The migration tool offers the option of creating multiple connections. It is also possible to switch connections.
This is particularly interesting if you want to merge several Shopware installations (or other systems such as Magento) into one Shopware 6 installation. However, if you change the profile during a migration that has not yet been completed by the user with Complete migration, the checksums are mixed up. This behavior has been confirmed by Shopware Support.
It would therefore be a good idea to add a parameter for the active connection to the checksums to prevent mixing by switching open migration…
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration: Possibility to deactivate Category migrations/comparison
If you start the migration the first time, it is OK to migrate all categories and its content for the first time.
But late in the process it would be nice to be able to deaktivate the category migration/comparison.For example: if you want to update the customers and orders from SW5 to SW6 it always overwrites the categories. Basically almost all preparations you did in the categories for the SW6 launch are gone.
2 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration: Automatic placeholders for missing values
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration…
3 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Data clean-up within the migration
It would be great if you could contribute directly to data cleansing in the migration tool.
For example, "No guest orders", "Orders in the last X months" or similar.1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration: Transfer of additional fields (variants) from shopware 5 to shopware 6.
At the moment, additional fields are completely ignored during migration. However, if these fields were intensively maintained under shopware 5, they should also be present in some form in the variant on the shopware 6 side.
9 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 24 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration Assistant wrongly configures products with variants
After using the Migration Assistant, the 'buy button' is shown in the product listing page even when a product has multiple variants and the main variant has stock>0. Only when the main product stock=0, the 'details' button is shown. In case of variants, the 'details' button should always be shown in listing pages, as without the customer will buy the main product when clicking on the 'buy button'.
Cause: the radio-button 'main product' in the Shopware 6 backend that forces to show the 'detail' button in frontend in case of multiple variants, is not selected after migration. Normally, you…
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migration from various platforms
Either standard migrations from the most common platforms like Shopify would be good, and alternatively a documentation on best-practice and a guideline on how to migrate from other platforms.
Like with Magento we have used the one from Shopware, which works good. Like with Shopify we have had to write our own set of CLI tools to migrate products etc over to Shopware, but this should be a more general feature.
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
"Sales" column in the product overview should be updated after the migration
After the migration, the "Sales" column in the product overview should also be updated.
This means that all sales from the 5 shop should also be displayed.This column is currently not updated or is write-protected.
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Migrate advanced search configuration to all Storefronts
The configuration options in the advanced search are numerous and complex to maintain.
If you want to set boostings, actions and synoyms in all storefronts, the same configuration has to be made 24 times in our case, although we only have 4 different languages.
This maintenance effort could be considerably simplified by a migration feature/option.9 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Links and downloads input for products
In sw5 there was a tab where you could enter links and downloads.
Would be nice to have this as standard in SW6.It would also be nice for the function to take over this maintained data when migrating from SW5 to SW6.
17 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 24 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
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.
-
It should be possible to migratate customers without firstname and family names.
Currently you need a first name and family name to migrate customers from SW5 to SW6. Sometimes Customers are not real persons but companies.
There should be an option for that.1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Allow saving changes by pressing Enter in the Admin
Allow saving changes by pressing Enter in the Admin
Description:
In Shopware 5, it was possible to save many changes simply by pressing the Enter key after editing a field. This made product maintenance much faster because users did not have to move their hand from the keyboard to the mouse to click Save or the checkmark.In Shopware 6, after editing fields such as prices, users always have to click the save/checkmark button with the mouse.
For merchants maintaining hundreds or thousands of products every day, this results in many unnecessary mouse clicks and slows down the workflow.
Expected…
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.
-
It should be possible to import digital products
Right now, there is no way to import digital products. Neither using the Im-/Export feature, nor using the API.
It should at least be possible to create/import digital products using the API, because otherwise it is not possible to comfortably connect a different erp-system for digital products or to migrate from another shopware instance.
5 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Shopware Account Plugin License List Update
The current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same way…
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.
-
Advanced search for additional information in the order overview
In connection with the order overview, there is a customer need to be able to search for external order references (e.g., Amazon/eBay order numbers or member names).
This data is currently only stored in the "additional information" of the order during import and is therefore not found in the standard administration search function.Requirement/Use Case:
Customers want to be able to search the order overview for these external references to more easily find orders for accounting or support.
Typically, this involves fields such as:
Amazon order number
eBay order number
eBay username
Current status:
The standard search in the order…
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.
-
Customer feedback: Improvement of e-mail dispatch in Shopware 6
Dear Shopware team,
We support the customer uba-arbeitsschutz.de (KdNr. 324128). After the customer migrated to Shopware 6 Evolve and is already online, we regularly exchange suggestions regarding the functionality of Shopware 6.
We have a few suggestions for improvement regarding the handling of sending and receiving emails.
1st example:
When a customer pays for their order in the shop via PayPal, they receive an email stating that the payment currently has the status 'unconfirmed'. As the customer is already checked during the payment process with PayPal to see whether the payment was successful, sending this information by email from Shopware…1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
- Don't see your idea?