Knowledge Base

CropLabel System Documentation

Everything you need to configure your harvest terminals, map geospatial plots, query regulatory guidelines, and synchronize tag data with the ledger.

System Configuration

Before syncing scale data, establish a local config on your gateway device. This config binds physical scales, chooses appropriate communication ports, sets local buffers for offline operations, and targets the primary ledger node.

By caching weighments in a local database, CropLabel terminals can operate in mountainous or remote farm plots with poor connectivity, queuing transactions to sync automatically when network access is recovered.

config.json
{
  "node_id": "DE-MUC-NODE-012",
  "scale_port": "/dev/ttyUSB0",
  "baud_rate": 9600,
  "mqtt_broker": "mqtts://ledger.croplabel.com:8883",
  "tag_type": "RFID-UHF",
  "local_buffer_path": "/var/lib/croplabel/cache/"
}

Integration Guides

Get your telemetry system running in three simple phases

Step 1

Terminal Scale Setup

Connect your physical scale terminal to our gateway software via USB/Serial, BLE, or MQTT protocol.

  • Download the CropLabel Scale daemon (Linux/Windows).
  • Configure serial settings e.g., 9600 baud, 8N1 parameters.
  • Add scale credentials to your local system's secure config.
Step 2

Tag Provisioning

Register new RFID tags or barcode blocks to link them with live harvest weights.

  • Load blank RFID or thermal tag labels into your printer node.
  • Query local API to fetch authorized crop batch signatures.
  • Print and anchor labels to target harvest crates or bins.
Step 3

GIS Compliance Sync

Assign geographical coordinates to your harvest batch for automated deforestation validation.

  • Upload coordinates (GeoJSON polygon) of the harvest field.
  • System executes a Sentinel-2 query to check historical tree cover.
  • Cryptographic compliance receipt is generated if plot is cleared.

Need API Endpoints Specs?

If you are a developer looking to integrate scales directly or query batch certificate records programmatically, consult our comprehensive API references.