Admin Guide¶
Operational documentation for people who run a Badger Commerce site — store operators, charity administrators and platform staff. It points at the feature docs that matter day-to-day and adds operator-focused guidance on top.
Running a storefront¶
| Task | Where |
|---|---|
| Operate multiple storefronts from one instance | Multi-Tenancy |
| Move catalogue & config between environments | Site Data Transfer |
| Configure payments and saved cards | Payment Processing |
| Sell and redeem gift cards | Gift Cards |
| Reclaim UK Gift Aid on donations | Gift Aid |
| Manage products, variants and collections | Product Catalog Management |
| Check search health, rebuild the index, see what shoppers search for | Search section |
| Tune search, facets and merchandising | Search and Discovery |
| Make searches find the right products (synonyms, "why doesn't X show") | Search Synonyms |
| Give a product extra words to be found by ("coach bolt", "decking screws") | Search section: Search terms |
| Find and change any site setting | Settings |
| Let Claude run the shop with you (products, orders, pages, campaigns) | Connecting Claude |
| Use the dashboard, product list and orders day to day | Dashboard, Products and Orders |
| Put products first or last on a category or a search, send a search to a page, or show a banner on a search | Search Rules: Pins, Redirects, Banners |
| Pick and change the storefront theme | Choosing a Theme |
| Respond to a GDPR Subject Access Request | Subject Access Requests |
| Run reports, bills, gift cards, donations and fundraisers | Finance and Fundraising |
Taking payments in person¶
The Mobile POS turns a phone into a card terminal using Stripe Tap to Pay — for events, pop-ups and counters. The admin guide page covers enabling it per site, granting agents access, and how transactions appear back in the order history.
Configuration¶
Most site behaviour is controlled from Settings (/admin/settings, see Settings), backed by SuperSiteConfigService. Configuration is either site-specific or global, and sensitive values (API keys, tokens) are stored encrypted and excluded from data exports. Feature pages call out the specific config keys they use.