Adobe Commerce DateTime attribute type is not implemented for customer attributes. They are date only. This causes an issue with being able to provide a customer with a full omnichannel experience of accurately viewing activity on how they interact with an organization outside of just their ecommerce purchases. With Date only and not DateTime for customer attributes, the activity of the customers interaction last interaction/transaction outside of Adobe Commerce - for example presentation of the last purchase in a brick and mortar location will be presented twice to the customer when other updates have occurred to the customer profile in Adobe Commerce.
... View more
See more ideas labeled with:
For example, if we search for "fiter" it shows us results for "filter" in the response as expected but there's no messaging for "Did you mean?" or "showing results for filter" Currently, there is nothing in the live search response indicating what it's showing results for when the customer mis-types or it is showing results due to a fuzzy match. Because of this, we can't show that it Didn't find results for "fiter" but it's showing you results for "filter" instead.
... View more
See more ideas labeled with:
In the BO we are able to create a fixed_tax attribute, and apply it for some products. But we are not able to import it with our products via a csv file. It would be nice to have a column fixed_tax, to import the tax.
... View more
See more ideas labeled with:
It would be very useful to mass import synonyms against a SKU.
... View more
See more ideas labeled with:
<action name="*">
<section name="messages"/>
</action> We have some actions and don't want to reload messages section when them are called. For current, there is no way so we must customize from js function: Magento_Customer/js/section-config::getAffectedSections
... View more
See more ideas labeled with:
We submitted a ticket saying we synchronize orders in Magento to NetSuite. We bring them over using the Magento ID as the sales order ID in NetSuite (itemid, not internalid). Incrementing by 3 is very confusing for our staff, making it hard to notice if an order has been overlooked in processing. This can lead to frustrated customers and lost revenue. The idea that this is a restriction of Adobe Cloud's database clusters and cannot be fixed is frustrating.
... View more
We have a Adobe Commerce Instance with multi brand and multi country stores, and we share the same product catalogo accros de stores and also the same category tree. And we need the feature to sort products on the categories in the diferent way for each website. For example we have the website A and de website B in the same instance, and we have the same category tree for these two website and also share the same products. We need sort the products on category TVs, and we have the procuts with codes 10001 and 10002, we need put first the product 10001 for the website A, and put first the product 10002 for the website B. Now the sort on categories is global. If you need more information please let me know. Thank you.
... View more
See more ideas labeled with:
Hello, I believe this is more of a question than a suggestion. Amasty adds a block with technical information in the admin area (see below). Is it safe? Is it possible to add it to vanilla Magento to avoid every extension vendor adding this information? Access control would be more convenient to set up to one page rather than many.
... View more
See more ideas labeled with:
when a product creation fails it still creates the media items but doesnt clean them up
... View more
Not all countries require a phone number on the shipping label, so it would be great to have the option to select per store view if you want to ask the customer for a phone number in the checkout or not. Per country is maybe even better, but that might be a bit much. Statistics show that conversion drops when you ask potential customers for their phone number.
... View more
There is no limit on the number of unsuccessful guesses made when submitting a 2FA code, this increases the chance for a user to correctly guess a voucher code using scripting or automation. It is possible that users of the site may successfully discover valid code through brute force guessing. The application offers no mechanism to restrict the number of code attempts to mitigate this attack. We should add a limit for the unsuccessful guesses in the 2FA module.
... View more
See more ideas labeled with:
In Page Builder, when selecting images, the tiled view is acceptable until you have a lot of images in a single folder. Another view option, list / details, would be optimal here. This would allow you to see the full file name, size, type, etc. and allow for sorting on any of the columns.
... View more
See more ideas labeled with:
Category surrogate keys are added on product pages. Due to this all cached product pages are flushed when a category needs to be flushed. By removing the surrogate key from the product page, we can avoid this making overall cache more effective. Here is that it looks like on a typical product page. Surrogate-Key: cat_c c9 c18 c4 c201 c6 c206 c208 store cb cb_weltpixel_pre-footer cb_weltpixel_footer_v3 p103697 cat_p cb_weltpixel_global_promo_message_2 text All the c9 c18 surrogate keys are coming from the categories populated in Top Navigation. So when C18 is invalidated the all pages of magento are technically flushed.
... View more
See more ideas labeled with:
The suggestion here is to create an integration with AWS Code Commit to Adobe Commerce Cloud in such a way we can control our source code in AWS Code Commit and have a continuous integration flow running at Magento Cloud, similar to what happens with GITHub and GITLab. Thanks
... View more
See more ideas labeled with:
Shared Catalog entity is among few entities that do not have extension attributes support. B2B clients frequently request creating assign additional attributes for Shared Catalogs, and extension attributes feature would be really helpful to achieve that.
... View more
See more ideas labeled with:
Currently PWA Studio supports Braintree payments out of the box in its Venia storefront implementation. It will be great if it can support all the payment methods which comes by default with luma theme. Here I am requesting to have Purchase order payment method compatible with PWA studio in native magento. Thank you!
... View more
We need to use the Quick Order functionality for the Venia theme but this is not available for Venia theme. This functionality is only compatible with luma theme. As this is a core feature available for Adobe commerce, hence the expectation is we should be able to use if we are going with pwa (venia). Ref - https://experienceleague.adobe.com/docs/commerce-admin/b2b/quick-order.html?lang=en
... View more
See more ideas labeled with:
Login as customer functionality from admin panel is not available if we use venia theme. This feature works with luma theme and leads to 404 if we are using venia theme. Please implement this feature in upcoming releases. Thank you!
... View more
See more ideas labeled with:
According to the three test results below, if I set up the “Product to Match” rule using the country(Spain or Italy) store view, not all store view, each buy page cannot show corroding the specific related product. Same Product(some-product-001) information : • All store view (default store view) : ABC Backend url : https://someplace.com/admin/catalog/product/edit/key/5a49698c937c019619cffe01f2d4b6ec/id/169/ • Spain store view : 111 Buy page : https://someplace.com/es/9some-product-001-default-fone-15.html • Italy store view : 222 Buy page : https://someplace.com/it/9some-product-001-default-fone-15.html My test result : (Every test scenario has to clear the cache and wait for the reindex) Test scenario 1 : 1. Setup the “Product to Match” rule’s name : Product Name contains 111 (Spain store view) 2. Setup the “Product to Display” rule’s name :Product Product Name contains Constant Value fone15 3. Check the Spain buy page, it didn’t show any related product on the related product section Test scenario 2 : 1. Setup the “Product to Match” rule’s name : Product Name contains 222 (Italy store view) 2. Setup the “Product to Display” rule’s name :Product Product Name contains Constant Value book15 3. Check the Italy buy page, it didn’t show any related product on the related product section Test scenario 3 : 1. Setup the “Product to Match” rule’s name : Product Name contains ABC (All store view) 2. Setup the “Product to Display” rule’s name :Product Product Name contains Constant Value fone15 3. Check the Spain and Italy buy page, it will show each fone15 products on the correct buy page Our expectations are: • Spain buy page show the fone15 related products • Italy buy page show the book15 related products If the Product name is only able to read productName from the All store view only, but when I test in the “Product to Display” rule using all store view product name as productName, the frontend buy page can’t show the related product. If I setup the “Product to Display” rule using the Italy store view product name as productName, the frontend but page will show the related product. All store view 12-22 10-46-56-005 Italy store view 2022-12-22 10-56-25-464 In my observation, “Product to Match” needs to use the All store view product name, and “Product to Display” need to use the country(Italy) store view product name. If the related product is designed as a global function, why productName in the “Product to Display” rule and “Product to Match” is read different values (all store view/country store view)? Due to our test result, the “Product to Display” rule needs to use the country store view product name as productName, so we expect the “Product to Match” rule also use the country store view product name. My test result is that “Product to Match” needs to use the All store view product name, and “Product to Display” need to use the country(Italy) store view product name. If related product functions need to use all store view product name only, why is the logic of “Product to Display” and “Product to Match” different? Not all use all store view product name. I was wondering if there is something wrong with this part or if this is the original design?
... View more
See more ideas labeled with:
This would provide ability to set certain products to be only purchasable using the allowed payment methods. For example, this would exclude product from global payment methods to be purchasable only by credit card.
... View more
See more ideas labeled with: