Technical Specifications & Data Dictionary

The Canadian Postal Code Database is a comprehensive electronic dataset containing all valid postal codes across Canada, enhanced with geographic coordinates, census linkages, and demographic data. The database includes approximately 900,000 postal codes covering urban, suburban, and rural areas nationwide.

Unlike raw Canada Post postal code files, our database adds significant value through latitude/longitude coordinates, Statistics Canada census geography integration, multiple delivery formats (Access, Excel, CSV), and monthly updates to ensure accuracy. The database supports address validation, geocoding, territory mapping, demographic analysis, and CRM/ERP system integration.

Each edition is designed for different use cases and organizational needs:

Our database enhances Canada Post postal code data with valuable additions not available in raw Canada Post files:

• Latitude/Longitude Coordinates: We add geocoding data with ~99% coverage, enabling mapping and GIS applications
• Statistics Canada Census Integration: Business edition includes pre-linked PCCF data, eliminating complex file joins
• Multiple Formats: Available in Microsoft Access, Excel, and CSV formats for easy integration
• Monthly Updates: Automated delivery of current data with 12 months of updates included
• Supplemental Tables: Cross-reference files for municipalities, streets, and accented names (Business edition)
• Enhanced Fields: Timezone, DST, elevation, population, and demographic data not present in basic postal code files

Our database is optimized for database integration with normalized fields, comprehensive documentation, and technical support, making it ideal for organizations needing postal code data in production systems without the complexity of managing raw Canada Post files.

All three formats are included with every purchase for the full 12-month license term:

• Microsoft Access (.MDB): Relational database format with tables, indexes, and relationships pre-configured. Ideal for direct querying or integration with Access-based applications.
• Microsoft Excel (.XLS): Spreadsheet format with data organized in worksheets. Suitable for analysis, reporting, or importing into business intelligence tools.
• CSV (Comma-Separated Values): Universal plain-text format compatible with all database systems, programming languages, and data processing tools. Field delimiter is comma, text qualifier is double-quote.

All formats contain identical data and are updated simultaneously each month. You can use different formats for different purposes throughout your license term without additional cost.

The database contains approximately 900,000 active postal codes covering all Canadian provinces and territories. This includes:

• Urban civic addresses (street addresses in cities and towns)
• Rural route addresses (RR, suburban service, mobile routes)
• Post Office Box addresses and lock box ranges
• General Delivery addresses
• Large Volume Receiver (LVR) postal codes

The database is updated monthly to reflect new postal codes added by Canada Post, retired postal codes, and changes to existing records. Each monthly update typically includes several thousand additions, deletions, and modifications.

Canadian postal codes are assigned to different address types based on delivery method:

The RecordType field in all editions indicates the postal code type, allowing you to filter or handle different address types appropriately in your applications.

Coordinates are derived from multiple validated sources and provide FSA-level accuracy with street-level precision in urban areas where data is available. Typical accuracy ranges from 50-500 meters depending on postal code type, with urban civic addresses being most precise.

Accuracy by postal code type:

• Urban Civic Addresses: 50-200 meters (street-level precision in most cases)
• Suburban/Small Town Addresses: 100-300 meters
• Rural Route Addresses: 200-500 meters (service area centroid)
• PO Box and General Delivery: Postal facility location (not individual recipient addresses)

Rural routes and PO Boxes represent approximate service area centroids rather than exact delivery points, as these postal codes serve geographic areas or postal facilities rather than specific street locations.

Coordinates are continuously validated and improved based on user feedback and cross-referencing with authoritative geographic sources. Coverage is approximately 99% of all postal codes, with the highest precision in urban centers.

Coordinate differences between data providers are common and result from several factors:

• Geocoding Methodology: Different providers use different algorithms and reference datasets (street centerlines, building footprints, parcel boundaries, or address points)
• Source Data Quality: Accuracy depends on the underlying geographic reference data, which varies by region and update frequency
• Postal Code Geography: A single postal code may cover multiple street segments or a geographic area, requiring providers to choose a representative point (centroid, delivery point, or route midpoint)
• Update Timing: Postal codes change over time as communities develop; coordinates may reflect different points in time
• Rural vs. Urban Treatment: Rural postal codes lack precise street addresses, requiring approximation methods that vary by provider

For most applications (territory mapping, demographic analysis, proximity searches), differences of 100-500 meters are acceptable and do not impact results. If your application requires higher precision for specific postal codes, see the next FAQ for improvement strategies.

Several strategies can help you work effectively with postal code coordinates and improve accuracy where needed:

Validation and Quality Control:

• Validate Against Known Addresses: Cross-reference coordinates for your critical locations (stores, facilities, customers) against known accurate addresses
• Report Discrepancies: Contact us with specific postal codes that appear inaccurate; we continuously improve coordinates based on user feedback
• Use FSA Centroids for Aggregation: For demographic or market analysis, use Forward Sortation Area (first 3 characters) centroids rather than full postal code coordinates to minimize precision requirements

System Design Considerations:

• Implement Tolerance Thresholds: Design proximity searches and territory assignments with appropriate distance buffers (e.g., 500m-1km tolerance) to account for coordinate variability
• Understand Postal Code vs. Civic Address Differences: Postal codes represent delivery areas, not individual buildings; civic addresses provide more precise geocoding when available
• Use Address Validation: Combine postal code coordinates with full civic address validation for applications requiring high precision
• Leverage Census Boundary Files: Business edition's PCCF linkage allows you to use Statistics Canada boundary files for precise geographic assignment rather than relying solely on point coordinates

The Forward Sortation Area (FSA) is the first three characters of a Canadian postal code (e.g., "K2G" in "K2G 0P7"). It represents a broader geographic region used by Canada Post for mail sorting and routing.

Key Differences:

FSA Structure: The first character indicates province or region (e.g., K=Eastern Ontario, M=Toronto, V=British Columbia). The second character indicates urban (0) or rural (1-9). The third character defines a specific area within that region.

The Deluxe and Business editions include FSA-level population and dwelling counts from Statistics Canada, making FSA analysis useful for demographic profiling without requiring full postal code precision.

The database is updated monthly, with 12 updates included during your license term. Updates are typically released during the first week of each month and reflect changes from Canada Post as of the previous month's end.

Each monthly update includes:

• New postal codes added by Canada Post
• Retired or deleted postal codes
• Changes to existing postal code attributes (municipality names, boundaries, etc.)
• Coordinate refinements and corrections
• Census geography updates (Business edition, when Statistics Canada releases new boundary files)

Updates are provided as complete database files in all three formats (Access, Excel, CSV). We do not provide delta/change-only files; each monthly release is a full replacement dataset.

Yes, all postal codes in the database are validated against Canada Post's official postal code data and represent currently deliverable addresses. Our monthly update process ensures:

• Active Postal Codes Only: The database contains only postal codes currently in use by Canada Post for mail delivery
• Retired Code Removal: Postal codes that Canada Post has retired or replaced are removed in monthly updates
• New Code Addition: Newly created postal codes (for new developments, subdivisions, or address changes) are added as Canada Post releases them
• Attribute Accuracy: Municipality names, provinces, and other attributes reflect current Canada Post designations

However, it's important to understand the scope of validation:

For complete address validation (verifying both postal code and civic address correctness), you should integrate the database with address validation logic that checks street number ranges, street names, and municipality consistency.

These three columns were added in July 2026 to Deluxe and Business. They exist because the two fields that came before them cannot answer the question people actually ask.

TimeZone tells you which zone a postal code is in. DST tells you whether the clock moves there. Neither tells you what the offset is — and that is what you need to convert a timestamp, schedule a delivery window, or stamp a record with local time. The three new columns give you the resolved answer for both halves of the year.

The three values of DSTBehavior:

• SEASONAL — the clock moves. The summer offset is one hour ahead of the standard offset. This is most of Canada.
• STANDARD_ONLY — the clock never moves. Both offsets are the same value, and that value is the location’s standard time.
• PERMANENT_DST — the clock never moves, but the fixed offset is the one the location used to observe in summer. Several Canadian jurisdictions have legislation of this kind at various stages, not all of it in force, so treat membership of this category as something to read from the file rather than to assume from the news.

Why the offsets are decimals and not integers. Newfoundland is -3.5 / -2.5 — UTC−3:30 in winter and UTC−2:30 in summer. It is the reason the columns are declared Decimal(3,1). Rounding them to whole hours, or reading them into an integer column, puts every Newfoundland record thirty minutes wrong.

Worked examples, all real records from the current file:

Rules you can rely on:

• Offsets are hours from UTC, negative west of Greenwich. Local time is UTC + offset.
• Where DSTBehavior is SEASONAL, UTCOffsetSummer is always exactly one hour ahead of UTCOffsetStandard.
• Where it is not SEASONAL, the two offsets are equal — so code that always reads the right column for the date is correct everywhere and needs no special case.
• The changeover dates are the North American ones: second Sunday of March to first Sunday of November.

These columns describe the location, not an instant. To stamp a particular timestamp you still choose which of the two offsets applies based on the date — the file tells you what both of them are, and whether the choice matters at all.

Yes, the database includes bilingual naming support for Canadian locations, particularly important for Quebec and officially bilingual regions:

Standard and Deluxe Editions:

• Municipality names are provided in their official Canada Post designation (may be English, French, or bilingual depending on location)
• Province codes are standard 2-letter abbreviations (QC, ON, NB, etc.)
• Mixed-case city names carry postal-standard spelling with proper capitalisation (e.g., "Montreal", "Quebec") — the accented display forms come from the Accent Supplement

Business Edition (Additional Bilingual Support):

• Accent Supplement Table: Maps unaccented to accented name variations (8,315 records) with special character encoding for French diacritics
• Municipality Cross-Reference Table: Includes alternate names in both English and French where applicable (8,126 records)
• Street Names: full address components with French street type codes (RUE, BOUL, CHEMIN, etc.). Street names follow the same postal convention as city names — unaccented, with the Accent Supplement carrying the accented forms
• Census Geography Tables: Federal Electoral District names provided in both English and French

The accent handling allows applications to perform searches using either accented or unaccented input while maintaining proper display formatting.

Canada Post publishes its place and street names without accents, so that is how they are stored — MONTREAL, not MONTRÉAL. Accents are handled in three places instead:

All Editions:

• Mixed-Case Fields: CityMixedCase (all editions) and the address component fields (Business) carry proper capitalisation — Montreal rather than MONTREAL
• Statistics Canada columns: the census geography names in Business are StatCan's own and are accented — Québec, Saint-André, Côte-ouest
• Encoding: the Business CSV is Windows-1252 (Latin-1), not UTF-8 — read it as Windows-1252 and convert on the way in. Standard and Deluxe contain no accented characters at all, so the question does not arise for them. See File formats.
• Database Collation: Access and Excel formats maintain accent-sensitive sorting and searching

Business Edition (Enhanced Accent Support):

The Accent Supplement Table (8,315 records) provides explicit mappings between unaccented and accented name variations using special character codes:

This supplement enables fuzzy matching and search normalization, allowing users to find locations whether they type "Montreal" or "Montréal", "Quebec" or "Québec".

The Municipality Cross-Reference Table (8,126 records, Business edition only) maps alternate, abbreviated, or historical municipality names to their current official Canada Post designations.

Use Cases:

• Address Validation: Resolve user input like "Milliken" to official name "Markham" for postal code validation
• Historical Data Cleansing: Update legacy databases with old municipality names to current designations
• Abbreviation Handling: Match common abbreviations (e.g., "St. John's" vs "Saint John's") to official forms
• Regional Name Variations: Handle neighborhood names that users may enter instead of official municipality names
• Municipal Amalgamation: Resolve former municipality names that were merged into larger jurisdictions

Table Structure:

The Valid Flag allows you to distinguish between current alternate names (which may appear on official documents) and purely historical names (useful for data archaeology but not current validation).

The Postal Code Conversion File (PCCF) is Statistics Canada's linkage file that connects postal codes to census geographic areas. It enables demographic and socioeconomic analysis by allowing you to attach census data to postal code records.

Our Business Edition Provides PCCF-Equivalent Linkage:

Unlike Statistics Canada's separate PCCF file (which requires complex joins and technical expertise), our Business edition includes census geography linkages pre-integrated directly into each postal code record. This provides the same analytical capability as PCCF without separate file management, complex joins, or additional licensing. Census geographies are already integrated into each postal code record, ready for immediate analysis.

Linked Census Geographies (Business Edition):

• Census Metropolitan Area (CMA/CA): Major urban centers and surrounding areas
• Census Division (CD): Counties, regional districts, or equivalent
• Census Subdivision (CSD): Municipalities and equivalent areas
• Census Consolidated Subdivision (CCS): Grouped municipalities
• Dissemination Area (DA): Small, stable geographic units (~400-700 people)
• Dissemination Block (DB): City blocks or equivalent small areas
• Census Tract (CT): Neighborhoods in large urban centers
• Federal Electoral District (FED): Parliamentary constituencies
• Economic Region (ER): Economic analysis regions
• Population Centre (PC): Urban core classification
• Designated Place (DPL): Named communities

Practical Applications:

• Demographic Profiling: Link postal codes to census profiles (income, education, household composition) for customer segmentation
• Market Analysis: Aggregate sales data by census geography for market research and planning
• Territory Planning: Align sales territories with census boundaries for demographic consistency
• Site Selection: Evaluate potential locations using census demographic and economic indicators
• Government Reporting: Report data by Federal Electoral District or other official boundaries

The Business edition includes comprehensive census geography integration with 46 core fields in the main postal code table plus 17 supplemental reference tables.

Census Geography Fields (UIDs and Names):

Each postal code record includes both the unique identifier (UID) and descriptive name for the following census geographies:

Additional Geographic Fields:

• Street-Level Address Components: Area name, street name, street type, direction, suffix (for civic addresses)
• Municipality Name: Official municipality designation
• Population & Dwellings: FSA-level counts from census data

All census geography fields include both UID (unique identifier for database joins) and descriptive names (for reporting and display), eliminating the need for separate reference table lookups in most applications.

The Business edition eliminates the need for manual linkage - census geographies are already integrated into each postal code record. However, understanding the methodology helps you use the data effectively:

Pre-Linked in Database (Business Edition):

Each postal code record includes census geography UIDs (unique identifiers) and names in dedicated fields. Simply query the postal code to retrieve its associated census geographies:

-- Example: Find census data for a specific postal code
SELECT 
    PostalCode,
    CensusMetropolitanAreaName,
    CensusDivisionName,
    CensusSubdivisionName,
    CensusDisseminationAreaUID
FROM PostalCodes
WHERE PostalCode = 'K2G0P7';

Joining to Statistics Canada Census Profiles:

Once you have the census geography UID from a postal code, join it to Statistics Canada's census profile data using the UID as the key:

-- Example: Link postal codes to census demographic data
SELECT 
    pc.PostalCode,
    pc.City,
    pc.CensusDisseminationAreaUID,
    census.TotalPopulation,
    census.MedianHouseholdIncome,
    census.PercentUniversityDegree
FROM PostalCodes pc
LEFT JOIN CensusProfiles census 
    ON pc.CensusDisseminationAreaUID = census.DAUID
WHERE pc.Province = 'ON';

Using Supplemental Geography Tables:

The Business edition includes 17 supplemental tables with complete census geography reference data. These tables provide additional attributes beyond what's in the postal code records, such as Population Centre classifications, Federal Electoral District names in English and French, and hierarchical linkage files showing how different census geographies nest within each other.

Yes, the Business edition's census geography linkage is specifically designed to enable demographic data appending. Here's how:

Method 1: Use Census Geography UIDs (Recommended)

Join postal code records to Statistics Canada census profile data using the census geography UID fields:

1. Download Census Profiles: Obtain demographic data from Statistics Canada (available free at statcan.gc.ca)
2. Choose Geography Level: Select appropriate level (DA, CSD, CT, etc.) based on your precision needs
3. Join on UID: Match the UID field from postal codes to the geography UID in census profiles
4. Append Demographics: Pull desired census variables (income, education, age, household size, etc.) into your postal code records

Available Demographic Data from Census:

• Population and household counts
• Age and sex distribution
• Income statistics (median, average, distribution)
• Education levels and field of study
• Labor force characteristics and occupation
• Housing characteristics (dwelling type, tenure, value)
• Language and immigration status
• Family and household composition
• Commuting patterns and mode of transportation

Common Applications:

• Customer Segmentation: Profile customer base by income, education, or lifestyle characteristics
• Site Selection: Evaluate potential locations based on demographic fit
• Market Sizing: Estimate addressable market using population and household counts
• Direct Mail Targeting: Select postal codes matching target demographic profiles
• Risk Assessment: Score credit or insurance risk using neighborhood demographics

Two license types are available based on how you intend to use the database:

Regular Licenses (Internal Use):

• Scope: Use within your organization for internal operations, analysis, or systems
• User Tiers: Three tiers based on number of users: 1-5 users, 6-50 users, or 51+ users (enterprise)
• Multi-Year Terms: Available in 1-year, 2-year, or 3-year terms with volume discounts
• Permitted Uses: Address validation, internal reporting, CRM/ERP integration, sales territory mapping, customer analysis, operational systems
• Restriction: Data cannot be redistributed, resold, or provided to external parties

Redistribution Licenses (External Distribution):

• Scope: Embed data in commercial products, provide to clients, or otherwise distribute outside your organization
• End-User Tiers: Three tiers based on number of end-users who will access the data: 1-5 end users, 6-50 end users, or 51+ end users
• Term: 1-year only (multi-year not available for redistribution licenses)
• Permitted Uses: SaaS applications, commercial software products, consulting deliverables, client-facing tools, API services

User Count Guidelines:

A "user" is any individual who accesses the database directly or indirectly through an application or system. Count all employees, contractors, or API consumers who interact with postal code data derived from the database.

The key distinction is whether data leaves your organization:

Redistribution Indicators (Requires Redistribution License):

• Embedding database in commercial software sold or licensed to customers
• Providing postal code data or lookups to clients as part of consulting services or deliverables
• Operating a public or client-facing API that returns postal code information
• Including postal code data in reports, datasets, or analysis provided to external parties
• Allowing partners, vendors, or contractors outside your organization to access the data

Regular License Use (No Redistribution):

• Internal address validation for order processing, shipping, or customer records
• Territory mapping and sales planning for internal use only
• Demographic analysis and market research for internal strategic planning
• CRM, ERP, or database enrichment for internal operational systems
• Multiple departments or locations within your organization (count total users across all)

Yes, Regular licenses are available in 1-year, 2-year, or 3-year terms with significant volume discounts. Redistribution licenses are 1-year only.

Multi-Year Benefits:

• Cost Savings: 2-year and 3-year terms offer 10% discounts compared to annual renewal pricing
• Price Lock: Protect against future price increases for the duration of your term
• Administrative Efficiency: Fewer renewal transactions and license management overhead
• Continuous Updates: Receive all monthly updates throughout the multi-year term (24 updates for 2-year, 36 updates for 3-year)

Sample Pricing Comparison (Business Edition, 1-5 Users):

Multi-Year License Details:

• Monthly Updates Included: 12 updates per year for the entire term (e.g., 36 monthly updates for 3-year license)
• All Formats Included: Access, Excel, and CSV formats for the full term
• User Count Fixed: User tier selected at purchase applies for the entire term (cannot upgrade mid-term; contact us if needs change)
• No Refunds: Multi-year licenses are non-refundable after 30 days; ensure user count and edition meet your long-term needs

Each edition includes a progressively expanded field set designed for different use cases. Here are the key fields for each edition:

Standard Edition (8 fields):

PostalCode, City, Province, AreaCode, Latitude, Longitude, CityMixedCase, RecordType

Deluxe Edition (18 fields) - Adds:

ProvinceName, CityFlag, TimeZone, DST, Elevation, Population (FSA-level), Dwellings (FSA-level)

Business Edition (46 fields) - Adds 28 additional fields including:

• Address Components: AreaName, StreetName, StreetTypeCode, StreetDirCode, StreetSuffix, MunicipalityName, AddressType
• Census Geography UIDs and Names: CensusMetropolitanArea, CensusDivision, CensusSubdivision, CensusDisseminationArea, CensusTract, CensusConsolidatedSubdivision, FederalElectoralDistrict, DesignatedPlace, EconomicRegion, PopulationCentre

For every column with its type and edition availability, see the data dictionary above.

Yes, the database integrates easily with most address validation systems, CRM platforms, ERP systems, and custom applications. Standard formats (CSV, Excel, Access) ensure compatibility with virtually any technology stack.

Compatible Platforms and Systems:

• CRM Systems: Salesforce, Microsoft Dynamics, HubSpot, Zoho, SugarCRM
• ERP Systems: SAP, Oracle, Microsoft Dynamics 365, NetSuite
• Database Platforms: MySQL, PostgreSQL, SQL Server, Oracle Database, MongoDB
• Business Intelligence: Tableau, Power BI, Qlik, Looker
• E-Commerce: Shopify, WooCommerce, Magento, BigCommerce
• Custom Applications: Any platform supporting CSV import, ODBC, or database connectivity

Integration Use Cases:

• Real-Time Address Validation: Query postal code table during data entry to validate city/province against entered postal code
• Geocoding Service: Convert postal codes to lat/lon coordinates for mapping applications
• Territory Assignment: Use census geography fields to assign customers to sales territories
• Demographic Enrichment: Append census data to customer records based on postal code
• Data Cleansing: Standardize existing address data against postal code reference

The Business edition includes 17 supplemental reference tables providing cross-reference data, census geography details, and alternate name mappings. These tables enhance the main postal code dataset and enable advanced address validation and demographic analysis.

Cross-Reference & Supplemental Data Tables (3 tables):

• Municipality Cross Reference (8,126 records): Maps alternate, abbreviated, or historical municipality names to current official Canada Post designations. Includes valid/invalid flags and FSA associations for address validation and data cleansing.
• Accent Supplement (8,315 records): Provides mappings between unaccented and accented name variations using special character codes. Enables accent-insensitive search while maintaining proper display formatting for French names.
• Street Supplement (9,552 records): Links alternate or obsolete street names to current official names. Includes street types, directions, and municipality context for comprehensive address standardization.

Census Geography Reference Tables (11 tables):

• Census Division (293 records): County, regional district, or equivalent boundaries with UIDs, names, and provincial associations
• Census Tract (6,247 records): Neighborhood-level areas in large CMAs (~2,500-8,000 people)
• Census Dissemination Area (57,936 records): Small, stable geographic units (~400-700 people); smallest standard geography for demographic analysis
• Census Dissemination Block (498,786 records): City blocks or equivalent areas; smallest census geography
• Census Consolidated Subdivision (1,757 records): Grouped municipalities for rural/small town analysis
• Census Subdivision (5,161 records): Municipalities (cities, towns, villages) and Indian reserves
• Census Metropolitan Area (156 records): Major urban centers (100,000+ population) and surrounding areas
• Economic Region (76 records): Groups of census divisions with similar economic characteristics
• Federal Electoral District (338 records): Parliamentary constituencies (ridings) with names in English and French
• Population Centre (1,030 records): Classification of urban cores by population and density
• Aggregate Dissemination Areas (5,433 records): Grouped dissemination areas for privacy-compliant demographic reporting

Geographic Reference & Relationship Tables (3 tables):

• Province (13 records): Full names and abbreviations in English and French, plus numeric codes
• Designated Place (1,685 records): Named population centers without official municipal status
• Dissemination Geographies Relationship File (498,786 records): Hierarchical linkage showing how different census geographies nest within each other based on Statistics Canada 2021 DGUID structure

Yes, all postal code types are included in the database: urban civic addresses, rural route addresses (RR/SS/MR), Post Office Box addresses, general delivery addresses, and Large Volume Receiver addresses.

The RecordType field identifies the postal code type, allowing you to filter or handle different address types appropriately in your applications.

Implications for Applications:

• Address Validation: All postal code types can be validated; civic address components (street, number) are only available for urban addresses
• Geocoding: Coordinates are provided for all types but precision varies
• Routing & Logistics: Rural routes and PO Boxes require special handling as coordinates don't represent delivery destinations
• Demographic Analysis: Census linkage works for all postal code types; rural areas may have larger geographic coverage per postal code

Use the RecordType and AddressType fields (Business edition) to implement appropriate logic for different postal code types in your address validation and geocoding workflows.

Monthly updates are delivered through your online account with multiple access options:

Standard Delivery (All Customers):

1. Account Download: Log into your account at account_database.asp using your username and password
2. Access Current Release: Monthly updates are posted around the 15th of each month
3. Download All Formats: All three formats (Access, Excel, CSV) are available for download simultaneously
4. Full Database Files: Each monthly release is a complete database (not delta/change files); download and replace your previous version

FTP Access (Optional):

Customers can request FTP access for automated monthly retrieval. FTP credentials and directory paths are provided upon request, allowing you to configure automated pull scripts.

Download Specifications:

• File Sizes: Vary by edition (Standard ~20MB, Deluxe ~30MB, Business ~150MB compressed)
• Compression: Files are ZIP compressed to reduce download time
• Access Period: All monthly releases from your license start date remain accessible throughout your license term

Technical Support: If you experience download issues or need alternative delivery arrangements, contact info@zip-codes.com or call 1-800-425-1169 for assistance.

Yes, you receive email notifications when each monthly update is released. Notifications are sent to the email address associated with your account.

Email Notification Content:

• Announcement of the new release month (e.g., "October 2025 release")
• Direct link to your account download page
• Your account username (password not included for security)
• Contact information for support questions

Managing Notifications:

• Whitelist Our Address: Add info@zip-codes.com to your email whitelist to ensure delivery
• Update Email Address: Contact us to change the email address receiving notifications
• Unsubscribe: Notifications can be disabled via the unsubscribe link in each email (you'll still have account access)

Notification Timing:

Emails are typically sent within 24 hours of the update being posted to your account, usually during the first week of each month.

Yes, FTP access is available upon request for automated monthly retrieval. FTP is particularly useful for organizations with automated data pipelines or those who want to eliminate manual download steps.

FTP Access Details:

• Availability: Available to all license types and editions (Standard, Deluxe, Business)
• Request Process: Contact info@zip-codes.com or call 1-800-425-1169 to request FTP provisioning
• Provisioning Time: FTP credentials typically provided within 1-2 business days of request
• Access Type: Pull-only access (you retrieve files from our server; we do not push files to your server)

FTP Configuration:

Upon approval, you'll receive FTP server address, username & password, directory path, and connection details (typically FTP port 21 or SFTP port 22).

Automated Pull Setup:

Customers configure their own FTP clients or automated scripts to pull updates on their preferred schedule. Files are posted to your FTP directory during the first week of each month (typically by the 5th). All three formats (Access, Excel, CSV) are available, and previous months' files remain accessible throughout your license term.

Customer Responsibility:

• Configure and maintain your FTP client or automation scripts
• Set your own retrieval schedule (daily, weekly, monthly)
• Implement error handling and retry logic as needed
• Manage storage and archiving of downloaded files

For assistance configuring FTP access or troubleshooting connection issues, contact our technical support team at info@zip-codes.com.