Core Principle
Do not deactivate source catalog products just because one website should not show them. Keep the master catalog reusable, then control product visibility at the storefront level for the storefront, buy buttons, marketing feeds, and agentic feeds.
condimentholder.com exposes only condiment-holder-related SKUs.
Three Site Types
Brand Site
Use for the full brand catalog, product education, support content, and multiple ways to buy: BMOS checkout, Amazon, Walmart, eBay, Shopify, distributors, or other channels.
Mini Site
Use for one product, one product family, or one narrow search intent. Curate a small SKU set from a larger source catalog.
Distributor Site
Use for broad catalogs across many brands, suppliers, categories, and content types, with stronger feed, pricing, and visibility operations.
Brand Sites
A brand site should be the product authority hub. It may sell directly through BMOS while also linking to Amazon, Walmart, eBay, Shopify, distributors, or other marketplaces.
- Preserve established product pages and live URLs.
- Map each page to the correct BMOS sellable SKU or child variant SKU.
- Add BMOS
.bmos-buybuttons where direct checkout belongs. - Keep useful product education, SEO content, internal links, and structured data.
- Add new BMOS catalog routes in parallel when replacement is risky.
- Only redirect legacy URLs after content, SKU, image, metadata, and conversion parity are verified.
Mini Sites
A mini site should stay focused. If a larger catalog has 30 products and only 4 belong on the mini site, keep the catalog active but expose only those 4 products for that storefront.
- Show only relevant products in the storefront UI.
- Generate buy buttons only for relevant SKUs.
- Submit only relevant products to Google Merchant Center.
- Expose only relevant products in the agentic feed.
- Hide unrelated products from this storefront instead of deactivating them in the source catalog.
Distributor Sites
A distributor site needs broader operating tools because it may sell across many catalogs, brands, product groups, and landing page patterns.
- Attach multiple catalogs where appropriate.
- Use brand, category, and catalog filters.
- Manage product visibility per sales channel.
- Use pricing and margin overrides.
- Keep Google Merchant Center feeds clean by excluding products without valid landing pages, images, prices, or identifiers.
Buttons vs Full Stores
| Use | Best When |
|---|---|
| Buy Buttons | The site already has strong pages, existing URLs should be preserved, or only selected products need checkout. |
| Full Store Builder | The site needs a catalog grid, product detail pages, search, filtering, and BMOS as the main commerce presentation layer. |
| Hybrid | The site has legacy pages worth preserving but also needs BMOS-powered catalog routes, feeds, and checkout. |
Marketing Feeds
The product page, buy button, and Google Merchant Center feed should be treated as one connected workflow.
- The product exists in the source catalog.
- The storefront decides whether the product belongs on this website.
- The product has a valid HTTPS landing page URL.
- The landing page has a purchase path, such as BMOS buy buttons or marketplace links.
- The Google feed includes only valid products for that storefront.
- The agentic feed exposes only products intended for machine-readable commerce discovery.