PIM for Shopify: When You Need One, and How the Sync Works

Most Shopify stores do not need a PIM. Some badly need one and have not noticed, because the symptoms look like staffing problems: the same description fixed in three places, a supplier spreadsheet nobody trusts, a translated site that is always a week behind.

This post is about the Shopify side: what Shopify can hold on its own, the signs you have outgrown it, and how a PIM actually connects to it. If you are choosing between PIM products, start with choosing PIM software in 2026.

What Shopify can hold on its own

Shopify’s product model is far more capable than it was a few years ago, and for one storefront it is often enough.

• Metafields add custom fields to products, variants, collections and other resources. Merchants can create up to 256 metafield definitions per resource type.
• Metaobjects hold structured content that is not a product, such as a size guide, an ingredient or a designer profile. Stores get 128 metaobject definitions, or 256 on Plus, each with up to 40 fields and up to 1,000,000 entries.
• Category metafields come from Shopify’s Standard Product Taxonomy. Choose a category such as shirts and Shopify offers attributes like size, neckline, fabric and colour, with default values you can use or change.
• Variants: up to 2,048 per product, but still only three options.
• The bulk editor edits products, variants and their metafields in a spreadsheet-style grid.
• CSV import and export handles products and product metafields. Variant metafields are not supported in the CSV, so they go through the bulk editor or the API.
• Languages: a store can sell in up to 20 languages, or 30 on Plus, and languages can be set per market. Shopify’s Translate & Adapt app auto-translates into a maximum of two languages. Beyond that, translation is manual or comes in through another app.

If one team maintains one catalogue for one storefront, that toolkit usually does the job. The habit that matters is modelling attributes as metafield definitions rather than burying them in the description. Do that and you have much of what a small PIM would give you, and a clean starting point if you need one later.

The signs you have outgrown it

The trigger is rarely the number of SKUs. It is the number of places a product has to be right, and the number of people who touch it on the way. One of these on its own is manageable. Two or three together usually mean you are already paying for a PIM in staff time and errors, without getting one.

Several channels. Your Shopify store, a marketplace, a retailer’s feed and a printed catalogue all need the same product, each in a slightly different shape. Shopify is a good source for its own storefront and an awkward one for everyone else’s.

Many suppliers. Data arrives as spreadsheets in a dozen formats. Someone cleans and merges them by hand before anything reaches Shopify, and that person has become the bottleneck.

Rich attributes. Specifications, compliance data, dimensions, compatibility. Shopify can store them as metafields. A PIM adds the governance around them: each product family has its own required attributes, and a product is not ready for a channel until they are complete.

Translations. Twenty languages is plenty of room. The work is keeping them in step when products change every week. A PIM holds each language as its own value with its own completeness check, and the connector pushes it to Shopify. Shopify’s translations API covers metafields and metaobjects as well as core product fields, provided the metafields are publicly accessible.

B2B catalogues. Since 2 April 2026, B2B basics have been available on Shopify’s Basic, Grow and Advanced plans, not just Plus, with up to three active B2B catalogues outside Plus and unlimited catalogues on it. A catalogue decides which products and prices a trade customer can access. The data trade buyers expect, such as carton quantities, spec sheets and technical attributes, still has to be mastered somewhere.

Approval workflows. If legal, compliance or a brand team has to sign off copy before it goes live, that is a workflow, and PIMs are built around one. Run it inside Shopify and it tends to become draft products and a long message thread.

How a PIM to Shopify sync works

The main vendors’ connectors share one pattern: the PIM pushes, Shopify receives.

• Akeneo builds the Akeneo App for Shopify, listed for its SaaS packages. It syncs products, variants, metafields and media from Akeneo into Shopify, with secondary locales and market prices as options. Syncs run manually or on a schedule from hourly to monthly, as the full catalogue or as a delta of changes. Product status maps across, enabled to Active and disabled to Draft. Deletions do not sync either way: a product deleted in one system has to be deleted by hand in the other.
• Salsify builds its own Shopify app, which publishes product content from Salsify into Shopify, including core and custom metafields.
• Inriver announced its own Shopify adapter in November 2025. It publishes product content from Inriver to Shopify, and Inriver says metaobjects can be managed alongside products.
• Pimcore: the connectors we looked at are built by partners. Hamari Agency’s app on the Shopify App Store syncs products, variants, collections, attributes and metafields from Pimcore to Shopify. Webkul sells a connector bundle installed on the Pimcore side.

If no connector fits, or the PIM’s data has to pass through middleware first, the answer is a custom Shopify app. Since 1 January 2026, new custom apps are created in the Dev Dashboard rather than in the Shopify admin.

Whichever route you take, the connector is rarely the hard part. The mapping is. Every PIM attribute has to land somewhere specific in Shopify: a core field, one of the three options, a metafield definition, or a metaobject. A PIM product family with four variant axes has to be reshaped, because Shopify will not take a fourth option. Every product also needs one identifier both systems agree on, or the sync creates duplicates.

What stays in Shopify, and what the PIM owns

The rule we work to: every field has one owner, and nothing is edited in two places.

The PIM owns product content. Titles, descriptions, attributes, specifications, media, translations and the relationships between products.

Shopify owns what happens around the sale. Orders, customers and checkout live in Shopify. Inventory lives there too, often fed from an ERP or warehouse system. Price usually belongs to the ERP or to Shopify, including market prices and B2B catalogue pricing.

Some connectors blur the line. Akeneo’s app can sync market prices, and by default it maps product status as well. Either can be the right call, as long as it is a decision. If the PIM owns price, nobody changes price in Shopify. If Shopify owns it, switch the price sync off.

The failure we see most is a quiet one. A one-way sync overwrites whatever it owns, so a merchandiser who fixes a description in the Shopify admin finds it reverted after the next sync. Tell the team which fields are now read-only in Shopify before go-live, not after the first complaint.

Where to start

List every product field, who edits it today and where. Then decide who should own each one. Only then choose the PIM, because the ownership map tells you which features you need and which connector questions to ask.

Our Shopify-certified developers implement and integrate PIM platforms, model the attributes, and map them into Shopify. More on our PIM implementation work and our Shopify development work.

---

Sources: Shopify developer docs on metafield limits, metaobject limits, translated content and the 2,048 variant limit; Shopify Help Center on product CSV files, languages, Translate & Adapt, B2B plan features and custom apps; Akeneo App for Shopify synchronisation; and the Salsify and Pimcore PIM Connector listings on the Shopify App Store.