AI Agent Hub
Back to skills
Longway ERP Read-Only Queries icon

Longway ERP Read-Only Queries

Business Operations Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @org-qzhylp8y/longway-erp-skills into my AI assistant.

About this skill

Longway ERP business data is spread across RFQ, inventory, sales, purchasing, receivables, payables, and customer profiles. When querying from a conversational host, engineers face two common problems: business fields, statuses, enum values, and pagination rules are hard to align, and hand-built HTTP or JSON calls can easily mishandle authorization links, host identity, and data formatting. This skill keeps those constraints inside the bundled lw-erp CLI, while the host only calls the CLI, reads stdout, and programmatically parses authorization JSON.

Core Capabilities

  • RFQ: rfq-inquiry queries customer inquiries, and rfq-seek queries supplier quotations.
  • Inventory and pricing: inventory queries model stock, in-transit quantity, cost, sales price, and purchase price.
  • Sales management: covers sales-order, sales-delivery, sales-return, and sales-quotation, with filters for customer, salesperson, product, and status.
  • Purchasing management: covers purchase-order, purchase-receipt, and purchase-return, with filters for supplier, purchaser, product model, and status.
  • Receivables and payables: ar-receivable, ap-payable, and arap-payment-record query outstanding balances, overdue records, receipts, and payments.
  • Customer relationships: customer and supplier query customer or supplier profiles, including trading and contact recency signals.

Boundaries

The skill is read-only and does not promise to modify ERP data. The host must explicitly provide host-type and current logged-in user context identity parameters, such as openid or unionid; these are not Longway ERP user IDs and must not be asked from end users. Authorization buttons must come from the CLI stdout authorization JSON. The host should only parse label and url, then render the clickable Markdown link unchanged, without rewriting, compressing, masking, or reordering the URL. Before querying or authorizing, read references/operating-contract.md to confirm installation, exit codes, polling, field validation, pagination, and --filter enum contracts.

Use Cases

  • Sales ops checks a customer's sales order, delivery note, and collection status before responding.
  • Procurement verifies supplier delivery against the purchase order, receipt note, and payment status.
  • Finance reviews customer and supplier receivables and payables by overdue status at month-end.
  • Customer success checks customer profile for last trade and contact recency to plan follow-up.

Best For

  • Sales operations who need customer, salesperson, and product-level order, delivery, and collection status.
  • Purchasers who need supplier, buyer, and model-level purchase, receipt, and payment progress.
  • Finance staff who need receivable and payable balances, overdue items, and payment records for reconciliation.
  • Customer success staff who need customer and supplier profiles plus trading and contact recency for follow-up.