magento / magento/community-features

Visual Merchandiser - Improvement proposal

Open
#310 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
46
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Hello @magento-admin ,

The current possibilities of the Visual merchandiser are too limited to be really acceptable by any business team managing a big catalog with Configurable products. Based on the usage of multiple alternative solutions, I warmly recommend you to improve it this way :

Issue #1: The Visual Merchandiser product grid should enable a business team to organize only the "catalog, Search" products. The product list is unusable because of the presence of all the "Not Visible Individually" products.

Issue #2: The Visual Merchandiser product grid should enable a business team to PIN some products on top of a set of predefined sort rules.

Issue #3: The pagination of the Visual Merchandiser product grid does not reflect the category pages pagination. For instance, If you display 9 products per category page on the front end, then, the Visual merchandiser should do the same - at least by default - so a business team can preview what they are doing. Note: this requires you to fix Issue #1 first.

Issue #4: The Visual Merchandiser product grid should enable a business team to move products in mass to a page X.

Issue #5: Find products feature is missing in the Visual Merchandiser product grid.

Issue #6: You may enable a business team to have the possibility to select into the Visual Merchandiser settings the attributes to show on the product tile. Indeed, in many businesses, an SKU + product name is not enough to uniquely identify a product.

Best regards,

Many thanks,

Guillaume

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by breaking the Visual Merchandiser product-grid proposal into separately scoped issues, then review the existing grid and catalog-page behavior for each requested capability. Done would require an agreed scope and acceptance criteria for the six listed improvements.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.