How to keep product price and stock updated in your ads
A beginner-friendly guide to avoiding out-of-stock products, expired promotions and inconsistent data between your store, feed and ad channels.
Julia Villegas

Keeping product price and stock updated in your ads helps you avoid promoting items that are out of stock, discounts that have expired or landing pages that do not match the ad. The key is understanding that your store, your product feed and each advertising channel do not always update at the same time.
What product price and stock mean in advertising feeds
In ecommerce, product price and stock are two of the most important fields in your catalog. They tell ad platforms what a product costs and whether it can be bought. Simple idea, complex workflow.
A product can be available in your store, imported into a feed tool, transformed for a specific channel and then downloaded by Google, Meta, TikTok or another platform. Those steps are related, but they are not the same thing.
| Term | What it means | Why it matters |
|---|---|---|
| Store | Where you manage products, variants, prices and availability | Usually the main source of truth |
| Import | The moment a feed tool reads your store or source file | If the tool has not imported a change, the feed cannot reflect it |
| Product feed | A file or URL containing product data prepared for a channel | It must use valid fields, formats and values |
| Channel download | The moment an ad platform reads the feed URL | It may happen on a different schedule from your store update |
This distinction matters because “my store is updated” does not automatically mean “my ad platform has already read the new data”. You might change stock at 10:00, import that change into your feed later, and have the channel download the feed after that. A live feed can reduce manual work, but it does not make every advertising channel update instantly.
Google’s product data specification explains that submitted product data should accurately describe the product and match the landing page. Meta’s catalog documentation also refers to fields such as product ID, availability, price and link in its catalog specifications. Requirements vary by product type, country and channel, but the fundamentals are consistent: stable IDs, useful titles, valid links, coherent prices and reliable availability.
Why product price and stock matter for catalog ads
When product price and stock are out of sync, the issue is not only operational. It affects user trust, campaign quality and the amount of time your team spends fixing avoidable problems.
Common situations include:
- An out-of-stock product still appears in ads. The shopper clicks, lands on a product page and cannot buy.
- A sale price remains visible after the promotion ends. The ad or creative shows a discount that no longer exists.
- The feed price differs from the landing page price. The channel may flag warnings or disapprovals depending on its rules.
- Variants are handled too broadly. One size or color is unavailable, but the product is still advertised as if every variant were in stock.
- Large sale updates are applied without testing. One rule affects hundreds or thousands of products before anyone notices.
For a small catalog, you may catch some of these issues manually. For a store with hundreds or thousands of SKUs, you need a repeatable process: import the data, normalize it, segment the catalog, generate the feed and check the result before relying on it in campaigns.
If you are preparing a seasonal campaign, this process also connects to creative planning. For example, the same feed discipline is useful when building holiday product sets like the ones covered in our guide to catalog ads for Christmas.
Example: a store with weekend promotions
Imagine a fictional sports retailer with 8,000 products. Every Friday, the marketing team launches promotions on running shoes, technical apparel and accessories. Some offers end on Sunday night. On Monday morning, however, several ads still show the discounted price.
The team finds three issues:
- The price was updated in the store, but the feed was not regenerated immediately.
- Some products with no stock were still included in the promotional product set.
- The advertising channel downloaded the feed on its own schedule, not at the exact moment the store changed.
The solution is not to rebuild the whole campaign every Monday. The better approach is to isolate the data flow:
- keep the same product ID over time;
- check whether the sale price has a valid start and end date;
- exclude out-of-stock products from the relevant feed or set;
- test one SKU before applying broad rules;
- confirm that the feed URL returns the expected data when it is downloaded.
This is a fictional example, but the pattern is common. Teams often look for the problem inside the campaign when the real issue is earlier in the product data chain.
How to build a feed with reliable product price and stock
A reliable feed is not the feed with the most fields. It is the feed with the right fields, valid formatting and predictable updates.
1. Keep product IDs stable
The product ID is how the channel recognizes an item. If you change the ID whenever you change the title, category, price or promotion, the platform may treat the item as a different product.
Good practices:
- use a unique ID for each product or variant, depending on channel requirements;
- do not reuse old IDs for different products;
- avoid building IDs from fields that change, such as price or discount;
- document your ID logic before migrations or platform changes.
This is especially important for variants. A T-shirt may have one parent product, but each size and color can have different availability. If the channel needs variant-level data, stock should refer to the specific variant being advertised.
2. Match the price to the landing page
The feed price should match what the shopper sees on the product page. If you use taxes, country-specific pricing, automatic discounts or local currencies, check how those values appear in the store and how they are exported.
Review these points:
- correct currency;
- decimal format accepted by the channel;
- final price visible on the product page;
- sale price only when the promotion is active;
- start and end dates when the channel supports promotion timing.
Not every platform uses the same fields in the same way. Google Merchant Center has its own product data attributes, while other channels have their own specifications. If you advertise across multiple destinations, it is usually safer to create channel-specific feeds instead of forcing one generic file to do everything.
3. Define a clear stock rule
Stock is not always a simple yes or no. A product may be available online, available in store, on preorder, backordered, temporarily unavailable or sold out in one variant but not another.
For beginners, a practical first rule could be:
- if stock is greater than zero, send the product as available;
- if stock is zero, exclude the product or send it as unavailable, depending on the channel and your strategy;
- if the product has no valid landing page, exclude it;
- if the sale end date has passed, remove the sale price from the output.
The rule is simple, but it prevents many common errors. The important part is applying it before the channel downloads the feed.
4. Segment by intent, not only by category
One catalog can feed multiple channel outputs and product sets. You do not need to send exactly the same products to every campaign.
| Set | Suggested rule | Possible use |
|---|---|---|
| Always-on products | In stock and stable price | Evergreen catalog campaigns |
| Active promotions | Sale price is active and not expired | Flash sales or seasonal campaigns |
| Gift ideas | Available, within price range, relevant category | Holiday or gift campaigns |
| Clearance | Limited stock and active discount | Fast-moving inventory campaigns |
This makes troubleshooting easier. If the “active promotions” set has a problem, you do not need to inspect products that were never part of the promotion.
How to manage product price and stock with AdMotion
With AdMotion Feed Manager, the workflow starts from your catalog and ends with channel-ready feeds. AdMotion can connect to Shopify, BigCommerce, Tiendanube or any product file or feed, then help you map, clean and segment the data before publishing it.
A practical workflow looks like this:
- Connect the product source. Use your store or an existing file. The goal is to read fields such as ID, title, link, image, price, sale price, stock and category.
- Map the fields. Match your catalog fields to what the destination requires: price, availability, link, image or identifier.
- Normalize with rules. Clean values, complete fields or transform data. For example: “if stock is 0, exclude from the promotions set” or “if the sale end date has passed, do not use the sale price”.
- Create product sets. Segment the catalog by intent: available products, active offers, gift ranges or seasonal items.
- Generate the channel feed. Each destination may require a specific format. With Export Channels, you can prepare feeds for Meta, Google Shopping, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising, Thribee, ChatGPT and a custom channel.
- Review errors and warnings. The analyzer checks each feed against the channel specification. This can help catch missing fields or formatting issues, but it is not a guarantee of approval by the platform.
- Copy the feed URL into the channel. The URL is generated at the moment of each download. The channel then reads it according to its own settings and frequency.
That last point is essential: the tool’s import frequency and the channel’s download frequency are different. A live feed helps keep the output current and reduces repetitive manual edits, but it does not promise instant synchronization inside every ad platform.
If you also show product data inside the ad image, the Templates Editor can generate one image per product using catalog fields such as photo, title, price and brand. In that case, promotion dates deserve extra attention because the price is no longer only in the feed; it is visible in the creative too.
Test changes with one SKU first
Before applying a rule to thousands of products, test it with one representative SKU. Choose an item that has a normal price, a sale price and controlled stock.
Use this checklist:
- Change the SKU’s stock or price in the store or source file.
- Check that the new value is imported into your feed workflow.
- Confirm that the rule includes or excludes the product as expected.
- Open the feed URL or preview the output if your workflow allows it.
- Verify that the product ID has not changed.
- Compare price and link with the product page.
- After the channel downloads the feed, review any errors or warnings.
Testing one SKU prevents two problems: assuming a rule works because it sounds logical, and discovering too late that it affected products that should not have changed.
It also helps with documentation. If several people manage campaigns, write down which rule controls stock, which rule controls promotions and which product set feeds each campaign.
Common mistakes when updating product price and stock
Even with a good feed workflow, some process mistakes happen again and again:
- Using a manual export once a day for fast-moving inventory. This may work for small catalogs, but it is risky when availability changes often.
- Sending products without valid links. If the shopper cannot reach the product page, the product should not be active in performance campaigns.
- Mixing business rules with one-off manual fixes. Exceptions can break the logic of the feed.
- Ignoring promotion end dates. A discount without a clear expiry can keep appearing after the campaign is over.
- Using one generic feed for every channel. Each platform has its own required fields, accepted values and formatting.
- Changing IDs during a migration. This can disrupt how the channel recognizes products.
A useful rule of thumb: every value shown in an ad should be traceable to a specific field in the catalog. If you do not know where a price, discount or availability value comes from, it will be hard to fix when something goes wrong.
What to do this week
- Audit 20 active products. Choose items from different categories and compare store, feed and ad data. Check ID, price, availability, link and image.
- Find promotions with end dates. If you run temporary discounts, confirm that your feed separates regular price, sale price and promotion expiry.
- Define your stock exclusion rule. Decide whether sold-out products should be excluded from promotional sets or sent as unavailable, depending on the channel and your strategy.
- Create a set for active offers only. Do not mix always-on products with weekend deals or short campaigns.
- Test one SKU before scaling. Change price or stock for one product, inspect the feed and wait to see how the channel processes it.
Keeping product price and stock updated is not about chasing errors every morning. It is about building a workflow where changes are imported, transformed, checked and published in a way your team can understand. If your catalog changes often, start with the source data, the rules and the feed URL; scaling channels and creatives becomes much easier after that.
Frequently asked questions
How often should I update product price and stock in my feed?
It depends on how often your catalog changes and how frequently each advertising channel downloads the feed. Fast-moving inventory needs more regular imports and a feed URL that reflects current data. However, the channel may still read the feed on its own schedule, so do not assume instant updates everywhere.
Should I exclude out-of-stock products or send them as unavailable?
It depends on the channel and campaign strategy. For active sales campaigns, excluding sold-out products from promotional sets is often cleaner. In other cases, sending them as unavailable may be acceptable if the platform supports it. The important point is that feed availability matches the store and landing page.
Does an updated feed guarantee that all products will be approved?
No. A well-prepared feed can reduce formatting issues, inconsistent data and manual work, but every platform applies its own policies and review processes. Landing pages, required attributes, market rules and product category can all affect approval. Always review feed errors and warnings before scaling campaigns.
Sources
- Feed Manager de AdMotion — AdMotion
- Especificación de datos de producto de Google — Google
- Export Channels de AdMotion — AdMotion
Related posts

Product feed format: CSV, XML or Google Sheets?
Choosing between CSV, XML and Google Sheets is not just a technical preference. It depends on catalog size, update frequency, team workflow and the ad channels you need to feed.

Feed rules: how to clean titles, prices and descriptions without editing products one by one
Feed rules help you fix repetitive catalog data issues without editing every product manually. Learn how to remove HTML, normalize prices and improve titles with a safe, reviewable workflow.

Product titles: how to clarify variants without stuffing your feed
Product titles help Google Shopping, Meta and other channels understand what each catalog item is. Learn a simple brand/type/attribute pattern to describe variants clearly without artificial keyword stuffing.