ERPNext sales order fulfillment board for your ops team

Build me a sales order fulfillment control board that my operations team opens every morning to see which ERPNext orders are moving, which are stuck, and which are late.

The main view is a board of cards, one card per open sales order, grouped into three fulfillment states: submitted but not yet delivered, partially delivered, and delivered but not yet invoiced. Read the orders with List Documents on Sales Order, and read deliveries with List Documents on Delivery Note. Derive the three groups from the order's own progress fields: nothing delivered yet means per_delivered is 0, partially delivered means per_delivered is above 0 and below 100, and delivered but not billed means per_delivered has reached 100 while per_billed is still below 100. Request the fields you need explicitly on the list call, including name, customer, transaction_date, delivery_date, status, docstatus, per_delivered, per_billed, grand_total and currency, since ERPNext returns only the document name by default.

Any order whose promised delivery date (the delivery_date field) has already passed is flagged as late, sorted to the top of its group, and shows a plain days late number, so a card reads something like 6 days late. Keep that number simple and unmissable rather than a colored bar or a percentage. Each card should show the customer, the order id, the order value, the promised delivery date, and the delivered and billed progress, so someone can scan the board without opening anything.

Default the board to submitted orders only, meaning docstatus is 1, so drafts and cancelled orders stay out of the way. Give me a filter by customer and a filter by warehouse, and let me clear them to see everything. The warehouse filter should match against the warehouse set on the order's line items.

Clicking an order opens a detail panel. Load the full order with Get Document on Sales Order so the panel can list every line item with item code, description, quantity ordered, quantity delivered, warehouse and rate. In the same panel, show the linked delivery notes and sales invoices for that order: find them with List Documents on Delivery Note and Sales Invoice filtered by the originating sales order on their item rows, and pull details for any one of them with Get Document. Show each linked document's id, status and whether it is still a draft.

From the detail panel I want four actions. First, raise a draft delivery note for the order using Make Delivery Note from Sales Order. Second, raise a draft sales invoice using Make Sales Invoice from Sales Order. Important: both of these mapping methods return an unsaved document object, so the handler must post the returned object back with Insert a Document (frappe.client.insert) to actually persist it, then show me the new draft's id and link. Leave both new documents as drafts for a human to review and submit; never submit them automatically. Third, let me leave a note on the order with Add a Comment. Fourth, let me post a status update about the order to our fulfillment channel with Slack Bot Send a Message, prefilled with the order id, customer, fulfillment state and days late so I only have to tweak the wording.

Every order card also carries a Chase this order button that kicks off a background agent for that specific order. The agent should: read the order with Get Document to get its line items; check on hand quantity for every line item with Get Stock Balance, using the item code and the warehouse on that line; look at whether any linked delivery note for the order is still sitting in draft rather than submitted; draft a customer update email in Gmail with Create a Draft, addressed to the order's contact, explaining the current status and the expected next step; and finally write its diagnosis back onto the order with Add a Comment, in a couple of plain sentences that name the actual blocker, for example that two lines are short on stock in the main warehouse, or that a delivery note has been sitting in draft since last Tuesday. Because the diagnosis lands as a comment on the order, the board and the detail panel should surface the most recent chase comment next to the order so the reason it is stuck sits right beside it, along with when the chase last ran.

Two hard rules. Never auto send anything to a customer: every customer facing email must land as a Gmail draft that a human opens and sends, and the app should say so on the button. And remember that submitted ERPNext documents cannot be edited, so the app must never try to modify a confirmed sales order in place; it only creates new draft documents, adds comments to the timeline, and posts to Slack.