Why did updating my InDesign product data source not update the merged catalog I already edited?

Identify which of the three catalog objects needs updating

The source file contains product records. The target template contains field placeholders and layout instructions. The merged document contains the resulting catalog pages, potentially including manual edits made after generation. Updating one object does not make all three interchangeable.

InDesign's Update Data Source command refreshes the target's source connection while preserving existing field placements. The separate Update Content in Data Fields command applies only to eligible merged documents using parent-page placeholders. It maintains the current layout and provides an update log.

Start a change request with three identifiers: source revision, target template revision, and merged catalog revision. Add the product record keys affected by the change. This prevents a revised spreadsheet from being mistaken for proof that an already edited catalog contains the latest prices.

The merchant should also identify the final approved deliverable separately. A previously delivered PDF is not a live data-connected catalog and should not be treated as automatically updated.

Branch A: update eligible merged content without rebuilding the layout

Use this branch when the existing merged document was built with parent-page placeholders and the requested changes concern supported record-content updates rather than new field structures or merge settings.

Illustrative exercise: imagine a 24-product accessories catalog. Two existing SKUs receive corrected prices, and one new product record is added. The merchant wants to preserve the current catalog layout while evaluating whether the merged-content update is eligible.

Save and close the revised source, then open the actual eligible merged document. Choose Window > Utilities > Data Merge and select Update Content in Data Fields from that panel’s menu. Inspect the resulting log and changed records; selecting Update Data Source in the target template alone is a different action.

The acceptance worksheet should name each changed SKU, expected price, product identity, and relevant description. Long product names deserve separate layout attention because retaining the current layout does not establish that newly inserted text fits its available space.

Do not approve the revised catalog merely because an update command completed. The merchant still needs confirmation that the intended records changed and that unrelated products retained their correct associations.

Branch B: rebuild when fields or merge structure change

Choose a new merge when the catalog requires additional fields, different placeholders, or changed Create Merged Document settings. An existing merged document with placeholders only on ordinary document pages must not be assumed eligible for the parent-page update mechanism.

Illustrative exercise: imagine a packaging catalog gaining a new mandatory recycling-instruction field. The previous template contains no corresponding placeholder. This is a structural change, not merely a corrected value inside an established field.

Keep the manually edited catalog as a reference before planning regeneration. Record its deliberate typography, page-specific adjustments, product ordering, and approved exceptions. Do not assume those edits will transfer automatically into a newly merged document.

Revise the target structure, identify the intended source revision, and define the new merge settings. Require a comparison between the regenerated catalog and the previously approved version, particularly where manual corrections had been applied.

If the new field contains required packaging information, hold records missing approved values rather than treating successful field mapping as proof of content completeness.

Create a controlled handoff between data owners and designers

Assign the merchandising owner responsibility for approved prices, SKU identity, and product facts. Assign the designer responsibility for template structure, page composition, and preservation of deliberate manual changes. Assign the release owner responsibility for identifying the approved catalog revision.

Use a change manifest containing source revision, target revision, merged-document revision, affected SKUs, requested operation, and unresolved exceptions. Mark whether the request is a content update or a structural rebuild.

For price-sensitive products, require an explicit comparison against the approved commercial price list. A correctly populated field can still contain the wrong product's price if record identity was mishandled upstream.

No InDesign operation, data merge, PDF export or print test was performed. The examples are fictional and no Itemlume integration is claimed.

Illustrative exercise: catalog update or regeneration decision

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)