Rebuilding & Auto-Building Products
Summary
How to manually rebuild products and listings with their currently linked inventory, and how to automate building, rebuilding, and listing at the source level.
Rebuilding re-runs the build for a product using its currently linked inventory. Whether it updates data on a product that already exists is set in the Product Builder (Don't update is the default). You can rebuild on demand from the Products tab, or turn on automation at the source level to build, rebuild, and list products without manual steps: best when you control your source data and do not customize products.
- Rebuild on demand: re-run the build for selected variants using their current linked inventory.
- Original builder vs. a specific one: reuse the last builder and template, or pick a different one for the rebuild.
- Auto-create: automatically build products and listings as inventory imports from a source.
- Auto-rebuild: rebuild products and listings automatically when a source import changes a mapped content field. Price and quantity changes do not trigger it.
- Auto-list: publish and update auto-created listings on your channels.
| Option | Description | When to use |
|---|---|---|
| Re-Build using the original builder and mapping template | Reuses the builder and template last used for this product, applying their current logic. | Fastest path when your last configuration is still right. |
| Select a specific builder & mapping template | Pick or create a builder and template to apply during the rebuild. | When you need different mapping or newly added fields. |
| Re-Build Parents As Well | Includes the product parent along with the selected variants. | When parent-level attributes or relationships must refresh. |
Source-level automation
| Setting | What it does |
|---|---|
| Auto-Create Products & Listings | Builds products (and optionally listings) as inventory imports. Without Listing Creation Rules, all inventory from the source is created. |
| Auto-Rebuild Products & Listings | Rebuilds a product and its listings when a source import changes a content field your mapping template maps, so static product data flows from the source to linked products and listings. Price and quantity (PQS) changes do not trigger a rebuild, and SKU never changes. |
| Auto-List to Channel | Automatically publishes and updates auto-created listings on your channels. |
A full-catalog rebuild fails after about 30 minutes with no actionable errors
Rebuild in smaller batches rather than the entire catalog at once. If a specific builder and mapping-template combination fails repeatedly, report both IDs to support.
The parent channel listing did not rebuild when its variant did (item still shows a sale price)
Known issue: a variant auto-rebuild does not always trigger the parent listing rebuild. Manually rebuild the parent listing until this is resolved.
Auto-Create builds every item from the source
Without Listing Creation Rules, Auto-Create includes all inventory. Choose the Advanced option and add workflow rules to narrow which inventory auto-creates.
When should I rebuild?
When products did not build as expected, new inventory variants were linked, or the source sent new or updated data you want reflected.
How do I auto-rebuild only some products when vendor data changes?
There is no selective auto-rebuild. The only automatic option is Auto-Create / Auto-Rebuild per source, which affects all inventory. Support recommends selectively rebuilding with filters instead.
Will rebuilding also update the parent?
Only if you check Re-Build Parents As Well in the rebuild flyout, and the Product Builder's setting for product parents allows existing data to be updated.
Do price or quantity changes trigger Auto-Rebuild?
No. Changes to price and quantity (PQS) fields never trigger an auto-rebuild. Only a change to a content field that your mapping template maps does.
Which fields trigger Auto-Rebuild?
Any content field your mapping template maps. A change to a field the template does not map is ignored.
Why did many products rebuild right after I edited the mapping template?
Changing the mapping counts as a change. Moving a field from mapped to Don't map, or setting it to empty, triggers a rebuild of every affected product on the next import. After that first rebuild, only real content changes from the source trigger it.
Can Auto-Rebuild use a different mapping template, or update only some fields?
No. It uses the builder and mapping template that created the product (the one set in the source's Auto-Create settings) and re-applies every field that template maps. It cannot be narrowed to another template or to a subset of fields.
Does a rebuild change the SKU?
No. SKU is a protected field and never changes on a rebuild.
Who should use Auto-Building?
Users who control their source data (for example an internal warehouse) and do not customize product data. It is not recommended when dropshipping from multiple suppliers with varied data.