{"id":81966,"plugin_id":"plugin_asdk_app_6adb8b000cbc8191a5b0646bbba32e50","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-05T01:19:48.342Z","digest":"532a33849cecda006f1ea8aa32d0001d5c0fac4a5275721b4844fa2d6a2dcf6f","against":null,"payload":{"description":"Reply to a purchase order a supplier received by EDI, or to a change to it: the 997 receipt, the 855 acknowledgment, the 856 ship notice with SSCC labels, and the 810 invoice. Use when the user has an 850 (or an 850 and an 860) and asks how to respond, acknowledge, ship or invoice it.","included_files":[],"name":"purchase-order-response","skill_md_contents":"---\nname: purchase-order-response\ndescription: Reply to a purchase order a supplier received by EDI, or to a change to it: the 997 receipt, the 855 acknowledgment, the 856 ship notice with SSCC labels, and the 810 invoice. Use when the user has an 850 (or an 850 and an 860) and asks how to respond, acknowledge, ship or invoice it.\n---\n\nUse this workflow when a supplier has received an X12 850. The user's own instructions take priority over these steps.\n\n## Steps\n\n1. If the user has not seen what the PO contains, call `explain_edi_document` with it.\n2. Ask which lines they can ship as ordered, and which are backordered (how many, and when), changed or rejected. If the buyer sent a PO change (860), pass it as `change_edi_text` so the replies follow the changed order.\n3. Ask for what the documents need, and never invent it:\n   - their next control number (`control_number_start`), so each draft gets its own;\n   - for the 856: ship date, carrier SCAC, ship-from name and address, their GS1 Company Prefix and next SSCC serial, cartons or one pallet, and lot or best-by dates when the products need them;\n   - for the 810: their invoice number.\n4. Call `draft_edi_responses` with `line_decisions` and those details. Include `\"997\"` in `responses` when they also need the receipt.\n5. Reply with what each draft says in one line each, then the placeholders the result lists (\"Before you send, replace...\"). The widget shows the EDI.\n6. If an 856 was drafted, offer the carton labels: call `create_sscc_labels_pdf` with the labels arguments the draft result gives, so the labels match the ASN carton for carton. Do not pass the 856 text from the reply: it may be shortened.\n\n## Rules\n\n- \"Acknowledge the PO\" usually means the 855; the 997 is a technical receipt. If unclear, give both.\n- If the result suggests a GS1 Company Prefix from the PO's UPCs, ask the user to confirm it before using it.\n- Mention deadlines the retailer notes give (for example a 24-hour 855).\n- Drafts go out through the user's own EDI connection or provider; nothing is sent from here.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}