Guest planning
Import and review registry products
Product documentation · Reviewed
Import and review registry products
Open your wedding’s Registry products area in the owning workspace. Couples and business members with full private workspace access can use the same product list. An invitation to a shared wedding, a guest household link or a restricted staff role does not grant access.
Registry products describe what you requested. Received gifts & thank-yous remains a separate record of gifts you actually received. Importing a product does not record a purchase, change a gift, send a message or put anything on your wedding website.
Paste rows or choose a CSV
Paste tab-separated spreadsheet rows with a heading row, or choose a CSV file. CSV supports quoted commas and multiline cells. Pasted tab-separated text uses one physical line per product; use CSV for multiline descriptions. Name the retailer or original source, then choose Map these columns.
Map the title, optional description, retailer product ID, source registry URL, product URL, requested quantity, exact unit price in cents and currency. A missing quantity means one. A missing price remains unknown; supply both the price and its three-letter currency code or leave both blank.
For example, a unit price of 2499 with USD means 2,499 US cents. 24.99, $24.99, negative amounts and fractional quantities are invalid. Zero cents is retained as an explicit zero price. A EUR row stays EUR; the import does not combine currencies or calculate an exchange rate.
The web review accepts up to 1,000 rows and 900 KB of source text. Versioned API requests have a separate 200 KB JSON-body limit. Split larger API submissions into independently reviewed imports. The importer reads the supplied data only; source links are not fetched and retailers are not synchronized.
Review the mapped products
Preview import saves the original cells, mapping and normalized product values. Nothing is added yet. Review each row’s result, its original source values and the counts of valid, duplicate and invalid rows. History pages keep older rows reachable.
Duplicate checks use retailer/source name plus a case-sensitive product ID, a product URL, or—when neither is provided—the source name plus normalized title. URL checks ignore fragments and common tracking parameters while keeping product-variant parameters. A match to any retained identity skips the row; quantities are never combined. Earlier identifiers remain associated with a product after you edit it, so a repeat export does not create a duplicate under its old identifier.
Invalid and duplicate rows are skipped. Correct their source data and make a fresh review if you want to include them. The original review remains available. Two imports approved at the same time recheck current products before adding anything.
Import, resume and retry
After checking the review confirmation, choose Approve and import first 50. Each completed batch is saved. Choose Continue import for the next batch of up to 50. You can close the page and resume from Import reviews & recovery later. Each new batch requires your current workspace access; revocation prevents further changes.
If a response is interrupted, retry the same unchanged decision. Its saved request identity recovers the original result. If another operator changed the import or product, refresh and review its current revision before making a new decision.
Explicitly match a received gift
First record the received gift in the wedding’s existing gift list. Open Link a received gift on a product, select that gift, review its description and value, enter the represented quantity and confirm the match. If the gift changed after you reviewed it, the link is rejected until you review the current gift.
The product price and received-gift value can differ; linking does not overwrite either. Linked quantities cannot exceed the product’s requested quantity. Gift selectors have separate history pages for weddings with many received gifts.
Use Unlink this match to correct an incorrect association. The original product and gift snapshots, quantity, operator and unlink history remain. If someone explicitly deletes the original gift, its former match is labeled as historical and is no longer counted as an active received quantity. No thank-you is drafted or sent by these actions.
Undo without losing later work
From an import review, explicitly confirm Undo untouched products. Undo removes only unchanged products created by that import from the active list. It preserves edited products, every product with received-gift link history, and products retained by a published website revision. Unimported rows are stopped; undo never creates them. Large undos use the same resumable batches of 50.
Every removed product and its original import row remains in retained history. Preserved rows explain their reason. A repeated import cannot undo products created by another import. The separate received-gift CSV importer also preserves a gift that has registry-link history, even if the match was later unlinked.
Wedding website registry links are still selected and published manually. If a visible registry section contains an exact current product URL, publication review freezes the matching product reference. An intervening product edit or undo requires a fresh publication review. Editing the private product afterward does not change the published page. Replaying an older publication does not add references to products imported later.
This workflow needs the application database and ordinary account setup. It has no retailer connection, background purchase detection, automatic publication or outgoing notification to activate.