License plate region contract fields

Plate number and plate state belong on different lines on most storage agreements.

Why we built it

Templates often split license plate and state/region into separate blanks. A single combined field forced awkward workarounds or wrong auto-fill. License plate region contract fields add Car License Plate State (car_license_plate_state) to the field catalog. Values pull from each car’s license plate state on the record. When you upload a PDF, label inference recognizes plate state, registration state, and combined headers like License plate / state without treating the whole label as the plate number—so repeated vehicle rows stay aligned.

Who it is for

Admins building multi-vehicle storage agreements with per-car plate lines.
Teams importing cars with plate state populated from VIN decode, migration, or manual entry.
Staff sending contracts who rely on auto-fill instead of retyping CA, TX, or ON on every send.

What you can do

Drag Car License Plate State onto the template next to Car License Plate on vehicle rows.
Let upload auto-suggest the field when AcroForm or OCR labels match common state/region wording.
Send or sign with state filled from the linked car—same behavior in onboarding bundles and bulk send.
Keep plate number and state as separate columns in Create a contract template field review.

Contract template editor with vehicle fields on the PDF — Place state in its own box on the PDF; auto-fill reads licensePlateState from the car profile.

How it fits your day

Upload a legacy PDF with separate PLATE and STATE columns, accept suggested Car License Plate and Car License Plate State mappings, and publish. On send, each vehicle row fills both values from the garage record.

Get started

Edit a template, add Car License Plate State to one vehicle row, send a test contract for a car with a known state, and confirm the PDF shows the correct abbreviation before customer signing.