AI product readCopy and carry a gift registry recipient's shipping address from MyRegistry.com to merchant checkout pages, with optional auto-fill for supported retailers
When shopping for gifts from a registry, users must toggle back and forth between the registry page and the merchant checkout to manually copy the recipient's shipping address. This extension eliminates that friction by capturing the address once and displaying it alongside checkout, with one-click auto-populate for supported sites.
1. User browses MyRegistry.com and navigates to a recipient's shipping/PurchaseAssistant page. 2. Extension scrapes the shipping address from the page DOM (#FirstName, #AddressLine1, etc.) and stores it in chrome.storage.sync. 3. User navigates to a merchant checkout page (e.g., Amazon, Target). 4. Extension injects a draggable floating widget displaying the stored address. 5. If the merchant is supported (server-fetched CSS selectors match), a 'Populate' button auto-fills the checkout form fields.
Reads recipient shipping address (name, address, city, state, zip, country) from MyRegistry.com PurchaseAssistant pageStores address in chrome.storage.sync for persistence across tabsDisplays a draggable floating widget showing the recipient's address on any merchant checkout pageAuto-populates shipping form fields on supported retailers (Amazon mode 1, Target mode 2, Bed Bath & Beyond mode 3, and generic mode 0)Fetches website-specific CSS selector configurations from MyRegistry.com server for auto-populate supportRemembers widget position across sessions
- Target users
- MyRegistry.com registry users who are buying gifts for someone's registry / Online shoppers who purchase from multiple retailers using a shared registry
- Cannot verify whether MyRegistry.com's PurchaseAssistant page requires login or is accessible via shared links without login
- Cannot confirm whether MyRegistry.com (the destination service) has paid registry plans that might affect the user experience
- The extension fetches website-specific selector configs from MyRegistry.com server endpoint (/BrowserExtensions/Shipping/v1_0/handlers/ExtensionHandler.ashx) which could change server-side behavior
MonetizationNo paid features detected
The extension contains no subscription logic, payment processing, feature gating, premium tiers, or payment integrations (no Stripe, PayPal, etc.). The deterministic heuristic's 'paid' keyword hits are all false positives: 'pro' matches refer to font names (Proxima Nova, Source Serif Pro) and generic JS (Promise, prop, hasOwnProperty), while 'purchase' and 'checkout' refer to the shopping use case (making purchases at merchant checkouts), not paid features of the extension. All extension features (address display, auto-populate) are available to all users without any paywall.
- Confidence
- 90
- Payment platform
- --
- Source
- AI / High
- Login required
- Yes
- Reason
- The extension itself does not implement any login UI, authentication, or account system. However, its core workflow requires the user to be on MyRegistry.com's PurchaseAssistant.aspx page where it scrapes shipping address data from DOM elements (e.g., #FirstName, #AddressLine1). To access a registry's shipping address on MyRegistry.com, a user must be logged into MyRegistry.com. The extension reads this data only when the page contains valid address fields and the user has navigated to the Purchase Assistant page.