# A process for checking ecommerce feeds before a campaign

URL: https://ekom.blog/a-process-for-checking-ecommerce-feeds-before-a-campaign/
Published: 2026-09-11
Author: Ekom
Topics: Tools & automation

> A practical guide to a process for checking ecommerce feeds before a campaign, with attention to verified facts, clear ownership and release readiness.

The campaign goes live tomorrow. The feed was last reviewed before the stock and price changes. Some products have new variants, some are unavailable, and the landing page expects items the feed may not contain.

A feed check before launch is cheap. A wave of disapprovals, or ads showing the wrong price, is not.

The feed is a structured handoff between the store and a channel. Review the source data, the transformations, eligibility, destinations and update timing. A successful upload doesn't prove every listing matches the live product or the campaign conditions.

## Confirm the campaign scope

List the products, variants, markets, languages, destinations and dates in the campaign. Confirm which channels use the feed and whether they have different requirements. Keep a clear owner for campaign eligibility and approved claims.

Compare the campaign plan with the actual catalogue. Check that items are available, offer terms are approved and product pages exist. If the campaign includes a bundle, discount or limited period, confirm the start and end rules with the commercial owner.

Don't rely on product titles alone. I match feed records to the store and the campaign list with stable identifiers, because a similarly named variant can have a different price, availability or landing URL.

## Verify source fields and transformations

Identify which system controls title, description, identifier, image, price, currency, availability, link and other channel fields. Record any feed rules that transform those values, such as truncation, concatenation, filtering or label mapping.

Check the transformations keep the product facts accurate. A generated title shouldn't drop a key distinction or add an unsupported claim. If the feed carries a campaign label, confirm the channel allows it and that it matches the offer.

Look at missing and malformed values. A blank field may be deliberate or a data problem. Decide how the feed treats discontinued products, unavailable variants, new items and products without optional attributes. I won't fill gaps with guesses just to make the export look complete.

## Test URLs, images and destination pages

Open representative landing URLs and confirm each lands on the right product and variant. Check redirects, canonical behaviour, query parameters and market-specific routing. A URL that resolves but ends up on the wrong product is still a serious mismatch.

Check images for availability, correct variant, sufficient clarity and stable access. If a CDN or third-party service supplies images, confirm that the destination can fetch them. Review the actual feed URL and rendering rather than relying only on the media library.

Compare page content with the feed's price, currency, availability and promotion. If the offer differs by market or account, ensure the feed destination and fields reflect the intended audience. Avoid advertising a price that a visitor cannot access or purchase at.

## Review channel diagnostics and policy

Use the channel's current documentation and diagnostic tools. Check errors, warnings and product status after processing. A file accepted for upload may still contain item-level issues or be rejected later.

Do not treat a warning as a reason to invent data. Determine whether the field is required, recommended or irrelevant to the product type. Consult the product owner or channel support when the rule is unclear.

Review campaign claims and images for accuracy and permission. Follow destination policies and the organisation's legal or brand approval process. If an item is not eligible for promotion, exclude it rather than hiding a limitation in the landing page.

## Check timing and update behaviour

Find out how often the feed refreshes and whether changes are pushed or polled. If campaign prices or stock can change quickly, choose a process that keeps values current enough for the offer. Confirm time zones and schedule boundaries where they matter.

Test a change through the whole path: update the source, generate the feed, let the destination process it, inspect the listing, open the landing page. Note how long each stage takes. Don't promise real-time availability if the integration isn't built for it.

Assign someone to monitor the first campaign processing and handle rejected products. Keep a rollback or pause procedure if the feed sends incorrect prices or availability. The person who can pause ads may be different from the person who can repair product data.

## Keep the review record

Save the campaign product list, feed version, validation result, reviewer and date according to the team's data policy. Record exceptions and how they were resolved. This helps explain why a product was excluded or why a later report differs.

After launch, check actual listings and customer paths. If a product or promotion changes, update both the source data and campaign creative. A feed is operational content, not a file that can be forgotten after export.

## Reconcile feed and campaign approvals

Keep a record of which campaign copy and feed fields were approved, especially when discounts or claims vary by market. If the commercial team changes the offer after the feed export, repeat the affected checks rather than assuming the earlier validation still applies.

For a large catalogue, use a representative sample plus automated checks for broad patterns, then manually review exceptions and high-risk products. Automation can flag a mismatch; an owner still has to decide whether the item is eligible.

## Keep responsibility clear during active campaigns

Agree who can pause a campaign, correct the feed and approve a new export. If the product team changes stock while marketing adjusts the offer, a shared status note stops competing updates. Use the normal change channel and keep the latest approved version.

## Related reading

- How to reconcile landing page data across analytics and Search Console

- Keeping AI prompts and source files together in an audit

- A safer workflow for bulk editing metadata in a spreadsheet

A feed audit is about consistency from product record to campaign destination. Which field is most likely to go stale before your next promotion, and who will verify it?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
