Township Canada for Ag Retailers and Grain Companies
Crop input retailers, grain companies, and agronomy service providers cover defined sales territories — usually drawn around an elevator, a dealership, or a multi-RM service zone. The customers in those territories own and operate land identified by legal land description: every customer record, lease record, and field record references a DLS quarter section. Township Canada converts those descriptions to coordinates and maps so territory planning, customer-parcel mapping, agronomist route optimization, and CRM enrichment all run from the descriptions that customers already use.
For retailer-scale work — hundreds to thousands of customer parcels — batch conversion, route planning, and the API for CRM integration are usually what gets used most.
What ag retailers use it for
Mapping a customer book across a sales territory
A territory manager covers an area roughly 200 km by 150 km — half a dozen RMs in central Saskatchewan, or three counties along the Highway 16 corridor in Alberta. The customer book is in the CRM with legal descriptions in the address field. Without a map, the territory manager works from memory: who's where, who's adjacent to whom, which customers are clustered for a half-day field visit and which require a longer trip. The batch converter takes the customer CSV, returns coordinates and a downloadable KML, and lets the territory manager see the whole book on a map for the first time.
Field agronomist routing
A field agronomist with twelve grower visits scheduled for a Tuesday in late June covers more ground efficiently with a routed list than with a paper book. The route planner takes legal descriptions as input (no GPS needed), converts them, optimizes the order across range roads and township roads, and outputs turn-by-turn directions. For a typical agronomist visit day, the route optimization saves 60–90 minutes of driving.
CRM enrichment with coordinates and boundaries
Customer records in Salesforce, HubSpot, or a dedicated ag retail CRM need GPS coordinates to feed downstream tools — precision ag platforms, fleet dispatch, mailing list services, and BI dashboards. The Township Canada API takes a description and returns coordinates, township, range, meridian, and an optional boundary polygon. Nightly batch jobs keep the CRM in sync as new parcels enter the customer book.
Territory analysis and prospecting
Knowing which parcels in a territory are not currently customers — and which are adjacent to existing customers — supports prospecting and route-density planning. While operator-level prospecting depends on data sources outside Township Canada's current scope, parcel-level mapping of a territory polygon against a customer book is straightforward with batch conversion plus a mapping tool.
PRODUCT TEAM: The Ag Bundle PRD's Territory & Prospecting tool (issue #162) is intended to ship a polygon-draw + operator-inference UI inside Township Canada. Until that's live, retailer customers use external GIS to combine our parcel coordinates with their own customer data. This page should be updated to point to the in-app tool once it ships.
The retailer workflow
Annual planning. Map the territory. Identify customer clusters and underserved zones for the upcoming season.
Pre-season. Build the agronomist schedule. Run customer descriptions through batch conversion. Plan route density for each visit week.
In-season. Daily field routes. Same-day or next-day routing for emergency calls (pest pressure, equipment, agronomy questions). Updated maps as customer records change.
Post-harvest. Customer-by-customer recap visits. Year-end CRM cleanup with batch verification of every legal description in the book.
What retailers get from Business and API plans
Business plan — batch CSV upload, all export formats (Shapefile, CSV, KML, GeoJSON for GIS team consumption), team management for territory managers and agronomists, route planner for daily field schedules, and team-shared saved place management.
API access — programmatic conversion for CRM enrichment. Most retailer-scale workflows fit in the $50–$100/month tier (10,000+ requests/month). Larger grain companies with thousands of customers run on the enterprise tier. See API pricing.
PRODUCT TEAM: When the Ag Bundle Retailer tier launches in Stripe, this page should highlight that SKU specifically. Current copy intentionally uses the legacy Business + API tier names since the Ag SKU isn't deployed yet.
Related resources
- Batch Conversion of Legal Land Descriptions
- Route Planner for Field Visits
- API for Land Description Conversion
- Google Sheets Add-on for Customer List Enrichment
Map your customer book
Upload the customer CSV. Get coordinates and a KML map back. Plan the agronomist schedule from a real territory view.