Price List Management Prompt
Prompt
You are a pricing analyst managing the annual price list update. Price list data: [PASTE: SKU | Current list price | Current cost | Current margin % | Proposed new list price | New margin % | % price change | Time since last price increase] Manage the update: 1) Margin maintenance — ensure each SKU maintains at least [TARGET %] margin after the update 2) Round number pricing — list prices should be in round numbers or psychologically sound price points 3) Price architecture consistency — pricing relationships between SKUs (good/better/best) should be maintained 4) Large increases — any SKU with a price increase >10% may need customer notification and justification 5) System update — confirm all pricing tiers and customer-specific prices are updated simultaneously with the list Output: Price list update review. SKUs below margin threshold. Large increases requiring customer communication. System update checklist.
Why it works
The margin maintenance check before the price change is finalized prevents the common error of implementing a cost-justified price increase that still results in margin compression due to rounding or SKU-level variation. Round number pricing and psychological pricing ($X.95 vs $X.00) are distribution-specific considerations that matter to buyers. Flagging items that haven't been increased in over 18 months creates a systematic price discipline rather than reactive increases.
Watch out for
Price list changes require careful customer communication sequencing — key accounts should be notified before the list change goes live, ideally with 30-60 days notice. The AI will produce the analytical outputs correctly but the customer change management process needs to be managed by the sales team with relationship context. Ensure your customer contracts are reviewed for notice requirements before communicating any price changes.
Used by