These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Logistics/TMS for Agriculture and Produce
- Features
- Produce pickup
Produce pickup
Keep farm, harvest and temperature evidence with the pickup review.
OverviewReview Decisions Default List×
Logistics/TMS for Agriculture and Produce · Produce pickup
New
Review Decisions Default List
Review decisions
| Parent | Reviewer | Decision | Reason | Decided at | Source revision | |
|---|---|---|---|---|---|---|
| LDS-43930 | Approve | Approve rd-452 | 05 Oct | 330 | ||
| LDS-39115 | Return | Reject rd-381 | 08 Oct | 390 | ||
| LDS-20086 | Approve | Return rd-624 | 06 Oct | 670 | ||
| LDS-65921 | Return | Approve rd-130 | 04 Oct | 390 | ||
| LDS-18607 | Approve | Reject rd-995 | 18 Oct | 30 |
6 of 6 records
Approve rd-452Review decisions · RD-50624
ApproveParentLDS-43930
Decided at05 Oct
Source revision330
What you can do
Record the condition at collection
Pickup Coordinator links a produce pickup check to the load and operating organization. The check holds the farm, pickup time, temperature and harvest date. These observations travel with the movement and give Review Manager a concrete basis for deciding whether the collected produce can proceed toward delivery release.
The coordinator prepares the check in draft and submits a specific revision. Supporting files can be attached to the same load with an evidence type, upload time, visibility and uploader. A photo or document should describe the actual observation, not stand in for an unrecorded temperature or farm identity. The reviewer can inspect the check alongside the load’s promised delivery and related evidence.
Review Manager records an independent decision against the relevant load revision. The decision contains an approval, rejection or return, its reason, reviewer and time. A submitted check becomes approved only after that decision; completion follows the operation receipt for the accepted pickup. A rejected check remains a visible outcome for correction and renewed review.
How the work is organized
- Collection facts. Farm, pickup time, harvest date and temperature identify the observed produce pickup.
- Revision. Submission fixes the version being reviewed and keeps later changes distinguishable.
- Decision evidence. Reviewer, reason and linked operation receipt explain the release.
What to agree during setup
Agree who measures temperature, the unit and point of measurement, and which evidence type should accompany an exception. Define who may return a check for correction and how a new revision is submitted. Keep the reviewer separate from the person entering the pickup observations so an approval is an actual decision.
Check the handoff on an actual case
At a farm pickup, record the farm, collection time, harvest date and measured temperature on a check tied to the load. Attach the supporting evidence and submit the check. Ask Review Manager to compare it with the current load revision and record a reasoned decision. If the temperature needs investigation, return or reject the check; do not mark it complete. For an approved revision, confirm that the operation receipt and completed check refer to the same movement. Dispatcher should be able to identify the approved pickup before releasing the load for delivery.
What your team sees
- Loads Default List — The linked load and original delivery promise while the pickup check is reviewed.
- Review Decisions Default List — The reviewer, decision, reason and source revision for the load.
Follow the work through
See the operating process and implementation for the first rehearsal.
What it keeps track of
Data model- Produce pickup checks
- Produce pickup checks supporting accept a produce pickup: quality and temperature evidence retained before delivery release.
- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Review decisions
- Independent approval, rejection or return decisions on a source revision
- Record attachments
- Evidence files attached to loads with visibility and evidence type
- Operation receipts
- Idempotent operation receipts recording executed or failed actions with stable keys
Who uses it
Permissions- Pickup Coordinator
- Records farm observations and attaches evidence to the load.
- Review Manager
- Examines the submitted check against the current load revision and decides whether the pickup can proceed.
- Dispatcher
- Reads the outcome before releasing the movement.
Set up Logistics/TMS for Agriculture and Produce your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.