E-commerce Connectors Perfion Webshop Sync Guide
Feed every webshop from the product record: Shopify, BigCommerce, Magento and Sana Commerce, each with its own assortment and field mapping, synchronised on a schedule, in every market and language, with a clear result for every product.
A Perfion connector synchronises product data to Shopify, BigCommerce, Magento or Sana Commerce. A channel decides what each shop sells, with products related to its channel nodes, and a mapping links each Perfion feature to its field in the shop. The connector reads the channel from the E-commerce API and keeps the shop up to date with full and delta synchronisation runs, sending translations, market prices and metafields from the same record.
At a glance
- Perfion name
- E-commerce connectors, channels and mappings
- Where
- Channels are managed in the Perfion web client; each connector runs beside its shop platformChannelsMappingsSynchronisationEach connector is a licensed module in the Perfion licence
- Used by
- E-commerce, product data and marketing teamsContent is kept in Perfion and sent to each shop by its connector
- Works with
- Localizable featuresImagesLanguages
- Four standard connectors
- 4 standard e-commerce connectors, each a licensed moduleSShopifyBBigCommerceMMagentoSSana Commerce
How Perfion feeds a webshop, from the record to the live shop
A connector is chosen for the shop platform, the channel decides what the shop sells, the mapping decides where each value goes, and scheduled runs keep the shop current, with a result for every product.
Pick the connector
Perfion has a standard connector for Shopify, BigCommerce, Magento and Sana Commerce. Each is a licensed module in the Perfion licence.
Build the channel
A channel holds what the shop sells: channel nodes arranged like the shop, with products related to each node.
Map the fields
A mapping links each Perfion feature to its field in the shop. Fields left unmapped stay with the shop or its other apps.
Synchronise on a schedule
The connector reads the channel from the E-commerce API and keeps the shop up to date with full or delta synchronisation runs.
Read the results
Sync messages show what happened to each product, and the Magento connector lists its batches with warnings and errors.
Manual uploads vs Perfion connectors: what changes when shops are fed from the record
Manual uploads copy product data into each shop by hand, file by file. Perfion connectors send each shop its own view of the one product record, on a schedule.
| Task | Uploaded by hand | Perfion e-commerce connectors |
|---|---|---|
| What the shop sells | A spreadsheet of products kept for each shop. | Products related to the nodes of a channel. |
| Product content | Exported, pasted or uploaded file by file. | Read from the product record through a mapping. |
| Variants | Sizes and colours entered again in every shop. | Variant dimensions added, renamed and translated by the connector. |
| Languages | Translations typed into each shop’s admin. | Translated values sent from localizable features. |
| Prices by country | A separate price sheet for each market. | A fixed price for each Shopify Market, mapped from Perfion. |
| Changes | Re-uploaded when someone remembers. | Sent on a schedule by delta synchronisation. |
| Other apps | Overwritten by the next bulk upload. | Fields that are not mapped are left alone. |
| Problems | Found by customers, or by returns. | Sync messages for each product; batch warnings in Magento. |
See how your own webshops would be fed from Perfion.
See it for your webshop →Perfion E-commerce Connector capabilities: eight ways to keep every webshop right
Each capability shows what it does in Perfion and what it is worth to the business.
Operational Reality (Capabilities)
Perfion has a standard connector for each of four e-commerce platforms, and each is a licensed module that must be included in the Perfion licence. The Shopify and BigCommerce connectors run as a hosted service on a Microsoft IIS website. The Magento connector works with Adobe Commerce as well and is downloaded in Magento after the licence is bought. The Sana Commerce connector has versions for Sana Commerce Cloud and for on-premise Sana. The connectors read the channel’s products from the E-commerce API; for the hosted connectors, the Perfion API must run on a secure HTTPS address.
- A licensed module for each platform
- Shopify and BigCommerce as a hosted service
- Magento with Adobe Commerce; Sana in the cloud or on premise
Executive ROI Value
The business connects its shops with a standard, maintained connector instead of commissioning and maintaining its own integration.
- Standard
- Maintained
Operational Reality (Capabilities)
In the Channels section of the web client, a channel is managed as a structure: channel nodes are added, deleted, reordered and arranged into hierarchies, and each node carries its own metadata. The items related to the selected node are shown beside the structure, and their data can be edited there with the same tools as anywhere else in Perfion. Removing an item from a channel node only removes the relationship between the item and the node: the item and its data are not affected.
- Nodes added, reordered and arranged in hierarchies
- Metadata on each channel node
- Removing an item removes only the relationship
Executive ROI Value
What each shop sells is decided in Perfion, beside the product data, and taking a product off a shop never deletes it from the record.
- One assortment
- Nothing lost
Operational Reality (Capabilities)
The Shopify connector updates products and collections, filled from Perfion categories through its category mapping. It can add, delete, rename, reorder and translate variant dimensions, and it synchronises images to products and variants, including images shared by several variants. The Magento connector creates attributes from their settings in Perfion and checks them against Magento’s restrictions, builds configurable products, and keeps categories in the order they have in Perfion. It recognises products by a unique Perfion identifier instead of the SKU, so a changed SKU does not break the link. The BigCommerce connector maps products, variants and categories, and sets the first image as the thumbnail when none is set.
- Shopify collections and variant dimensions
- Magento attributes, configurable products, category order
- Magento products recognised by Perfion identifier, not SKU
Executive ROI Value
The shop’s catalogue, from categories down to each size and colour, is built from the same record as every other channel.
- Same catalogue
- No re-entry
Operational Reality (Capabilities)
Perfion features fill the fields each platform uses for specifications. In Shopify, the connector fills metafields of many kinds: rich text from Perfion rich text features, files, money using Perfion units and currency, dimension and volume, and product references mapped from Perfion related products. Collection references can be used with the category mapping. In Magento, the connector supports multi-select, boolean, decimal and image attributes, and localizable multivalue features.
- Shopify rich text, file, money, dimension and volume metafields
- Product references from Perfion related products
- Magento multi-select, boolean, decimal and image attributes
Executive ROI Value
Technical specifications reach the shop as structured fields that shoppers can read and filter, not as a block of pasted text.
- Structured specs
- Searchable
Operational Reality (Capabilities)
Values from localizable features are sent as translations. In Shopify, the connector translates product content, variant dimensions, SEO titles and descriptions, including those of collections. A Market mapping on products and variants decides which Shopify Markets each one is published to, and a price can be set for each market. In Magento, localised values go to the store views set by the language deviation mapping; images can differ by store view, with alt text following the same localisation, and category images can be set for specific store views.
- Translated content, variants and SEO in Shopify
- Shopify Markets and a price for each market
- Magento store views, with localised images and alt text
Executive ROI Value
The business sells in a new country or language from the record it already maintains, instead of building a separate copy of the shop’s content.
- New markets
- One record
Operational Reality (Capabilities)
The connectors carry more than descriptions. The Shopify connector can update inventory quantities for each location, set product status, including Unlisted, which hides a product from search, collections and sales channels while keeping it reachable by its direct address, and schedule publishing to the Online Store for products and collections. The Magento connector imports stock, including Multi-Source Inventory, handles related, cross-sell and up-sell products and custom relations, and generates URL rewrites for categories and products, with a check for duplicate URL keys.
- Shopify inventory by location and scheduled publishing
- Shopify Unlisted status, reachable by direct address
- Magento stock, cross-sell and up-sell, URL rewrites
Executive ROI Value
Launches, stock levels and cross-selling follow the product record, so a product goes on sale with everything a shopper needs to buy it.
- Launch on time
- Sell more
Operational Reality (Capabilities)
The connectors keep the shop up to date with full and delta synchronisation runs. The Shopify connector runs at an interval in minutes or at set times using Cron expressions, updates products and collections in parallel, handles translations and metafields in batches, and waits and retries when it reaches Shopify’s API rate limits. If the E-commerce API returns an error, the synchronisation handles all products or none. The Magento connector fetches and processes batches for all channels on a schedule, and during a full run it can remove or disable products that are no longer in Perfion.
- Interval or Cron schedule in Shopify
- Waits and retries at Shopify rate limits
- All products or none if the E-commerce API errors
Executive ROI Value
Changes made in Perfion reach every shop on a known rhythm, without anyone exporting, uploading or checking that a file went through.
- No uploads
- Known rhythm
Operational Reality (Capabilities)
Old sync messages for a product are cleared when it synchronises without errors or warnings, in the Shopify and BigCommerce connectors, so a message that remains points to a current problem. In Magento, batches show a filterable level, a summary of warnings and errors, and up to five distinct errors for a failed batch; a mapping problem skips only the attribute concerned, with a warning naming it, and exceptions can be sent by email. The connectors also share the shop: fields that are not mapped are left for other apps to manage, the Shopify connector can be limited to deactivating or deleting only products that come from Perfion, and Magento can hold products not managed in Perfion.
- Messages cleared once a product syncs clean
- Magento batches with warnings and errors
- Unmapped fields and non-Perfion products left alone
Executive ROI Value
The team sees exactly which products need attention, and the shop’s other apps keep working alongside Perfion.
- Clear results
- Shared shop
5 Core Concepts of E-commerce Connectors in Perfion
The first decides what each shop sells and the second how each value reaches it. The third settles who owns each field, the fourth takes one record into every market, and the last runs the shop on a rhythm you can read.
-
Concept 01 · What each shop sells, kept in Perfion
Decide What Each Shop Sells in Perfion
The product data problem it solves
Each shop has its own product spreadsheet. A new gift set is added to the dealer webshop list but not to the consumer store, and a discontinued kettle is still on sale online three months after the factory stopped making it.
The concept explained
A channel is the shop’s structure and assortment, kept in Perfion: channel nodes arranged like the shop’s navigation, with metadata on each node and products related to them. The products are not copied into the channel; each node points to the one product record. Adding a product to a node puts it in that shop, and removing it from the node removes only the relationship, so the product and its data stay exactly as they were.
Everyday analogy
A shop window. The stock is in one warehouse; each window is arranged to show the pieces chosen for it.
BPAS method · toolDeploy EnterpriseDesign before configurationThe data model is designed and signed off before anything is configured: the Design phase of toolDeploy Enterprise.In Perfion
Channels are managed in the web client, with the structure on the left and the items related to the selected node on the right. Nodes can be added, deleted, reordered and arranged into hierarchies, and the data of related items can be edited from the channel.
One channel for the online store: products are related to its nodes, and taking Spares off the store leaves its items untouched. -
Concept 02 · Features linked to the shop’s fields
Map Each Field Once, for Each Shop
The product data problem it solves
Product titles are written one way in the ERP export, another way in the shop and a third way on the dealer site. Capacity appears in the description on one shop and in a filter on another, so the same pressure cooker cannot be found the same way twice.
The concept explained
A mapping links a Perfion feature to a field in the shop: the title, the description, the price, the images, a Shopify metafields or a Magento attribute. It is set up once for each shop, and from then on every product in the channel is sent the same way. Specifications travel as structured fields, so capacity or material can be shown and filtered as data. A field that is not mapped is not sent at all, which leaves it to the shop or to another app.
Everyday analogy
A wiring diagram. Each wire from the board goes to one socket, and every house built to the plan is wired the same way.
In Perfion
The Magento connector creates attributes from their settings in Perfion and checks them against Magento’s restrictions. If a mapping does not match, it skips only that attribute and reports a warning naming the mapping; the rest of the batch still imports.
Five features mapped to Shopify fields and metafields; Supplier code is not mapped, so it never reaches the shop. -
Concept 03 · Perfion, the shop or another app
Decide Who Owns Each Field
The product data problem it solves
A marketplace app sets the shop’s prices and a review app adds badges. After the first bulk upload from the product spreadsheet, both are overwritten, and a set of products created directly in the shop for a festival sale disappears.
The concept explained
A connector changes only what it is given. Fields that are not mapped are left for the shop or its other apps to manage, so ownership is decided field by field. The Shopify connector can be set to deactivate or delete only products that come from Perfion, and to set prices only when a product is created, leaving later price changes to another system. Magento can hold products that are not managed in Perfion, and categories without a Perfion identifier are not affected when categories are removed.
Everyday analogy
A shared kitchen with labelled shelves. Each cook uses their own shelf, and nobody clears a shelf that is not theirs.
In Perfion
In the Shopify connector, fields such as gift card, images, SEO title and description, status and tags are ignored if they are not mapped. When no sales channel mapping is configured, the connector does not overwrite sales channel assignments. In BigCommerce, price, width and weight are ignored if their mappings are missing.
Perfion owns the mapped content; the pricing app and the review app keep their fields; a festival bundle made in the shop is left alone. -
Concept 04 · Countries, languages and store views
Sell in Every Market From the Same Record
The product data problem it solves
The shop opens for customers in the UAE. A second copy of every product is made with Arabic titles typed in by an agency and prices in dirhams kept on a separate sheet. Within a quarter, the two copies no longer match.
The concept explained
Translations, markets and store views are values of the one product record. Text held in localizable features is sent as translations, including SEO titles and descriptions and the names of variant dimensions. In Shopify, a Market mapping decides which Markets a product and each variant is published to, and a fixed price can be set for each market. In Magento, the language deviation mapping sends localised values and images to the right store views. A new market is a mapping and a set of values, not a new copy of the catalogue.
Everyday analogy
One recipe card, printed in the language of each kitchen it is sent to, with the price written in the local currency.
In Perfion
An empty value on the Shopify Market mapping removes the product from all markets. In Magento, a language with no matching store view is reported as a warning, and an image feature marked localizable is assigned to, or hidden from, each store view.
One pressure cooker, two Shopify markets: English and rupees for India, Arabic and dirhams for the UAE, from the same record. -
Concept 05 · Scheduled runs with readable results
Run the Shop on a Rhythm You Can Read
The product data problem it solves
Listings are uploaded whenever the e-commerce executive has time. Nobody knows whether last night’s file went through, and errors surface as customer complaints about wrong sizes and missing photos.
The concept explained
The connector synchronises on a schedule: in Shopify, at an interval in minutes or at set times with Cron expressions, using delta synchronisation between full runs. It waits and retries when the shop’s API is busy, and if the E-commerce API returns an error it handles all products or none, so a shop is never left half updated. Sync messages for each product are cleared once it synchronises cleanly, and the Magento connector lists its batches with warnings and errors, so the team can see exactly which products need attention.
Everyday analogy
A bus timetable. Buses leave at known times, and the board at the depot shows which ones ran and which were held back.
In Perfion
The Shopify connector updates products and collections in parallel and handles translations and metafields in batches. In Magento, a cron job fetches and processes batches for all channels, and exceptions can be sent by email.
Related:From BPAS · prodRecord newsletterprodRecordKeeping the record straight.One product data practice every month, written in plain English for product data teams.Two scheduled runs a day: the night run sends 14 changed products and waits out a rate limit; one product keeps a warning to fix.
10 Best Practices for E-commerce Connectors in Perfion
Each practice says what well-run connected webshops look like and what it costs to ignore it. Designing channels and mappings for your shops is what BPAS consultants do.
-
01Give each shop its own channel, shaped like the shop
The rule
Each webshop has its own channel, with nodes that follow the shop’s navigation, so what a shop sells can be read straight from Perfion.
Risk if ignored
A shop’s assortment kept in a spreadsheet nobody else can see, and products on sale in the wrong shop.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 01Vocabulary: Channel
-
02Relate products to channel nodes; never keep a second copy
The rule
Every shop shows the one product record through its channel, and no shop keeps its own edited copy of product content.
Risk if ignored
Shop copies that drift from the record, and corrections made in one place only.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPAS -
03Map every field on purpose, and leave the rest unmapped on purpose
The rule
Each shop’s mapping is agreed field by field, with specifications sent as structured fields and internal fields never mapped.
Risk if ignored
Specifications buried in descriptions, and internal codes or cost fields showing on the shop.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 02Vocabulary: Mapping
-
04Decide who owns each field before the first synchronisation
The rule
For every field, it is agreed whether Perfion, the shop or another app owns it, and the mapping matches that decision.
Risk if ignored
Prices, badges or sales channel settings from other apps overwritten by the connector.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 03FAQ 03
-
05Keep products that are not managed in Perfion out of harm’s way
The rule
Products created directly in the shop are never deactivated or deleted by a synchronisation run.
Risk if ignored
Festival bundles and marketplace listings removed from the shop overnight.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 03FAQ 02
-
06Hold translations and market prices in Perfion
The rule
Translations, SEO text and prices for each market are values in Perfion, sent through the mapping, and not typed into the shop.
Risk if ignored
A second catalogue for every country, out of step with the first within months.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 04Capability: Markets, languages and store views
-
07Schedule synchronisation to fit the business day
The rule
Each shop is synchronised at times that suit how the business works, such as overnight and before a launch, and everyone knows when changes go live.
Risk if ignored
Changes that appear at random times, and launches that miss their hour.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 05Capability: Scheduled full and delta synchronisation
-
08Review sync messages and batches as a daily routine
The rule
Someone owns the results of every run and clears each warning or error at its cause in Perfion.
Risk if ignored
Problems found by customers, and the same error repeated every night.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Concept 05Capability: Sync messages, batches and shared shops
-
09Send images with alt text, on the right variant
The rule
Every product and variant has the images it needs in Perfion, with alt text where the platform uses it, before it is synchronised.
Risk if ignored
Variants shown with the wrong photo, and images without alt text for search and accessibility.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPASRelated:Capability: Products, variants and categoriesGuide 11: Binaries
-
10Keep each connector in step with its platform
The rule
Connector versions follow the platform’s current API, and authentication uses the method the platform currently supports.
Risk if ignored
A connector that stops working when the platform retires an API version or an older way of signing in.
Get it right with BPAS
Not sure this is in place for your webshops? Talk to a BPAS consultant.
Talk to BPAS
Webshop connector self-audit: how many are in place today?
Tick each of the ten practices above that your business already follows. Your score updates as you go.
Tick the practices that are in place.
Nothing you tick is stored or sent.
Illustrative scenario: an Indian kitchenware maker, with every listing uploaded by hand
A maker of pressure cookers, cookware, tawas and kettles sells about 1,800 products through a Shopify store for customers in India and the UAE, and a Sana Commerce webshop for 1,200 dealers. Orders, stock and invoicing are in the ERP. Product content for both shops is kept in spreadsheets.
The Operational Challenge
Every week an e-commerce executive exports a product spreadsheet, cleans it, and uploads it to Shopify, then keys the same changes into the dealer webshop. Prices for the UAE sit on a separate sheet, and the Arabic titles are typed into Shopify by an agency.
Sizes are added as new variants by hand, discontinued products are hidden one by one, and a price app’s settings are overwritten by every bulk upload. Wrong capacities and missing photos come back as returns and complaints.
- Weekly spreadsheet uploads to two shops
- UAE prices on a separate sheet
- Arabic titles typed into the shop
- Errors found by customers
The Financial Transformation
In Perfion, each shop has its own channel, with products related to its nodes. A mapping for each shop sends titles, specifications as metafields and images, while the price app keeps the fields it owns. Arabic text comes from localizable features, and UAE prices are set for the Shopify Markets.
Delta synchronisation runs twice a day keep both shops current. The team reviews sync messages each morning and fixes each one at its cause in Perfion, and products taken off a shop stay in the record.
- Both shops fed from the product record
- One mapping for each shop
- Arabic and UAE prices held in Perfion
- Sync messages reviewed every morning
| Cost line | Before (per month) | After (per month) | Difference (per year) |
|---|---|---|---|
| Listing uploads and edits | ₹ 80,000 | ₹ 20,000 | ₹ 7,20,000 |
| Translations and market prices | ₹ 30,000 | ₹ 10,000 | ₹ 2,40,000 |
| Listing errors and returns | ₹ 20,000 | ₹ 5,000 | ₹ 1,80,000 |
| Total | ₹ 1,30,000 | ₹ 35,000 | ₹ 11,40,000 |
See how your own webshops would be fed from Perfion.
Book a webshop review →prodRecord Live
Enterprise product data insights from BPAS
Keeping the record straight, live every month
prodRecord Live is a monthly webinar series on product information management, held on the second Wednesday of every month from January 2027. Each session takes one product data topic and works through it in plain English with time for your questions.
- Jan
- Feb
- Mar
- Apr
- May
- Jun
- Jul
- Aug
- Sep
- Oct
- Nov
- Dec
Who benefits from webshops fed from the product record: one record, three answers
-
Promoter & CXOs
Can we open a new shop or country without a new team?
Each shop is a channel and a mapping on the record the business already maintains, so a new shop or market starts from content that is already there.
-
E-commerce Manager
Will the shop always show what we sell, correctly?
The channel decides what each shop sells, delta runs run on a schedule, and sync messages point to exactly the products that need attention.
-
Product Data Manager
Will every shop show exactly what we hold?
A mapping sends each value to the right field, and fields that are not mapped stay with the shop or its other apps.
E-commerce Connector Vocabulary and Definitions
From connectors and channels to mappings, delta synchronisation, Shopify Markets and Magento store views. Each term shows what it means, why it matters, and a household comparison.
-
E-commerce connector
Connectors · basicsOne for each platform
Operational definition
A licensed Perfion module that synchronises product data from Perfion to one e-commerce platform: Shopify, BigCommerce, Magento or Sana Commerce.
Why it matters in Perfion
Shops are fed by a standard, maintained integration rather than a custom one.
Everyday analogy
The supply line from one warehouse to one shop.
See it in action:Four standard connectors under Capabilities →
-
Channel
Connectors · assortmentThe shop, in Perfion
Operational definition
A structure in Perfion for one sales channel, such as a webshop: its nodes, the metadata on each node, and the items related to each node.
Why it matters in Perfion
What each shop sells is decided beside the product data.
Everyday analogy
A shop window, arranged from the stock in one warehouse.
See it in action:Concept 01 under Core Concepts →
-
Channel node
Connectors · assortmentItems related, not copied
Operational definition
One node in a channel structure, such as a shop category, with its own metadata. Items are related to it; removing one removes only the relationship.
Why it matters in Perfion
Taking a product off a shop never deletes it from the record.
Everyday analogy
A shelf label pointing to stock kept in the store room.
See it in action:Channels in the web client under Capabilities →
-
E-commerce API
Connectors · sourceServes the channel
Operational definition
The part of Perfion that serves a channel’s products to the e-commerce connectors.
Why it matters in Perfion
Every connector reads from the same governed source.
Everyday analogy
The dispatch counter where each delivery van collects its load.
See it in action:Four standard connectors under Capabilities →
-
Mapping
Connectors · fieldsFeature to field
Operational definition
The link between a Perfion feature and a field in the shop, such as a title, a price, a metafield or an attribute. Fields not mapped are not sent.
Why it matters in Perfion
Every product reaches the shop the same way, and other apps keep their fields.
Everyday analogy
A wiring diagram: one wire to one socket.
See it in action:Concept 02 under Core Concepts →
-
Delta synchronisation
Connectors · scheduleChanges since the last run
Operational definition
A synchronisation run that sends what has changed since the last run, as opposed to a full run.
Why it matters in Perfion
Shops stay current without resending the whole catalogue each time.
Everyday analogy
Posting only the pages of a manual that changed, not the whole manual.
See it in action:Concept 05 under Core Concepts →
-
Hosted service
Connectors · runningAlways running on IIS
Operational definition
How the BigCommerce connector and the Shopify connector above version 2.0 run: as an always-running service on a Microsoft IIS website, reading from a Perfion API on HTTPS.
Why it matters in Perfion
The connector keeps working on its schedule without anyone starting it.
Everyday analogy
A night watchman who is always on duty.
See it in action:Four standard connectors under Capabilities →
-
Markets
Shopify · reachCountries and prices
Operational definition
In Shopify, the countries or regions a store sells to. The connector can publish products and variants to Markets and set a fixed price for each.
Why it matters in Perfion
One store sells in several countries from one record.
Everyday analogy
One shop with a price tag in each customer’s currency.
See it in action:Concept 04 under Core Concepts →
-
Metafield
Shopify · fieldsStructured specifications
Operational definition
A custom field in Shopify, filled by the connector from a Perfion feature, such as rich text, a file, money, a dimension or a product reference.
Why it matters in Perfion
Specifications reach the shop as data shoppers can read and filter.
Everyday analogy
The labelled boxes on a product spec sheet.
See it in action:Attributes and metafields under Capabilities →
-
Store view
Magento · reachOne view per language
Operational definition
In Magento, a view of a website, typically one for each language. Localised values and images go to the store view set by the language deviation mapping.
Why it matters in Perfion
Each language gets its own text and images from the same product.
Everyday analogy
The same shop with signboards in the local language.
See it in action:Markets, languages and store views under Capabilities →
E-commerce Connectors: questions e-commerce teams ask
Short answers, each with a link to the part of this guide that explains it.
-
Shopify, BigCommerce, Magento, including Adobe Commerce, and Sana Commerce, with versions for Sana Commerce Cloud and for on-premise Sana. Each connector is a licensed module that must be included in the Perfion licence, and each has its own minimum Perfion version. The Shopify connector is released for specific Shopify API versions and updated as Shopify releases new ones.
More on Four standard connectors -
Yes. The Shopify connector can be limited to deactivating or deleting only products that come from Perfion. Magento can hold products that are not managed in Perfion, and categories without a Perfion identifier are not affected when categories are removed.
More on Concept 03 -
Not for fields that are not mapped. In Shopify, fields such as images, SEO title and description, status and tags are ignored if they are not mapped, and sales channel assignments are left alone when no sales channel mapping is set. In BigCommerce, price, width and weight are ignored if they are not mapped. Shopify prices can also be set only when a product is created.
More on Concept 03 -
Yes. Localizable features are sent as translations, including SEO titles and descriptions and variant dimensions. A Market mapping on products and variants decides which Shopify Markets each is published to, and a fixed price can be set for each market.
More on Concept 04 -
On a schedule you set. The Shopify connector runs at an interval in minutes or at set times using Cron expressions, with delta runs between full runs. The Magento connector fetches and processes batches for all channels on a schedule.
More on Scheduled full and delta synchronisation -
The Shopify connector waits and retries when it reaches Shopify’s API rate limits, and if the E-commerce API returns an error, it handles all products or none. Sync messages show the products that need attention. In Magento, batches list their warnings and errors, a mapping problem skips only the attribute concerned, and exceptions can be sent by email.
More on Concept 05 -
Yes. The connectors read product data from Perfion itself, so this guide applies whichever ERP your other data comes from. What changes from one ERP to another is the integration that brings ERP data into Perfion.
More on ERP integration
Still have a question?
Ask about your own products, categories and channels. A BPAS consultant will answer in plain English.
Ask BPASSee your webshops fed from your product data
See how your webshops would be fed from Perfion, in every market and language you sell in. Choose the path that fits the ERP you run.
The world's first Boyum Partner Center of Excellence.Hosted in the cloud and available for evaluation and proof-of-concept work across the Boyum Solutions portfolio.See it to believe it — get convinced by working on it.Explore the PACE sandbox→