· Andrei M. · Integrations · 14 min read
Connect MicroPIM to Shopify: The Complete Product Sync Playbook
Step-by-step guide to connecting MicroPIM with your Shopify store. Map fields, sync inventory, and automate daily product updates.
Shopify is one of the most capable e-commerce platforms available today. But anyone who has tried to manage a catalog of more than a few hundred products using Shopify’s native tools has run into the same wall: bulk imports are fragile, field mapping is rigid, and there is no structured way to keep product data synchronized between your internal systems and your storefront.
MicroPIM fills that gap. It acts as the central product data hub between your ERP, supplier feeds, or internal catalog and your Shopify store — handling the shopify product import integration, field mapping, inventory sync, and automation so your team manages products in one place and Shopify stays current without manual intervention.
This guide walks through every step: connecting your store, mapping fields, syncing inventory across locations, validating the integration, and automating recurring syncs so updates happen on schedule without anyone pressing a button.
Why Shopify and MicroPIM Work Well Together
Shopify’s native CSV import is designed for small-scale, one-time catalog uploads. It works for getting started. It does not work for ongoing operations where prices change, stock moves between warehouses, new variants are added, and product descriptions need to be enriched across dozens of fields before publishing.
Here is where Shopify’s built-in import falls short in practice:
Rigid CSV structure. Shopify’s product CSV format has a fixed schema. If your source data uses different field names, different variant structures, or custom attributes, you reformat the spreadsheet manually every time you run an import. For catalogs updated daily or weekly, this becomes unsustainable.
No field transformation. Shopify CSV import accepts data as-is. If your ERP stores dimensions in millimeters but your store displays centimeters, or if your supplier feed uses different category names than your Shopify collections, there is no transformation layer. You fix it in the spreadsheet.
No metafield support in bulk imports. Shopify metafields are where the real product enrichment lives — technical specs, compatibility data, care instructions, custom SEO fields. The standard CSV import does not touch metafields. You either use the Admin API manually or install a third-party app for each use case.
No inventory location awareness. Shopify supports multiple inventory locations, but the CSV import does not map stock per location. You manage location-specific inventory separately, through the admin or the API.
No sync — only overwrites. Import is destructive. Running a CSV import again to update prices means every field in the file overwrites what is in Shopify. If your team has made edits directly in Shopify that are not reflected in your source file, those edits are lost.
MicroPIM replaces all of this with a proper shopify api product import pipeline: structured field mapping, transformation rules, metafield support, per-location inventory sync, and scheduled automation that updates only what has changed.
For a broader look at how MicroPIM compares Shopify against other platforms from a product management perspective, see Shopify vs BigCommerce: Which Platform Wins with MicroPIM.
Prerequisites
Before connecting MicroPIM to your Shopify store, you need two things: a MicroPIM account with at least one product catalog configured, and a Shopify custom app with the correct API access scopes.
Shopify API Credentials
MicroPIM connects to Shopify through the Admin API using a custom app access token. To generate one:
- Open your Shopify admin and navigate to Settings > Apps and sales channels > Develop apps.
- Click Create an app, give it a name (for example, “MicroPIM Sync”), and assign it to your store.
- Under Configuration, select the Admin API access scopes your integration requires.
- Click Install app to generate the access token.
- Copy the Admin API access token — Shopify shows it only once.
The access scopes MicroPIM requires are:
| Scope | Purpose |
|---|---|
read_products, write_products | Create, update, and delete products and variants |
read_inventory, write_inventory | Sync stock levels per location |
read_locations | Map MicroPIM warehouse entities to Shopify locations |
read_product_listings | Read published product state |
write_metaobjects, read_metaobjects | Sync product metafields |
You will also need your Shopify store URL in the format your-store.myshopify.com. Use the .myshopify.com domain, not a custom domain.
MicroPIM Account Requirements
- At least one product catalog with products already imported or mapped
- Admin-level access to MicroPIM settings
- If syncing inventory: warehouse entities configured in MicroPIM
If you are setting up MicroPIM for the first time, the Getting Started with MicroPIM guide covers catalog creation, field setup, and your first product import before you proceed here.
Connecting Your Shopify Store
With your API credentials ready, navigate to the Integrations section in MicroPIM. This is where all channel connectors are managed.
[SCREENSHOT: MicroPIM integrations page with Shopify connector card highlighted]
On the Integrations page, locate the Shopify connector card and click Connect. MicroPIM opens the Shopify connection settings panel.
[SCREENSHOT: Shopify API credentials input form in MicroPIM settings]
Enter the following values in the connection form:
- Store URL: Your
.myshopify.comdomain - Admin API Access Token: The token generated in the previous step
- API Version: MicroPIM defaults to the current stable Shopify API version. Only change this if your store requires a specific version for compatibility with other apps.
Click Test Connection. MicroPIM makes an authenticated request to your Shopify store’s API and confirms that the credentials are valid and the required scopes are present. If the test fails, double-check that the access token was copied in full and that all required scopes were enabled before the app was installed.
Once the connection test passes, click Save Integration. The Shopify connector card in the Integrations list will show a green connected status.
MicroPIM retrieves your Shopify store’s locations automatically at this point and stores them for use in the inventory sync configuration covered later in this guide.
Mapping Shopify Product Fields
Field mapping is where the integration takes shape. MicroPIM’s field mapping interface lets you define exactly how each field in your MicroPIM product model translates to a field in Shopify’s product schema.
[SCREENSHOT: Field mapping interface showing MicroPIM fields mapped to Shopify fields]
Navigate to Integrations > Shopify > Field Mapping to open the mapping editor.
Core Product Fields
The following fields have direct equivalents in Shopify and are pre-mapped by default. Review them to confirm the mapping matches your data model:
| MicroPIM Field | Shopify Field | Notes |
|---|---|---|
name | title | Product title displayed in storefront |
description | body_html | Supports HTML; MicroPIM stores formatted content |
vendor | vendor | Brand or manufacturer name |
productType | product_type | Used for Shopify collections and filtering |
tags | tags | Comma-separated; MicroPIM flattens tag arrays |
slug | handle | URL handle; MicroPIM slugifies automatically |
status | status | Maps active/draft/archived states |
seoTitle | metafields_global_title_tag | SEO title override |
seoDescription | metafields_global_description_tag | SEO meta description override |
Variant Fields
Shopify’s product model separates product-level data from variant-level data. In MicroPIM, variants are child entities of the product with their own field set. The variant mapping section handles this automatically.
| MicroPIM Variant Field | Shopify Variant Field |
|---|---|
sku | sku |
barcode | barcode |
price | price |
compareAtPrice | compare_at_price |
weight | weight |
weightUnit | weight_unit |
requiresShipping | requires_shipping |
taxable | taxable |
option1, option2, option3 | option1, option2, option3 |
Shopify allows up to three option dimensions per product (for example, Size, Color, Material). If your MicroPIM variant structure uses more than three dimensions, you will need to consolidate them or create separate products per variant group. MicroPIM flags this during the mapping validation step.
Product Images
MicroPIM stores images as a structured array attached to each product and variant. The image sync sends images to Shopify in the configured display order. The first image in the MicroPIM array becomes the featured image in Shopify.
Image sync behavior is controlled by two settings in the mapping configuration:
- Overwrite existing images: When enabled, MicroPIM replaces all Shopify images on each sync. When disabled, MicroPIM only adds images that are not already present (matched by filename or URL).
- Sync variant images: When enabled, variant-specific images are linked to their matching Shopify variant records.
For catalogs where images are managed directly in Shopify (for example, by a design team that edits images in the Shopify admin), disable overwrite to avoid losing those edits on the next sync.
Metafields
Shopify metafields allow you to attach structured data to products beyond the standard schema — technical specifications, material composition, compliance certifications, compatibility information. MicroPIM maps custom product attributes to Shopify metafields using the metafield mapping section.
For each metafield mapping, specify:
- MicroPIM attribute key: The field key as defined in your MicroPIM product attributes
- Shopify namespace: The metafield namespace (for example,
custom,specifications,seo) - Shopify key: The metafield key name
- Value type:
string,integer,json,boolean,url,color,weight,volume,dimension, orrating
Metafield sync requires the write_metaobjects scope to be active on your Shopify custom app. If metafield updates are failing, verify the scope is present.
For a detailed walkthrough of managing custom product attributes before syncing to Shopify, see Product Attributes and Custom Fields in MicroPIM.
Syncing Inventory in Real-Time
Inventory sync is configured separately from product sync because inventory changes frequently — sometimes multiple times per day — while product data changes far less often. Separating the two allows MicroPIM to run lightweight inventory updates on a tight schedule without re-processing the full product payload each time.
Mapping Warehouses to Shopify Locations
MicroPIM’s warehouse entities represent your physical or logical inventory locations. Shopify uses a similar concept called locations. Before inventory sync can run, you map each MicroPIM warehouse to its corresponding Shopify location.
Navigate to Integrations > Shopify > Inventory Sync. MicroPIM displays a table with all configured MicroPIM warehouses on the left and a dropdown of Shopify locations on the right. Select the matching Shopify location for each warehouse.
If you have a warehouse in MicroPIM that does not have a corresponding Shopify location — for example, a supplier-facing or internal storage warehouse that does not fulfill online orders — leave it unmapped. MicroPIM skips unmapped warehouses during inventory sync.
For a comprehensive guide to multi-warehouse inventory management in MicroPIM before connecting to Shopify, see Multi-Warehouse Inventory Sync.
Inventory Sync Behavior
MicroPIM supports two inventory sync modes:
Set: MicroPIM sends the exact stock quantity to Shopify and replaces whatever Shopify currently shows. Use this when MicroPIM is the authoritative source for inventory.
Adjust: MicroPIM sends the delta — the difference between what MicroPIM recorded last time and what it records now. Use this when Shopify also processes orders and adjusts inventory independently, and you want to avoid overwriting those adjustments.
For most setups where an ERP or warehouse management system feeds inventory into MicroPIM, the Set mode is correct. Shopify becomes a read-only display of the inventory numbers MicroPIM provides.
Real-Time vs Scheduled Inventory Sync
MicroPIM supports two triggers for inventory sync:
Webhook-triggered sync. When a product’s inventory changes in MicroPIM (for example, an ERP pushes updated stock counts), MicroPIM can push the update to Shopify immediately, typically within seconds of the change. This requires the Shopify integration to be configured as a sync target on the relevant MicroPIM product catalog.
Scheduled sync. A cron job runs the inventory sync at a defined interval — every 15 minutes, every hour, or once per day depending on how time-sensitive your stock accuracy needs to be. Scheduled sync is covered in the automation section below.
For most businesses, scheduled inventory sync every 15 to 30 minutes provides sufficient accuracy without the infrastructure overhead of real-time webhooks. High-volume stores with fast-moving inventory should use webhook-triggered sync to avoid overselling.
Testing the Integration
Before activating the integration for your full catalog, test it against a small subset of products. This catches mapping errors, metafield configuration issues, and inventory location mismatches before they affect live listings.
Pre-Sync Validation Checklist
Use this checklist before running your first full sync:
- Connection test passes in MicroPIM Integrations settings
- All required API scopes confirmed on the Shopify custom app
- At least one MicroPIM warehouse mapped to a Shopify location
- Variant option dimensions do not exceed three per product
- Metafield namespaces and keys match what exists in Shopify (or are new — Shopify creates metafields that do not exist on first write)
- Image overwrite setting reviewed and set to intended behavior
- Test product selected with all field types populated (title, description, variants, images, at least one metafield)
Running a Test Sync
Navigate to Integrations > Shopify > Sync Now and select Selected Products rather than Full Catalog. Choose two or three products that represent different structures in your catalog — a simple single-variant product, a product with multiple variants, and a product with metafields.
Click Run Sync and monitor the sync log. MicroPIM displays each product processed, the fields sent, and any errors or warnings. Common issues at this stage:
Variant option mismatch. If a product in MicroPIM has variant dimensions that do not match the options already configured in Shopify, the sync will fail for that product. Resolve by aligning the option names in MicroPIM with the existing Shopify options, or by deleting the product in Shopify and letting MicroPIM recreate it with the correct structure.
Image upload failures. Images hosted on URLs that Shopify cannot reach (private internal servers, expired CDN links) will fail to upload. Ensure product images in MicroPIM are publicly accessible URLs or uploaded files.
Metafield type conflicts. If a metafield already exists in Shopify with a different value type than what MicroPIM is sending, Shopify rejects the write. Align the type in MicroPIM’s metafield mapping with what Shopify expects.
After a successful test sync, verify the products in your Shopify admin. Confirm that titles, descriptions, variant prices, stock quantities per location, and metafields all reflect what is stored in MicroPIM. If everything looks correct, you are ready to run the full catalog sync and configure automation.
Automating Daily Syncs
A manual sync solves the one-time import problem. The real value of the MicroPIM Shopify integration is automation: product updates, price changes, and inventory adjustments flowing from your source systems to Shopify on a schedule, without anyone initiating the process.
MicroPIM’s Automation feature uses a cron-based scheduler to run sync jobs at configurable intervals.
Configuring Automated Sync Jobs
Navigate to Automation in the MicroPIM sidebar. Click New Automation and select Shopify Product Sync as the job type.
Configure the following settings:
Sync scope. Choose between Full Catalog (resends all products every run), Changed Products (only products modified since the last successful sync), or Custom Filter (a saved product filter that defines the subset to sync). For daily operations, Changed Products is the recommended scope — it is faster, uses less API quota, and reduces the risk of accidental overwrites.
Schedule. MicroPIM uses standard cron syntax. Common schedules:
| Schedule | Cron Expression | Use Case |
|---|---|---|
| Every 15 minutes | */15 * * * * | Inventory-only sync for fast-moving stock |
| Every hour | 0 * * * * | Frequent price or stock updates |
| Daily at 2 AM | 0 2 * * * | Full product sync during off-peak hours |
| Weekdays at 6 AM | 0 6 * * 1-5 | Business-day updates aligned with ERP schedules |
Notification on failure. Configure an email address to receive alerts when a scheduled sync job fails. This ensures that a failed overnight sync does not go unnoticed until a customer reports a missing product or incorrect price.
Retry policy. MicroPIM retries failed API calls automatically — the default is three retries with exponential backoff. For Shopify rate limit errors (HTTP 429), MicroPIM respects Shopify’s Retry-After header and pauses before retrying.
Separating Product and Inventory Sync Schedules
Product data (titles, descriptions, images, metafields) changes less frequently than inventory. It is good practice to configure two separate automation jobs:
- Product sync running once daily, during off-peak hours, with Changed Products scope.
- Inventory sync running every 15 to 30 minutes, covering all mapped warehouse-to-location pairs.
This separation keeps the frequent inventory updates lightweight and ensures the daily product sync does not compete with order processing traffic on your Shopify store.
For deeper context on MicroPIM’s Automation capabilities — including how to chain sync jobs and trigger syncs from ERP webhook events — see Automate Imports and Exports with MicroPIM.
Monitoring Sync Health
MicroPIM logs every automation run in the Automation History view. Each run record shows:
- Start and end time
- Products processed, succeeded, and failed
- API calls used (relevant for Shopify’s rate limits)
- Error details for any failed products
Review automation history weekly in the early weeks after go-live. Once the integration is stable and error rates are consistently zero, monthly reviews are sufficient.
Connecting MicroPIM to Shopify moves your product operations from reactive to systematic. Instead of reformatting spreadsheets before every import and manually updating prices and stock, your catalog stays synchronized automatically — product data flows from its source, through MicroPIM’s mapping and enrichment layer, and into Shopify on the schedule you define.
The setup described in this guide — API connection, field mapping, inventory location mapping, test sync, and scheduled automation — is the same pattern used by MicroPIM customers running catalogs from a few hundred to tens of thousands of SKUs. The integration scales with your catalog without requiring changes to the configuration as your product count grows.
Ready to connect your Shopify store? Start your free 14-day trial and have your first products syncing to Shopify today.
Looking for more MicroPIM guides? Start with Getting Started with MicroPIM, learn how to save time on e-commerce product management, and explore the full integrations overview for all supported channels.
