Rebuilding Products

June 28, 2026

Summary

Rebuild products to re-apply your current builder/template: when to rebuild, how to run it from the Products tab, and what it overwrites.

What this covers

What rebuilding does

Re-runs the build with the currently linked inventory variants. Whether existing data is updated depends on the Product Builder settings.

When to use it

When products didn't build as expected, new variants were linked, or the source provided updated data.

Rebuild flyout options

Choose how the rebuild runs: original builder/template, a specific one, or include parents.

Automating rebuilds

Set conditions in Rebuild Settings to trigger rebuilds automatically when criteria are met.

What rebuilding does

Rebuilding re-runs the product build with the currently linked inventory variants. Whether it changes products that already exist is set in the Product Builder, under Product Match Rules: for product variants and for product parents, the question "should existing data be updated during building?" can be Don't update (the default), Always update, or Only update if new inventory is linked. If sources or mappings changed after the original build, those updates reach an existing product only when the builder is set to update it.

When to rebuild

Common trigger	What it means
Products didn't build as expected	Variant(s) didn't build the way you expected on the first pass.
New inventory variants linked	New inventory variant(s) have been linked and should populate product content.
Source data changed	Source feeds changed, or new data points were recently imported into Flxpoint and you want them reflected in products. The Product Builder must be set to update existing data.

Rebuild from the Products tab

Rebuild selected product variants using the current linked inventory variants.

Step	Action
1	Select the product variant(s) to rebuild.
2	From the Products tab (not the Inventory tab), click Actions.
3	Click Re-Build Product(s). A flyout appears with options for how the rebuild is performed.

Choosing how the rebuild runs

Once the flyout opens, pick one of the options below and confirm.

Option	What it does	When to use
Re-Build using the original builder and mapping template?	Uses the builder/template last used for this product, applying any current updates in those configs.	Fastest path when your last configuration is still the right one.
Select a specific builder & mapping template	Create, edit, or select a specific builder/template to apply during the rebuild.	When you need different mapping or newly added fields.
Re-Build Parents As Well?	Includes the product parent in the rebuild along with the selected variants. The parent's existing data changes only if the Product Builder's setting for product parents allows an update.	When parent-level attributes or relationships must be refreshed.

Things to know

A rebuild updates existing data only if the builder says so

A rebuild re-runs the building process. Whether it overwrites existing product data is decided by the Product Builder, where "For product variants, should existing data be updated during building?" and "For product parents, should existing data be updated during building?" are each set to Don't update (the default), Always update, or Only update if new inventory is linked. Where the builder is set to update, changes made after the original build are replaced by the rebuild output.

"Original builder and template" means the selection, not old values

Re-Build using the original builder and mapping template means Flxpoint remembers which builder/template you last used - not the old field values. If you've modified that builder/template since the last build, those changes will be reflected in the rebuilt product.

FAQs

Why am I unable to rebuild my Parent/Variant SKU value?

That's expected behavior, not an issue. In the Product or Listing Builder, the SKU is the identity/match key for a rebuild, so it's protected on update. The rebuild uses the incoming row's SKU to find the existing product, then applies the template's field mappings to everything except the SKU itself.

Where do I start a rebuild?

From the Products tab - not the Inventory tab. Select the product variant(s), click Actions, then Re-Build Product(s). A flyout appears where you choose how the rebuild is performed.

Will rebuilding pick up changes I made to my builder or template?

Yes. Re-Build using the original builder and mapping template reuses the builder/template you last selected and applies any updates currently in those configs. If you modified the builder or template since the last build, the rebuilt product reflects those changes.

Can I rebuild the product parent too?

Yes. In the rebuild flyout, check Re-Build Parents As Well? and confirm. The product parent associated with the selected variants will be rebuilt along with them - useful when parent-level attributes or relationships need to be refreshed. The parent's existing data changes only if the Product Builder's setting for product parents allows an update.

Can rebuilds happen automatically?

Yes. You can automate when rebuilding occurs via Rebuild Settings (Automate When To Rebuild) to trigger a rebuild on specific conditions.

Rebuild appears to do nothing when including parents?

If you select Re-Build Parents As Well and the process appears to complete without making any changes or throwing an error, verify that the parent SKU in your Master Catalog matches the parent SKU on the Sales Channel listing. If these SKUs differ, the rebuild will not execute for the parent. To resolve this, either ensure the parent SKUs are aligned or exclude the parent from the rebuild request.

I fixed the UPC or GTIN mapping but existing products didn't change. Why?

The inventory import updates price, cost, quantity, MSRP and MAP on items that already exist; identifiers such as UPC are kept from the existing record. A change to the mapping template reaches existing products only when they are rebuilt. Products built after the change get the new mapping.

Back to Product Catalog