Using registries

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

This walkthrough follows one registry end to end: a customer builds it, shares it, guests buy gifts, and the public page keeps the remaining counts honest.

1. Create a registry

Log in and open My Account → Gift Registries. The list shows your existing registries; below it is a Create a new registry form:

Registry name, required (defaults to My gift registry if you somehow submit it blank).
Event type, wedding, baby shower, birthday, housewarming or other.
Event date, optional.

Submit and you land on that registry’s manage view.

2. Add products

Browse to any purchasable product. Under the add-to-cart button is an Add to gift registry control: a dropdown of your registries and an Add to registry button. Pick one and submit. This is a plain form post, no JavaScript, so the page reloads with a confirmation. If you own no registries yet, the control instead links you to My Account → Gift Registries to create one.

Back in the manage view, each item shows its Wanted quantity (editable number field), its Purchased count, and an × remove button. Change the numbers and click Update quantities; setting a quantity to 0 removes that item. Adding the same product again increases its desired quantity rather than duplicating the row.

In the manage view, the Shareable link field holds the registry’s public permalink, click it to select, or use Open. The public page is read-only and excluded from search, so it is only reachable by this link. Guests need no account to view it or buy from it.

4. How guests buy a gift

Each item on the public page shows its image, price and N of M purchased progress, plus an action:

With direct purchase on, Buy this gift adds the item straight to the guest’s cart.
With direct purchase off, or when the item is out of stock or not purchasable, the button reads View product and links to the product page, where the guest can pick variations before buying.

Either way the order records which registry the gift belongs to.

5. How purchase tracking keeps counts right

When the gift order reaches processing or completed, Registry adds the bought quantity to the registry. The public page then:

marks an item whose purchased count meets or exceeds its desired quantity as Fully purchased, and
shows the updated N of M purchased progress on partially-covered items.

Counts come from real, paid orders and each order is counted exactly once, so the page always reflects what is genuinely still needed, two guests won’t unknowingly buy the same gift.

Storefront behaviour notes

The public registry and the My Account area are server-rendered PHP with no JavaScript of their own, every action (add, update, remove, delete) is a real form submit handled on template_redirect before output, so it redirects cleanly and survives scripting being off. The delete button asks for a native confirm() first. The only front-end asset is a stylesheet, enqueued only on pages that actually render a registry, so it adds nothing to other pages.

Styling is built on --registry-* CSS custom properties (accent, gap, radius, border) so you can re-theme from your theme stylesheet without fighting markup. The accent defaults to a warm rose and inherits your theme’s primary colour where one is exposed. A dark-mode palette and prefers-reduced-motion handling are built in; the fulfilled-item ribbon and seal animate in only when motion is allowed.

Configuration, the two settings and storage details.
FAQ, common questions.