Aug 20, 2013
Matt Becker wrote
We have two web stores that share the same SKUs, but have different tier pricing for the two stores. Currently Store Manager only supports uploading tier pricing to a single store. A separate upload to one stores overwrites the previously uploaded values for the other store. This is a confirmed limitation from Store Manager (meaning, I'm not missing something) and presents a significant problem for initial data import as well as ongoing price maintenance.
Completed
1 vote
Vote
Reply
7 Answers
Aug 21, 2013
Alex Pryshlivskiy
agent
wrote
Hello Matt
It seems you use old version of Store Manager for PrestaShop.
I recommend to update software.
In our last versions you can import data to multistore.
Example:
step 1 - select Store 1 - do import for store 1
step 2 - select Store 2 - do import for store 2
There is no problem with multistore import.
Please try again with latest version.
It seems you use old version of Store Manager for PrestaShop.
I recommend to update software.
In our last versions you can import data to multistore.
Example:
step 1 - select Store 1 - do import for store 1
step 2 - select Store 2 - do import for store 2
There is no problem with multistore import.
Please try again with latest version.
Aug 21, 2013
Matt Becker
wrote
Hello,
I am using Store Manager for Magento 2.13.2 (not PrestaShop).
I have been able to successfully import data to different stores with the exception of Tier Pricing.
When I perform an upload of Tier Pricing and follow the steps that you list, Step 2 overwrites the data that was uploaded in Step 1. Meaning, the Store 1 data is lost and all that is left is the data that was uploaded to Store 2.
This behavior has been confirmed by eMagicOne Tech Department personnel. The email correspondence has the following code in case that helps: GCH-JONKT-728. In this correspondence, I was told that this is confirmed/expected behavior and it would be fixed in future releases depending on the priority the feature request is given in this Support Portal.
I am using Store Manager for Magento 2.13.2 (not PrestaShop).
I have been able to successfully import data to different stores with the exception of Tier Pricing.
When I perform an upload of Tier Pricing and follow the steps that you list, Step 2 overwrites the data that was uploaded in Step 1. Meaning, the Store 1 data is lost and all that is left is the data that was uploaded to Store 2.
This behavior has been confirmed by eMagicOne Tech Department personnel. The email correspondence has the following code in case that helps: GCH-JONKT-728. In this correspondence, I was told that this is confirmed/expected behavior and it would be fixed in future releases depending on the priority the feature request is given in this Support Portal.
Aug 22, 2013
Alex Pryshlivskiy
agent
wrote
Hello Mat!
I see, thanks for explanation.
You are right.
We'll try to implement this feature in this year - 2013.
I see, thanks for explanation.
You are right.
We'll try to implement this feature in this year - 2013.
Aug 22, 2013
Matt Becker
wrote
That's exciting to hear, although it would really be helpful to have for uploading our data now as we get ready for a relaunch...
Seriously, though: will we receive any sort of notification once this feature becomes available? We perform regular updates to our versions of Store Manager, but it's unlikely that we'll be testing to see if this feature has been enabled every time we perform an update.
Thanks for all of your help!
Seriously, though: will we receive any sort of notification once this feature becomes available? We perform regular updates to our versions of Store Manager, but it's unlikely that we'll be testing to see if this feature has been enabled every time we perform an update.
Thanks for all of your help!
Aug 22, 2013
Alex Pryshlivskiy
agent
wrote
You can get more info about new release here - What's new in Store Manager section - http://www.mag-manager.com/discover-the-latest-updates-of-store-manager-for-magento
Aug 22, 2013
Alex Pryshlivskiy
agent
wrote
Please follow us ...
May 09, 2014
Volodymyr Hnyda
wrote
Implemented in ver. 2.13.0.908