Online pharmacies on Shopify: connect Farmatic with Farmasync

January 7, 2025

An online pharmacy on Shopify needs the store and its management software to exchange data under clear rules. If you use Farmatic, Farmasync is a connection option to evaluate for its specific scope: catalogue, prices, stock and orders. The project must demonstrate what it synchronises, in which direction and what happens when something goes wrong.

Farmacia online en Shopify: conectar Farmatic con Farmasync

An online pharmacy on Shopify needs the store and its management software to exchange data under clear rules. If you use Farmatic, Farmasync is a connection option to evaluate for its specific scope: catalogue, prices, stock and orders. The project must demonstrate what it synchronises, in which direction and what happens when something goes wrong.

The connection should not be presented as permission to sell any product or as a guarantee of perfect stock accuracy. Catalogue classification, applicable compliance and payment conditions require separate review. Here we focus on operations between systems.

What problem should the connection solve?

Without a defined flow, the team can end up copying prices, correcting stock and entering orders in two places. Integration aims to reduce that repetition, but each data field needs a source of truth. Start by explaining how the pharmacy works today and which tasks you want to automate.

Does Farmatic create the products published on the website?
Which prices and promotions should Shopify receive?
Which warehouse or inventory pool will be available online?
When should a Shopify order enter the management system?
Who reviews errors, cancellations and returns?

These answers should be part of the Farmasync proposal or any other connector proposal. The product name is no substitute for a verifiable description of the contracted service.

Catalogue: match the same item

Define the identifier linking the Farmatic item to the Shopify product or variant. You may need to retain both an internal code and a commercial identifier. Do not match products merely because their names look similar.

Check formats, units and duplicates with a representative sample. A single package and a multipack should not share the same stock without a rule explaining the conversion. Also decide which fields the pharmacy controls in the ecommerce store, such as photographs or marketing copy, so each synchronisation does not overwrite them.

Stock: reservations, locations and delays

Store inventory should reflect what you can actually fulfil. Review what happens when an item sells at the counter and online almost simultaneously, when a unit is reserved and when it is released. If there are several locations, define which are used and how availability is calculated.

“Automatic synchronisation” does not mean no delays or errors. Ask about frequency, alerts and recovery. A safety buffer may help for items with few units, provided it fits the commercial flow and everyone understands how it applies.

Prices and promotions

Document whether Farmatic is the source of retail prices and how its changes interact with Shopify discounts. Avoid a synchronisation undoing a campaign or applying a reduction twice.

Test case	Outcome to define
Retail price changes in the management system	Which price reaches Shopify and when.
Online discount	Whether it affects the base price, order or a separate promotion.
Product without a valid price	Whether it is blocked, unpublished or flagged for review.
Update error	How it is detected and which data is retained.

Orders: prevent duplicate entries

Decide which event sends an order to the management system. Order creation, confirmed payment and fulfilment do not mean the same thing. The integration should use an identifier that allows retries without duplicating the transaction.

Include discounts, shipping charges, taxes and payment methods in the checks. For a return, distinguish refunding money from restocking inventory. Not every product or situation follows the same process.

What not to assume about Farmasync

Before committing, confirm version compatibility, included features, support, access and recovery. Do not assume batches, expiry dates, multiple pharmacies, electronic prescriptions or carriers are covered unless they are explicitly included in the scope and tests.

Do not rely on an exclusivity claim or success story without documentation either. You need observable results in your installation, rather than a promise that the connector works identically in every pharmacy.

Permitted catalogue and personal data

Online medicine sales are regulated in Spain; Distafarma and the BOE provide references for reviewing the scope. Connecting pharmacy software does not replace the pharmacy's requirements or authorise a category on its own.

Limit data shared by each system to what is necessary, and review permissions and traceability. Do not send keys by email or messages to speed up installation. Access and connection should follow a secure, documented process.

Launch with specific tests

Review the current flow and agree which data will synchronise.
Prepare a sample and check its identifiers.
Update price and stock from the intended source.
Process a controlled order, cancellation and return.
Verify alerts and retries without duplicates.
Document who maintains each part and how to request support.

If you want to evaluate Farmasync for connecting Farmatic with Shopify, tell us which system you use and which manual tasks you need to stop doing. That information helps define a test and scope before activating the full operation.

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