/
/
Find store SKUs missing from Dynamics GP and drifting prices
For operations teams who want the WooCommerce catalog matched to Dynamics GP items by SKU, with prices compared, by their AI assistant.
On this page
Connector
Connect WooCommerce, pick your AI tool and paste the prompt.
The problem
Store products with no ERP item and drifting prices
Products get added to WooCommerce without a matching item in Dynamics GP, and store prices drift from the GP list price. Checking each product and variation one by one rarely happens until an order fails.
Without PopdockAI
- Open each product and variation
- Look up its SKU in Dynamics GP
- Compare store price with the GP list price
- Find out when an order fails
With PopdockAI
- Products and variations are read
- Each SKU is looked up by exact item number
- Store prices are compared with the GP list price
- Multiple price rows are listed rather than flagged, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Compare the WooCommerce catalog with Dynamics GP items, matching store SKU to GP item number, for products in category {category} (default: all categories), up to {max-products} products (default 100), and report SKUs missing from GP and list price differences in currency {currency-id} (default: whatever currency GP returns).
**Step 1: Read the store catalog (woocommerce)**
Call `woocommerce-get-product` with max-records set to {max-products} (default 100), and categories.contains set to {category} when it is given. For every product whose type is variable, call `woocommerce-get-product-variation` with its product-id, because the variations carry the SKUs and prices. Keep the sku, name, regular-price and product or variation id of each. Set aside any product or variation that has no SKU.
**Step 2: Find each SKU in Dynamics GP (dynamics-gp)**
For each SKU call `dynamics-gp-get-iv-item` with item-number set to the SKU. If nothing comes back, record the SKU as in the store but not in GP and continue with the next one.
**Step 3: Compare list prices (dynamics-gp)**
For each matched item call `dynamics-gp-get-iv-item-price` with item-number, and currency-id set to {currency-id} when it is given. Use the row whose unit-of-measure equals the item's selling-u-of-m from step 2. Compare its list-price with the store regular-price. A difference under 0.01 is a match.
**Step 4: Report**
1. In the store, not in GP: SKU and product name.
2. Price differences: SKU, product name, store regular price, GP list price, difference. Sort by the largest difference.
3. No SKU in the store: product name and id.
4. Summary: products checked, matched, missing from GP, price differences, no price in GP.
**Rules & Guidelines:**
* Tools whose names start with woocommerce- are on the woocommerce MCP server; tools whose names start with dynamics-gp- are on the dynamics-gp MCP server. If a tool from either server is not available, stop and say which server is not connected.
* If the user names a Dynamics GP company, pass it as company on every dynamics-gp call.
* Match a store SKU to a GP item number exactly, after trimming spaces. If that fails, try the SKU in upper case once. Never match on descriptions or partial codes.
* This prompt is read-only. Do not call `woocommerce-update-product`, `woocommerce-update-product-variation`, `woocommerce-add-product`, `dynamics-gp-iv-item-add`, `dynamics-gp-iv-item-update`, `dynamics-gp-iv-item-price-add` or `dynamics-gp-iv-item-price-update`. To fix prices, point the user to the sync-prices-from-gp prompt.
* Work from the store side only. Do not page through every GP item looking for items the store lacks.
**Validation:**
* If step 1 returns no products, say so and stop.
* If GP returns several price rows for the selling unit of measure (for example one per currency) and {currency-id} was not given, list them all and do not flag a difference.
* If GP has no price row for the selling unit of measure, report the price as missing in GP, not as a difference.Who it's for
One answer, three teams that use it
Operations managers
Find SKUs missing from GP
Store SKUs with no GP item are listed, so they can be set up before orders arrive.
Which WooCommerce SKUs in the Accessories category are missing from Dynamics GP?
Pricing managers
Spot price drift
Price differences are sorted by size, so the biggest gaps get fixed first.
Show WooCommerce products whose price differs from the Dynamics GP list price.
Catalog managers
Fix products with no SKU
Products with no SKU are listed, since they cannot be matched to any item.
Reconcile the full WooCommerce catalog with Dynamics GP and list products with no SKU.
How it works
What PopdockAI does when you ask
You can name a category, and your AI assistant matches every store SKU to Dynamics GP. It only reports, so neither system is changed.
01
Ask
You name a category, or leave it open.
02
Read
It reads store products and their variations.
03
Match
It finds each SKU in GP by exact item number and compares list prices.
04
Report
You get missing SKUs, price differences by size and no-SKU products.
What PopdockAI provides
The tools behind the answer
Ready made tools for WooCommerce and one secure connection to your AI tool. No code, no exports.
woocommerce-get-product
woocommerce-get-product-variation
microsoft-dynamics-gp-get-iv-item
microsoft-dynamics-gp-get-iv-item-price
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
Catalog gaps and price drift caught early
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)
