Magento® only lets you set prices at the Website level. With our extension, you can set product prices for each store view separately.
OverviewBack to top
You can now set product prices for each store view separately. This extension appends the Store View Price scope in addition to the Website and Global. Magento® only lets you set prices at the Website level, but with our extension, you can set different prices at the Website and Store View level.
Our extension gives you the greatest amount of flexibility and control over your product prices. When running your international business, you can’t set the same product prices for every Store View. With M1 Store View Pricing, you tailor your prices to the specific geolocation, resulting the greatest amount of sales. Let’s say you are selling a pair of tennis shoes and you sell it to 3 geolocations: India, Australia and South Africa. In order to maximize sales, you can’t set the same price for your tennis shoes for all three regions. The market and economy is different in each of these countries. With our extension, you have the control to set different store view prices in order to match the given market.
How your site will appear and function with our extension:
The only difference you will see when our extension is submitted is the pricing for each product. The product’s pricing will be set according to the Store View the customer is using.
How the Extension works:
For example, let’s say you have the following Website, Store Groups and Store Views:
Website (Brand, which can be different companies):
Your Fishing Brand
Your Jewellry Brand
Your Apparel Brand
Your Wholesale Website
Your Retail Website
Store Views(used to target international localizations):
Magento® only lets you set specific product prices at the Website level, meaning that you can’t set different product prices for each store view.
With Store View Pricing, you can set specific prices for your Spanish, English and French Store views for every one of your websites.
Specific Price per Store View
You can set different prices at the Store View Level. If we reference the example above, you can set different prices for the Spanish, English and French store views for every one of your brands (fishing, jewellry and apparel brands).
Group pricing per Store View
You can set specific group prices for every store view. For example, let’s say you want to offer a discount on a product when a certain amount of is ordered. This can be done at the store view level.
Special Pricing per Store View
You can set Special pricing for any product you want to feature or promote with discounts or new prices. For example, let’s say you want to offer a New Product price for your fishing pole. This special price can be set at each store view level.
Tier Pricing per Store View
Let’s say you want to offer a discount to customers who order a certain amount of product. For example, let’s say you want to offer tier pricing on your bracelet. If the customer purchases one bracelet, it costs $30. If the customer purchases two bracelets, you want it to cost $50. Finally, if the customer purchases 3 bracelets, you want it to cost $70. This tier pricing can be set for each store view for your jewellry brand.
Auto-generation of indexes after price scope has been changed
This means that after you update pricing in your website’s admin, our extension will update the frontend automatically for you.
Release NotesBack to top
- Compatible with CE: 1.7 1.8 1.8.1 1.9 1.9.1 1.9.2 1.9.3
- Stability: Stable Build
March 19, 2018
Updated all namespaces
March 16, 2018
All code was validated for the Magento Marketplace
Feb 14, 2017
Release of version 184.108.40.206+build.2+build.17
Jan 11, 2017
Release of version 220.127.116.11+build.2
Aug 21 2016
Improved #5 Uninstall Script to remove files and sql
improved #3 Setup Modman
Improved #3 Added Documentation and Licensing
Fixed Bug #1 Fixed an exception on base installation
Fixing the problem with indexing Magento CE 1.9
Standardization of the repository
Added User Manual Page
Install and configure modman in repository
Fix bug with website id
Apr 10, 2016
Apr 10, 2016
Apr 10, 2016
Apr 10, 2016