39 results found
-
Implement mapping for document_number in order-export
Implement mapping for document_number in order-export
2 votes -
Export/import for worlds of experience
An export and import function would be very helpful, especially for very extensive worlds of experience.
This would allow individual backups of individual worlds of experience to be created quickly and easily without having to restore the entire store.
As experience worlds are worked on often and frequently, this would also allow experience worlds to be prepared in staging environments, for example, and quickly restored in the event of errors.
2 votes -
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 vote -
AI Export Assistant: improve functionalities
We would like to request the addition of several data query capabilities to the Export Assistant feature in the AI Copilot. Below are some example prompts that we believe would be highly beneficial:
All orders with the voucher code XY in the period from X to Y
All orders from the XY sales channel
All orders with payment method XY from the XY sales channel
Abandoned orders in the period XY
All orders with a shopping cart larger than XY
All orders with zip codes from X to Y
We do not believe these queries involve highly complex data analyses.…1 vote -
No mandatory fields for Import
The fact that there are mandatory fields during import means that unnecessary data (e.g. stock in the event of a price change) is transferred, but this only delays the duration of the import and makes no sense.
For example, it is not necessary to change the stock when changing prices. This is not necessary and only delays the duration of the import. For large customers, the import takes many hours.
It would therefore be desirable to be able to deactivate the dependencies.
1 vote -
More export options
It should be possible to export more information - especially with regard to bookkeeping.
It should be possible to export items such as return quantities, return values of orders, transaction codes, etc.
1 vote -
Export of order data (also after cancellation)
Show sales after cancellation...
The order data exported in the following way ‘Import / Export under Settings > Shop > Import / Export’, also show the turnover of the original shopping cart if the customer has cancelled (a product for example) in the meantime.
I need an export list of the orders that also show the turnover that the customer has made after cancelling.
And I need an export list of the orders, in which the comments are shown, which are entered in the backend when processing a cancellation.
1 vote -
Post-import Download with new Id's
After import of NEW products the funktion to download the import-data should include the new created Id's of the new products. They are needed for further import of extended prices, accessories, similars, properties and media.
That would be much easier and faster rather then picking them out of the complete stock of articles that must be downloaded again and again.1 vote -
"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 vote -
Support of dynamic product groups and rules for export
It would be very helpful if the export of products or other data could be restricted via a dynamic product group or via a rule. For example, I would only like to export orders from the last 2 weeks or products from a specific dynamic product group.
similar idea: https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/47229503-filtern-beim-export
1 vote -
Product export files should have standardised separators
Different decimal separators: The export file for products contains different decimal separators for the representation of fractions. A standardised representation with a point (.) or comma (,) should be defined for the entire export file. PaymentCost is currently transmitted with the separator "point". All other price details have the separator "comma".
1 vote -
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 migrations.
If…
1 vote -
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 vote -
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 vote -
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 have…
1 vote -
Cloud: Deactivating the e-mail function
If you import customers, for every customer will be sent a registration mail. You can't deactivate the mailer in the cloud to prevent this.
There will be need an option. Here, not every customer may receive a mail again.
1 vote -
Cooperation with PIM software
Cooperation with PIM (Product Information Management) software like Pimcore or Akeneo. These both software tools are Open Source. Goal is to better and faster integrate the PIM software with Shopware 6.
1 vote -
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 vote -
Reduction of resource consumption
When importing / exporting or comparing products, the system requirements increase very quickly. Sometimes a memory_limit of 1G is not enough, which stops the whole export. But on some servers it is not possible to increase the resources arbitrarily. There were a few customer feedbacks that a resource saving solution is desired for this.
1 vote
- Don't see your idea?