Issue Summary In the current contact information workflow, DriveCentric allows users to enter Address → City → State/Province → Zip/Postal Code. When the Zip/Postal Code is entered, the system often overrides the correctly entered city with an incorrect or unrelated city/county/area. This behavior creates unnecessary rework and introduces data inaccuracies. Current Problem Users correctly enter the city first. Upon entering the Zip/Postal Code, DriveCentric auto-updates the city field. The updated city is frequently wrong (random county or nearby area). Users must then backtrack and correct a field that was already accurate. This is inefficient, frustrating for staff, and leads to inconsistent or incorrect customer address data. Business Impact Slower data entry and increased admin time Higher risk of inaccurate customer records Redundant corrections that break workflow momentum Increased user frustration during high-volume data entry (sales, service, finance) Requested Solutions (Either Option Would Solve the Issue) Add a Toggle to Disable City Auto-Override Allow dealerships to turn off auto-population of the city when a Zip/Postal Code is entered. If a city is manually entered, it should be treated as authoritative. Change the Field Entry Order / Logic Allow Zip/Postal Code to be entered before the city. When tabbing forward, the city can then be reviewed or modified in sequence. This allows users to correct errors moving forward, rather than being forced to go backward and re-fix valid data. Why This Matters A forward-only, correction-as-you-go workflow is faster, cleaner, and reduces mistakes. If the auto-fill is wrong, users can fix it immediately. If it’s right, they can keep tabbing without interruption. This aligns with how staff actually enter data in real dealership environments. Summary This small workflow change would eliminate redundancy, improve data accuracy, and significantly speed up daily CRM usage across sales, service, and finance teams.