Bulk product FAQs on Shopify are how a catalog gets answers without opening every product by hand. Product FAQs for AI Crawler can loop FAQ generation across the products you select. Each pass uses the same generation call for that product. You still review the draft before you save it. A run that starts many products does not skip the edit.
Shopify Managed Pricing enforces a monthly FAQ-creation limit on AI generation and on manual creation. When the limit is reached, creation is blocked and the app shows an upgrade prompt. The feature catalog does not state a product count or a price for that limit. Match the work to the allowance you see on the plan screen in the app. A staff note that quotes a number from somewhere else will go stale the moment the plan screen says otherwise.
What a bulk pass actually does
You pick products with Shopify's resource picker. Bulk mode loops the per-product call. For each product, the app reads the title, description, vendor, and type, sends that to the generation service, and returns FAQ content in the editable wizard. It does not merge the catalog into one shared answer. A shirt and a candle should not inherit each other's drafts.
The catalog does not describe a fixed batch size. Plan your time as one review per product, even when the selection was large. If the description is thin, the draft will be thin. Fill in materials and measurements on the product before you generate, or expect to delete most of the draft. Description mode, with clarification questions, is the other path when you are writing from a paragraph rather than from a saved product.
- Selection: one or more products from the resource picker.
- Loop: the same generation call, once per product.
- Inputs: title, description, vendor, and type.
- Output: editable FAQ content, not a live storefront update, until you save.
Review before you publish
Generated FAQs are fully editable before saving. In a bulk run this is the whole job. Open each draft and look for a measurement, a material, or a policy the source text does not contain. Delete that sentence. Keep the question if you can answer it yourself from the spec sheet. Assign the group to the product it belongs to. A shop-wide group, with no products assigned, is the wrong place for a fit note that is true of one SKU.
Saving writes the group's fields, its question and answer pairs, and its product links. The storefront reads Shopify metafields from that save. It does not call the app just to display the FAQ. If you fix a draft later, edit the group and save again so the metafield updates. There is no accuracy score in the product that can approve a batch for you.
When the monthly limit stops the run
The limit is checked on the creation flow. A long selection can run until the shop hits the monthly allowance, and then the next creation is blocked. That is expected behavior, not a broken loop. The upgrade prompt is how the app tells you the plan's limit is spent. The catalog confirms the prompt and the block. It does not confirm how many creations remain, because it does not publish the cap.
Spread the work across the month if the allowance is smaller than the catalog. Finish the products that generate the repeat emails first. A complete FAQ on the ten items people actually ask about is more useful than a shallow draft on every SKU. Manual entry uses the same monthly check, so typing the rows yourself does not bypass the limit.
After the groups are saved
Place the product-page block on the product template so assigned groups appear. Place the page block where a shop-wide group should show. The app embed loads the script. Choose Accordion, Grid/cards, Boxed, or Minimal per block. Add the widget search if the list is long. Search filters question and answer text inside the FAQ. It does not search the catalog.
Both blocks emit FAQPage JSON-LD in the light DOM from the saved FAQ data, outside the widget shadow DOM. Bulk generation does not change that. A bad sentence saved at scale is a bad sentence on every product you assigned. The admin list lets you search by name, filter by category, switch status tabs, and delete a group, including a confirmed multi-select delete. Use delete when a draft should not have been saved. Use edit when the facts are right and the wording is not.
Order the work by the questions that already arrive, not by the size of the catalog file. Generate the products support names most often, edit those drafts, and save them. Then select the next set. A loop that returns drafts for products with empty descriptions will spend the monthly allowance on text you have to delete. Fill the description, or skip that product, before you include it in the picker.
After a correction, reload the product page and read the widget, not only the admin preview. The shopper sees the metafield the block reads. If the old sentence is still there, the group was not saved, or the block is rendering a different group than the one you edited. Product assignment is the usual mix-up: the draft was saved on a shop-wide group, or on a sibling product. The listing is Product FAQs for AI Crawler.
Questions about bulk FAQ generation
Does bulk generation publish every product at once?
It loops a generation call per product and returns editable drafts. The storefront updates when you save, because save writes the metafield.
Where is the monthly cap written down?
On the plan screen in the app. The feature catalog says the limit exists and does not give the number.
Can I skip review if the description is detailed?
No. A detailed description still needs a person to confirm the draft did not add a claim. There is no accuracy score.
See how product selection and editing work on Product FAQs for AI Crawler. Generate a small set first, correct it, and only then select the next products.