GITNUXSOFTWARE ADVICE
Agriculture FarmingTop 10 Best Crop Production Software of 2026
Top 10 crop production software for farms ranked with tradeoffs across Agrivi, FarmERP, Climate FieldView, Croptracker, and Taranis.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Croptracker is the best fit for farm teams that need traceable crop records tied to harvest and packing workflows, whereas FarmERP works better when you need structured crop execution and record continuity across larger farm operations.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Croptracker
Scouting and work records attach to both field entities and spatial context for after-action review.
Built for fits when farm teams need traceable field workflows with map-linked scouting history..
FarmERP
Editor pickField-linked work orders connect crop plans to what teams do, then to harvest and traceability records.
Built for fits when farms need structured crop execution and record continuity across field teams..
Taranis
Editor pickImage-based crop scouting that produces field findings and routes them into follow-up workflows.
Built for fits when teams need image-driven scouting with follow-through into field work..
Comparison Table
Croptracker
vertical specialistProduce farm management software for crop records, harvests, traceability, and packing operations.
Scouting and work records attach to both field entities and spatial context for after-action review.
Croptracker’s core strength is tying field mapping and scouting notes to structured farm records, so users can track activity from planning through execution. Crop plans can be broken into dated planting and subsequent field work, and scouting entries stay connected to specific fields. Map-linked workflows help teams validate observations spatially while maintaining a searchable audit trail of field events.
A common tradeoff is that Croptracker’s value rises with consistent data capture habits, because the system’s reporting and traceability depend on users recording observations and work in the right field and crop context. Croptracker works best when farm staff are already operating with defined field boundaries and repeatable scouting routines, such as weekly crop checks during critical growth stages.
- +Field activity history stays linked to crop and field context
- +Map-linked scouting reduces mismatch between observations and locations
- +Rotation planning structure supports multi-season record continuity
- +Exportable farm records support reporting for agronomy reviews
- –Strong ROI depends on disciplined data entry by field teams
- –Advanced automation requires careful workflow design and standard templates
- –Some precision-ag workflow steps depend on external map generation
- –Reporting flexibility can lag behind custom farm-specific processes
Agronomy managers
Review scouting history by field
Faster agronomic follow-ups
Farm operations supervisors
Track work orders across seasons
Cleaner operational traceability
Show 2 more scenarios
Precision ag analysts
Audit spatial observation patterns
More defensible field decisions
Analysts review map-linked scouting entries to correlate patterns with management actions.
Crop planners
Manage planting and rotation timelines
Less plan drift
Planners structure planting schedules and rotation steps to keep future work tied to past context.
Best for: Fits when farm teams need traceable field workflows with map-linked scouting history.
FarmERP
enterpriseAgricultural ERP software for crop planning, farm operations, procurement, and traceability.
Field-linked work orders connect crop plans to what teams do, then to harvest and traceability records.
FarmERP is a strong fit for operations that run many field activities and need structured planting and execution records. Crop planning is organized so planting schedules and work orders connect to specific fields, which helps teams track what should happen and what actually happened. Crop scouting and harvest records are recorded in the same system, which reduces manual re-entry when reconciling plans with outcomes.
A notable tradeoff is that FarmERP’s automation depth depends on how farms set up their workflows up front, because standard processes are driven by configuration rather than ad hoc rules. FarmERP works best when teams want consistent work order execution for the season and when field teams can follow a defined input flow for scouting and harvest updates.
- +Work orders stay linked to field activities for execution tracking
- +Crop planning supports practical planting schedules and variety selection
- +Scouting entries and harvest records support traceability within one system
- +Role-based access separates field entry from management approvals
- –Advanced automation requires careful workflow setup and ongoing governance
- –Deep precision agriculture integrations may require external tooling
- –Reporting flexibility can lag behind spreadsheet-driven agronomy teams
- –Field mapping workflows feel lighter than farm GIS-first products
Crop operations managers
Coordinate planting and execution
Fewer status gaps
Agronomy teams
Run scouting and harvest follow-through
Clearer crop history
Show 1 more scenario
Farm administrators
Control access across roles
Tighter governance
Use role-based access to restrict approvals and maintain consistent data entry across users.
Best for: Fits when farms need structured crop execution and record continuity across field teams.
Taranis
precision agricultureTaranis provides crop scouting and monitoring workflows using imagery and agronomic analytics.
Image-based crop scouting that produces field findings and routes them into follow-up workflows.
Taranis centers field scouting on image-based detection workflows that route findings into work planning rather than stopping at visualization. Field mapping is used to keep observations tied to where the issue was seen, which improves consistency when multiple scouts or agronomists contribute. The platform also maintains observation and action histories that can be reviewed during later planning cycles.
A key tradeoff is that the value depends on image capture quality and disciplined follow-up, because detection outcomes drive what actions are created. Taranis fits farms where frequent scouting is already scheduled and where agronomic teams want tighter linkage from what was observed to which work orders get executed.
- +Computer-vision scouting converts imagery into actionable field findings
- +Field mapping ties observations to location for consistent follow-up
- +Observation and action histories support season-to-season review
- +Configurable workflows help route findings into operational tasks
- –Image capture quality strongly affects detection usefulness
- –Field onboarding and workflow setup require time before full benefit
- –Integrations depend on the farm data exchange path and formats
- –Work planning coverage is narrower than full ERP-style farm management
Crop scouting teams
Convert imagery into scouting findings
Faster issue identification
Agronomy advisors
Standardize scouting-to-action routines
More consistent responses
Show 1 more scenario
Farm operations managers
Track field actions from sightings
Reduced missed follow-ups
Operational tasks get tied to observed issues so status is auditable.
Best for: Fits when teams need image-driven scouting with follow-through into field work.
AgriXP
SMBFarm record-keeping and crop production management application for field activities and compliance.
Field-centric work execution that links planting plans, scouting notes, and harvest records to the same field timeline.
AgriXP is crop production software that centers on planning-to-field execution for farm work, not just reporting. Core modules cover field activities like planting schedules, work orders, and crop scouting logs, with agronomic notes attached to fields and dates.
The system supports farm recordkeeping such as harvest and traceability-style tracking tied to specific fields and operations. AgriXP is also positioned for external connectivity through import and integration options that matter when combining agronomy data from multiple sources.
- +Planning and work orders stay tied to fields and scheduled dates.
- +Crop scouting and agronomic notes link observations to specific field activity.
- +Harvest records and traceable field history support operational continuity.
- +Import and integration options reduce manual re-keying across systems.
- –Advanced prescription mapping and variable-rate workflows require extra setup or add-ons.
- –Multi-site governance features like granular RBAC and audit trails need validation in rollout.
Best for: Fits when mid-size crop teams need field-linked work orders and scouting records for day-to-day execution.
Agworld
vertical specialistFarm management software for crop planning, work orders, chemical records, and collaboration.
Scouting captured as field-linked records that can drive follow-on work orders with consistent crop context.
Agworld turns farm field activity data into structured crop production records, with planning, scouting, and work tracking tied to fields and seasons. Crop plans can be translated into actionable tasks through configurable work orders and status tracking across agronomic teams.
Scouting entries support observation workflows used for crop health monitoring and follow-up actions, with consistent linkage to the underlying field and crop context. Agworld also provides an integration-oriented layer for exchanging operational data with external systems, which matters for interoperability with existing agronomy and farm data tooling.
- +Field-linked scouting workflow keeps observations tied to the right crop context
- +Configurable work orders support turn plans into trackable field activities
- +Operational records stay structured around fields and seasonal crop instances
- +Integration support supports data exchange with external farm data systems
- –Crop rotation planning depth can be limited for multi-year scenarios
- –API and automation depend on external system mapping and agronomic data cleanup
Best for: Fits when agronomy teams need field-level planning and scouting with task follow-up.
Granular
enterpriseFarm business management and agronomy software covering production planning, labor tracking, and profitability analysis.
Granular’s linked record model ties scouting inputs and field activity history directly to planned agronomic actions.
Granular targets farm teams that need field-by-field agronomy planning, execution tracking, and documentation for compliance and continuity between seasons. Its core workflow connects field activities, scouting notes, and work records to agronomic recommendations and application planning.
Granular also emphasizes data exchange through integrations and an API for syncing external systems like weather, satellite sources, and farm management tools. For governance, it provides role-based access and audit logging so operations and admins can separate permissions while retaining a trace of changes.
- +Field activities and scouting notes stay linked to planned work records
- +API access supports automation and data sync with external agronomy and telemetry tools
- +Role-based access separates farm user tasks from admin functions
- +Audit logging supports change history for records and configuration
- –Setup effort rises when multiple data sources and field boundaries must match
- –Some agronomic decision support workflows require structured inputs to avoid gaps
Best for: Fits when farm operators need planning and execution records connected to agronomy decisions, with integration into existing systems.
EOSDA Crop Monitoring
API-firstSatellite crop monitoring software for field scouting, weather analysis, and vegetation tracking.
Field boundary driven monitoring dashboards that prioritize scouting areas using remotely sensed condition signals.
EOSDA Crop Monitoring pairs satellite-based field mapping with agronomic monitoring workflows that focus on crop condition signals rather than document-first farm records. The system supports field boundary management, automated remote sensing analytics, and exportable outputs for downstream agronomy planning and work execution.
Its strength sits in how monitoring results can be turned into field activities and scouting priorities using configurable views for multiple crops and seasons. For teams that need repeatable monitoring-to-action pipelines across fields, it offers more operational structure than generic imagery viewers.
- +Remote sensing condition layers tied to field boundaries reduce manual field lookups
- +Configurable monitoring views support multi-crop and seasonal comparisons
- +Field exports fit variable-rate and scouting workflows that need map-like inputs
- +Automation reduces repeated checks by highlighting where attention is needed
- –Some agronomy recordkeeping still needs external systems for complete farm traceability
- –Precision workflows depend on consistent field boundary setup and crop assignment
- –Deep integration requires careful configuration of file formats and identifiers
- –Advanced IPM plan authoring remains limited compared with crop planning suites
Best for: Fits when teams need repeatable remote-sensing monitoring tied to field boundaries and scouting actions.
xFarm
SMBDigital farm management software for field records, crop activities, sensors, and sustainability data.
Field activity work-order execution linked to the same crop and season structure used for planning.
xFarm is crop production software focused on turning field plans into day-to-day field activities. It centralizes crop planning artifacts like planting schedules and work orders so agronomy teams can align operations, scouting, and follow-up tasks around the same season and fields. The tool also supports agronomic recordkeeping for field outcomes so agronomy decisions can reference past actions and results.
- +Field-based workflow ties crop planning to work orders for execution tracking
- +Season and field history improves consistency across agronomy decisions
- +Scouting and observation capture supports ongoing crop monitoring
- +Exportable records support downstream reporting and agronomic reviews
- –Precision agriculture features like variable-rate prescription maps are limited
- –Integrations for weather and satellite inputs are not as deep as specialist tools
- –Advanced rotation planning workflows can feel manual for complex multi-field farms
- –Role governance and audit visibility are weaker than dedicated farm governance systems
Best for: Fits when agronomy teams need field activity tracking that follows crop planning into operations.
Climate FieldView
enterpriseClimate FieldView software supports crop inputs planning, field activities tracking, and farm data management.
Field-level tasking and agronomic records stay connected across scouting, mapping, and performance reporting workflows.
Climate FieldView manages field activity records and performance data tied to specific fields, tasks, and seasons. The system pairs mapping, scouting entry workflows, and agronomic decision support outputs so teams can convert observations into documented next actions.
Climate FieldView also supports satellite and weather data ingestion and connects to guidance and variable-rate workflows through export and integration paths. For crop production software buyers ranking in the middle of the market, the main differentiator is how consistently FieldView keeps field-level context attached to agronomy actions across the season.
- +Keeps field context linked across scouting notes, tasks, and performance history
- +Supports weather and remote sensing data ingestion for ongoing crop monitoring
- +Provides practical field mapping and boundary management for prescription workflows
- +Works well for routine agronomy documentation without custom development
- –Automation depth depends on partner workflows and integration choices
- –Custom reporting and governance controls can be limiting for highly regulated setups
- –Advanced precision-ag workflows may require add-on configuration for full coverage
- –Data interoperability can require careful planning around identifiers and exports
Best for: Fits when mid-size teams want field-level scouting, documentation, and agronomy outputs tied to map-based context.
Farmers Business Network
enterpriseAgronomic and commerce platform offering field-level analytics, input purchasing, and grain marketing.
Peer benchmarking tied to field outcomes, with partner-aware workflows for converting recommendations into tracked farm records.
Farmers Business Network is a crop production software option aimed at growers and agribusiness partners that need agronomic benchmarking alongside planning and execution records. The core workflow centers on field activities, crop plans, and harvest and outcome tracking that connect agronomic decisions to observed results.
FBN also supports data sharing with standardized product and activity identifiers so partner integrations can pull and contribute farm records. Crop production teams typically use it to manage field-level decisions while keeping performance context across seasons and vendors.
- +Field activity tracking links decisions to outcomes at the farm level
- +Benchmarking context helps validate agronomic choices against peer performance
- +Catalog-driven product and input records reduce duplicate data entry
- +Collaboration with agronomic partners supports multi-entity workflows
- –Field setup and historical data import require disciplined preparation
- –Precision mapping workflows are less central than field records and planning
- –Automation options are narrower than tools built primarily for work-order dispatch
- –Integration depth depends on external partner connections rather than broad native connectors
Best for: Fits when growers need field-level planning plus benchmarking context, and partner integrations matter for execution records.
Conclusion
After evaluating 10 agriculture farming, Croptracker stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right crop production software
Crop production software in this buyer’s guide spans end-to-end farm execution records and map-linked agronomic workflows across Croptracker, FarmERP, and Climate FieldView. The tool set also includes Taranis, AgriXP, Agworld, Granular, EOSDA Crop Monitoring, xFarm, and Farmers Business Network for teams that vary across scouting capture, work order routing, and remote sensing monitoring.
The strongest differences show up in how each platform links field entities to scouting, work orders, and harvest traceability records, plus how automation can be extended via API and workflow configuration. Croptracker leads the shortlist on attaching scouting and work records to both crop and spatial context, while FarmERP emphasizes connecting crop plans to field-linked work orders and traceability continuity.
Crop production software for map-linked planning, execution, scouting, and agronomic recordkeeping
Crop production software records crop planning and turns it into field activities using work orders, tasking, and scouting workflows tied to map context. Croptracker is a clear example because scouting and work records attach to field entities and spatial context for after-action review.
FarmERP focuses on structured execution by linking field activities to work orders that connect crop plans to what teams do, then to harvest and traceability records. Climate FieldView supports field-level scouting and agronomic records that stay connected across scouting, mapping, and performance reporting, with weather and remote sensing ingestion for ongoing monitoring.
Crop production software features that change execution outcomes
Crop production software matters when field teams must keep crop plans, scouting results, and field execution records aligned to the same field context. The practical differentiator is how each platform links field entities to scouting and work records so after-action reviews and traceability stay consistent.
Map-linked scouting and field activity after-action review
Croptracker attaches scouting and work records to both field entities and spatial context so teams can reconcile observations with where they were taken. Taranis builds image-based scouting into field findings and links those findings to field mapping for consistent follow-through workflows.
Field-linked work orders that connect crop plans to execution and harvest records
FarmERP links field activities to work orders so crop plans connect to what teams do and then to harvest and traceability records. AgriXP ties planting plans, scouting notes, and harvest records into the same field timeline for day-to-day execution tracking.
Remote sensing monitoring dashboards tied to field boundaries and scouting actions
EOSDA Crop Monitoring prioritizes scouting areas with remotely sensed condition layers tied to field boundaries. Climate FieldView connects field-level tasking and agronomic records across scouting, mapping, and performance reporting while also ingesting weather and remote sensing inputs.
API access and automation surface for syncing agronomy inputs and extending workflows
Granular provides API access that supports automation and data sync with external agronomy and telemetry tools while keeping scouting and field activity history tied to planned actions. xFarm offers field activity work-order execution tied to the planning season and field structure, but its precision agriculture capabilities and integration depth are more limited than specialist monitoring or planning tools.
Work order conversion from scouting with crop context continuity
Agworld captures scouting as field-linked records that drive follow-on work orders while preserving the correct crop context. Farmers Business Network adds peer benchmarking context tied to field outcomes to help validate agronomic choices while converting recommendations into tracked farm records.
Decision framework for choosing crop production software by workflow control
Crop production software selection should start with what must remain linked end-to-end: field location context, crop plan context, and execution records that become traceability inputs. After that, the integration and automation surface decides whether the platform can ingest or synchronize the data pipelines already used in operations.
Pick the workflow anchor: after-action recordkeeping or image-based scouting
Choose Croptracker when teams need scouting and work records attached to field entities and spatial context for after-action review. Choose Taranis when teams want image-based crop scouting that converts imagery into field findings and routes them into follow-up work workflows.
Match execution depth: work orders tied to crop plans and harvest traceability
Choose FarmERP when crop plans must connect to field-linked work orders and then carry through harvest and traceability records. Choose AgriXP when field-centric work execution needs a single field timeline that links planting plans, scouting notes, and harvest records.
Select the monitoring model: field-boundary monitoring dashboards or execution-first records
Choose EOSDA Crop Monitoring when repeatable remote-sensing monitoring tied to field boundaries is required to prioritize scouting areas. Choose Climate FieldView when field-level tasking and agronomic records must stay connected across scouting and performance reporting with weather and remote sensing ingestion.
Validate data integration expectations against each platform’s automation surface
Choose Granular when automation and data sync with external agronomy and telemetry tools matter and the platform’s API access will be used to move structured scouting and planned work into your existing systems. Choose FarmERP or Agworld when advanced automation must be designed through workflow setup because deep precision agriculture integrations and rotation planning depth can require external system mapping or configuration work.
Check governance and onboarding friction for multi-site rollouts
Choose Agworld or AgriXP when work order follow-up can be configured, but expect crop rotation planning depth or workflow setup effort to affect multi-year consistency. Choose Croptracker or Granular when record linking depends on disciplined data entry and field boundary matching across multiple data sources.
Who should use each crop production software approach
Different teams need different alignment points between field context, scouting, and execution records. The best match depends on whether the operation is driven by spatial after-action review, structured work order execution, or monitoring dashboards that route scouting effort.
Farm teams that must reconcile scouting observations with exact field locations
Croptracker fits when scouting and work records must stay linked to both field entities and spatial context so after-action reviews remain consistent. Taranis fits when scouting teams operate from imagery capture and need computer-vision outputs tied into location-based follow-up tasks.
Operations that manage crop execution through structured work orders and traceability continuity
FarmERP fits when crop plans must connect to field-linked work orders that then carry into harvest and traceability records. AgriXP fits when a single field timeline must link planting plans, scouting notes, and harvest records for daily execution tracking.
Teams using remote sensing to prioritize scouting areas inside fixed field boundaries
EOSDA Crop Monitoring fits when field boundary driven dashboards must reduce manual lookup time and support multi-crop seasonal comparisons. Climate FieldView fits when remote sensing and weather ingestion must remain tied to field-level tasking and agronomic recordkeeping across monitoring and performance reporting.
Growers integrating agronomy and telemetry tools with automation and data synchronization
Granular fits when API access is needed to support automation and data sync while keeping scouting and planned agronomic actions connected. Farmers Business Network fits when benchmarking context must be paired with field-level planning and partner-aware workflows for tracked farm records.
Teams running day-to-day field execution where precision mapping features are secondary
Agworld fits when field-linked scouting must reliably turn into configurable work orders with consistent crop context even if crop rotation planning depth is limited for multi-year scenarios. xFarm fits when field activity work-order execution must follow the same crop and season structure used for planning while keeping variable-rate prescription maps limited.
Common pitfalls when rolling out crop production software
Most failures happen when teams assume the platform will fix record alignment issues that actually come from field data quality, boundary setup, and workflow discipline. The highest-risk mistakes are mismatches between field context and the scouting or work records that must later support traceability and performance review.
Running scouting and work capture without a disciplined data entry workflow
Croptracker relies on disciplined data entry by field teams because strong return depends on keeping map-linked scouting and work records accurate. Granular also increases setup effort when multiple data sources and field boundaries must match closely to prevent gaps in planned work connections.
Treating remote-sensing monitoring as a replacement for complete traceability recordkeeping
EOSDA Crop Monitoring reduces manual field lookups by tying remote sensing layers to field boundaries, but some agronomy recordkeeping still needs external systems for complete farm traceability. Climate FieldView supports weather and remote sensing ingestion, but automation depth depends on partner workflows and integration choices for regulated governance needs.
Under-scoping workflow configuration and governance for automation-heavy deployments
FarmERP can connect crop plans to field-linked work orders and traceability, but advanced automation requires careful workflow setup and ongoing governance to avoid execution drift. AgriXP supports field-linked work orders and scouting records, but precision agriculture features like advanced prescription mapping can require extra setup or add-ons.
Expecting precision mapping depth from a platform whose workflow center is execution tracking
xFarm links field activity work-order execution to crop planning and season structure, but precision agriculture features like variable-rate prescription maps are limited. Farmers Business Network emphasizes peer benchmarking and partner-aware workflows, so precision mapping workflows are less central than field records and planning.
How We Selected and Ranked These Tools
We evaluated Croptracker, FarmERP, Taranis, AgriXP, Agworld, Granular, EOSDA Crop Monitoring, xFarm, Climate FieldView, and Farmers Business Network for end-to-end linkage between crop planning, field activity, scouting capture, and traceability outcomes. Features carried 40% of the weighting, with ease and value each at 30% to reflect deployment friction and ongoing operational fit.
Croptracker separated itself by attaching scouting and work records to both field entities and spatial context for after-action review, which directly supports consistent location-based follow-through. FarmERP ranked highly for structured execution continuity by linking crop plans to field-linked work orders and then connecting into harvest and traceability records.
Frequently Asked Questions About crop production software
How do Agrivi-style workflow tools differ from data-first monitoring platforms like EOSDA Crop Monitoring?
Which tools link scouting outcomes to work orders and harvest records on the same field timeline?
What breaks if an operation needs field-level map context for every record but uses a record-only workflow?
How does Taranis turn imagery into operational follow-through instead of just observations?
When is an API or integration layer like Granular’s more relevant than manual data import?
Which systems support SSO and security controls such as RBAC and audit logs for multi-user farms?
How does data migration typically work when moving historical scouting and work records into Croptracker or FarmERP?
What admin control gaps appear when choosing between FarmERP, Agworld, and Granular for compliance-oriented execution?
When does Farmers Business Network fit better than EOSDA Crop Monitoring for farm teams working with vendor partners?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Top 10 Best Cow Calf Management Software of 2026
- Top 10 Best Farm Bookkeeping Software of 2026
- Top 10 Best Small Farm Accounting Software of 2026
- Top 10 Best Cattle Tracking Software of 2026
- Top 10 Best Ag Dealer Management Software of 2026
- Top 10 Best Drip Irrigation Design Software of 2026
- Top 10 Best Soil Sampling Software of 2026
- Top 10 Best Soil Testing Software of 2026
- Top 10 Best Soil Analysis Software of 2026
- Top 10 Best Livestock Record Keeping Software of 2026
- Top 10 Best Lawn And Garden Software of 2026
- Top 10 Best Irrigation Mapping Software of 2026
- Top 10 Best Yield Mapping Software of 2026
- Top 10 Best Wholesale Nursery Software of 2026
- Top 10 Best Weed Growing Software of 2026
- Top 10 Best Vertical Farming Software of 2026
- Top 10 Best Vegetable Software of 2026
- Top 10 Best Vegetable Planting Software of 2026
- Top 10 Best Vegetable Garden Planning Software of 2026
- Top 10 Best Vegetable Garden Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Agriculture Farming alternatives
See side-by-side comparisons of agriculture farming tools and pick the right one for your stack.
Compare agriculture farming tools→