40 results found
-
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.7 votes -
Simplified import of variants
Up to now, the import of variants has only been possible via a multi-level import. If variants are imported frequently, this is very tedious and frustrating.
A single-step import would therefore be desirable so that the main article and the variants are created directly. At least one extension shows that this is possible, but unfortunately it is no longer being developed.
3 votes -
Export existing Product Reviews
Currently there is no way to export product reviews from Shopware. This prevents us from using this very valuable data throughout the company.
We need an export function for product reviews because it allows shop owners to efficiently analyze customer feedback, identify trends, and improve products and services. This feature also helps with marketing and compliance, making it easier to share insights across all departments and stakeholders.
3 votes -
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 that many…
2 votes -
Function: Export what you see
In discussions with larger Shopware customers, there is always a request for the export to be expanded.
The export module is fine. However, as requested in other programs, a button for exporting what is currently being displayed is missing on individual pages (e.g. order overview, customer overview).
The export module does not have this simple but helpful function. You first have to switch to the module and then export and select all entries. This is very complicated and takes a lot of time and many unnecessary clicks in daily work.
It would therefore be very helpful and time-saving to have…
1 vote -
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.7 votes -
Export for tax consultants/tax office
Within Shopware 5, it was possible to select and export data from various database columns for the tax office/tax consultant.
e.g.: ‘all orders from 1.7.2024 to 30.9.2024 and also specify the country of delivery and the tax rate per product’
This is no longer possible with Shopware 6, but should be standard for quarterly tax reports.
3 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 -
simplify import of new Products
The import of new products should be significantly simplified. As in SW5, it should be possible to edit profiles more easily and make ALL nodes/extensions for advanced prices, media, properties, cross-selling, etc. available to provide ALL relevant data for new products in one upload.
In its current form, the import and export process is extremely cumbersome and very inconvenient.3 votes -
Import Custom Product Options and Prices
Add profile and mappings to import custom product options and prices
2 votes -
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 votes -
Add Returns-Management Mappings to Order Export
Add mappings for returns lineItems, refund price, reason and such to the order export.
2 votes -
Filtern beim Export
Das nur bestimmte Kunden/Bestellnummern exportiert werden können.
18 votes -
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 -
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 votes -
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.
3 votes -
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
- Don't see your idea?