Sahney Kirkwood - ERPNext AI Assistant

What is this?

This is an AI-powered assistant that lets you talk to Sahney Kirkwood's ERPNext system in plain English. No more clicking through menus, memorising filters, or building reports manually. Just ask a question and get an answer.

It's powered by Claude, an AI by Anthropic, connected securely to your ERPNext using the Model Context Protocol (MCP). Think of it as giving Claude read access to your ERP — so it can answer your questions with real, live data.

"What's the status of Sales Order SO-2024-1234?"
"Show me all pending purchase orders from last month"
"How much stock do we have for part number SK-4500?"
"List unpaid invoices over 30 days"

What you can do

Look up sales orders, quotations, and invoices instantly
Check inventory levels and stock movements across warehouses
Track purchase orders, deliveries, and GRNs
Search for items by part number or description
Review bills of materials and production plans
Get payment and outstanding balance summaries

Playbook: Create Work Orders from a Sales Order

When a Sales Order has items that are made at different manufacturing units (e.g. Gonde and Unit 1), you usually only want Work Orders for the items produced at one specific unit — including sub-assemblies from the BOM that aren't listed on the Sales Order itself. Paste the prompt below into Claude to run this flow.

You are creating Work Orders for Sahney Kirkwood from a Sales Order. Rule: only items whose item-master default warehouse belongs to the target manufacturing unit get a Work Order. Sub-assemblies follow the same rule. Target unit: Gonde Sales Order: <SO-NUMBER> BOM recursion depth: 2 Planned start date: <YYYY-MM-DD, defaults to today> Steps: 1. get_sales_order(<SO-NUMBER>) and list each line item. 2. For every SO line item, get_item(item_code) and read the "Item Defaults" block. Pick the default_warehouse for company "Sahney Kirkwood Private Limited". 3. If that warehouse name contains "Gonde" → IN SCOPE. Otherwise skip and note why. 4. For every in-scope parent item, get_default_bom(item_code) and for each child row call get_item and repeat the check. A sub-assembly whose default warehouse also maps to Gonde is in-scope even though it isn't on the Sales Order. 5. Print a plan table and ask me to confirm. 6. On confirmation, call create_work_order once per in-scope item, linking each WO back to the Sales Order. 7. Print a summary of created WOs and skipped items. Never create a Work Order for an item whose default warehouse does not contain "Gonde". If an item has no default warehouse set, flag it as a data-quality issue and skip — do not guess.

Swap "Gonde" for "Unit 1" (or any other unit name) to run the same flow for a different site. Depth 2 covers the parent plus one level of sub-assemblies; increase it if your BOM is deeper.

Getting Started

Open claude.ai and sign in to your Claude account
Look for the ERPNext connector in your list of available integrations — your administrator has already configured it for you
When prompted, sign in with the account you just created
Start asking questions!