← Pretture ERP AICONTENT HISTORY
WHAT CHANGED
Update to Pretture ERP AI
Snapshot Oct 26, 2026 · 12:07 UTC · version 1.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Pretture ERP AI and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use Pretture ERP Analytics to run safe backend-calculated sales reports.",
"included_files": [],
"name": "pretture-erp-get-started",
"skill_md_contents": "---\nname: pretture-erp-get-started\ndescription: Use Pretture ERP Analytics to run safe backend-calculated sales reports.\n---\n\n# Pretture ERP Analytics\n\nUse this plugin when the user wants to summarize Pretture ERP sales, review sales breakdowns, apply sales filters, or include/exclude returns in backend-calculated sales metrics.\n\n## How To Use The MCP Tools\n\n1. Call `get_sales_analytics` for total sales KPIs over an inclusive date range.\n2. Use the `group_by` argument for monthly, yearly, customer, product, store, location, category, subcategory, or size groupings.\n3. Use the `filters` argument for exact-match sales filters such as customer, store, city, category, product, size, color, sales type, sales nature, or transaction type.\n4. Use `include_returns=false` only when the user asks to exclude return rows; otherwise keep the backend's net-sales return handling.\n5. Treat the backend response as the source of truth. Do not recalculate sales, returns, costs, counts, or profit from raw rows.\n6. Do not ask users for ERP JWTs, API keys, OAuth tokens, or credentials in chat. Authentication is handled by the Pretture MCP server.\n\n## User-Facing Behavior\n\n- Use `get_sales_analytics` only for read-only sales analytics requests.\n- If a user asks for unsupported ERP areas such as inventory or payments, explain that this plugin currently supports sales analytics only.\n- Report errors honestly, including authentication, disabled API, validation, or upstream availability failures.\n- Keep responses focused on business outcomes and cite the returned date range, grouping, and filters when relevant.\n\n## Safety Boundaries\n\n- Do not expose or request credentials.\n- Do not perform payment, deletion, or destructive ERP actions.\n- Do not infer private ERP records outside the connected user's authorized scope.\n"
}SHA-256 of public snapshot: fcf77742af3e51b1dc366d37d3e6b62790ba2e1658f35d075eb1068d93007276