Frequently asked questions

Grouped as the app groups them:

• Content: title, description, vendor, product type, tags, status.
• SEO: meta title and meta description.
• Media: images.
• Metafields: product level metafields, all of them or only chosen namespaces.
• Pricing & Inventory: price, compare at price, unit price, charge tax, cost per item, barcode, sell when out of stock, weight, country of origin, HS code.

Every one of them is a checkbox. On a new store, description, vendor, product type, tags, SEO, images and metafields are on. Title and status are off, and the whole Pricing & Inventory group is off.

Inventory quantities, warehouse and location assignments, and fulfillment service are never written, whatever the config says. Beyond that, the app only ever writes the fields in the list above: it does not create or delete products, change a product’s handle or SKUs, edit collections, or touch orders, customers or discounts.

Yes. Data only ever moves from a parent to its children. Editing a child does not update the parent and does not update the other children.

Your edit stands until the next sync for that rule, and then any field that is enabled in the config is overwritten with the parent’s value. Fields that are not enabled are never written, so an unchecked field on a child is safe indefinitely.

That is why title and status are off by default: regional children usually need their own title and their own published state.

Not for a single child. Field choices live in a named sync config, and a config is assigned to a parent, so every child under that parent follows the same rules.

If one family of products needs different rules, create a second config on the Sync Configs page and assign it to that family’s parent. If a single child needs to keep one field, turn that field off for the whole rule.

Saving a parent in your admin normally reaches its children within a few seconds. Shopify notifies the app that the product changed, and the app starts the sync straight away.

A rule with many children, or children with many images or metafields, takes longer, because the app paces itself against Shopify’s API rate limits and retries when it is throttled rather than failing.

Turning images on makes the child’s images match the parent’s exactly. The app removes the images already on the child and re-uploads the parent’s, so anything the child had that the parent does not have is gone after a sync.

Only images are mirrored. Video and 3D models on either product are left alone.

With metafields enabled, every product level metafield on the parent is written to the child, key for key, keeping its type.

You can narrow this by listing namespaces in the config. With a list, only metafields in those namespaces are copied. With the list empty, all namespaces are copied. Metafields on the child that the parent does not have are not removed.

Prices only if you ask it to. The whole Pricing & Inventory group is off by default, and price, compare at price and unit price are separate checkboxes inside it.

Inventory quantities are never changed. The group’s name refers to variant level settings such as cost per item, barcode, weight and whether a variant keeps selling when out of stock. How many units you have, and where they are, is not something the app writes.

By variant title first, and by position in the list when no title matches. A child variant with no counterpart on the parent is left untouched.

Because Shopify stores this data on variants even for products with no options, the Pricing & Inventory fields apply to single variant products too.

No. A product belongs to at most one rule, and no product can be a parent and a child at the same time. The app blocks the attempt and points you at the rule that already owns the product, so there are no chains and no loops.

There are two plans:

• Free. Two sync rules, with every field, image and metafield option available.
• Pro. Unlimited sync rules, at $5 a month or $50 a year, with a 14 day free trial.

Billing runs through Shopify and appears on your normal Shopify invoice. If you move from Pro back to Free, the rules you already have keep syncing. You only lose the ability to create more than two. The App Store listing always shows the current price.

There is no limit on how many children one parent can have. The Free plan allows two sync rules (two parents), and Pro is unlimited. The app tells you when you have reached the limit and links to its plan page.

Two technical ceilings are worth knowing: the app reads up to 250 images, 250 metafields and 250 variants from a parent in one pass, and the recommendations scan looks at the first 1000 products in your catalogue.

No. Parents and children live in one store. Every rule, config and log belongs to the store it was created in, and the app never reads or writes another store’s products.

Each rule page has a Sync History (last 30) table listing the child, the result, whether a webhook or a person triggered it, the error message if any, and the time. View Logs on the dashboard shows the last 200 results across the whole store.

A failed row carries Shopify’s own message. Fix the cause (an invalid metafield value or a product that has since been deleted are the usual ones) and click Sync Now to try again.

Three degrees of it:

• Remove a child on the rule page stops that one product from being updated.
• Remove a parent on the dashboard deletes the whole rule, including its children and its history.
• Unticking a field in the sync config stops that field from being written for every rule using the config.

None of these undo anything. Values already copied to a child stay as they are, and you are free to edit them.

Your access credentials are deleted immediately, so the app can no longer read or write anything in your store. Shopify then sends a store redaction request about 48 hours later, and everything the app holds for your store is deleted: rules, child links, configs, logs and the store record. A reinstall inside that window finds your setup intact.

Product data that was already mirrored stays on your child products. Uninstalling stops future writes, it does not roll back past ones. See the privacy policy for the full list of what is stored.