Warranty Form in HTML — Working Code Template
A warranty registration form — product model, serial number, purchase date, receipt upload, customer info. POSTs to splitforms; webhook into your warranty-tracking system or CRM.
A warranty form captures the proof you'll need if the customer ever files a claim — product model, serial number, purchase date, receipt upload, customer contact info. Make every field required; warranty claims that can't be matched to a registered product are a customer-support headache you don't want.
Use `type="date"` for the purchase date — native browser date picker, ISO format on submission (YYYY-MM-DD) which is easy to filter and query later. Use `type="file"` with `accept="image/*,.pdf"` for the receipt upload — most customers snap a photo of the receipt from their phone, so accept images alongside PDFs.
splitforms accepts file uploads up to 10 MB per file on every plan. The receipt arrives as an email attachment AND a downloadable file from the dashboard AND a signed URL in any webhook. For a warranty product, webhook into your warranty-tracking spreadsheet (Google Sheets, Airtable) or directly into your CRM (HubSpot, Salesforce, Pipedrive).
If you sell hardware with serial number traceability, the serial-number field is the key — register the warranty against the serial so any future claim can be matched automatically. Cross-reference the serial with your manufacturing records on receipt to flag invalid serials (counterfeit or fraudulent registrations).
How to set this up
Capture serial number + purchase date
These are the keys to matching future claims. Make them required.
Accept receipt as image or PDF
Most customers photograph the receipt on their phone. Accept image/* alongside .pdf.
Webhook into your tracking system
Airtable, Google Sheets, HubSpot — splitforms ships signed webhooks on every plan.
Cross-reference serial numbers
On webhook receipt, check the serial against your manufacturing database. Flag invalid registrations.
Serial + date + receipt upload. The keys to matching any future claim.
Frequently asked questions
What fields should a warranty registration form include?
Product model, serial number, purchase date, purchased from (retailer name), receipt/proof upload, customer name, email, phone, address. All required — warranty claims that can't be matched to a registered product create support headaches.
What file types should I accept for the receipt?
image/* (any image format, including phone photos) and .pdf. Most customers register from mobile and snap a photo of the paper receipt.
How do I prevent fraudulent warranty registrations?
Cross-reference the serial number against your manufacturing records on receipt. Use a webhook to your inventory database; flag and reject registrations with invalid serials. splitforms's dashboard surfaces flagged submissions separately.
How long should warranty data be retained?
For the warranty period plus a buffer for late claims — typically 2-3 years for consumer electronics. splitforms stores submissions permanently by default; export and delete after the retention period if you have a strict policy.
Related guides
Ship the form, not the backend.
Free for 1,000 submissions/month. Email delivery, AI spam filtering, signed webhooks, real dashboard — all on the free plan. No credit card.
Get a free access key →