Match packing slip photos to open purchase orders on receipt
When a delivery arrives, staff photograph the packing slip, and a decision model picks which open purchase order it belongs to and whether it looks complete, so the buyer only reviews mismatches and short shipments.
Uses image input, which TypeSafe AI labels a preview feature for Jev. Test it on your own sample images before relying on it.
An example pattern written by Agents Lookup. We have not yet found a public build of this exact job.
The use case
Receiving goods means matching each delivery to the right purchase order and noticing short or wrong shipments. Staff photograph the packing slip at the door, and Jev is given the photo plus a short list of open purchase orders for that supplier as text. It picks which purchase order the slip matches, or none, and answers whether the slip appears to list everything on that order. Matches that clear a 0.85 confidence are logged against the order. Anything unmatched, partial, or unsure goes to the buyer. Jev does not accept or reject goods, approve supplier invoices, or contact the supplier. The buyer checks flagged deliveries, counts stock where needed, and decides what to raise with the supplier.
Example workflow
- Receiving staff photograph each packing slip and upload it through a Google Form on a phone.
- Make looks up open purchase orders for that supplier in a Google Sheet and sends them as text with the photo to Jev.
- Jev answers a Choice question, which open purchase order this packing slip matches, with each open order number plus none of these as the allowed answers, and a Noul question, the slip lists every line on the matched order.
- Confident matches are logged against the purchase order with the photo link and marked received pending count.
- Unmatched, partial, or low-confidence receipts are posted to the buyer in Slack.
- The buyer confirms counts, updates the order, and follows up with the supplier as needed.
Tools
- Jev (TypeSafe AI)
- Google Forms
- Google Sheets
- Make
- Slack
- Gmail
Risks and guardrails
- Image input is a preview feature in Jev 1.14 and TypeSafe says it is not production-ready yet — guardrail: test it on a few hundred of your own photos against a person's labels before relying on it, and keep a person checking every answer until the results hold up.
- A Choice question holds at most 255 options — guardrail: send only the open orders for that supplier, which keeps the list short and the choice easier.
- Handwritten corrections on a slip can be missed — guardrail: a Noul question asks whether the slip has handwritten changes, and those go to the buyer.
- Received status could be mistaken for a full count — guardrail: the log says received pending count until a person confirms quantities.
Related recipe
Supplier Purchase Order Follow-Up Agent: An agent scans your PO tracker for missing confirmations, ship dates, ASNs, and late orders, drafts supplier follow-ups for a buyer to approve, and proposes ETA updates only after a person checks the reply.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- Gmail (official page): developers.google.com/workspace/gmail (checked 2026-11-19)