Once a Magento Open Source store is installed, the work shifts to running it well: organising customers and orders, promotions and SEO, extensions, several store views, integrations, upgrades and troubleshooting. This page collects the best practices for those day-to-day and advanced tasks. Requirements, installation and hosting are covered in our main Magento handbook.
Our main guide, Magento Open Source for Developers and Merchants: A Complete Handbook, explains what Magento 2.4 needs, why it runs on a VPS rather than shared hosting, how to install it, and how to keep it fast and patched. Read it first.
Run the store in production mode on a VPS, change code only on a staging copy, and install extensions and updates with Composer. Use customer groups and price rules instead of custom code for pricing, set indexers to "Update by Schedule", and use the REST or GraphQL APIs for integrations. Apply Adobe's security patches promptly and test every upgrade on staging before the live store.
1. Customers, orders and returns
- Customer groups (Customers › Customer Groups) drive tax classes, catalogue prices and promotions. Create groups such as Retail, Wholesale or Staff rather than hard-coding special prices.
- The order flow is order → invoice → shipment. Invoice only when payment is captured, and create shipments with tracking numbers so customers get the update email.
- Refunds are issued as credit memos from the invoice. An online credit memo refunds through the payment gateway if its extension supports it; an offline one only records the refund.
- Taxes: set up tax classes, rates and rules to match your GST obligations, and ask your accountant how prices should be shown and invoiced.
2. Promotions and SEO
- Catalog price rules discount products before they reach the cart; cart price rules handle coupon codes, free shipping and "buy X get Y". Give every rule an end date and test it on staging.
- Upsells, cross-sells and related products are set per product and are the cheapest way to raise order value.
- Search engine friendly URLs and URL rewrites are built in. Set a meta title and description for categories and key products, keep the XML sitemap enabled, and use canonical links for categories and products to avoid duplicate content.
3. Extensions and customisation
- Install with Composer, from the vendor or the Adobe Commerce Marketplace, never from "nulled" download sites.
- Test on stagingwith
bin/magento setup:upgradeandsetup:di:compilebefore touching the live store. - Customise in your own module, using plugins, observers and preferences. Never edit files in
vendor/: an update overwrites them. - Remove what you don't use.Every module adds code to every request.
4. Several stores, APIs and headless
- Scopes: one installation can run several websites, stores and store views (for example, one per language). Most settings can be overridden per scope, so check the scope switcher before you change anything.
- APIs: Magento has REST and GraphQL APIs. Use integration tokens with the narrowest permissions for ERPs, accounting and shipping tools.
- Headless front ends use the GraphQL API with a separate front-end app. They suit teams with front-end developers; a well-tuned standard theme is simpler for most stores.
5. Upgrades and migrations
Keep a staging copy of the store, upgrade there first, then repeat on the live site with maintenance mode on. The exact commands are in the handbook's security section. After an upgrade, test search, checkout with each payment method, emails and the admin.
Magento 1 reached end of life in 2020. If you still run it, move to Magento 2 with Adobe's Data Migration Tool (data only; themes and extensions must be rebuilt) or to another platform. From WooCommerce or Shopify, migrate products, customers and orders with an import tool or extension, and set 301 redirects from old URLs.
6. Troubleshooting
- Check the logs first:
var/log/system.log,var/log/exception.logand the reports invar/report/. - After a code or config change: run
bin/magento cache:flush, and check indexers withbin/magento indexer:status. - Blank pages or 500 errors after an upgrade usually mean a module needs
setup:upgradeandsetup:di:compile, or file permissions changed. - Checkout or payment errors: test the gateway in sandbox mode on staging, and check the gateway extension's own log.
Magento 2.4 needs an OpenSearch service, Composer and a cron job every minute, which shared hosting does not provide. A Domain India VPS gives you root access and is self-managed: you install, secure, update and back up the stack yourself.
Frequently asked questions
What is the difference between catalog and cart price rules in Magento?
Catalog price rules discount products before they are added to the cart. Cart price rules apply in the cart, for coupon codes, free shipping and quantity-based offers.
Can one Magento installation run several stores?
Yes. Magento supports several websites, stores and store views in one installation, for example one store view per language, with settings overridden per scope.
How do I move from Magento 1 to Magento 2?
Use Adobe's Data Migration Tool to move products, customers and orders, and rebuild the theme and extensions for Magento 2. Test the migrated store thoroughly on staging before switching over.
Can I run Magento on Domain India shared hosting?
Not properly. Magento 2.4 needs OpenSearch, Composer and a cron job every minute, which shared hosting doesn't provide. Use a Domain India VPS, which is self-managed.
Ready to run your store properly? Read the Magento handbook, compare VPS plans, or open a support ticket if you are not sure which fits.
Root access on KVM virtualisation, with the memory a Magento store needs.
See VPS plans