Produce types

SETUP -> Produce types

This is a layer of produce grouping between SETUP -> Categories and SETUP -> Varieties. Examples include Apples, Pears. There is also an option here to indicate if grower payments should quote load-in instead of load-out references when available.

  • Description - name of produce. Also used as the Common name for MPI tab on LOGISTICS -> Sales.
  • Category - select from SETUP -> Categories.
  • MPI botanical name - used in the MPI tab on LOGISTICS -> Sales.
  • MPI class - used in the MPI tab on LOGISTICS -> Sales.
  • PNZI crop - name used by Pipfruit New Zealand in the Market Regulatory Info files, used in the MPI tab on LOGISTICS -> Sales.
  • Harvest units - type of unit that is used for harvesting and average weight of one of these full units.
  • Packed units - type of unit that is used for packing and average weight of one of these full units.
  • Sale prefix - if entered, this will be the prefix for LOGISTICS -> Manual load-outs and LOGISTICS -> Sales codes when using the magic wand to generate them.
  • Alias(es) - when EDI files have different values to your Code, enter other codes here.
  • Active? - untick if no longer used which will hide in lookup lists.

Overrides

  • SLI description - template used for the SLI description lines on LOGISTICS -> Sales. You can enter field values by putting the field name is square brackets. Valid components are [VarietyDesc] [ProduceDesc] [OriginCountry]. If left blank the default of "Fresh [ProduceDesc] [VarietyDesc]" will be used.
  • MPI description - template used for the MPI description lines on LOGISTICS -> Sales. You can enter field values by putting the field name is square brackets. Valid components are [Units] [PackUnit] [ProduceDesc] [OriginCountry]. If left blank the default of "Fresh fruit - [Units] [PackUNDesc] of fresh [OriginCountry] [ProduceDesc]" will be used.
  • Income description - template for the description you would like to show on the LOGISTICS -> Sales income lines if different from the default. You can enter field values by putting the field name in square brackets. Valid components are [BrandDesc][CategoryDesc][GradeCode][GrowMethodDesc][OriginCode][PackDesc][PackInvDesc][ProduceDesc][SizeDesc][VarietyDesc], spaces are automatically added between fields
  • Split sale income lines by container? - if ticked the income lines for these LOGISTICS -> Sales will be split by container, allowing prices to be set differently by container and easier if you want to invoice separately for each container (if you have multiple containers on a sale).
  • Use inward reference on grower payments? - use load-in reference as opposed to the load-out reference on grower invoices.

Market overrides

If a record exists for a market, sales to that market will use this MPI botanical name, otherwise the MPI botanical name entered above will be used.

  • Market - for sales going to this market.
  • MPI botanical name - the alternate name to use if different from above, leave blank to use the value above.
  • MPI declaration - the default declaration used in the MPI tab on LOGISTICS -> Sales for this produce type and market. Leave blank for pipfruit as this should come from the PNZI Market info.