Decision framework
Farm, product, and market websites or Crop, field, inventory, and equipment records?
Farm, product, and market websites and crop, field, inventory, and equipment records can both be reasonable responses to seasonal records live in disconnected files, but they solve different layers of the problem. The right choice depends on the operating result, not the more impressive label.
Choose Farm, product, and market websites when
This path fits when the core need can be addressed within the current system boundary and mobile-friendly offline-tolerant workflows is understood well enough to test safely.
- Seasonal records live in disconnected files
- Mobile-friendly offline-tolerant workflows
- Mapping, inventory, and sensor integrations
Choose Crop, field, inventory, and equipment records when
This path fits when the current behavior is only a symptom of a broader workflow, ownership, or platform limitation involving exports, audit history, and seasonal reporting.
- Inventory and availability change faster than the website
- Equipment and field history is difficult to retrieve
- Exports, audit history, and seasonal reporting
Compare the tradeoffs
Evaluate time to useful value, migration risk, reversibility, user disruption, and long-term ownership. Avoid treating feature count as a substitute for fit.
- Time to verified result
- Data and access risk
- Maintenance responsibility
- Ability to reverse course
A low-risk decision sequence
Inspect the existing state, prove the most uncertain assumption, and write acceptance checks for both paths. Choose only after the evidence explains which boundary must change.
- Inventory
- Focused test
- Decision record
- Scoped implementation