/
/
Find estimating catalog costs that have drifted
For estimating and purchasing teams who want Procore catalog unit costs compared with Business Central item costs, by asking their AI assistant.
On this page
Connector
Connect Procore, pick your AI tool and paste the prompt.
The problem
Catalog unit costs go stale unnoticed
Estimators price from catalog costs in Procore while purchasing costs change in Business Central. Comparing them item by item is slow, so drift builds up until an estimate comes in under what the work costs.
Without PopdockAI
- Export the catalog items from Procore
- Look up each item in Business Central by number or description
- Check units agree before comparing costs
- Work out the percentage difference for every item
With PopdockAI
- Catalog items matched by number first, then description
- Approximate and ambiguous matches kept separate
- Costs compared only where the units agree
- Items outside your tolerance listed with counts by match type
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** For the Procore estimating catalog {catalog-name}, find catalog items whose unit cost differs from the matching Business Central item by more than {tolerance-percent} percent (default 10), so estimates are priced from current costs.
**Step 1: Read the catalog items (procore-preconstruction server)**
Call `procore-get-estimating-catalogs-items` with {catalog-name} as `catalog-name` and `max-records` of 100. Keep name, catalog-number, description, unit, unit-cost and unit-labor-cost. If no catalog matches, call `procore-get-estimating-catalogs` with no filter, list the catalog names and stop.
**Step 2: Find the matching items in Business Central (business-central server)**
For each catalog item, call `business-central-get-item` with the catalog-number as `item-number`. If that finds nothing, call it again with the item name as `description.contains`. Treat an item-number match as exact and a description match as approximate; if a description search returns several items, record it as ambiguous. Keep item-number, unit-cost, last-direct-cost, standard-cost, unit-price, base-unit-of-measure and blocked.
**Step 3: Compare**
For matched items compare the catalog unit-cost with the Business Central last-direct-cost, or with unit-cost when last-direct-cost is zero. Only compare when the Procore unit and the base-unit-of-measure agree; otherwise report a unit mismatch instead of a cost difference.
**Step 4: Report**
Table of items outside the tolerance: catalog item, match type, Procore unit-cost, Business Central cost used, difference in percent, and blocked flag. Then counts of items matched exactly, matched approximately, ambiguous, unit mismatched and not found.
**Rules & Guidelines:**
* `procore-get-estimating-catalogs-items` and `procore-get-estimating-catalogs` are on the procore-preconstruction server. `business-central-get-item` is on the business-central server.
* Do not call any create or update tool on either server. Never change catalog prices or Business Central items; only report the drift.
* Do not assume the catalog uses Business Central item numbers; say how many matched by number versus by description.
**Validation:**
* If most items are not found by either route, say the catalog does not map to Business Central items and stop before listing every item as missing.
* Procore and Business Central may use different currencies; do not compare figures across currencies.Who it's for
One answer, three teams that use it
Estimators
Reprice from costs you can trust
See which catalog items are out of line with current purchasing costs before building an estimate.
Which items in the Electrical catalog are more than 10 percent from Business Central costs?
Purchasing managers
Tell estimating where prices have moved
Give estimating a list of items whose purchase cost has shifted, with the size of the move.
Compare the Concrete and Steel catalog with Business Central item costs and flag big movers.
Preconstruction leads
Check the catalog maps to the ERP
Find out how many catalog items match Business Central by number or only by description.
How many items in the Mechanical catalog match Business Central by item number, and how many only approximately?
How it works
What PopdockAI does when you ask
You name the catalog and your AI assistant matches it to Business Central items. It only reports the drift and never changes prices or items.
Ask
You name the catalog and optionally a tolerance in percent.
Read
It reads the catalog items with their units and unit costs.
Match
It finds each item in Business Central by number, then by description, marking approximate and ambiguous matches.
Report
You get items outside tolerance with the difference in percent, and counts by match type and unit mismatches.
What PopdockAI provides
The tools behind the answer
Ready made tools for Procore and one secure connection to your AI tool. No code, no exports.
procore-get-estimating-catalogs-items
procore-get-estimating-catalogs
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Estimates priced from current costs
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
