Call Toll Free: 888-623-2374

Request InformationSupport

Punchout Catalog for Magento and Our Approach to Updates

Magento continues to evolve and releases updates to it's core quite often. Our Punchout Catalog connector continues to evolve as well. How do we handle updates and release patches?

Punchout Catalog for Magento and Our Approach to Updates

Mar 03, 2012

Magento_logo.pngSince 2001, our parent company VBWebSites.net has developed countless e-commerce initiatives for companies all around the globe. We were introduced to Magento in 2007 and immediately fell in love with the platform, flexibility and GUI.

Magento, today, is the #1 open source shopping cart solution. Our first punchout catalog launched in 2007 and was integrated with Magento which accommodated 75,000 products. PunchOut2Go features a robust Punchout Catalog Gateway that enables CXML transactions with minimal alterations needed on a typical magento install.

Magento continues to evolve and releases updates to it's core quite often. Our Punchout Catalog connector continues to evolve as well. We take several measures to ensure a trouble-free punchout catalog solution for the both the Current Magento Builds as well as future Magento releases.

How do we handle Punchout Catalog updates and release patches for Magento?

When a new version of Magento is released, we test and make updates on our development systems, test and qa the updates against development installs of shopping carts and procurement systems before any changes are released to production.

If something is changing such that we feel we need to maintain support for both the updates and the existing protocol it replaces, then we are able version the different mechanisms.

For example, we might version a storefront punchout connector. If we have a change to the magento module and a complimentary change exists on our storefront connectors. The connector would be versioned, and updating the profile to use the updated connector would be done in coordination with the updates to clients website while other clients would be able to keep using the old connector until their sites could be updated. 

Release processes - Depending on the clients preferences, if we have an update that we need to release to a clients site, we are able to schedule updates during non-peak hours. This is done so if any issues are found, we are able to revert any changes.

Development Storefront - In addition, if an update is needed to a storefront (assuming that we are responsible and or the host for the punchout storefront) we can sync up a temporary instance of a store to test updates prior to moving to production.

If you have any questions pertaining to our Punch-Out Catalog solution, please contact us.

We are working on other shopping cart punchout integrations and encourage you to follow our Punchout2Go Lab. We are always open to recommendations and can also be contracted for custom punchout integrations.



Category: Announcements