Someone at the dock photographs the packing slip that came in the box, and the receiving log gains a row with the supplier, the delivery date, the reference, and every line item with its quantity. Shortages and over-shipments are flagged against the order before the box is even unpacked.
The app embedded on this page is the Quick Apps Feedback, a real Taskade Genesis build you can submit to from a phone right now. It is a short mobile submission surface rather than a receiving log, so use it as the starting point: click "Use this app" to clone it in about ten seconds, replace the questions with a supplier picker, a received-by name, and a File field, then add the reading and extraction steps.
Concretely: a Deliveries Project holds one row per shipment, with received lines kept as connected records so a delivery with twelve lines is still one delivery. The published form is built for a warehouse phone, with a File field, a supplier picker, and a received-by name. The Convert File to Text step reads the slip, and packing slips are almost always creased carbon copies photographed under bad warehouse lighting, so the extraction prompt tells the agent to leave unreadable values blank and flag them. An Ask Agent step returns supplier, delivery note number, purchase order reference, delivery date, carrier, and a list of lines with part number, description, and quantity received. The photo attaches to the row, so a later dispute over what actually arrived is settled by the document rather than by memory.
The receiving picture renders where it is needed:
- Table view for the receiving log with supplier, reference, and quantities
- Board view to move deliveries through Received, Checked, and Put Away
- Calendar view for arrivals by date across the week
- Plus List, Mind Map, Gantt, and Org Chart across the 7 project views
Automations turn a delivery into a signal. With Taskade automations, a short delivery pings purchasing in Slack with the part number and the gap, a delivery against an open order updates the order status, and a delivery with no matching order is held for review. Across 100+ bidirectional integrations, forms and webhooks pull slips in while Slack and Google Sheets push the log out. The AI agents inside the app carry 34 built-in tools with persistent memory, so an agent can answer "which supplier short-shipped us twice this quarter" without a spreadsheet exercise.
Make the submission part of unloading rather than an office task afterwards. A photograph taken at the tailgate, with the slip flat against the box, reads far better than one taken from a stack on a desk at five o'clock, and the receiving-by field means you know who to ask when a line is queried. Give the dock a single pinned link and nothing else to remember. It is also worth deciding what happens to a delivery with no matching order, because that is the case that reveals whether people are ordering outside the process, and holding it for review surfaces the pattern rather than hiding it.
Clone the app, invite the warehouse and purchasing, and the log, the photos, and the flagging rules are yours.
Read the upload behavior in File Uploads in Your App, the format list in Read Scanned Paperwork and Photos, and the build pattern in Build a Document Intake App. Shape the line structure with Databases in Projects, browse live builds in the Community Gallery, or explore automations. Pair this with Match Purchase Orders to the Invoices That Arrive to complete the three-way check, and Load Supplier Spec Sheets Into a Product Catalog to keep the catalog current.
Frequently Asked Questions
Will a creased carbon-copy slip read?
Often, and the design assumes it sometimes will not. Photograph the slip flat, filling the frame, in the best light available. Values that cannot be read come back blank and flagged, so the dock worker fixes one field instead of typing the whole slip.
Can it flag short deliveries automatically?
Yes, when there is an order to compare against. Reference the purchase order in the prompt and the comparison reports quantity received against quantity ordered per line, marking short, over, or complete.
Does it work offline in a warehouse with poor signal?
The submission needs a connection to reach the automation. In practice the pattern that works is photograph now, submit when back in signal, because the camera roll holds the photo and the form accepts a HEIC or JPG file taken earlier.
Can several people receive deliveries at once?
Yes. Each submission is its own row, and the received-by field records who logged it. Turn on App Users if you want every submission tied to a named signed-in person rather than a typed name.
What if the slip has twenty line items?
Ask for the lines as a list in the extraction step and write them into a connected Project so the delivery and its lines stay linked records. The log stays readable while the detail is still one click away.
Where does the photographed slip end up?
Attached to the delivery row and in your workspace Media tab. Disputes are settled with the actual document.
Is there a limit on the photo size?
Keep photos and scans under 20 MB, which is the ceiling for reading words off an image. A supplier who emails a typed PDF slip is read as text instead, bounded by your plan upload size.
Can it read a slip that is partly obscured by a stamp?
Often, since the stamp usually covers a signature area rather than the line items. Values it cannot read come back blank and flagged, so the dock corrects one field. The photograph stays attached, which settles any later argument about what the stamp said.
