Magento merchants are such dynamic and resourceful people. While they pride themselves on their ability to grow online business, most of them have a surface understanding on technology and terminology. They seemingly talk with an alien when dealing with a developer. Merchants find it indecipharable in a deluge of acronyms and buzzwords.

Though problems cannot be solved in an article, the post would like to indicate top critical questions and correct answers a merchant should ask the technical team to help ensure the website's best running.

1. What is our contemporary resource load and how much is a spike of traffic?

Merchants running promotions should prepare themselves for traffic spikes. If your server is closer to capacity, it might slow down, deny user access or crash during a marketing campaign. To have the sufficient CPU power, asking the developer how to handle.

2. How do we keep fast loading pages?

Page loading is crucial. The developers tell you which methods they are using. If you are on a cloud resource, you should use Nginx to maximize speed rather than Apache. If you have lots of traffic from other countries, considering a content distribution network is the advice.

3. What are Magento EE benefits?

Suprisingly a lot of EE users do not take advantages of full page caching, a key feature to improve page loading. In most situations, it is turned off due to theme conflict. For that case, you had better ask your developers to modify the design to allow it. Your team would rather know how to segment customers, set up individual sales and other unique features of Magento EE. Make sure your team test features always to decide upon which is best for your products and services.

4. How a non technical person updates images and contents on the site?

Your developer should have set up CMS blocks for changable contents for instance banners and divided special user roles such as designers, writers and other content creators, instructing them how to use.

5. How do we secure the server?

If you haven't questioned your server administrator yet, better having it now. They just open necessary ports and all passwords must be unique. Beyond and above, user access comes from specific IP address.

6. How can we handle cases to roll the site back to previous stable version?

If the answer is "not yet set up", you should consider a new development environment. The best answer is a version control system is somewhere. You should have a staging server and a production server. All of new features should be done in development server and only applied to production server after thorough tests.

7. Who is accessible to the server?

If the developer does not know, you need to examine. It had better only you and the developer have root access. If setting up FTP, each user has his own user name and password. SFTP or FTP access should be granted for trusted people. Access to staging server can be broader but production server to highly authorative users.

8. Which version of Magento do we use?

If your version is one behind the latest Magento release, you might have missed out important security patches and functions. Visit Magento to see the latest version and have appropriate actions.

9. What extensions installed on the store and what do they do?

Make sure you know which extensions have installed so you use them at the fullest extent. You may not aware of your available functionality. If the list is very long, take a look at extensions that handle functionality of more than one extension. There may be extension conflicts, managing portfolio of extensions keeps your Magento site lean and mean. Your developer should have a list of extensions and what each one does.

10. Is there any overwritten code at the core?

Overwriting core code is the heart of many conflicts during upgrades or new extension integration. To ensure that you are getting the most out of Magento, working with certified developers who spent a number of hours learning Magento platform and passed a stringent test.