Skill: Investigate Price

---
name: investigate-price
description: Compares the lowest raw price from the storefront's active public price lists with the storefront preview for a Norce SKU. Explains any discrepancy — identifying whether the problem is in the data, business logic, VAT, rounding, or propagation lag.
---

You are investigating a potential price problem for a Norce SKU.

Application ID: Use the application ID from your session instructions. If no
application ID is available, ask the user which storefront to investigate before
proceeding.
SKU to investigate: $ARGUMENTS

If no SKU is provided, ask the user for the PartNo before proceeding.

**Step 0 — Resolve application context**

Run the following two lookups in parallel before checking prices:

1. **Primary currency** — call norce_config_get_application_overview for the
   application ID. Retrieve the primary currency for this application. Use this
   currency for all price calls below.

2. **Public price lists** — call norce_pricing_list_price_lists filtered to this
   application. Collect the codes of all active, public price lists assigned to
   the application. These are the price lists a storefront customer is exposed to.

**Step 1 — Gather prices**

Run the following two calls in parallel:

1. **Raw stored prices** — call norce_pricing_get_sku_prices for this PartNo,
   filtered to the public price lists identified in Step 0. Retrieve all active
   prices across those lists. Identify the lowest active price and which price
   list it comes from.

2. **Storefront preview** — call norce_pricing_preview_prices for this PartNo
   with the application ID and primary currency from Step 0. Retrieve the
   calculated price shown to a customer, including VAT breakdown and any rule
   adjustments.

**Step 2 — Diagnose**

Compare the lowest raw price from the public price lists with the storefront
preview price and produce a diagnosis:

---
**Price investigation — [PartNo]**
Application: [storefront name]
Currency: [currency code — from application config]
Investigated: [timestamp]

**Raw price (public price lists)**
- Lowest active price (ex. VAT): [amount] [currency]
- Price list: [code and name]
- Other active public prices: [list any additional public price list prices]
- Last updated: [date]

**Storefront preview price**
- Price shown to customer (inc. VAT): [amount] [currency]
- Price ex. VAT: [amount] [currency]
- VAT rate applied: [%]
- Price list rule adjustment: [description or "None"]
- Rounding applied: [yes/no, rounding rule name]

**Diagnosis**
Are the prices consistent? State clearly whether the price looks correct or
whether a discrepancy exists.

If a discrepancy exists, identify which of the following is the most likely
cause and explain it:
- **Data problem** — the wrong price is stored (e.g. import error, wrong
  price list code)
- **Price list rule** — a rule is applying an unintended discount or markup
- **VAT misconfiguration** — the VAT rate applied does not match what is
  expected for this product or sales area
- **Rounding** — rounding rules are producing an unexpected result
- **Propagation lag** — the import completed recently and the storefront
  preview may not yet reflect the new price (wait and check again)
- **Wrong application** — the storefront is using a different price list than
  expected for this application

**Recommended action**
State clearly what needs to be investigated or fixed, and which team or
system owns the fix.
---

If the user provides multiple PartNos, investigate each one separately and
produce a summary table at the end showing which SKUs have discrepancies.

If the user asks to compare prices across two storefronts, run Step 0 for
each application to get its primary currency and public price lists, then
run Step 1 for each. Pass the same currency ID to both preview calls so the
Pricing MCP converts using Norce's stored exchange rate. Small differences
caused by rounding in the target currency are expected and should not be
flagged as errors unless the difference exceeds what rounding would explain.