WT Catalog

WT (Wijntransport B.V.) supplies wine and beer to restaurants, hotels, shops and wholesalers. This
plugin puts that assortment on your own WordPress website: a wine listing, a beer listing and a
page per product, filled straight from WT’s catalog every time a visitor looks at them. Nothing is
copied into your site and kept there, so a product that changes at WT changes on your website too.

Who it is for. WT customers who have a WordPress website. You need an API URL and an API key
from WT; without them the plugin has nothing to show. Ask your WT contact for both. There is no
free or public catalog behind this plugin.

What a visitor gets. A listing of your assortment with a picture, a name, the alcohol
percentage, the colour, the bottle size and the case quantity for every product. Down the side (or
behind a “Filters” button on a phone) are filters for country, colour, bottle size and producer,
each showing how many products are behind it, plus a search box. Ticking a filter narrows the list
and the other filters’ counts immediately. The filters need JavaScript in the visitor’s browser;
the search box is an ordinary form and works without it. Clicking a product opens its own page
with the producer’s own name for it, the region it comes from, its rating, badges such as ORGANIC
or NEW, the tasting note, the food pairing, and the specifications split into “Characteristics”
and “Bottle”.

No prices, anywhere. WT’s prices are per customer and are not part of what this plugin shows.
No price is displayed, and none is stored on your site.

What you control. Two things, both under WT in the WordPress admin menu:

• Which products are hidden. See “Blocked products” below.
• Which slice of the catalog each listing shows: everything WT sells, or only what you have
  actually bought in the last 3, 6 or 12 months, or ever. Wine and beer are set separately, so you
  can show every wine but only the beers you stock.

External services

This plugin depends on one external service: the WT catalog API. It is the source of every
product, picture, filter and piece of text the plugin displays. Your site has no catalog of its
own.

Where it connects. To the address you enter yourself under WT → Settings (“API URL”). The
plugin ships no address of its own; you receive the URL and the key together from WT.

What is sent, and when. Every request carries your API key, so the service knows which
customer’s assortment to answer with. A request is made when a visitor opens a listing or a
product page and the plugin has no fresh copy of it, and once a day to rebuild the product index.
Along with the key the plugin sends only what the visitor asked for: the page number, the search
term they typed, the filters they ticked (country, colour, bottle size, producer), which drink the
page is for, your purchase-history setting, and the identifier of the product being viewed. No
personal data of your visitors is sent — no name, e-mail address, IP address, cookie or user
account is forwarded, and the plugin sets no cookies of its own.

What is stored on your site. One settings row holding your API URL, your API key, your two
purchase-history choices and your block list; a small index of the catalog (identifier, base
number, link, name, vintage, drink, thumbnail) used to build product addresses and the XML
sitemap; and short-lived cached copies of listing and product responses. No price is ever
requested for display, shown or stored. Deleting the plugin from Plugins → Installed Plugins
removes all of it, including your API key.

Terms and privacy. The catalog is a service of WT for its own customers, and its use is
governed by your customer agreement with WT. Nothing about your website’s visitors is sent to it —
see above — so no visitor-facing privacy policy applies to the plugin’s requests. Company site:
https://wt.group/

The screens, one by one

The wine listing (screenshot 1) is an ordinary WordPress page to which you gave the page
template “[WT] Wine listing”. The plugin fills it: search box, the filter panel, the result count,
the grid of products and the pager. Every filter choice is in the page’s own address, so a
filtered list can be bookmarked, shared and linked to. Filter labels — country names, colour names
— come from WT in the language attached to your key, which is why they may read Dutch on an
English site.

The beer listing is the same page, with the page template “[WT] Beer listing” instead. It
shows beer only, has its own purchase-history setting and its own search. You only need it if you
sell beer.

The product page (screenshot 2) lives under whichever listing the visitor came from —
/wines/product/1015-chat-maucoil-chateauneuf-du-pape-rouge-bio/. You do not create these pages;
the plugin answers those addresses itself. Text blocks that WT has not filled in are left out
rather than shown empty, and the specification rows differ per drink: closure type, vintage and
colour are wine rows, degrees Plato is a beer row.

On a phone (screenshot 3) the filter panel folds into a “Filters” button above the results,
with the number of active filters on it. Opening it shows the same filter sections; each opens on
a tap.

WT → Settings (screenshot 4) is where the API URL and the API key go, and where you choose the
purchase-history filter per listing. Underneath is a status panel: which URL is in use and whether
a key is saved, how many products are in the index and when it was last built, which SEO plugin is
providing meta tags and the sitemap, which pages are acting as your wine and beer listings, and
how many products you have blocked. Two buttons sit below it: Rebuild product index now, which
fetches the whole catalog again, and Flush cache, which throws away the pages the plugin is
remembering. Saving a key checks it against the catalog before storing it, and tells you if it was
refused; a refused key never replaces the saved one.

WT → Blocked products (screenshot 5) is a search box. Type a product name or a base number,
and every match comes back with its base number, name, drink and vintages. “Block” hides that
product from the listing, from its own product page and from the sitemap — every vintage of it,
because blocking works on the base number. The “Blocked” tab lists what you have hidden, and
unblocks it again.