Norce Backend MCP Servers for Pricing Managers

This guide is for pricing managers who want to use AI to work faster and more accurately with pricing in Norce Commerce. It assumes the Backend MCP Servers are already connected to your AI assistant — if not, start with Using the Norce Backend MCP Servers.

What changes for a Pricing Manager

The Admin UI lets you inspect one price list or one product's price at a time. It is not built for running structural audits across all price lists, comparing prices across storefronts, or checking compliance across hundreds of SKUs before a sale.

With the Pricing MCP connected to an AI assistant, you can:

• Audit the full price list configuration and catch structural problems — missing warehouse links, invalid rules, expiring lists, mixed currencies — before they cause issues in production
• Investigate price discrepancies by comparing the raw stored price with what the storefront actually shows, and across different storefronts simultaneously
• Set up and preview campaign pricing before it activates — create a price list with a future start date and inspect the resulting prices in the backend straight away
• Run Omnibus compliance checks before a sale to verify that advertised discounts reference the actual lowest price in the last 30 days
• Import prices from external systems and verify that the data landed correctly before relying on it

Skills for Pricing Managers

Two skills handle the most common recurring checks. Install them once and they run immediately.

• Check Pricing Health — audits the full price list configuration and returns a plain-language report classifying every finding as Critical, Warning, or Passed. Run before any significant change or on a scheduled weekly basis.
• Investigate Price — given a PartNo, fetches the raw stored price and the storefront preview side by side and diagnoses any discrepancy from six named causes.

See the Skills customization guide for how to pre-wire your application ID and currency.

Campaign price list setup and preview

Setting up a campaign price list involves several steps — creating the list, linking it to a parent price list and sales area, configuring pricing rules, and optionally narrowing it to specific products, manufacturers, or flags. The AI handles the full sequence and confirms each step before proceeding.

A key advantage: when you set a future start date on the campaign price list, you can query the backend to preview what prices products will have when the campaign activates — before any customer sees it. This lets you validate the outcome in advance and catch configuration errors while there is still time to correct them.

Sample prompts

"Set up a new campaign price list for our Summer Sale. It should apply a 20% discount on top of our standard retail price list, run from July 1st to July 31st, and apply only to products with the 'Summer' flag (ID 55)."

"The Summer Sale price list is set up. Before it goes live, show me what prices 10 of our top products will have when the campaign activates: [list]."

"Check the Summer Sale price list configuration — run full validation and tell me if there are any issues that would prevent it from working correctly."

Reusing a permanent campaign price list

A common pattern is to maintain a permanent campaign price list and control which products are included by adding or removing them from a campaign flag, rather than creating and expiring a new price list for each campaign. This works well with scheduling — prepare products today, preview their prices, and schedule the flag assignment to happen at a specific time.

"We're adding 10 products to our ongoing Clearance campaign on Monday morning. Preview how they will be priced once they're included in the Clearance price list, and confirm they all look correct."

"Schedule the following 10 products to have the Clearance flag (ID 40) added on Monday at 06:00. Today, show me a preview of how they will be priced once the flag is applied."

Omnibus compliance check

The EU Omnibus Directive requires that any advertised "reduced from" price references the actual lowest price charged for the product in the preceding 30 days. norce_pricing_get_best_price_history retrieves this history from the Norce audit log.

Run this check before any sale campaign to verify compliance — and export the results as evidence if needed.

Sample prompts

"Before we launch the Summer Sale on July 1st, check the lowest price recorded for each of these SKUs in the 30 days before the sale: [list]. Flag any where our planned sale price would be presented as a discount from a higher price than the actual 30-day low."

"We're planning to mark these products as 30% off from their regular price. Check the Omnibus history for each one and confirm we're compliant: [list]."

"Run an Omnibus compliance check for our entire Summer Sale product range. Use the flag 'Summer' (ID 55) to identify the products and check 30 days back from June 30th."

Price import and verification

When importing prices from an external system — an ERP, a supplier feed, or a pricing tool — the full workflow involves submitting the import, polling for completion, and spot-checking that the data landed correctly.

A short propagation delay is normal after a price import before the storefront preview reflects the new values. Wait a moment before running a preview check to avoid treating a propagation lag as an import failure.

Sample prompts

"Import these retail prices to our standard price list. The data is attached. Let me know when the import is done and verify a sample of 5 SKUs afterwards."

"The price import finished — check these 10 SKUs and confirm the new prices match what we sent: [list]."

"I have a campaign price file with prices for both Sweden and Norway mixed together. Identify which price list each record belongs to, then import the Swedish prices to our Swedish campaign price list and the Norwegian prices to our Norwegian campaign price list."

For file-based imports that recur regularly — for example a weekly supplier cost price feed — consider using the Import from File skill, which saves the field mapping after the first import so subsequent runs need no setup.

Tips

Combine with the Config MCP to look up sales area IDs and VAT code IDs when setting up or modifying price lists. These are required for correct price list configuration and can be fetched without leaving your conversation.

Combine with the Product MCP for cross-domain validation — check_price_list_setup can flag pricing rules that reference deleted product flags, categories, or manufacturers when you have context from the Product MCP.

Use norce_config_list_applications to confirm which application IDs correspond to which storefronts. Include them in your instructions so you do not have to look them up each session.

Always preview campaign prices before launch. A campaign price list with a future start date can be fully validated — pricing rules, population rules, and resulting prices — before it goes live. Build this preview step into every campaign setup workflow.