一键导入
pricing-reconciliation
Analyzes and resolves CPG pricing discrepancies using deterministic ERP recipes and retailer contract RAG.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyzes and resolves CPG pricing discrepancies using deterministic ERP recipes and retailer contract RAG.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Classifies a post-extraction email-channel sales-order envelope into one-click approve, standard review, low-confidence, or fatal-reject. Triggered on EMAIL_ORDER_ENTRY_REQUEST events.
Triaged a back-order / out-of-stock condition on an inbound order line and ranks resolution options — alternate DC, substitute SKU, split shipment, or reschedule. Triggered on BACK_ORDER_OOS events.
Classifies shipment delay severity (SD-DELAY-001 minor / SD-DELAY-002 severe) and ranks expedite / split-ship / reschedule options. Triggered on DELIVERY_DELAY events.
Detects and classifies Duplicate Purchase Order (PO) exceptions in B2B order intake. Triggered on EDI_850_DUPLICATE_PO events.
Classifies non-duplicate EDI 850 line mismatches (SKU, qty, UOM, ship-to) and selects the appropriate resolution path. Triggered on EDI_850_LINE_MISMATCH events whose metadata.mismatch_sub_type is not PRICE_MISMATCH.
Decides whether to round a PO line up to the Minimum Order Quantity, accept below MOQ, or escalate for a KNMT waiver. Triggered on MIN_ORDER_QTY events.
| name | pricing-reconciliation |
| description | Analyzes and resolves CPG pricing discrepancies using deterministic ERP recipes and retailer contract RAG. |
| metadata | {"version":"1.2.2","author":"CPG Expert-Systems-Architect","required_tools":["mcp-sap-connector","mcp-pinecone-search"],"recipes":["PriceAdjustmentRecipe.py","CreditHoldReleaseRecipe.py"],"constrained_generation":["Guidance","Outlines"]} |
This skill is triggered when an inbound order (EDI 850) contains a price variance compared to the SAP Master Data. It determines the intent of the discrepancy and applies a deterministic Recipe to execute the fix.
Use Guidance / Outlines for all machine-consumed outputs:
PriceAdjustmentRecipe.pyCreditHoldReleaseRecipe.pyFAIL_TO_HUMANBefore calling any recipe, check the Compliance Shadow. If the shadow returns RED, halt execution and explain the compliance breach.
Always include the Recipe Execution Log snippet for audit traceability.