Pallet Files Setup

These settings control how the system processes incoming pallet data files and what validation it applies during import and confirmation.


Check Pallet Mandatory Fields

  • OFF: No mandatory field checks are applied during pallet import. Pallet records can be imported even if key fields are missing. This can result in pallet lines entering the system without crucial information.

  • ON: The system enforces that every pallet record includes both the system-required fields (such as Commodity Group, Inbound Channel, and Outbound Channel) and any additional fields your business has configured as mandatory. Records with missing values are rejected. Best practice: switch this ON.


Suppress Validations

Controls how thoroughly the system validates a pallet file during container confirmation.

  • OFF (default): The system applies a rigorous, multi-stage validation before any values are updated:

    1. All fields that reference lookup lists (commodities, locations, channels, freight points, etc.) are validated to confirm that the values in the file actually exist in the system’s master data.

    2. Cross-field consistency checks are run (duplicate detection, quantity and weight checks, pallet base and height consistency, transaction sequence checks).

    3. The system confirms that each Pallet ID in the file exists in the system.

    4. Field values in the file are compared against the values on the existing pallet lines — differences are flagged in the error log.

    5. The pallets in the file are compared against those on the freight container.

  • ON: Simplified matching is used — the system matches only on Pallet ID, bypassing all field-level validation and comparison. Additionally, any field that references a lookup list is not updated from the file, and the pallet quantity is also not updated. This prevents writing invalid values to the system but means those fields retain their existing values rather than being refreshed from the file. Use this when the pallet data already in the system (commodity, variety, size, outer pack, produce code, quantity, etc.) is trusted to be correct and does not need to be updated from the file. The primary purpose in this mode is to compare the pallet IDs in the file against the pallet IDs on the freight container — identifying pallets that were physically loaded but not allocated, and pallets that were allocated but did not actually load.


Suppress Pallet Qty Checking

  • OFF (default): The system checks that pallet quantities match the Quantity per Pallet defined in your Pallet Packing Setup. If a mismatch is found, a warning is added to the error log (“The total quantity on the pallet does not match the default for the pallet capacity”). This is an ignorable error — the user can acknowledge it and continue processing the file.

  • ON: The quantity check is skipped entirely. No warning is generated. Use when pallet quantities legitimately vary from standard packing setup definitions.


Disable Pallet Lot No. Edit on Pallet File

  • OFF (default): The Pallet Lot No. field can be edited on the pallet file import buffer before confirming.

  • ON: The Pallet Lot No. field is locked during pallet file import and cannot be changed. Prevents accidental overwriting of lot numbers. Recommended: switch this ON.


Allow Manual Confirmation Dates

  • OFF (default): The confirmation date on each pallet is set automatically to the date the file is confirmed in the system.

  • ON: Users can enter a confirmation date manually on the pallet file before confirming. The pallets will then carry that date as their confirmation date rather than today’s date.

    Example use case:

    A business buys pallets from another exporting company, with an agreement date of 5 April. Payment terms are calculated from that date. The pallet file only arrives on 9 April. If the user confirms on 9 April without this setting, the confirmation date on the pallets will be 9 April — which does not reflect the agreement date and would skew payment due date calculations. With this setting enabled, the user can set the confirmation date to 5 April before confirming, so the pallets carry the correct date for payment scheduling.


Allow Pallet Transfer Without Pre-Allocation

  • OFF (default): Pallets can only be transferred via a Transfer Produce Order that has been created in advance, with specific pallets pre-allocated to it.

  • ON: Pallets can be transferred without a pre-existing Transfer Produce Order. The system reads the destination from the pallet file and performs the transfer allocation automatically.

    Example use case:

    Pallets are packed at an inland packhouse and confirmed in the system via pallet intake files. Transport to a commercial cold store near the port is arranged by the packhouse — the business does not control which specific pallets are loaded onto the truck and therefore cannot pre-allocate them. The packhouse submits a Pallet Out file for the loaded pallets. With this setting ON, the system can process that file as a transfer and allocate the pallets to the correct destination automatically, without requiring a pre-created Transfer Produce Order.


Std. Pack Qty. Rounding Precision

Specifies the rounding increment applied to pack quantities. For example, a precision of 0.5 means quantities round to the nearest 0.5 unit. Works in combination with the Rounding Type setting.


Std. Pack Qty. Rounding Type

Controls the direction quantities are rounded:

  • Nearest — rounds to the closest value (e.g., 4.3 → 4.5 if precision is 0.5)
  • Up — always rounds up to the next increment
  • Down — always rounds down to the previous increment

Std. Pack Qty. Decimal Places

Sets how many decimal places are displayed when showing pack quantities throughout the system.


Apply Pallet Height from Pallet Packing Setup

  • OFF (default): The pallet height code from the file is applied to the pallet line, provided that the value exists in the system’s master data. If the height code in the file is not recognised as valid master data, it will not be applied.

  • ON: The system overrides the pallet height code from the file with the height defined in your Pallet Packing Setup for that commodity and pack combination. This ensures that incorrect or inconsistent height codes sent by external packhouses or suppliers are automatically corrected to match your internal standards, without requiring manual intervention.


PO Export File Document No.

Controls which reference number appears as the Document No. in pallet export files sent to freight/logistics partners:

  • Produce Order No. — your internal produce order number
  • Freight Container Code — the container reference in ProduceLinc
  • Container External Document No. — the external reference assigned by the freight forwarder or shipping agent

PO Export File Order No.

Controls which reference number appears as the Order No. in pallet export files (same three options as above). Configure based on how your freight partners expect to receive references.