What is it?
Address form pre-fill populates the address form with delivery details already stored in the retailer's e-commerce platform or other connected systems. Returning shoppers see their address ready to go — no manual re-entry required.
Address form pre-fill is part of Ingrid's Address Form. It uses a dedicated Ingrid API to securely exchange data between the retailer's system and the address form.
Key benefits
For retailers
Faster checkout for known shoppers — address fields are populated from existing systems
Higher checkout completion — pre-filled forms reduce friction at the address step
Better data consistency — retailer data flows directly into checkout, keeping systems aligned
Personalized experience — returning shoppers feel recognized
Lower input errors — pre-validated retailer data reduces typos and format issues
For shoppers
Less typing — address details appear pre-filled
Edit if needed — review and adjust before submitting
Faster, more personal checkout — recognized as a returning customer
How it works
The shopper proceeds to checkout
Ingrid checks if the shopper's delivery details exist in the retailer's connected system
If valid data is found, the address fields auto-fill via Ingrid's dedicated API
The shopper reviews, confirms, or edits the pre-filled information
Updated address data is synced back to the retailer's system, keeping records consistent
Pre-fill vs address book
Address form pre-fill is different from the address book:
Aspect | Pre-fill | Address book |
Data source | Retailer's backend systems | Shopper's browser |
Persistence | Permanent, on the retailer side | Browser-based |
Cross-device | Yes — tied to the retailer's customer record | No — tied to a single browser |
Pre-fill and address book can coexist — pre-fill applies the retailer's stored address, while the address book offers additional saved addresses the shopper can choose from.
Use cases
Logged-in returning customer
A shopper logs in to the retailer's site, adds items to cart, and proceeds to checkout. Their saved address pre-fills immediately — they confirm and continue.
Edit and sync back
A returning shopper has moved. The form pre-fills with their old address; they update the apartment number and submit. The retailer's system is updated automatically.
Fallback for unknown shoppers
A new shopper proceeds to checkout. Ingrid finds no matching record in the retailer's system, so the form is empty — the shopper completes it as normal.
Configuration
Address form pre-fill requires an API integration between Ingrid and the retailer's backend system. The integration is configured per retailer.
To set up pre-fill, contact your Ingrid contact.
FAQ
Q: How is pre-fill different from the address book?
A: Pre-fill pulls data from the retailer's backend systems. The address book stores data in the shopper's browser. Pre-fill works across devices; the address book is tied to a single browser.
Q: Do shoppers need to log in for pre-fill to work?
A: Typically yes — pre-fill needs a way to identify the shopper. Some retailers use session-based or token-based recognition without explicit login.
Q: Can pre-fill and address book work together?
A: Yes. Pre-fill applies the retailer's stored address; the address book offers additional saved addresses the shopper can switch to.
Q: What happens if the retailer's system is unavailable?
A: The address form falls back to empty, and the shopper completes it manually.
Q: Is the data exchange secure?
A: Yes. Ingrid's dedicated API is designed for secure, authenticated data exchange between retailer systems and the address form.
Q: Can shoppers edit pre-filled data?
A: Yes. Shoppers can review and update any field before submitting.
Q: Does pre-fill update the retailer's system?
A: Yes. Updated address data syncs back to the retailer's system on completion, keeping records consistent.