Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Product regular price on category page is using Default Store regular product price instead of Current Active Store product price #7251

Closed
lid3rs opened this issue Oct 31, 2016 · 7 comments
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@lid3rs
Copy link

lid3rs commented Oct 31, 2016

Preconditions

If we have multiple web stores (one website) and product is active on store A and on Store B (Store A and Store B are instances of one website; store A and Store B are NOT Store Views), but with different prices, then on category page, in Store A and in Store B, the product regular price is the same for store A and for Store B. Mismatch here is that in Admin panel in Store A regular price is different that in Store B. In Product Page, the regular price is different and is O.K. If we make Advanced Pricing, then the Special Price differs on Category View page, and is O.K.

The prices are configured to be different per Website.

Magento ver. 2.1.2

Steps to reproduce

  1. Create 2 Stores, which are placed in one website
  2. Configure to show different prices per website
  3. Create two root categories for Site A, Site B
  4. Place on product in Site A and Site B
  5. Define different regular prices for this product for Site A and Site B
  6. Go to category view and see the mismatch.

Expected result

In admin panel
Product A has A regular price for Store A, website A
Product A has B regular price for Store B, website A

In category page
Product A has A regular price for Store A, website A
Product A has B regular price for Store B, website A

In product page
Product A has A regular price for Store A, website A
Product A has B regular price for Store B, website A

Actual result

In admin panel
Product A has A regular price for Store A, website A
Product A has B regular price for Store B, website A

In category page
Product A has A regular price for Store A, website A
--> error -- > Product A has A regular price for Store B, website A

In product page
Product A has A regular price for Store A, website A
Product A has B regular price for Store B, website A

@rganin
Copy link
Contributor

rganin commented Oct 31, 2016

Thank you for reporting, the issue is actually in broken price scoping: price can have only global or website scope depending on configuration setting in Stores -> Configuration -> Catalog -> Price -> Catalog Price Scope field, and should not be scoped per store view.
Issue is already aknowledged in #5133.
Internal ticket created MAGETWO-54704.

@rganin rganin added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Component: Catalog bug report labels Oct 31, 2016
@lid3rs
Copy link
Author

lid3rs commented Nov 1, 2016

U'r welcome. I was expecting the price change not per store view, but per Store if we speak Website -> Store -> Store View.

A little offtopic:
What i'm trying to achieve, is that there are different Websites (businessess with different products), Stores (only different countries and prices), Store Views (Different Langs). So I used the Store to setup different prices. It worked as i expected in product page, but not in category page.

Is my approach wrong? If so, what could be teh best solution for such business organisation?

@ritschi72
Copy link

Is there any update on that issue? I am also facing that problem in Magento version 2.1.2

okorshenko pushed a commit that referenced this issue Dec 14, 2016
…te - scoping seems to be at store view level #5133 #7251 - for 2.1
mmansoor-magento pushed a commit that referenced this issue Jan 19, 2017
mmansoor-magento pushed a commit that referenced this issue Jan 19, 2017
mmansoor-magento pushed a commit that referenced this issue Jan 19, 2017
mmansoor-magento pushed a commit that referenced this issue Jan 19, 2017
@yaronish
Copy link

Fixed

@brekz
Copy link

brekz commented Mar 27, 2017

I got another interesting error related this issue:

We have 5 different stores.
Creating product. After created product we're correcting product name for each store. After that, I'm coming back to "Store View: All Store Views" & want to change price for entire product.

Changing, seems OK, but now I'm going to each store to check if price is changed - NO.
Interesting situation that price changing in that store where we didn't correct product name.

Interesting situation, that if I didn't change product name is store, price input following "Store View: All Store Views" changes. But if I correcting something in multi store, price is didn't changing.

We have "Catalog Price Scope: Website"

@brekz
Copy link

brekz commented Apr 13, 2017

Any answer?

@orca931
Copy link

orca931 commented Jul 18, 2018

I don't think this issue is fixed.
I am encountering exactly the same problem in Magento 2.2.3

I read that the prices in the category pages are coming from the price index (table catalog_product_index_price) which is not the case for the product details page.

In that table, there is a column website_id, but there is no column store_id. This means that a product which has different price in each store cannot have different indexed prices, it can have just one indexed price per website and therefore you will get only one price in the category page regardless which store are you browsing.

For me that is very strange and an obvious problem with the design of the index price table. I cannot understand why there is no store_id column in the price index table, and how people are dealing with this issue.

magento-engcom-team pushed a commit that referenced this issue Dec 8, 2021
Delivery of beta changes to 2.4-develop
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

6 participants