1065 results found
-
Storefront Presentation - Expand Properties
If you expand by a certain property (e.g. "color"), only those property options should be preselected in the listing article. If there are other properties (e.g. "Size") in addition to the color, all expanded items will automatically have an additional size preselected. However, it would be better to pre-select only the "Color" and to display a "Details" button in the listing instead of the "Add to cart" button, so that the user has to select the - in this case "Size" - himself before adding the item to the cart.
2 votes -
Possibility to change or correct the email address in the checkout process.
The possibility to correct the Email should be just as possible as the change of addresses. It happens again and again that typos creep in when entering the email. These can no longer be corrected during the final check by the customer.
Up to now there is the setting "Enter email twice", but this is cumbersome for the customer and most of the time the email is simply copied into the 2nd field.
3 votes -
Allow assigning Custom Products templates in bulk
Allow assigning Custom Products templates in bulk. Right now, you either have to assign a template for each product which takes forever or you do some dirty database magic which may or may not break everything long-term.
4 votes -
Price increase due to bulk edit
It should be possible to increase prices for a defined number of products, let´s say up to 20%, with the help tofo bulk editing.
2 votes -
Barcode scanning in the search
The customer should be able to use his mobile phone to create order lists and orders. He can use his mobile phone in the search and scan a barcode, for example. The article number is then inserted into the search field or into the quick order via the barcode. Especially interesting in the b2b sector
4 votes -
Override table listing page in app
Currently through Admin Extension SDK, we could add an extra table field (eg custom field data) in admin listing page of orders, products etc. Good to have it
3 votes -
After uninstall the app, custom entities is not retaining data
When we uninstall the app, all custom entities will be removed. (without clicking "Remove all app data permanently"). Is there any option to prevent this and retain data"
3 votes -
Cross domain post request. Security concerns
Since the app does not provide any hooks for review insert/update, we are posting
custom generated review form request to the app server when review
is added, and from there admin api will be triggered to insert reviews data along with custom entities data. But concerns regarding security in app url info, it can be directly seen thorough browser request and third person can exploit it.3 votes -
Add extra sort functionality in "sort by" feature of reviews list storefront.
The App has been provided with a "product-reviews-loaded" hook, but it is triggering
after loading all the reviews. Good to have a hook before loading reviews to add extra criteria and list reviews based on it.3 votes -
Switch search category without deleting search prompt in the admin
When using the search in the admin, switching the search category from "all" to any other entity, the search term or search prompt previously entered gets deleted.
It would be more practical if the search term remained and the results would be displayed accordingly after switching the search category.1 vote -
Prevent smileys in the comment field or transform them as special characters
If a wafi is used, smileys usually cause errors during import. An option that prevents the input or automatically converts it to special characters would be very helpful.
1 vote -
Translations for plugin setting values or translations for media files
Let's assume I want to add a plugin which adds a slider with images to the frontend. These images have to be different depending on which language is set for the shop. If the customer changes the language in the frontend a different image should be displayed.
There is no way to configure something like that in a comfortable way at the moment as far as I'm aware of.So the idea would be to either make the plugin setting values translatable or make media files translatable.
2 votes -
Insert dynamic URLs
Insert dynamic URLs. This is standard in a CMS. Dynamic URLs have the advantage that the links on a website are automatically adjusted with every update and do not have to be changed manually. Thus, the links should automatically adapt as soon as, for example, a landing page is moved or renamed.
4 votes -
Convert guest customers to real customer
Possibility to convert guests into real customers with an account.
21 votes -
Digital Sales Rooms without daily.co and/or Mercure
It should be optional to use Digital Sales Rooms without daily.co and/or Mercure. If these configs are not set no live video is possible.
1 vote -
"Return ratio" as option for the Rule Builder
As a shop owner, I want to be able to let customers pay only with prepayment when their return ratio is higher than 50 %, for example. An option "return ratio" within the Rule Builder would be helpful for it.
1 vote -
B2B Suite: Rule Builder for Sales Representative
It would be very helpful to automatically assign customers to the sales representative with the Rule Builder.
For example, based on postal code areas or tags.4 votes -
Enable SSO for enduser (Sign-up, Login)
Front-end APIs currently require a password to be sent in to authenticate customers into Shopware. Merchants who use a third-party Identity Provider (IdP), they want to have a third party maintain user information for use beyond just the e-commerce channel. In these instances, Shopware should not want to maintain the password for the customer, that should only ever be updated in the IdP. At the moment, the only way for a Merchant to implement SSO is in the fully-hosted model where they would be required to make some code changes to customize the platform. As it doesn't appear like assertion…
4 votes -
Retry logic for webhooks
If a webhook call in a Flow
Builder flow fails today, it is captured in a log, but no action is
taken on it beyond that. This makes the webhooks unreliable
as if there is ever a failure, the customer wouldn't know
without actively monitoring the logs. Adding a configurable
retry process (number of times to retry and retry interval)
would allow customers to have more confidence in using
Flow Builder webhooks.5 votes -
Send Order-Confirmation with flow-builder event
On event "Order-Placed" the email order confirmation is send to the customer.
It is NOT possible to stop this email, as it is send outside flow-builder.
Only after this event the flow-builder can be used to do some action.It would be better and more logical, to have this event already through flow-builder. This would give the possibility to react to the order content, payment, etc. and give more specialized order-confirmations.
2 votes
- Don't see your idea?