Migrating a pharmacy to Shopify: what to check before switching

January 7, 2025

Migrating a pharmacy to Shopify requires a review of the catalogue and operations before moving data. Selling dermocosmetics or non-medicine pharmacy products is different from selling medicines. The platform, payment methods and marketing channels have their own conditions alongside applicable regulations.

Migrar una farmacia a Shopify: qué revisar antes del cambio

Migrating a pharmacy to Shopify requires a review of the catalogue and operations before moving data. Selling dermocosmetics or non-medicine pharmacy products is different from selling medicines. The platform, payment methods and marketing channels have their own conditions alongside applicable regulations.

A move can make sense when the current store makes editing, maintenance or coordination with management software difficult. Not every pharmacy needs to migrate: first demonstrate that Shopify covers the functions that support today's operations and those you want to improve.

Classify the catalogue before designing the store

Separate medicines, medical devices, cosmetics, supplements and other categories with different requirements. Do not use a general “health” label to apply the same selling and communication rules to everything. That classification should guide publishing, payments and product content.

In Spain, online medicine sales are subject to specific regulations. Royal Decree 870/2013 concerns non-prescription medicines for human use and their sale by pharmacies under its requirements. Installing an age check or notice does not turn a generic store into an authorised channel.

Before including medicines, the operator should review the project with the responsible professionals and competent authority. For non-medicine pharmacy retail, also validate requirements by product type and payment provider conditions. Technical feasibility does not replace that review.

What problem should migration solve?

A catalogue that is difficult to organise or update.
Website stock that does not match the management system.
Technical dependency for publishing campaigns and content.
Integrations without traceability or with too many manual steps.
A shopping experience that poorly explains formats, availability or delivery.

Assign a test to each problem. If the objective is to avoid selling unavailable stock, demonstrate a stock change and simultaneous purchase. If it is greater autonomy, ask the team to create a category and publish a page without development. “A more modern website” is a visual direction, but not a sufficient acceptance criterion.

Define which system controls each data field

The pharmacy may manage internal codes, EANs, prices, promotions and stock outside ecommerce. Before connecting systems, decide where each item is created and edited. If the management software is the source of truth, the website should not overwrite it without an explicit rule.

Data	Decision to settle
Product	The identifier linking both systems and how duplicates are handled.
Stock	Location, reservations, safety buffer and update frequency.
Price	Retail price source, taxes and promotions applicable online.
Order	When it is sent to the management system and how duplicates are prevented.
Return	Commercial, accounting and inventory handling according to the product.

Move data deliberately

Inventory your products, images, customers, orders and content. Review which information is worth retaining and the basis for retaining marketing permissions. Do not transfer unnecessary sensitive data into commercial fields or assume the entire history needs to be available in every tool.

Import a sample representing difficult formats, sizes and categories. Then check counts, variants, identifiers and links. Consent cannot be reconstructed by assuming someone who purchased also wants to receive campaigns.

Preserve content that already attracts visitors

The pharmacy may receive traffic through brands, categories and articles as well as products. Export pages with clicks and impressions and prepare a URL map. Preserve the intent of each useful page and plan redirects when its path must change.

Health content needs an additional review. Do not use migration to multiply clinical advice without an author and professional review. Distinguish product information, commercial content and health information, and support published claims with appropriate sources.

Payments and channels: validate before commissioning design

Being able to build a store in Shopify does not demonstrate that a payment provider accepts the entire catalogue. Shopify Payments documentation distinguishes restricted activities and products. Also check the requirements of advertising channels or marketplaces you intend to use.

If a category needs a particular provider or treatment, include that work in the scope. It is better to detect it when assessing feasibility than after completing the website.

Tests before launch

Update price and stock from the primary system.
Place a controlled order under each relevant shipping condition.
Verify payments, notifications, taxes and the order entering management.
Check cancellation and return handling by product.
Review personal data, permissions and team access.
Test old URLs, search and filters on mobile.
Document incidents, recovery and responsibilities.

A Shopify migration proposal should separate the store, data transfer and connection with pharmacy software. That scope lets you evaluate budget and dependencies without relying on generic promises of compliance or sales.

Continue working on your store

Sources and review

Editorial review: the Migraciones.io team · 30 October 2026. Features, plans and availability are checked against the linked sources.

All articles