Black Friday Product Feeds: Keep Sale Prices and Stock Accurate
Black Friday website series · 2026
Black Friday product feeds need to reflect the offer a shopper can buy at the time they open it. Check the exact variant, currency, current sale state and stock. Then apply the destination’s rules. Google Merchant Center and OpenAI’s native catalog upload handle sale dates differently.
Keep a record of the planned offer beside the current storefront data. A future discount can be correct in your campaign plan while the product is still selling at its regular price. Your export needs to represent the right state for the integration receiving it.
Which format does your Black Friday product feed use?
Identify the receiving platform, registered feed and upload profile. Keep that information with the export. The Google product specification and OpenAI’s native specification describe their supported fields. Check the confirmed integration before translating an existing file.
Use the production specification for the destination you have selected. Keep a copy of the original export so a correction can be traced to the source record. Preserve identifiers as text, including any leading zeros. A spreadsheet that rewrites an ID can make two reviews appear to concern different items.
| Purpose | Google Merchant Center | OpenAI native upload |
|---|---|---|
| Item identifier | id | item_id |
| Product page | link | url |
| Main product image | image_link | image_url |
| Price | price, with currency | price, with currency |
| Sale price | sale_price | sale_price |
| Preorder stock value | preorder | pre_order |
| Sale interval | sale_price_effective_date | Uploaded sale dates do not schedule native price changes |
Start with the item the shopper will receive
Open the variant URL from the export. Check that it selects the size, color or edition represented by the row. Compare the image and stock status with that selection, then add the same item to the basket. Review the price in the currency that customer can actually use.
Keep the regular price, sale price and payable item price clearly named in your review. They can describe different parts of the same valid offer. Compare each value with its corresponding source field before deciding that a mismatch exists.
Make the product page readable at that destination. Use a descriptive title and H1, an accurate meta description, useful image alt text and links to delivery and returns information. A visitor following a shopping result should understand the selected product and the conditions attached to its offer.
Check what the sale dates actually control
Google’s effective-date attribute takes a start/end interval separated by a slash. Use explicit times and offsets for your campaign. A missing time zone falls back to UTC. Record the store’s intended schedule beside the raw interval so the reviewer can compare them.
For OpenAI native uploads, update the current price and stock when the offer changes. Its separately documented Promotions API has an active_period with start_time and end_time. Keep that structured promotion record aligned with the catalog and checkout.
| Route | Timing behavior | Work to assign |
|---|---|---|
| Google sale-price interval | Defines when the supplied sale price should display | Review the interval, offset and matching storefront price |
| OpenAI native product row | Carries current price and stock; uploaded dates do not activate changes | Prepare current-value updates for sale start, end and stock changes |
| OpenAI structured promotion | Uses active_period.start_time and active_period.end_time | Review the promotion’s benefits, targets and timing alongside checkout |
Review exported rows before the next upload
Choose the destination below and paste a small export from the catalog you are preparing. Keep the column headings. Start with the promotion’s priority variants, then review the reported issues against the live product pages and the integration’s specification.
Fix a repeated issue in the source system or export rule so the next file carries the correction too. Keep the affected item IDs with your release notes. For each row you change, record what was wrong, the new value and the time it was checked.
Use the results to prepare the upload review. The receiving platform’s processing status and the live offer are the next checks. A local row check describes the supplied file; a displayed product requires the rest of the integration to work.
Check a product-feed CSV
Paste a CSV export with its header row. This local preflight checks selected fields and sale rules for the chosen destination. Review the platform processing report after submission.
Pay attention to prices, stock and working URLs
A sale price needs the correct currency and relationship to the regular price. In the native OpenAI format, sale_price must be positive, lower than price and in the same currency. Check decimal formatting before making a bulk replacement across an export.
Stock needs a destination-specific value. An available parent product can have a sold-out variant. Check the exact selection represented by each row, and assign the update that follows a stock change. Use a separate review for backorders and preorders so their delivery information remains clear.
Follow product and image links after any URL change. Keep the selected variant intact through redirects. Review how products appear in AI shopping when deciding which product facts belong in the catalog and on the page.
Give the first update and the final update an owner
Name the person who changes the storefront price, the person who submits the export and the person who reviews the destination. They may be the same person. Record the order of those actions and the expected checks, including what happens if processing is delayed.
Keep the previous working export available. If a change affects the wrong variants, correct the source record and review the replacement file before resubmitting it. Check both a changed item and an unaffected item so a broad export rule does not hide a second problem.
Tie those updates into the website campaign schedule. Put the end-of-sale task on that schedule before the first promotional email goes out. An offer that ends in the store still needs its catalog and campaign material checked.
Keep coupon rules connected to the product data
A product sale and a basket coupon can have different eligibility rules. Record whether the offer changes the item price, requires a code, depends on basket value or applies only to a customer group. Test the intended purchase with the rule active.
For email promotions, the Gmail offers article covers the information that should stay understandable outside an email’s artwork. For purchase integrations, the agentic commerce guide explains the wider handoff from product information to checkout.
Frequently asked questions
More from this series
- Black Friday Website Preparation: SEO, AI Shopping, and Checkout
- Black Friday Landing Pages: What Shoppers Need Before Buying
- Why Black Friday Coupons Fail at Checkout
- Speed Up Your Store Before Black Friday Traffic Arrives
- How Much Can You Afford to Discount for Black Friday?
- Measure Black Friday Traffic From Google, ChatGPT, and Email
- What Happens to Your Black Friday Pages After the Sale?
Sources
See what ChatGPT is really searching
SubSeed captures the hidden Google queries ChatGPT runs behind every answer and enriches them with search volume, CPC, and keyword difficulty.
Related Posts
Read this post with an assistant
This is the whole prompt each button sends. Nothing hidden in it.
Read https://gridlok.co/blog/black-friday-product-feeds/ and give me the main points in a few sentences.
Make Gridlok a Preferred Source on Google
See Gridlok surfaced more often in your Top Stories, AI Overviews, and AI Mode. One click, applied across Google Search.