Have you got a business-objective?

We have a solution.

Get a consultation right now!

contact us

request a quote
Enter your name
Your contact number
Enter your message
Natalya Brinza Project Manager

What Does a Merchant Need to Know When Creating Magento Online Store?


What Does a Merchant Need to Know When Creating Magento Online Store?

Before developing Magento online store, every entrepreneur should know some facts about the platform's technical background. Let's take a look at the basic points of Magento action process.

Magento Community provides two versions: Magento Community Edition (CE), that is free-to-use, and Magento Enterprise Edition (EE), that can be used on a paying basis. Note that if you buy licensed Magento version, you get support services as well.

For further work with Magento site, you need a dedicated server with the ssh-access, because majority of the actions are performed with the console.

Also, pay attention to the system requirements Magento is compatible with:

  • Operating System Linux x86-64
  • Web Server Apache 2.x or Nginx 1.7.x
  • Database MySQL 5.6 (Oracle or Percona)
  • PHP 5.4.x or 5.5.x

creating Magento online store

Before Magento setup you need to check for next extensions: php5-curl, php5-intl, php5-mcrypt, php5-soap. For safety's sake, after the setup you should change the paths for an admin panel and a downloader one.

For fast system performance, you need over 256 Mb RAM (the more, the better). For the 1.x branch, it is optimal to leave 512-768 Mb, and for the 2.x branch – 1 GB, that is the minimum.

High software performance is achieved by setting up Full-Page Cache module. Also, download speed can be increased by including JS CSS minification to the admin panel – this function lets you rev up site's page speed on a higher level. But be careful, such tweak can bring your website down because of the conflict between attached scripts, carousel plugins, etc.

Now, let's touch the base of the out-of-the-box solution - compilation.

This method is efficient but can be troublesome if there is a mistake in one of the modules. You should know that if compilation is turned on, the current code can't be changed. Modules database is taken from the compiled cache. To apply the changes you need, compile all modules again; this is not an easy process. To avoid all these problems, check your instance on the modules of uncertain origin. Though, if you find a mistake in the module, but can't disable it, turn off the compilation. There is an important point — you can't turn off the compilation if it is the 2.x branch.

Magento Community has its own extensions store – Magento Connect. Here, you can find free and paid modules that have different functionalities (adding payment gateways, methods of shipment, and caching, that we already have talked about ). When choosing modules, few things should be taken into account: the Magento version (a module for Magento 1.9 won't function on Magento 1.7), module rate, number of downloads. 2.x branch modules aren't compatible with 1.x versions and vice versa. Also, except modules for extending Magento functionalities, there are themes. When choosing a theme, pay attention to the version, the reputation of the themes author, and, sure thing, themes feedback.

 Magento online store

So your Magento is already set up, customized and launched. What is next? Optimization, monitoring, and support of the last version.

Every eCommerce project being developed in 2016 needs SSL certificate. Also, online stores need add-on protection, search engines loyalty, green sign in browser's address bar – the list is big enough. For monitoring server overheads, it is advantageous to set it up at Munin software server . It allows you to get the results of system resources monitoring graphically.

Like every software, Magento keeps building up, and if there are any troubles, you may use patches. To always get information about updates and upgrades, subscribe to Magento mailings. Patches are necessary to be set up for whatever release. To check your online store, use the special resource

If continuing development, have a code database copy in a git repository. Setting up daily backups on server protects you from problems in the future.

Have an idea?
Enter your name