Known limitations
What LabelLens can and cannot do
LabelLens is built to be cautious. This page explains the boundaries of OCR reading, compatibility checks, regulatory safety data, pilot operations, and privacy — without marketing spin.
No guessingAdvisory onlyPilot-ready honesty
LabelLens product promise
Advisory only. Always follow the original pesticide label and seek expert guidance when information is unclear.
Transparency
Trust comes from clear limits
Partners, farmers, and field teams should know where the product stops and the pesticide label begins.
OCR limitations
- LabelLens reads visible text from photos. It does not see what is outside the image frame.
- Poor lighting, blur, glare, folds, dirt, or low resolution can cause unreadable or partial reads.
- Small print, mixed languages, and damaged labels may not be captured fully.
- When text cannot be read confidently, fields remain unknown rather than guessed.
- A clearer front-of-label photo — and a back-of-label photo when needed — improves results.
Compatibility limitations
- The tank-mix compatibility checker uses deterministic rules only. It does not use AI to decide mixing safety.
- Current rules are starter/demo data, not a complete regulatory or manufacturer database.
- If no rule exists for a product pair, the result is unknown — not safe.
- Compatibility results are advisory. The official pesticide label always overrides the checker.
- The checker does not provide mixing instructions or application rates.
Regulatory limitations
- Safety checks use maintained regulatory snapshots, not live government feeds.
- The bundled India dataset reflects a published government list snapshot and may not include the newest notifications.
- Crop-specific and state-specific rules only apply when those fields are known in the scan context.
- Ingredient matching is deterministic and may miss complex synonyms until verified aliases are added.
- LabelLens safety guidance is advisory and does not certify legal compliance.
Pilot limitations
- LabelLens is designed for controlled pilots with partner onboarding, not unsupervised mass deployment.
- Company visibility depends on farmer consent and product-library matching — not all scans are shared.
- Compatibility check usage is not centrally logged in the current pilot phase.
- Admin pilot dashboards show real saved data only; there is no formal pilot registry yet.
- Operational support should follow the documented escalation workflow during pilots.
Privacy limitations
- Farmer identity details are not shared with companies through the product-sharing flow.
- Consent choices for product sharing are stored in the farmer browser unless separately logged by your deployment.
- Revoking consent stops future sharing; it does not remove company records already created from earlier consented scans.
- Companies see operational scan and voucher fields only after explicit farmer consent and a product match.
- LabelLens does not replace your organisation's privacy policy, data-processing agreement, or consent paperwork.
For pilot partners
Use this page in onboarding conversations
Share it with company admins, extension officers, and farmer-group coordinators before a pilot starts.