On the home page of your environment, click Modules on the left-hand side. The different modules will then appear as green tiles. Click the Harvest tile.
At the bottom left, you can now find Configuration > Settings.
The different settings for the "Harvest" section are described below.
Unsorted overview: overview expires after (s): The harvest overview expires after the configured number of minutes and is then recalculated.
Harvest registration: Unsorted and/or Sorted: Here you can determine whether you want to create harvest registrations for sorted fruit only, unsorted fruit only, or both.
Harvest registration: Pick can be entered during registration?: Here you can specify whether the picking round must be registered when creating a new harvest registration. If this setting is set to No, the picking round is not relevant and will not be requested when creating a harvest registration.
Harvest estimate: "Expected picking date" required?: This setting makes the “Expected picking date” field mandatory when registering a harvest estimate.
Harvest estimate: "Storage period" required?: This setting makes the “Storage period” field mandatory when registering a harvest estimate.
Harvest registration: Duplicate load from 2nd print: If this setting is set to Yes, the existing harvest registration is duplicated when the harvest labels are printed again. New codes with the same details are then created, and you can print the harvest labels of the duplicate. If this setting is set to No, you can reprint the harvest labels of the existing harvest registration without duplicating it.
Harvest registration: Number of picks: Enter the number of possible picking rounds for the crop here. When creating a new harvest registration, you can then select a picking round up to the number entered here.
Harvest registration: Update harvest date when activated via picking performance: If this setting is set to Yes, the scan date when activating via the Harvest App is used as the actual picking date and, where applicable, overrides the previously registered harvest date. If this setting is set to No, the registered harvest date is always retained when the code is scanned.