Solving Price Update Issues for Multiple Store Views Using Magmi
Hello Paul,
I understand your frustration with updating prices across multiple store views using Magmi. Let’s troubleshoot this issue step-by-step.
Understanding Your Configuration
You have two store views under one website:
- Store View 1 (Code: abc)
- Store View 2 (Code: bab)
Your CSV file structure seems correct, with the following columns:
store: Indicating the store view to updatewebsites: Currently blank for both entriessku: The product’s SKU you want to updateprice: The new price for each store view
Here are your import attempts:
- Two separate CSV files: One for each store view
- Single CSV file with all products first, then next block of products
- Single CSV file with two rows per SKU (one for each store view)
- Adding a third row as a default value
Identifying the Issue
The problem could lie in your CSV configuration or Magmi’s handling of multiple entries for the same SKU.
Recommended Approach: Update CSV File Format
I suggest modifying your CSV file format to include the following columns:
store: Store view code (abc, bab)sku: Product SKUprice: New price for specified store viewwebsites: Can be left blank or use a dummy value like ‘all’- A new column:
entity_id- The unique product ID
Here’s an example:
store,websites,sku,price,entity_id
abc,all,1001,5.00,1234
bab,all,1001,7.00,1234
Key points:
- Use the actual store view codes (abc and bab)
- The
websitescolumn can be ‘all’ or a dummy value not associated with any existing website - Include the
entity_id(product ID) to uniquely identify each entry
Magmi Configuration Checklist
-
Enable Logging: In Magmi’s settings, enable logging to get detailed import results.
-
Profile Settings:
- Ensure you’ve selected the correct profile for your CSV format.
- The profile should be configured to handle multiple entries per SKU (this is crucial).
-
Server Resources:
- Check if your server has adequate memory and processing power to handle large imports without crashes.
- You mentioned that Magento’s default import feature is slow; Magmi should perform better with proper configuration.
Verification Steps
After updating the CSV file as suggested:
- Import using Magmi.
- Review the log file for any errors or warnings.
- Manually verify if both prices updated correctly in each store view after re-indexing and clearing cache.
If you continue to face issues, please share your Magmi log file here, and we can further troubleshoot the problem.
Remember, Magmi is a powerful tool but requires proper configuration and understanding of how it handles multiple entries per SKU. The key lies in correctly configuring your CSV file format and Magmi profile settings.
I hope this helps resolve your price update issue across store views using Magmi. If you have any further questions or need additional assistance, please don’t hesitate to ask.
Happy import!