Meridia Verify processes geospatial supply chain data. For that reason, usage and quota consumption are measured on a hectare basis, which is the most appropriate and widely used unit for geospatial analysis.

Hectares also serve as a practical proxy for associated sourcing volumes and, by extension, compliance and verification effort. This allows quota allocation and budgeting to scale in line with the real analytical workload performed by the platform.

Quota consumption is calculated based on the spatial footprint of the data processed:

To avoid penalising customers for operational workflows that require resubmission or correction of data, Meridia Verify tracks consumption based on unique spatial data only.

Farm plot ID is no longer a factor in duplicate detection or quota consumption.

Any modification to a plot’s geometry — including a single coordinate or decimal place — causes the plot to be treated as a new, unique feature and counted towards consumption.

Example 1.1: A single farm polygon is split into two plots. Although one plot retains the original ID ‘P-12334’, its geometry has changed, and a second plot with a new geometry and new ID ‘P-12335’ has been created. Both plots are recognised as new unique features and counted separately.

Example 1.2: A polygon’s geometry is corrected to resolve an overlap and reflect accurate farm boundaries. Even though the farm plot ID is unchanged, the updated geometry is treated as new and reprocessed accordingly.

Example 1.3: Any change to a geometry, including an empty Z coordinate being added or corrected, is treated as new geometry and incurs consumption.

From 1 June 2026 00:00:00 UTC, if a plot is resubmitted with a different farm plot ID but the same geometry, it is recognised as a duplicate and does not count towards quota consumption.

This covers common scenarios including:

Example 2.1: A plot previously submitted as ‘P-12334’ is resubmitted as ‘ABC-76896’. The geometry is identical. The system recognises this as the same physical plot and does not bill again.

Example 2.2: A geopoint is resubmitted with the same coordinates but a differently formatted farm plot ID. The system treats this as a duplicate and does not consume additional quota.

Running the same plot geometry against different verification profiles counts as a separate billable unit per profile.

Example 3.1: A plot is run against EUDR and DCF. This counts as two consumption units.

Example 3.2: A plot is run against EUDR, DCF, and Data Quality. This counts as three consumption units.

Example 3.3: A plot is run against the same profile twice within the same billing cycle. This counts as one consumption unit — the second run is treated as a duplicate.

From 1 June 2026 00:00:00 UTC, Meridia Verify determines quota consumption based on unique spatial data, using geometry and verification profile as the key dimensions for uniqueness.

This ensures customers are charged only for genuinely new analytical work, not for duplicate submissions, ID changes, or non-spatial corrections.

A plot is considered unique based on the following rules:

If the same physical plot is resubmitted with identical geometry but a different farm plot ID, it is treated as a duplicate and does not consume additional quota.

Farm plot ID is no longer used for duplicate detection.

If the same geometry is submitted again within the same billing cycle and processed under the same verification profile, it is treated as a duplicate.

Only the first submission consumes quota.

If the same geometry is processed under different verification profiles, each profile counts as a separate billable unit.

For example, EUDR + DCF = 2 consumption units, while EUDR + DCF + Data Quality = 3 consumption units.

Any change to geometry makes the plot a new unique feature, even if the farm plot ID stays the same.

This includes boundary edits, coordinate adjustments, polygon splits, overlap corrections, or technical geometry changes such as adding or modifying an empty Z coordinate.

Changes to farmer ID, farmer name, aggregator ID, mapping date, or similar descriptive fields do not consume additional quota.

As long as the geometry and verification profile remain the same, the plot is treated as a duplicate.

Quota consumption continues to be measured in hectares, based on the spatial footprint processed by Meridia Verify.

Polygons use the calculated geometric area. Geopoints use the reported plot size where available, or default hectare values if no size is provided.