Direct catalog pages
Present products that belong to The Sevens Horses or are sold through an authorized direct relationship.
Shop Subdomain
Direct product commerce for owned and authorized offers.
This subdomain is reserved for product commerce, managed catalog lines, and direct customer checkout experiences operated by The Sevens Horses.
If an offer belongs to an outside merchant or affiliate platform, the final purchase should occur on that merchant side. Shop is for products sold or formally managed through this business channel.
Catalog Direction
A storefront channel with a cleaner role.
Shop separates direct commerce from the corporate site and from paid-traffic funnel pages, so product journeys can stay focused and easier to expand later.
Structured commerce support
Support managed product launches, bundles, and merchant experiences under a dedicated domain.
Checkout-first UX
Keep product detail, payment, and support logic in one commerce channel instead of mixing it into campaign pages.
Published shop products will appear here once the executive team adds them.
Buyer Route Map
Move shoppers into the right purchase path.
The commerce system gets clearer when the buyer sees one honest route: qualify on offers if the click is still cold, stay on shop for direct commerce, and keep partner checkout visibly outside this cart.
Qualify Before Checkout
If the visitor still needs briefing, trust, or offer context, keep that traffic on the offers surface before showing a cart or payment step.
Direct Commerce Route
Use the shop path for owned products, managed offers, and buyer journeys that should stay inside a TSH-controlled product and checkout experience.
External Merchant Boundary
If the real purchase closes on another merchant, keep that boundary obvious here and send the buyer out cleanly instead of faking an internal checkout.
Commerce Models
Storefront routes this channel is built to handle.
These models keep owned products, executive-managed offers, and external merchant handoffs clearly separated so the shop does not drift into a mixed unclear sales surface.
Direct Catalog
Use this when the product is sold through the TSH storefront path.
Best for owned products, digital kits, and catalog offers that should stay inside the shop request flow.
Price, cart behavior, and fulfillment promise must all agree before publish.
Managed Offer
Use this when the team confirms fit, payment, or delivery manually.
Best for higher-touch bundles, onboarding-heavy offers, or pricing that needs executive handling.
Tell the customer exactly what happens after the request so the page does not feel unfinished.
External Merchant Handoff
Use this when the product page is discovery-only and final checkout happens elsewhere.
Best for approved merchant or partner paths that still need a strong product explanation on the TSH side.
Keep the merchant boundary obvious and never make external checkout feel like an internal payment screen.
Commerce Structure
What this domain is meant to handle.
Shop is the right place for catalog presentation, customer checkout, payment handling, and post-purchase support when the product is directly sold by the business.
Performance-led traffic can still originate elsewhere, but once the offer is a direct product sale, Shop should own the product experience, the checkout flow, and the customer communication path.
This keeps compliance, product pages, and order handling clearer than trying to force every commercial activity into the same public website surface.
Product detail and catalog views
Dedicated product presentation, benefits, pricing, and purchase context.
Payment and order capture
Future-ready space for cart, payment, order confirmation, and customer support flows.
Post-purchase communication
Order follow-up, support routing, and product-specific service handling under the same domain.
Storefront Planning
Preparing a direct product sales channel?
Use this path for owned products, managed catalog launches, or direct-commerce architecture that should not be mixed into campaign landing pages.