Order entry fields and confirmation draft
Customer PO says one rate. The rate card says another. The order entry screen wants a number.
Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files
Prepare the PO working
Use PO line ref, item, quantity, requested rate and approved rate. Include supplied delivery status and terms. Include the approved SKU, unit and unique PO line ref for each line.
Confirm missing details
Check PO against rate card and stock; do not promise a delivery date until confirmed.
Privacy Remove phone numbers, email IDs and payment details where not needed. Use only approved business names and facts.
Whenever I send PO lines for [Customer], PO [Customer PO], prepare order working. Approved terms: [Approved terms]. Sign off: [Sign off]. A. Extract one row per unique PO line ref with item code, item description, unit, ordered qty, requested rate, approved rate and requested value qty × requested rate. Hold duplicate line refs, missing/invalid or nonpositive qty, missing item code/unit/rate, negative rate or rate mismatch; no invented fields. Keep requested value for held rows separate. B. List passing and held rows and their values; the complete known order value counts passing rows only, with held requested values shown separately. Passing is not final order approval. For passing rows give a copyable handoff table with PO ref, PO line ref, SKU, unit, ordered qty, approved rate, status = review pending, and confirmed terms. Actual sales order ID is [confirm] until entered and approved. C. Draft short (up to 6 lines) acknowledgement, listing PO ref and items to clarify, no confirmed delivery or price on held lines. Use approved terms only. No actual order entry. Use only supplied facts. Never invent customer names, testimonials, urgency, prices, discounts, delivery dates or credit terms. A person reviews before sending or deciding. Line limits count body lines only, not subject, greeting or sign-off. Keep every required fact; if they do not fit, say so instead of dropping one.
Set it up once. Save the order fields and validation rules. Pick your tool at the top to see how.
What is that?
A Project is a folder in ChatGPT that keeps your instructions and files for every chat inside it. It's on the free plan too. Checked 14 Nov 2026.
What is that?
A Project in Claude is a workspace with its own instructions and files that every chat inside it uses. Checked 14 Nov 2026.
What is that?
A Gem is a custom Gemini that loads your instructions before every chat. Free on every plan; you create it on a computer. Checked 14 Nov 2026.
What is that?
Signed in with a work account, Microsoft's Copilot Chat applies enterprise data protection: your prompts aren't used to train its models. Checked 14 Nov 2026.
After that, each time: send each new PO and approved terms.
First time? Try it in a normal chat: paste and send.
Which model? Use your tool's strongest model with thinking turned on.
In your AI tool: attach the files with the + button, paste, send.
- L2Rate mismatch. ₹550 requested vs ₹500 approved.
- L4Qty missing. No value; ask customer.
- DeliveryTo confirm. Acknowledgement is not a delivery commitment.
Then send this: Check each field against PO, recompute totals for known rows and verify mismatches/unknowns not confirmed. Validate unique PO line ref, SKU/unit and approval status; do not infer a sales order ID.
It guesses qty
Reply: "Leave missing qty unknown."
It confirms mismatch
Reply: "Hold and ask for clarification."
It gives delivery date
Reply: "Delivery to confirm only."
Sir ne bola urgent. Ab bolo: ho gaya.
Did it work?
If your whole team does this, we'll set it up for all of them in one session.