Tuxedo Corn uses Harvest Point to connect product packed and labeled on the harvester with receiving, pallet tagging, sales, and shipping at the cooler. The result is one continuous operating record from field to shipment.
This case study describes Tuxedo Corn's operating workflow. It does not make quantified performance or savings claims.

The field-pack challenge
Unlike a shed-pack operation, Tuxedo Corn creates finished cases while harvesting. Product identity has to begin on the harvester and remain useful when the load reaches the cooler. That makes field labeling, dispatch, receiving, and pallet creation parts of the same process rather than separate records assembled later.
Labels begin the product record in the field
As corn is packed on the harvester, Harvest Point supports printing labels for the finished cases. The configured label can carry product and lot information needed to identify the packed product as it moves downstream.

The load continues into cooler inventory
Harvest Point carries the field-packed load into receiving at the cooler. The received product can be organized into pallet inventory and given pallet tags, keeping the cooler record connected to the product packed in the field.
Sales and shipping use the same operational flow
Once the product is received, Tuxedo Corn can continue using Harvest Point for sales and shipping. The workflow connects harvest and packing activity with the finished inventory used to fulfill outbound orders.
What Tuxedo Corn connects with Harvest Point
- Field packing on the harvester
- Case and product labeling
- Loads dispatched from the field
- Receiving at the cooler
- Pallet inventory and pallet tags
- Sales and shipping workflows
Could this operating pattern fit your crop?
Review the crop-neutral workflow for more detail.
See the Generic WorkflowSee how this workflow could fit your operation
Tell us how you currently pack, label, receive, and ship product.
Request a Demo