A brief instruction on the fields and fieldlogic is also included in the excel template, which can be downloaded below:
Multiple inspection template 24-11-25 blanco.xlsx
This document explains how our platform processes your Excel upload and decides whether rows should be grouped into one inspection or split into multiple inspections.
Understanding this logic helps you avoid unexpected inspection splitting.
1. General Processing Logic
When you upload an Excel template, the system compares certain fields across the rows.
If all grouping fields match → one inspection is created (containing one or more units).
If any grouping field differs → a new inspection is created.
Each inspection may contain several units. Unit-level fields, such as PalletID, do not influence whether a new inspection is created.
2. Fields That Trigger New Inspections (Grouping Fields)
The system creates multiple inspections when rows differ in any of the following fields:
Additional
Airwaybill
Brand
Consignee
Consignee Ref
Container Number
ETA
Flight Number
High Priority
Inspection Point
Inspection Type
Inspector
Instructions
Location
Pallet Amount
Shipment Type
Shipper
Shipper Ref
Trailer
Vessel
Waiting for Arrival
PalletID is not a grouping field and does not create new inspections.
3. How PalletID and PalletAmount Are Interpreted
PalletID (unit-level field)
Every unit may contain its own PalletID.
An inspection can contain multiple different PalletID values.
Differences in PalletID never cause new inspections to be created.
PalletID only affects how many pallets are recorded within an inspection — not how inspections are grouped.
PalletAmount (inspection-level field)
This field behaves differently depending on whether you leave it blank or fill it in the Excel template.
1. When PalletAmount is blank in the Excel
The system automatically calculates PalletAmount based on:
The number of unique PalletIDs across all units included in the inspection.
In this case:
PalletAmount is derived
PalletAmount does not affect grouping
Only the grouping fields listed above determine whether a new inspection is created
2. When PalletAmount is filled in in the Excel
This activates different behavior:
The platform stops calculating PalletAmount automatically
The value from the Excel file becomes part of the grouping logic
Therefore, if PalletAmount values differ between rows, the system will create multiple inspections
This can lead to unexpected splits, even when all PalletID values logically belong in the same inspection.
In summary:
Leave PalletAmount empty if you want the system to calculate pallet totals automatically.
Fill PalletAmount only if you want it to influence inspection grouping.
4. Examples
Case A: PalletAmount left blank (recommended)
RowPalletIDPalletAmount (Excel)LocationResult11001blankAMSSame inspection21002blankAMSSame inspection
→ Portal shows Pallet Amount = 2 (auto-calculated from PalletIDs)
Case B: PalletAmount is filled in (becomes a grouping field)
RowPalletIDPalletAmountLocationResult110012AMSInspection A210023AMSInspection B (different PalletAmount)
Even though PalletID would allow these rows to be combined, the system creates two inspections because PalletAmount differs.
5. Summary
The system groups rows based on a specific set of grouping fields (listed above).
PalletID is not a grouping field and never creates new inspections.
If PalletAmount is blank, it is automatically calculated.
If PalletAmount is filled in, it becomes part of the grouping logic and can split inspections.