Please audit and refresh the pricing in my FlipperForce Material Catalog.
1. Pull every material in my catalog with its title, current price, unit, SKU and product URL. Change nothing yet.
2. Tell me how many materials you found and how many have a product URL on file. Materials with no URL cannot be checked and should be listed separately for me to handle by hand.
3. For each material that has a URL, look up the current price on that product page. Do not substitute a similar product. If the page is gone or the item is discontinued, say so and move on.
4. Compare the current price to the price in my catalog and calculate the difference in dollars and percent.
5. Show me a table sorted by largest change first: title, catalog price, current price, difference, and where you got the number. Group anything that moved less than 2 percent at the bottom.
6. Flag anything suspicious rather than applying it. A price that moved more than 40 percent, a page showing a sale price rather than a regular price, a unit that does not match what my catalog says, or a page you are not confident is the same product.
7. Wait for my confirmation. Update only the materials I approve, and update only the price. Do not touch the title, unit, category, SKU or thumbnail.
8. When you are done, list what was updated with the old and new price for each, so I have a record of what changed.
Do not delete any material, do not create new ones, and do not update a price you had to estimate.
This is the highest risk automation in the library. It overwrites values you already have, and a wrong price in the catalog flows straight into your repair estimates and your material budget. Review the table properly rather than approving in bulk.
Price accuracy depends entirely on the product page. Retailer sites show regional pricing, sale pricing and bulk pricing, so a number that looks wrong usually is. That is what the flag list is for.
Updating an existing material already in an estimate changes the catalog record, not estimates that were already built. Rebuild or reselect the material on a project if you want the new price to carry through.
Each material is checked and updated individually, so a large catalog takes a while and can hit rate limiting.
You built the catalog once, from prices that were accurate the week you built it. Material prices move constantly, and nothing in the catalog tells you which ones have drifted.
So the estimator keeps pulling last year's number for a vanity that now costs $180 more. Nobody catches it, because the price looks specific and specific numbers feel trustworthy. The drift shows up at the end, as a material budget that came in over for no reason anyone can point to.
Your assistant reads every material in your catalog, visits the product URL on each one, and compares the price on the page today against the price stored in FlipperForce. You get a table sorted by biggest movement, with the source for each number.
Nothing is written until you approve it, and only the price field is touched. Anything that looks wrong, a discontinued item, a sale price, a mismatched unit, or a page that may not be the same product, gets flagged for you rather than applied.
What it will not do: it does not update a price it had to estimate, does not substitute a similar product when the original is gone, does not change the title, unit, category, SKU or thumbnail, does not create or delete materials, and does not apply a single change before you approve it.
This prompt requires a connection to the FlipperForce Public API. Once your AI agent is connected to your account, you can run any prompt in the library.
Learn how to connect your AI agent to the FlipperForce Public API
Before you run this, check:
Start with one category rather than the whole catalog. Check that the prices it comes back with match what you see on the page yourself, then widen the scope.