AIMS360 Fashion & Consumer ERP

Fetch Invoices RECORDS (read-only): one specific invoice by number, or a filtered list where each row IS a invoice. Use for: "show invoice 12345", "list open invoices", "invoices on hold last month". Add selectFields/filters/sortSpec as needed — the server resolves field synonyms (e.g. "hold reason" → orderStatusReasonDescription) automatically; on a miss it suggests the right name. LINE-ITEM detail of a specific invoice: single_record + expand (lineItems for orders, invoiceLines for invoices) — one row per line item, in ONE call; don't retry with different expands. (Orders return per-line rows; for a per-SIZE breakdown use invoice_analysis with a size dimension.) Looking up a specific invoice by number is a single_record call with ONLY filters.orderNumber — do NOT add a dateRange (that filters it out). For totals, rankings, breakdowns, trends, or per-style/size aggregation, use invoice_analysis instead. queryKind: single_record (requires filters.orderNumber) or raw_list. Always pass the user's wording in userQuery and clientDate as YYYY-MM-DD.

get_invoice_details

Fetch Orders RECORDS (read-only): one specific order by number, or a filtered list where each row IS a order. Use for: "show order 12345", "list open orders", "orders on hold last month". Add selectFields/filters/sortSpec as needed — the server resolves field synonyms (e.g. "hold reason" → orderStatusReasonDescription) automatically; on a miss it suggests the right name. LINE-ITEM detail of a specific order: single_record + expand (lineItems for orders, invoiceLines for invoices) — one row per line item, in ONE call; don't retry with different expands. (Orders return per-line rows; for a per-SIZE breakdown use order_analysis with a size dimension.) Looking up a specific order by number is a single_record call with ONLY filters.orderNumber — do NOT add a dateRange (that filters it out). For totals, rankings, breakdowns, trends, or per-style/size aggregation, use order_analysis instead. queryKind: single_record (requires filters.orderNumber) or raw_list. Always pass the user's wording in userQuery and clientDate as YYYY-MM-DD.

get_order_details

Aggregate / rank / trend / total Invoices (read-only). Requires dimensionKey + metricKey. Invoices = SALES / SOLD / REVENUE (shipped & invoiced), units shipped, margin. Use for "total sales", "top sold styles", "revenue by month", "margin by customer". TOP-N: "top customers by $" → grouped_summary + dimensionKey=customer (one row per customer); "top styles/sizes by units" → line_items + dimensionKey=style/size. Pick queryKind by what the user wants ONE ROW PER, not the word "top". "by month / quarter / year" → grouped_summary + a date dimension + timeGrain. For a specific record, use get_invoice_details. Line-item-only metrics (ship_quantity, back_order_quantity) MUST use line_items. Always pass the user's wording in userQuery and clientDate as YYYY-MM-DD. The server resolves dimension/metric synonyms automatically. SUPPORTED DIMENSIONS: customer=Customer, invoice_status=Invoice Status, order_source=Order Source, shopify_store=Shopify Store, division=Division, season=Season, sales_rep=Sales Rep, bill_to_state=Bill-to State, ship_to_state=Ship-to State, term=Payment Term, ship_via=Carrier, invoice_date=Invoice Date, due_date=Due Date, style=Style, color=Color, style_color=Style + Color, size=Size, style_size=Style + Size, style_color_size=Style + Color + Size SUPPORTED METRICS: total_amount=Total Amount, merchandise=Merchandise, balance=Balance, invoice_count=Invoice Count, ship_quantity=Units Shipped, back_order_quantity=Units Back-Ordered, margin_pct=Margin %, aur=Avg Unit Retail, net_sales=Net Sales, gross_margin=Gross Margin SUPPORTED BASE PATTERNS: overdue=Overdue invoices — Open invoices where dueDate has passed, outstanding_balance=Outstanding balance — Open invoices with a remaining balance

invoice_analysis

Aggregate / rank / trend / total Orders (read-only). Requires dimensionKey + metricKey. Orders = BOOKED / ORDERED (backlog, open units, allocation) — NOT yet shipped. For SALES / SOLD / REVENUE / units-shipped / margin use invoice_analysis. TOP-N: "top customers by $" → grouped_summary + dimensionKey=customer (one row per customer); "top styles/sizes by units" → line_items + dimensionKey=style/size. Pick queryKind by what the user wants ONE ROW PER, not the word "top". "by month / quarter / year" → grouped_summary + a date dimension + timeGrain. For a specific record, use get_order_details. Line-item-only metrics (ship_quantity, back_order_quantity) MUST use line_items. Always pass the user's wording in userQuery and clientDate as YYYY-MM-DD. The server resolves dimension/metric synonyms automatically. SUPPORTED DIMENSIONS: order_source=order source, customer=customer, status=status, ship_to_state=state, division=division, season=season, sales_rep=sales rep, term=payment terms, ship_via=shipping method, buyer=buyer, vendor=vendor, retail_order=retail order, bulk_order=bulk order, entered_date=entered date, complete_date=complete date, start_date=start date, style=Style, color=Color, cancel_reason=Cancellation Reason, style_color=Style/Color, size=Size, style_size=Style/Size, style_color_size=Style/Color/Size SUPPORTED METRICS: ordered_amount=Ordered amount, open_amount=Open amount, ship_amount=Shipped amount, original_booked_amount=Original booked amount, cancelled_amount=Cancelled amount, order_count=Order count, booked_qty=Booked Total, original_booked_qty=Original booked quantity, open_qty=Open units, ship_qty=Units shipped, cancel_qty=Cancelled quantity, fill_rate=Fill Rate, cancellation_rate=Cancellation Rate SUPPORTED BASE PATTERNS: overdue=Overdue orders — Open/Hold where completion date has passed, no_allocation=No allocation — Open/Hold orders with zero stock and zero WIP allocation

order_analysis