CMS / SHOPIFY
Shopify: Complete Guide to the Ecommerce Platform, Online Store & CMS
Shopify is a hosted commerce platform for creating, managing and growing online stores, with product management, themes, checkout, ecommerce tools, apps, APIs and international selling capabilities.
This guide uses Shopify’s own terminology accurately, with honest comparisons and no invented plan limits or pricing.
- Products, variants, collections, metafields and metaobjects
- Themes, Liquid, sections, blocks and the theme editor
- Checkout, Markets, SEO, apps, APIs and headless commerce
Checkout is the part Shopify controls most tightly and customises least. That constraint is also why it works so reliably.
THE BASICS
What Is Shopify?
Shopify is a hosted commerce platform. It provides a product catalogue, a storefront built from themes, a checkout, order and customer management, payment processing, shipping tools, an app ecosystem, APIs and tools for selling internationally — all on infrastructure Shopify runs.
Describing it as “WordPress for ecommerce” misses what it is. Shopify is commerce-first: the data model is built around products, variants, orders and customers, and content management exists in service of selling. It has pages and a blog, and they are supporting features rather than the point.
The thing that most distinguishes Shopify is checkout. Shopify owns the checkout flow, hosts it, secures it and handles payment processing. You get limited customisation in exchange for a flow that is tested, fast, PCI-compliant and familiar to shoppers. For most merchants that is the right trade — a broken checkout costs more than a bespoke one gains.
That same pattern runs through the platform: less control, less responsibility. No servers to patch, no PCI scope to manage, no plugin conflicts breaking a payment gateway. In exchange you work within one company’s platform, its pricing and its roadmap, and the store cannot be moved elsewhere as a working store.
On plans and limits: Shopify’s pricing, transaction fees, checkout customisation, API limits and feature availability vary by plan and change. Check shopify.com rather than any article’s figures.
What Shopify provides
PRODUCT: RUNNING SHOES
Each variant carries its own price, SKU, barcode and inventory. Options multiply, so six variants here — which grows quickly with a third option.
CATALOGUE
The Admin, Products and Variants
The Shopify admin is where a store is run: Products, Orders, Customers, Analytics, Marketing, Discounts, Content, Online Store, Apps, Markets and Settings. Apps add their own areas, and the navigation evolves, so treat any described layout as indicative.
A product is a sellable item in the catalogue, carrying a title, description, media, product category, tags, collections, SEO fields and status.
A variant is a specific configuration of that product. Options such as colour and size combine into variants, and variant-level data is where the commercially important fields live — price, SKU, barcode, weight and inventory all sit on the variant, not the product.
This distinction matters more than it first appears. Running Shoes is one product; Black/Size 9 is the variant a customer actually buys, the thing inventory is counted against and the thing that goes out of stock. Modelling a catalogue badly here — separate products where variants belong, or variants where separate products belong — causes problems in merchandising, inventory and SEO that are tedious to unpick later.
A useful rule: if customers would compare the options on one page before choosing, they are variants. If they would search for them separately, they are probably separate products.
Inventory is tracked per variant and can be tracked per location, supporting multiple warehouses or stores. Tracking, low-stock handling and overselling behaviour all depend on configuration rather than happening automatically.
ORGANISATION
Collections and Product Categories
These two get confused constantly, and they do entirely different jobs.
A collection is a merchandising group — New Arrivals, Men’s Shoes, Summer Sale, Under £50. Collections create browsable pages with their own URLs and are how customers navigate a store. A product can belong to many.
Collections can be manual (you choose each product) or automated (products join when they match conditions such as tag, price, type or stock level). Automated collections are the better default for anything rule-based — a Sale collection that maintains itself beats one somebody forgets to update.
A product category is a standardised classification from Shopify’s product taxonomy, describing what the product is. One per product. It drives attributes, filtering and how products are understood by sales channels and marketplaces — it is not a navigation feature and does not create a page.
Put simply: a category describes the product; a collection groups products for shoppers. A shoe’s category is a classification fact. Whether it appears in Summer Sale is a merchandising decision.
Manual vs automated collections
- Manual — you pick each product. Suits curated edits.
- Automated — products join by matching conditions.
- Conditions can use tag, type, vendor, price, stock and more.
- Automated collections maintain themselves as the catalogue changes.
├── Material → metafield (text)
├── Care instructions → metafield (rich text)
├── Technical specs → metafield (JSON)
├── Size guide → reference → METAOBJECT
└── Brand → reference → METAOBJECT
METAOBJECT: SIZE GUIDE
├── Title
├── Measurement table
├── Fit notes
└── Diagram image
Defined once. Referenced by every product it applies to.
METAOBJECT: BRAND
├── Name
├── Logo
├── Story
└── Country of origin
CUSTOM DATA
Metafields and Metaobjects
Shopify’s built-in fields cover standard commerce. Metafields and metaobjects cover everything specific to your business, and together they are what let Shopify model catalogues it was not designed for out of the box.
A metafield is custom structured data attached to a supported resource — a product, variant, collection, customer, order, page and others. Material on a garment, wattage on an appliance, ABV on a drink. Metafields have defined types including text, rich text, number, date, boolean, file, colour, measurement, JSON and references to other resources.
A metaobject is a reusable structured content object that exists independently and is referenced where needed. A size guide, a brand profile, an ingredient, a store location, a care-instruction set.
The difference is reuse. A metafield belongs to one record; a metaobject is defined once and referenced by many. Material belongs on the product — metafield. A size guide shared by forty products belongs in one place — metaobject, referenced by all forty, so correcting it corrects everything.
Both become available in themes through Liquid, so custom data appears on the storefront with the design you build for it. This is the mechanism serious Shopify stores use to display specifications, comparisons and structured attributes properly.
Worth planning before building a catalogue. Retrofitting structured data onto hundreds of products already created is considerably more work than defining it first.
STOREFRONT
Themes, Sections, Blocks and Liquid
A theme controls storefront presentation: layout, typography, colour, templates for products and collections, navigation and responsive behaviour. It does not change commerce functionality — products, checkout and orders work the same whichever theme is active.
The theme editor is where merchants customise visually. Its structure comes from sections and blocks.
A section is a configurable area of a page — a hero, a featured collection, an image-with-text band. Sections can be added, reordered and configured. A block is a smaller configurable piece inside a supported section — a heading, a paragraph, a button within that image-with-text band.
Which sections and blocks exist depends on the theme. Two themes can expose completely different settings, which is why theme-specific instructions often will not match what you see.
Liquid is Shopify’s templating language. It receives store data — products, collections, cart, customer, metafields — and determines the markup rendered. Theme development combines Liquid with HTML, CSS, JavaScript and JSON configuration, organised into templates, sections, snippets and assets.
Modifying a theme is where most Shopify technical debt originates. Edits made directly to a theme’s files are lost when the theme updates, so serious customisation belongs in a tracked, version-controlled workflow rather than the code editor in the admin.
Sections are reorderable page areas. Blocks are configurable pieces inside them. Which blocks a section accepts depends on how the theme defines it.
Theme structure
- Templates — per page type, often JSON
- Sections — configurable page areas
- Blocks — pieces within sections
- Snippets — reusable Liquid fragments
- Layout — the wrapper around every page
- Assets — CSS, JavaScript and images
COMMERCE OPERATIONS
Cart, Checkout, Orders and Store Operations
Navigation in Shopify is menu-based, linking to collections, products, pages and policies. Menu structure is also site architecture — how customers browse and how search engines understand the store’s organisation. See our technical SEO guide.
Search and discovery covers storefront search, collection filtering and product recommendations. Filters typically derive from product attributes, options and metafields — which is another reason structured custom data is worth planning early.
The cart holds selected variants with quantities, showing pricing and applicable discounts before checkout. It is session-based, which is why cart content resists caching in ways static pages do not.
Checkout is where Shopify’s model is most distinctive. Shopify hosts and controls it, handling customer information, shipping selection, taxes, discounts, payment and order creation. Customisation is deliberately limited and varies by plan. That constraint is why Shopify checkout is reliable, fast and PCI-compliant without you managing any of it.
Orders record what was bought, by whom, for how much, with payment and fulfilment status. Order management covers fulfilment, partial fulfilment, tracking, refunds, returns and customer notifications.
Customers have profiles with order history, addresses, marketing consent and optional accounts. Customer data carries privacy obligations — what you collect, how you store it and what consent you have are your responsibility regardless of platform.
Payments are processed through Shopify Payments where available or third-party gateways. Availability varies substantially by country, and so do fees. Check what is available in your region rather than assuming.
Shipping covers zones, rates, carriers, local delivery and pickup, all configuration-dependent. Taxes have tools and automatic calculation in supported regions — and the obligation to charge and remit correctly remains the merchant’s. Shopify provides calculation, not tax advice.
Discounts include codes and automatic discounts applied at cart or checkout, with conditions by product, collection, customer or order value.
SEO
Shopify SEO: Products, Collections and Technical Issues
Shopify provides SEO infrastructure: editable titles and meta descriptions, automatic sitemaps, canonical tags, a redirect manager, robots.txt control and clean URLs. It does not make a store rank. Content, relevance, competition and implementation decide that. See our website SEO guides.
Product SEO rests on something unglamorous: write your own descriptions. Supplier copy appears identically on every store selling that item, which is the single most common reason product pages fail to rank. Add titles that match how people search, real alt text on images, and specifications through metafields.
Collection SEO is routinely neglected. Collection pages often target broader, more valuable queries than individual products, and most ship with empty descriptions. Writing genuine content on your main collection pages is usually higher-value work than optimising another product.
Several technical issues are Shopify-specific and worth knowing:
Variant URLs can generate parameter URLs for each selection. Filtered collection URLs multiply quickly — a collection with four filters produces many combinations, and deciding what should be indexable matters. Discontinued products need a deliberate decision: redirect to a relevant collection, or leave a 404. Silently deleting products that had links and rankings wastes them.
Structured data for products typically comes from the theme, and quality varies. Verify what your theme actually outputs rather than assuming it is complete. See our schema markup guide.
Shopify SEO checklist
- Unique product titles and meta descriptions on priority products
- Collection titles and descriptions written, not left empty
- Product descriptions written for shoppers, not copied from suppliers
- Image alt text on product media
- Variant URL parameters reviewed for canonical handling
- Filtered collection URLs checked for indexability
- Redirects set for discontinued or renamed products
- Internal links between related products and collections
- Structured product data verified in theme output
- Pagination on large collections reviewed
- Out-of-stock product handling decided deliberately
- Core Web Vitals measured with real-user data
[ ] Unique product titles and meta descriptions on priority products [ ] Collection titles and descriptions written, not left empty [ ] Product descriptions written for shoppers, not copied from suppliers [ ] Image alt text on product media [ ] Variant URL parameters reviewed for canonical handling [ ] Filtered collection URLs checked for indexability [ ] Redirects set for discontinued or renamed products [ ] Internal links between related products and collections [ ] Structured product data verified in theme output [ ] Pagination on large collections reviewed [ ] Out-of-stock product handling decided deliberately [ ] Core Web Vitals measured with real-user data
INTERNATIONAL
Shopify Markets and International SEO
Markets is how Shopify manages selling to different countries and regions. A market defines which countries it covers and can carry its own currency, languages, pricing adjustments, product availability, domain or subfolder, and localised content.
This matters for international SEO because Shopify’s documentation describes configured Markets as handling technical elements automatically — hreflang annotations, canonical URLs, sitemaps and crawler access across localised URLs.
That automation is configuration-dependent, and the distinction is important. It applies to how your markets, domains, languages and localised content are actually set up. A store with Markets half-configured, inconsistent domain structure or untranslated content does not have working international SEO because the feature exists. The automation handles plumbing correctly once the structure beneath it is correct.
The URL structure decision comes first: country-specific domains, subdomains or subfolders, each with different implications for authority and management. Make it deliberately, because changing it later means redirecting everything.
Multilingual selling uses translated storefront content, product information and metadata, with a language selector. Translation depth and tooling depend on Shopify’s current features and the apps you use. Machine translation left unreviewed produces product pages that read poorly in every language — worth budgeting for properly.
Before installing an app
- What permissions is it requesting, and why?
- Is it actively maintained, with recent updates?
- Does it duplicate something already installed?
- What does it add to every page load?
- What happens to your data if you uninstall it?
EXTENDING SHOPIFY
Apps, APIs, Headless and Shopify Plus
Apps extend Shopify — reviews, email marketing, subscriptions, loyalty, shipping, analytics, product discovery, SEO tooling. They are how most stores get functionality beyond the core platform.
Two things to weigh. Permissions: apps request access to store data, sometimes including customer and order information, so read what you are granting. And performance: many apps inject scripts into every storefront page. Not every app is heavy, but accumulated apps are the most common cause of a slow Shopify store. Audit what is installed, remove what you stopped using, and check that uninstalling actually removes its code.
Shopify provides APIs for building beyond the platform. The Storefront API is a GraphQL API for custom shopping experiences, supporting product and collection browsing, cart and checkout workflows. The Admin API handles store management and data operations. Webhooks notify external systems when events occur. See our website APIs guide.
Headless Shopify uses these APIs so Shopify handles commerce while a separate frontend renders the store. Hydrogen is Shopify’s React-based framework for building such storefronts — one option among several, not a requirement for going headless.
Headless buys frontend freedom and costs real complexity: a frontend application to build, host, deploy and maintain, plus rendering, caching and SEO decisions the theme layer handled for you. It suits organisations with development capacity and specific requirements. For most stores a well-built theme is the better answer.
Shopify Plus is the enterprise offering, aimed at larger merchants with higher volumes, more automation, deeper integration and multi-store international operations. Not every large business needs it; the question is whether specific requirements justify it.
STORE QUALITY
Performance, Security, Accessibility and Content
Performance
Shopify handles hosting, CDN and image serving. Page weight is yours — oversized product images, accumulated apps, heavy theme code and third-party scripts are the usual causes of slow stores. Measure before optimising. See Core Web Vitals.
Security
Shopify handles infrastructure, HTTPS and PCI compliance for checkout — a substantial burden removed. What remains yours: staff account security and two-factor authentication, which permissions each person holds, what apps can access, and any custom code. No platform is completely secure.
Accessibility
Depends on your theme, apps, custom code and content. Semantic headings, alt text on product images, keyboard-operable variant selectors, contrast and form labels all matter — and an inaccessible checkout path costs sales directly. See website accessibility.
Pages and Blog
Shopify has static pages and a blog for About, Contact, policies, buying guides and content marketing. Useful supporting infrastructure, and lighter than a dedicated CMS — content-heavy stores sometimes pair Shopify with something else for editorial.
COMPARISONS
Shopify Compared With Other Platforms
These describe differences rather than declaring winners. Each platform suits some businesses and not others.
Shopify vs WooCommerce
The ecommerce comparison that matters most. The trade is managed commerce against ownership and control. Shopify handles hosting, security, PCI compliance and checkout; WooCommerce on WordPress gives unlimited customisation, no transaction fees beyond your gateway, and complete responsibility for keeping a payment-handling site secure and running. That last part is a real job.
Shopify vs Wix, Webflow and Squarespace
Wix, Webflow and Squarespace all sell, and commerce is one capability among many. Shopify’s catalogue modelling, checkout and commerce app ecosystem go deeper. For a few products alongside a brochure site, a general builder is often simpler; for a store where selling is the business, Shopify’s depth earns itself.
Shopify vs Joomla and Drupal
Joomla and Drupal are content management systems with commerce available through extensions. They model arbitrary content with granular permissions on infrastructure you control. Shopify models commerce natively with none of that overhead. A content-led organisation that also sells, and a store that also publishes, point in different directions.
Shopify vs WordPress with Elementor and WooCommerce
Three distinct layers on one side, worth naming precisely. WordPress is the CMS. Elementor is a third-party visual page builder plugin, not part of WordPress Core. WooCommerce is a separate ecommerce plugin, also not WordPress Core. Three pieces from different vendors, each with its own updates and compatibility.
That stack gives you a full CMS, visual page design and ecommerce, with complete ownership and no transaction fees beyond your gateway. It also means you own hosting, security, PCI scope, updates and the compatibility between three moving parts — on a site handling payments.
Shopify gives you commerce infrastructure, hosted checkout and PCI compliance handled, at the cost of platform dependency, subscription and transaction fees, and lighter content management.
The practical question is not which is better but what you want to be responsible for. A team with development capacity that values ownership will find the WordPress stack worth the work. A merchant who wants to sell rather than maintain a platform usually will not.
FIT
When Can Shopify Be a Good Fit?
Shopify can be considered when a business’s shape matches what the platform does well. Fit is the honest question rather than ranking.
Product-Based Selling
Where physical or digital products are the business.
Growing Stores
Where order volume is rising and reliability matters more than control.
International Selling
Where Markets, currencies and localisation are genuine requirements.
Integrated Checkout
Where a tested, compliant checkout is worth more than a custom one.
App-Driven Needs
Where subscriptions, reviews or loyalty come from the ecosystem.
Lean Teams
Where nobody wants to maintain hosting, security and PCI scope.
And where a project needs closer evaluation:
Unusual Commerce Logic
Pricing, bundling or fulfilment rules the platform does not model.
Content-Led Businesses
Where editorial depth outweighs catalogue depth.
Self-Hosting Requirements
Where data residency or infrastructure control is mandatory.
Platform Dependency
Where the inability to move the store is unacceptable.
Thin Margins at Volume
Where subscription and transaction costs need modelling carefully.
Complex Integrations
Where specialised systems must connect deeply.
Two considerations deserve weight. Platform dependency: a Shopify store cannot be moved elsewhere as a working store — product and customer data can be exported, but the store is a rebuild. And cost at volume: subscription plus transaction costs scale with revenue in a way self-hosted software does not, which is worth modelling against your actual margins rather than assuming either direction.
Fashion
Electronics
Jewellery
Beauty
Home & Furniture
Food & Drink
Digital Products
Subscriptions
B2B
D2C Brands
Wholesale
International
OPERATIONS
Migration, Maintenance and Troubleshooting
Migrating to Shopify — from WooCommerce, Magento, Wix, Squarespace or custom systems — is a rebuild with a data transfer inside it. The theme is built fresh; products, customers and content are migrated.
Three things reliably cause trouble.
Product data rarely maps cleanly. Variant structures, custom attributes and category systems differ between platforms. Expect to remodel rather than import, and decide where custom attributes become metafields before you start.
Customer and order history has limits. Not everything transfers directly, and passwords never do — customers typically reset. Historical order data may import partially or not at all depending on the source. There are privacy obligations around migrating customer data that are worth confirming rather than assuming.
URL mapping is the step that costs most when skipped. Shopify’s URL structure differs from other platforms, so most URLs change. Without a redirect for every product, collection and content URL, you lose accumulated search visibility and break every external link. Build the map before launch, not after.
On maintenance: hosted infrastructure removes server maintenance, not store maintenance. Product data ages, collections drift, apps accumulate, descriptions need writing, redirects need adding and checkout needs testing after changes. A store is an operation, not a project that finishes.
These are possible causes rather than diagnoses. The same symptom frequently has several causes.
Maintenance checklist
- Product data and descriptions kept current
- Inventory levels accurate across locations
- Collections reviewed as the catalogue changes
- SEO metadata set on new products and collections
- Unused apps removed
- Theme changes tested on a duplicate before publishing
- Performance measured periodically
- Orders and fulfilment running cleanly
- Redirects maintained for discontinued products
- Analytics reviewed
- Markets and translations kept in sync
- Staff accounts and permissions reviewed
- Full checkout tested after any significant change
[ ] Product data and descriptions kept current [ ] Inventory levels accurate across locations [ ] Collections reviewed as the catalogue changes [ ] SEO metadata set on new products and collections [ ] Unused apps removed [ ] Theme changes tested on a duplicate before publishing [ ] Performance measured periodically [ ] Orders and fulfilment running cleanly [ ] Redirects maintained for discontinued products [ ] Analytics reviewed [ ] Markets and translations kept in sync [ ] Staff accounts and permissions reviewed [ ] Full checkout tested after any significant change
REFERENCE
Shopify Core Concepts at a Glance
Shopify’s vocabulary is precise, and using it correctly makes documentation, apps and developer resources considerably easier to follow.
Model the Catalogue First
Products, variants and custom data before building.
Use Variants Correctly
Compared on one page means variants, not separate products.
Plan Metafields Early
Retrofitting structured data is far more work.
Write Original Descriptions
Supplier copy appears on every competitor's store.
Fill in Collection Content
Collection pages often target the better queries.
Audit Installed Apps
Each adds scripts and permissions.
Redirect Discontinued Products
Never delete a ranking URL silently.
Test Theme Changes
On a duplicate theme, before publishing.
Test Checkout Regularly
A broken checkout is invisible until revenue drops.
FAQ
Shopify: Frequently Asked Questions
Short answers to the questions people ask most about Shopify as a commerce platform, store system and development environment.
NEXT TOPICS
Related CMS and Ecommerce Topics
Each platform trades control, commerce depth, hosting responsibility and portability differently. Which suits a business depends on the business.
WordPress
A self-hosted CMS where commerce comes through WooCommerce.
Joomla
An open-source CMS with hierarchical content and granular access control.
Drupal
An open-source CMS built around arbitrary content modelling.
Webflow
A hosted platform with precise design control and lighter commerce.
Wix
A hosted builder with commerce as one capability among many.
Squarespace
A hosted builder with design templates and integrated selling.
Framer
A design-led site builder with a visual canvas and publishing.
Schema Markup
Product structured data and what it does for search results.
Explore the CMS and Ecommerce Landscape
Continue exploring CMS platforms, hosting, website development, SEO, performance and ecommerce topics.