Skip to content

Catalogue: products, collections, delivery and merchandising

The screens under Catalogue. They share the same patterns as the rest of the admin: a search box and filters on every list, a sticky save bar on every edit page and a typed confirmation for anything that can't be undone.

Products list

Catalogue > Products lists products as a table on desktop and as cards on a phone.

  • Filters. Enabled, Disabled and Issues, beside the search box. Choosing none shows everything. The old addresses for the Disabled, All and No image views still work.
  • Issues lists live products with something that loses a sale or looks broken in the shop, with the count on the tab. See Product issues.
  • Collection. Pick a collection from the Collection box (type to search; it copes with shops that have hundreds) to list only the products in it. The choice shows as a removable chip, "In: Screws", and works together with the search box, the status filters and the sort. Each collection chip on a product row does the same, and a collection's own page has a View products link. The address (?collection=screws) can be bookmarked or shared.
  • Search finds part of a name, URL slug or SKU, including a variant's SKU, so "pozi" finds "Pozi 3.5 x 25mm".
  • Sort by name, price or when it was last changed.
  • Stock is counted from the SKUs that actually hold stock. A product with variants shows the total across its variants, such as "436 in stock across 2 variants". It's red only when every variant has run out, and amber when some variants are out or running low (five or fewer). A product whose stock isn't counted shows "Not tracked" rather than "Out of stock".
  • Collections show as chips with their names. Two are shown, the rest collapse into "+2 more".
  • Find duplicate products is in the ... menu beside New product. It lists products that share a URL slug, with the copies side by side. Keep one and the rest are deleted, after a confirmation.

Product issues

The Issues tab lists live products with something wrong. Chips under the search box narrow it to one kind, and each row says what's wrong; the same label shows on that product's row under any filter, and the product's edit page lists its issues at the top. Disabled products never have issues.

Issue When
No fulfiller The product needs shipping, but an order for it would reach nobody: no fulfiller is set (by assignment or the older fulfilment code), or the one it resolves to is inactive or has no email, Slack channel or portal access. Only checked once the site has fulfiller records.
No price The price is missing or zero, or a variant is priced at zero (a variant with no price of its own sells at the product's). Donations and products where the shopper chooses the amount are exempt.
Variant has no weight The product needs shipping and has a weight, but a live variant weighs nothing. Delivery is worked out from the variant's own weight, so a basket holding only that variant weighs nothing and gets the lightest delivery band, which is often free. A variant that just weighs something different from the product isn't flagged. Give each variant a weight on its edit page.
No image The product has no images.

Products in no collection aren't flagged: shops often link a donation, gift card or ticket product from a page on purpose.

Editing a product

The page title is the product's name, with its status and a View on storefront link. ... holds Delete product, which asks you to type the word delete first. Changes show a save bar at the bottom of the screen (or press Ctrl or Cmd and S). Leaving with unsaved changes warns you.

Tab What's in it
Details Name, URL slug, price and compare-at price, collections and the main collection, the main category (when the site has a merchandising tree; see Category navigation), short and full descriptions, search terms for the shop's own search, whether it's shown in the shop and in the sitemap, and a search engine listing with a live preview and character counts
Settings Product types, SKU, barcodes, whether it needs shipping, how customers get it (collection only or delivery only), ways of paying it refuses (credit cards for a lottery entry, say), weight in grams, who fulfils it, the page template (a stereotype, picked from a list), promotion rank and custom attributes
Taxonomy Structured attributes, when a taxonomy is active
Variants The option types and values, and a table of variants with SKU, price and stock. Add missing combinations never touches variants that exist
Images The product's pictures, with order and remove
Stock Whether stock is counted. Off means always available. On shows the quantity. Also units sold, first and last sold, and how shoppers choose a quantity
Content blocks The blocks on the product page
Checkout link A link that goes straight to checkout

A variant has its own page with the same layout. Anything left blank there is taken from the product.

A product that isn't shown in the shop (disabled) keeps its collections, but it is left out of every collection page, product grid and featured-product block, and out of the product count and page numbers on them. Its own page returns "not found". Turn it back on and it reappears where it was.

Collections

A collection's page shows its name, whether it's visible, how many products are in it and View on storefront. Its settings are grouped as:

  • Basics: name, URL slug and description.
  • Where it sits: the collections it's inside, shown by name, and its position among siblings.
  • Visibility: four switches. Show in shop, Show the products (off shows only sub-collections), Include in the sitemap and Staff only (only signed-in customers with the Staff role can see it and buy what is sold only there; see Staff-only collections).
  • Search engine listing, Page layout and Advanced properties for the rarely used options.

Delivery options

Catalogue > Delivery options shows each option's name, the basket weight it covers (in kg, or "Any weight"), its price (or Free) and when it is shown. On the edit page, weights are entered in grams, the price in pounds, and every setting has a line of help. The code can't be changed after an option is created.

The Delivery promise card makes checkout show the date an order arrives instead of the option's description: turn on Promise a delivery date and give the fewest and most working days in transit (1 and 1 for next day, 2 and 4 for a range) and the days the carrier delivers. For a next-day option, Only when it can go today hides it once today's cut-off has passed (Still show it after the cut-off keeps it, with its later date), and Own cut-off sets an "order by 3pm" time in place of the location's. The cut-off otherwise comes from each location's Sending web orders card (courier collection), and non-working days from Settings › Shipping and labels › Delivery dates. See Delivery promise.

Merchandising trees

New tree can build the tree from the shop's collections (tick Build it from the shop's collections): one category per collection, in the same nesting and order, each showing its collection's products and replacing it. The home page collection is left out. This is the way to move a shop whose categories are its collections onto a tree. On a tree built another way, ... > Match collections by URL name records each category as replacing the collection with the same URL name, where nothing replaces it yet.

Catalogue > Merchandising trees lists the trees with how many nodes each has and when it last changed. The primary tree is marked. Open a tree to see its nodes as an outline, indented by level, with what each node shows products from. Add child adds a node inside another. The Ranking column shows how many products are pinned, boosted or buried on a node; Ranking on a row opens a form to set them (not offered on hand-picked-list and group nodes, which have no query to rank). Searches have their own rules under Search. Deleting a node or a tree asks first, and deleting a tree asks you to type the word delete.

Replaces on a row lists the collections that category has replaced, one URL name per line. When the shop's categories come from the tree, menus and other links to those collections lead to the category instead. A category built from a collection replaces it without being listed. The row shows a Replaces: ... badge.

Not a product home on a row marks a cross-cutting category, such as Stainless Steel Fixings or Waterproof Boots. Products still list there, but a product's breadcrumb never leads to it. The row then shows a Not a product home badge, and Allow as product home lifts the mark.

Everything on these pages can also be done through the REST admin API and by an AI agent over MCP; see Search and Discovery.

Category navigation

The Category Navigation Source setting (under Settings > Collections and listings) chooses where the shop's categories come from:

  • COLLECTIONS (the default): collections and their parent collections. A product's breadcrumb follows its main collection.
  • MERCH_TREE: the primary merchandising tree. A product's breadcrumb is Home, then its home category in the tree, then the product, and links to the /c/... category pages.

A product's home category is its Main category when one is chosen on the product's Details tab and that category is visible. Otherwise it's the deepest visible category the product is in, leaving out those marked Not a product home. If two are equally deep, the one that comes first in the tree wins. A product in no category gets a Home / product breadcrumb. It never falls back to collections, which would bring the old hierarchy back. Tree changes reach product breadcrumbs within a minute.

On the tree, collections stop being a second way to browse:

  • A collection a category has replaced (see Replaces above): its page /collection/... redirects permanently to the category, keeping any query string. Links to it lead straight to the category in menus, the collection menus, category rails, breadcrumbs, share links and Open Graph tags. It leaves the sitemap.
  • The home page collection (the one the landing page URL points at) keeps its page.
  • Any other collection goes by Collections No Category Replaces (unmapped-collection-visibility, same settings group):
    • HIDDEN (the default): its page is "not found", and it's left out of menus, collection menus, category rails, breadcrumbs and the sitemap.
    • NOINDEX: the page stays, kept out of search engines and the sitemap.
    • VISIBLE: the page stays as it is.

Hidden or not, a collection still works as a product set: content blocks that show a collection's products, and categories built from a collection, keep working. A collection that has been deleted but is still listed under a category's Replaces keeps redirecting, so retiring old collections doesn't break their addresses. The collections list shows each collection's status (Replaced by /c/..., Hidden, Not in search engines or Home page), and its edit page explains it.

The featured products content block can show a category's products: set Data Source - Category to the category's address, such as /c/fixings/screws. On a product page (for example from a stereotype, as a "more like this" row) it leaves out the product being viewed and still shows up to its Maximum Number of Products.

Menus refresh as soon as the tree or either setting changes. The setting is explicit, so you can build and check a tree before the shop uses it. Check Replaces covers every collection you link to before switching.

For shops that use Prodigi, the product edit page has a Print on demand card (admins only): map each SKU to a Prodigi product, its options and artwork, with a live comparison of Prodigi's price and the selling price. The product goes to Prodigi once every SKU is mapped. See Print on Demand.

Cost prices

Catalogue > Cost prices (admins and finance only) holds what each product and variant costs you, so margin can be measured and listings ranked for it. Find products by name or SKU and type a cost per unit against each product and variant (a variant left blank uses its product's), then Save changes; or Import a CSV of sku,cost lines with costs like 12.50 (a blank cost clears it). The page says how many were saved and lists any SKUs it didn't recognise.

Cost prices are commercially sensitive. Only admins and finance users can see them or the margin worked out from them; they never reach the shop, the search index, exports, site transfers or AI tools. It's part of Enterprise. See Cost Prices and Margin.

Subscription prices

A subscription option (a variant of a product with the subscriptionProduct type) renews at a recurring price in Stripe. You set and change those prices in Badger; you never need the Stripe dashboard or a price ID.

On the product's page, subscription products have a Subscription prices card above the tabs, with a row for each option:

  • Set a price: enter the amount and how often (monthly, every 3 or 6 months, or yearly) and choose Create price in Stripe. The option's shop price changes to match, because the first payment is taken at checkout at the shop price and Stripe takes the rest.
  • Change price: enter the new amount and choose what happens to people already subscribed:
    • Keep paying what they pay now (the default). Only new subscribers pay the new amount.
    • Move to the new amount at their next renewal. You type move to confirm. Tell your subscribers before it happens: neither Badger nor Stripe emails them.

Stripe prices can't be edited, so Badger makes a new price and archives the old one. Subscribers left on an archived price keep renewing.

Catalogue > Subscription prices lists every recurring price in the shop's Stripe account, which options use each, and how many subscribers it has. Options without a price are listed at the top. Open a price to change it, link it to another option, remove it from one, or archive it (only when no option uses it; type archive to confirm).

Check with Stripe compares your options with Stripe and lists anything wrong: an option with no price, a price missing from Stripe or archived there, a shop price that doesn't match what Stripe charges. Fix automatically recreates missing and archived prices and takes over prices made in the Stripe dashboard. Run it after switching Stripe from test to live mode: test prices don't exist in live mode, and this makes live ones. Prices made in the Stripe dashboard that no option uses are listed too, with a picker to link each to an option.

For regular giving with Gift Aid, give the product both the subscriptionProduct and donationProduct types, set its quantity type to Fixed, and set a price for each tier. See Subscriptions.

If no Stripe account is connected the pages say so and link to the payment settings, rather than failing.