CounterPoint Interface for Updating Magento Products
CPUpdateMagento – The fastest way to update Quantities, Prices and other Item Attributes in Magento from CounterPoint SQL
Magento Product Quantities can be updated from CounterPoint SQL on demand or can be scheduled to run as often as needed.
Magento’s Product IS_IN_STOCK flag is automatically changed to out of stock when quantity becomes zero and changes back to in stock when quantity is greater than zero
- A different view or table can be specified for using in updating Item Qty, Item Standard Attributes, and Item Custom Attributes
Magento’s Standard Product Attributes that can be updated. You can specify which fields you want to update.
- Name
- Description
- Short Description
- Quantity
- Price
- Special Price
- Special Price to Date
- Cost
- Weight
- Featured Product
- Meta Title
- Meta Description
- Meta Keywords
Magento’s Custom Product Attributes can be updated.
CPUpdateMagento supports updating up to 25 custom attributes. There is an additional setup charge based on the complexity of the additional custom product attributes. Please contact us to discuss your requirements.

- Varchar
- Text
- Decimal
- Date/Time
Requirements:
- CounterPoint SQL: 8.3.9, 8.4.4
- Magento Community Edition: 1.5.1+ (older versions are not compatible due to changes in Magento’s API)
- Direct Access to Magento’s MySQL Database is required
- Tested on SQL Server 2005, 2008, 2008R2 Express, Workgroup, Standard
- Tested on Windows XP, Windows 7 x64, Windows Server 2003, Windows Server 2008R2 x64
Note: a static public IP is required for the CounterPoint SQL Server in order to allow for a consistent direct database connection to Magento’s MySQL Database. The use of a dynamic public IP will result in the need to update the white-listed access to your Magento database every time your public IP changes.
Note: The Magento Hosting company must allow direct MySQL access
Recommended Magento Hosting Company is Nexcess.net
http://www.nexcess.net/magento-hosting
Update: SimpleHelix.com is removing their direct MySQL access due to their backup procedures
