purchase-orders-erp

byMeghna Rajawat

What we want built An AI agent that: 1. Monitors an order inbox (Microsoft 365 / Outlook / Front) and identifies emails that contain purchase orders. 2. Reads the PDF attachments and extracts the order data: PO number, customer, bill-to and ship-to, line items, quantities, units of measure, prices, requested dates, and shipping instructions (including third-party carrier account numbers when listed). 3. Handles real-world documents. Most are clean system-generated PDFs, but some are faxes, rotated or upside-down scans, multi-page documents with cover sheets and terms pages, and handwritten order forms. It must handle customer formats it has never seen before, so we are not looking for a per-customer template approach. 4. Matches order data against our ERP reference data (customers, ship-to addresses, item numbers including customer and legacy part numbers, units of measure, and prices), which we will provide. 5. Flags anything it isn’t confident about, such as unclear fields, price differences, unknown items or addresses, and missing PO numbers, so our reps know exactly what to check. 6. Outputs one CSV file per order in a defined format, to a location where our existing ERP import process picks it up.

No preview

Comments (0)

No comments yet. Be the first!

Architecture

No Services Diagrams Yet

Architecture diagrams will be automatically generated when the Project Manager creates tasks for your project.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.