RevCent Sites are AI-created, Next.js-based, RevCent-hosted ecommerce Sites for merchants who want source-level control over their storefront theme and business logic without having to build and operate their own hosting infrastructure.

A RevCent Site starts as a prepared ecommerce codebase, not a blank project. RevCent issues a Site repository that already contains the RevCent custom ecommerce framework, local development support, local testing patterns, visitor tracking, abstracted session handling, catalog plumbing, cart behavior, checkout support, Sale processing, upsell support, browser/server security patterns, and the structure needed for dev and live deployment.

The intended workflow is simple: connect your AI to the RevCent MCP, tell AI what Site you want, let RevCent issue the repository and hosting setup, clone the repo locally, have AI customize the Site theme inside the prepared Next.js codebase, test the changes, and push updates back to the assigned GitHub repository. RevCent handles deployment, environment setup, serverless hosting, and routing.

Important: RevCent Sites are an AI-only feature. There is no RevCent web app visual site builder for customizing Sites. AI is the intended developer for customizing the Site theme, views, branding, customer experience, and business logic.

Technical Overview

RevCent Sites are built for merchants who want the flexibility of a custom ecommerce application, the speed of AI development, and the convenience of RevCent-managed hosting.

Instead of using a closed hosted theme system, a RevCent Site gives the merchant and their AI access to a real GitHub repository. The repository contains a prepared Next.js ecommerce application designed for RevCent commerce. AI can read the code, read the repo documentation, customize the Site theme, test locally, and push changes.

AI And MCP Workflow

RevCent Sites are designed around the RevCent MCP.

In practice, the user connects their AI client to the RevCent MCP and asks AI to create or manage a Site. The AI can use supported RevCent Site operations to create the Site record, inspect Site status, review Site details, attach a Tracking Domain, check Site events, check Site logs, and help guide the user through the repository workflow.

A typical creation prompt might be:

Create a RevCent Site for my skincare brand.
Use this Product Group as the catalog.
Use this Payment Profile for credit card checkout.
Invite these GitHub collaborators.
I want a full shopping cart with search, coupons, checkout, and a post-purchase upsell.

The AI can translate that request into the supported RevCent operations, then explain the next steps once the Site and repository are issued.

Prepared Next.js Ecommerce Repository

Each RevCent Site is issued with a prepared Next.js ecommerce codebase.

This matters because AI is not starting from an empty application. The base repo already contains the RevCent ecommerce framework and the expected patterns for a working commerce Site. AI can inspect the existing structure, follow the included documentation, and customize the Site theme with context.

The prepared codebase is designed to include the plumbing AI needs for:

• local development,
• local testing,
• dev and live Site deployment structure,
• theme layer for merchant-specific customization,
• SEO and optimization foundation,
• automatic sitemap support,
• SEO-ready product catalog support,
• RevCent catalog usage,
• Product Group powered storefronts,
• product detail pages,
• product slugs and category organization,
• cart and checkout flows,
• coupon and discount presentation,
• credit card checkout through RevCent Payment Profiles,
• optional PayPal checkout when configured,
• visitor tracking,
• abstracted session handling,
• returning customer handling and saved customer information where available,
• Sale creation and processing through RevCent,
• order bumps,
• post-purchase upsells,
• product-line metadata for attribution,
• confirmation pages,
• customer-facing policies, FAQs, content pages, and supporting routes.

The repository documentation is intentionally more detailed than this Knowledge Base page. After cloning a Site repository, AI should read the repo documentation before editing. The repo docs explain the exact local commands, file structure, testing expectations, framework conventions, theme conventions, and implementation details for that Site.

Theme-Based Customization

RevCent Sites use a theme-based customization model.

This is an important distinction: full source control does not mean AI needs to rewrite the entire codebase. The core RevCent ecommerce framework is already in place. AI is expected to work primarily in the theme layer, where the merchant’s branding, views, customer experience, offer logic, and business-specific behavior live.

In plain language:

Core framework = RevCent ecommerce plumbing
Theme = merchant-specific storefront, flow, branding, views, and business logic

The framework provides the reusable ecommerce foundation. The theme uses and extends that foundation.

Themes are not only visual skins. A theme can define the actual customer experience:

• storefront views,
• product and category pages,
• landing pages,
• cart presentation,
• checkout presentation,
• offer and upsell pages,
• campaign-specific pages,
• content pages,
• route structure,
• server-side business logic extension points,
• custom session data usage,
• customer journey behavior.

This gives AI a clean methodology. AI can build almost any merchant-specific ecommerce experience while still relying on the framework for the hard plumbing that should already be solved: visitor sessions, cart state, checkout, Sale processing, security, environment variables, and RevCent API operations.

The result is full control without chaos. The user and AI have source access, but the normal customization path is to create and evolve a theme on top of the RevCent framework, not to replace the framework itself.

Source Control, Deployment, And Hosting

RevCent Sites use GitHub for source control.

When a Site is created, collaborators are invited through GitHub. A collaborator must accept the GitHub invitation before they can access or clone the Site repository.

After access is accepted, the workflow is familiar to developers and AI coding tools:

1. Clone the assigned Site repository locally.
2. Ask AI to read the repository documentation.
3. Describe the storefront, cart, lander, funnel, checkout, or business logic change.
4. Let AI customize the Site theme inside the Next.js codebase.
5. Run the local development server and local tests described by the repo.
6. Review the experience in dev.
7. Commit the changes.
8. Push the changes to the assigned GitHub repository.

This gives merchants full source control over their ecommerce Site while still letting RevCent manage the hosting layer.

RevCent-Managed Deployment And Hosting

RevCent handles the deployment, environment setup, and hosting for Sites.

The merchant does not need to create an AWS account, provision Lambda functions, configure hosting infrastructure, manage environment variables, operate servers, or maintain a deployment platform. The user’s job is to define the ecommerce experience, review the AI’s work, test the Site, and push approved changes to the assigned repository.

From the user’s perspective:

User describes the Site to AI
AI uses RevCent MCP to create the Site
RevCent issues the Site repository
Collaborator clones and edits locally
AI customizes the Site theme and business logic
User tests and pushes changes
RevCent deploys, hosts, and routes the Site

That division is the core value of RevCent Sites: full control over the customer-facing ecommerce code without forcing the merchant to become a hosting or infrastructure team.

Initial deployment and normal Site updates typically take around 3-5 minutes. That speed is a major part of the RevCent Sites workflow: merchants can ask AI to make a change, test it, push it, and see updates deploy quickly enough to support rapid innovation, landing-page iteration, offer testing, SEO tuning, and ongoing customer-experience refinement.

Serverless Architecture

RevCent Sites are hosted on a RevCent-managed serverless architecture.

At a product level, the architecture is:

Customer browser
    ->
RevCent-hosted Site route or custom domain
    ->
Next.js ecommerce Site on Lambda-backed hosting
    ->
RevCent commerce services

Lambda-backed hosting gives RevCent Sites a serverless runtime model. The Site framework includes abstracted state and session handling, so AI can build commerce flows without forcing the merchant to design low-level session infrastructure.

The important part for merchants is that RevCent manages this environment. Users and AI do not need to manually assemble the hosting stack. They get the benefit of a custom ecommerce codebase, dev and live deployment structure, and serverless hosting without having to operate the infrastructure themselves.

Optimization And SEO

Optimization and SEO are built into the RevCent Sites foundation.

The prepared Next.js framework is designed so Sites can achieve extremely strong page speed and SEO results without the merchant needing to assemble a performance stack from scratch. The core framework gives AI a fast, search-friendly foundation for storefronts, product pages, landing pages, content pages, funnels, and checkout flows.

For merchants, this matters because performance and SEO should not be afterthoughts. A custom ecommerce Site should load quickly, be easy for search engines to understand, and support clean page structure, metadata, internal linking, product content, campaign pages, and mobile-first customer journeys.

RevCent Sites are designed to score near-perfectly in SEO and page speed tests when the merchant theme, content, images, and custom business logic are implemented carefully. AI can then focus on fine tuning the theme, copy, structure, and customer experience on top of a framework that already takes speed and SEO seriously.

In other words, the framework is not only a place to put pages. It is a ready, optimized ecommerce engine that gives AI the core pieces needed to create a fast and search-friendly storefront.

Automatic Sitemap Support

RevCent Sites include automatic sitemap support.

The framework can expose sitemap entries for the active theme and catalog-driven pages, helping search engines discover the important public URLs for the Site. A theme can define the public pages it wants indexed, while the framework handles the sitemap structure and canonical Site context.

This is useful for:

• home pages,
• landing pages,
• campaign pages,
• content pages,
• category pages,
• product pages,
• other theme-defined public routes.

AI can then customize the theme’s public routes and sitemap behavior without needing to build sitemap infrastructure from scratch.

SEO-Ready Product Catalog

The RevCent Sites framework includes an SEO-ready product catalog foundation.

Products from the selected Product Group can automatically become part of the Site catalog. Product slugs, category paths, product detail pages, product cards, category pages, search views, and internal links can all work together to create a catalog that is useful for both customers and search engines.

The slug and site_categories metadata values help the Site build cleaner product URLs and category organization. AI can use that catalog foundation to create product pages, collection pages, category landing pages, comparison pages, and supporting content that improves the Site’s search footprint.

This means a merchant does not have to ask AI to invent an ecommerce catalog engine. The product catalog foundation is already part of the RevCent framework. AI can focus on catalog presentation, SEO copy, internal linking, product education, page layout, and business-specific catalog logic.

Metadata, Robots, And Search-Friendly Routes

The framework includes patterns for route metadata, canonical URLs, robots behavior, and public route organization.

That lets AI work in the theme layer to decide which pages should be public, how they should be titled, what descriptions they should use, which offer pages should be indexed, and which checkout or post-purchase pages should stay out of search results.

For ecommerce SEO, that separation matters. Product, category, content, and campaign pages should be discoverable. Checkout, confirmation, and sensitive funnel steps generally should not be treated like public SEO pages.

Combined with typical 3-5 minute deployments, this makes RevCent Sites useful for rapid SEO iteration:

• improving product page titles and descriptions,
• adding supporting content pages,
• refining landing-page headings,
• adjusting internal links,
• improving mobile layout,
• optimizing offer pages,
• testing stronger calls to action,
• tuning theme assets and images,
• improving checkout and funnel page clarity.

Visitor Sessions, Attribution, And State

RevCent Sites include full abstracted visitor session handling inside the prepared ecommerce framework.

This is important because ecommerce is not a single static page view. A visitor might arrive from an ad, browse products, search the catalog, add items to cart, apply a coupon, begin checkout, accept or decline an upsell, leave, return later, and continue the journey. RevCent Sites include the session foundation needed to support that kind of experience without forcing AI or the merchant to invent visitor, cart, and checkout state from scratch.

Automatic Visitor And Cart State

The framework abstracts the common state problems that ecommerce Sites need to solve.

This can include:

• visitor tracking,
• cart state,
• checkout state,
• coupon or offer context,
• upsell and order-bump flow state,
• confirmation context,
• returning customer context,
• saved customer information where available and appropriate.

The goal is that AI can focus on the merchant’s customer experience instead of rebuilding session mechanics. A merchant can ask AI to create a cart, funnel, lander, quiz, guided product selector, or returning-customer flow, and AI can work with the RevCent framework’s existing session patterns.

Session Attribution

Sessions also help connect visitor activity to the broader customer journey.

RevCent Sites are designed so visitor tracking and session attribution can help preserve useful context as a customer moves through the Site. This can help the Site and RevCent commerce records understand the path from visit to cart to checkout to Sale, including the offer, page, campaign, or funnel step that mattered.

For merchants, this is powerful because the Site can be customized around real ecommerce journeys:

• paid traffic landing on a campaign-specific page,
• visitors searching or browsing categories before purchase,
• cart sessions that continue into checkout,
• checkout sessions that continue into upsells,
• returning customers who come back with useful saved context,
• AI analysis that can later reason about which flows, offers, or pages are producing results.

Returning Customers And Saved Information

The session foundation can support returning-customer experiences where RevCent can safely make saved customer information available to the Site.

AI can build flows that feel more intelligent for repeat visitors and existing customers. For example, a Site can be customized to recognize returning customer context, simplify repeat purchase flows, continue a checkout journey, or present offers that make sense based on the customer and session state available to the framework.

This lets merchants build a more personalized ecommerce experience without asking AI to design a customer/session system from scratch.

Custom Session Data

RevCent Sites can also be extended with custom data attached to sessions.

Custom session data gives AI and merchants a flexible place to carry business-specific context through the customer journey. Examples include:

• campaign source,
• landing page variant,
• quiz answers,
• selected bundle options,
• offer step,
• audience segment,
• influencer or affiliate context,
• shipping or fulfillment hints,
• customer preference selections,
• internal funnel identifiers.

Custom session data should be used for ecommerce context, attribution, and business logic. It should not be used to store payment credentials, API credentials, secrets, full card data, or other sensitive information. The prepared framework already includes secure credential and payment handling patterns; custom session data should extend the customer journey, not bypass those boundaries.

The session foundation is powerful in itself: it abstracts visitor state, cart state, attribution, returning customer context, and custom session data so AI can build richer commerce experiences faster.

Built-In Security And Credential Handling

The RevCent Sites framework includes browser and server security patterns that are already built into the prepared codebase.

This includes protections and conventions for:

• browser-side security,
• server-side request handling,
• card testing prevention,
• DDoS prevention,
• secure card information handling,
• avoiding sensitive information in logs,
• using the RevCent API for primary commerce operations,
• applying environment variables automatically,
• keeping sensitive credentials out of the Site codebase.

The Site codebase should not store API credentials, payment credentials, secrets, or sensitive customer/payment information directly in source code. RevCent applies the required environment configuration for the hosted Site so AI and collaborators can focus on storefront and business logic instead of hardcoding secrets.

The framework is also designed so sensitive data is not logged by default. AI should preserve those conventions when extending the Site. Custom business logic can be added, but it should continue to use the RevCent API and the existing framework boundaries for checkout, Sale processing, session handling, and secure commerce behavior.

In plain language: the session foundation is already there, and it is extensible for custom business logic. AI can build custom ecommerce logic on top of the RevCent framework without needing to recreate core browser security, server security, credential handling, or payment-safety patterns from scratch.

Dev And Live Environments

RevCent Sites are structured around dev and live contexts.

The dev context is where changes should be tested and reviewed. Dev environments are issued a unique staging URL so users, collaborators, and AI can view deployed changes before merging or promoting those changes to live.

The live context is the customer-facing version of the Site. Live environments can be connected to a DNS Tracking Domain configured in RevCent. Once attached, RevCent automatically routes that Tracking Domain to the current live deployment.

AI and collaborators should use the Site repository’s documentation, local testing workflow, and dev staging URL before treating any change as ready for live traffic. RevCent handles the deployment mechanics and live routing, but the merchant is still responsible for reviewing the customer experience, checkout behavior, pricing, offer logic, tracking, legal content, and business logic before sending customers to the live Site.

Creating A Site With AI

RevCent Sites are created through AI-assisted workflows, usually through an MCP-capable AI client connected to RevCent MCP.

The user does not need to fill out a traditional visual builder. Instead, the user describes the Site they want, gives AI the necessary RevCent context, and lets AI create the Site using supported RevCent operations.

Requirements Overview

Before creating a Site, the user should have the core commerce pieces ready in RevCent.

Common requirements include:

• RevCent MCP access: Your AI needs access to the RevCent MCP so it can create and manage the Site.
• Site name: A clear internal name for the Site.
• Site description: A short description of the Site’s purpose.
• Product Group: The Product Group that should power the Site catalog or offer.
• Products: Products should be configured with the correct price, status, shipping, subscription, trial, or bundle behavior.
• Payment Profile: The Payment Profile used for credit card checkout.
• PayPal Account: Optional, only when PayPal checkout should be available.
• GitHub collaborators: The GitHub users who should be invited to the Site repository.
• Custom domain or Tracking Domain: Optional, used when the live Site should be reachable from a branded domain. Live custom domains use a RevCent Tracking Domain and the DNS A record IP provided by RevCent.

Product data matters because the Site framework uses RevCent commerce data. A clean Product Group and well-structured Products make it easier for AI to build a strong storefront.

Product Metadata For Site Catalogs

Products used in a RevCent Site catalog can include Site-specific metadata to help the storefront organize URLs and categories.

Recommended Product metadata names:

• slug: A clear, URL-friendly Product slug used by the Site for product URLs, links, and product detail paths.
• site_categories: A JSON string array of slash-delimited Site category paths used for navigation, filters, grouping, or landing-page organization.

Example:

[
  {
    "name": "slug",
    "value": "organic-coffee-beans"
  },
  {
    "name": "site_categories",
    "value": "[\"coffee/beans\",\"subscriptions\"]"
  }
]

Use slug values that are unique within the Site catalog. Use site_categories as a JSON array string. Each array item is a slash-delimited category path, such as coffee/beans or apparel/mens/shirts. A Product can belong to more than one category path, nested categories are represented with slashes, and paths with more than three levels are ignored.

Creation And Repository Workflow

Tell AI What To Create

The best way to start is to describe the business outcome clearly.

For a full shopping cart:

Create a RevCent Site for our supplement brand.
Use the Main Store Product Group.
Use our primary credit card Payment Profile and enable PayPal.
Invite these GitHub collaborators.
Build a full shopping cart with search, categories, coupons, checkout, and an upsell after purchase.

For a single product lander:

Create a RevCent Site for one product.
Use this Product Group.
Use this Payment Profile.
Make the Site a focused mobile-first product lander with testimonials, FAQs, offer details, checkout, and one optional order bump.

AI can then use the RevCent MCP to create the Site, confirm which collaborators were invited, and tell the user what to do next.

Repository Issuance

After the Site is created, RevCent issues the Site repository.

That repository contains the customization surface for the Site. The RevCent web app stores supported Site configuration and status, but the storefront theme itself is changed through the repository.

The issued repo is prepared for AI-assisted development. It contains the Next.js app, RevCent ecommerce framework, theme layer, local development guidance, testing guidance, and the conventions AI should follow when changing the storefront.

Collaborator Invitations

Collaborators are invited through GitHub.

The collaborator must accept the GitHub invite before they can access the repository. If a collaborator cannot clone the repo, the first thing to check is whether the GitHub invitation has been accepted.

After the invite is accepted, the collaborator can clone the repo locally and begin working with AI.

Clone Locally And Let AI Read The Repo

Once the repository is cloned locally, AI should read the repository documentation before making changes.

This is important because the Knowledge Base intentionally does not duplicate every implementation detail. The repo documentation explains the actual local commands, architecture rules, test workflow, framework conventions, and Site-specific guidance.

A good first prompt after cloning is:

Read the documentation in this repository.
Explain the local development workflow.
Then help me customize the Site for this offer.

AI should understand the prepared codebase and theme methodology before editing. That gives the user better results and reduces the chance of unnecessary framework rewrites.

Edit, Test, Commit, And Push

After AI understands the repo, the user can describe changes in natural language.

Examples:

Add a product comparison section to the home page.
Create a category page for coffee subscriptions.
Add an order bump to checkout for the travel case.
Change the upsell page to use a stronger value proposition.
Improve mobile checkout spacing.
Add an FAQ page and link it from the footer.

AI can then customize the theme layer, update components, add pages, adjust copy, change styling, and implement business logic that uses the Site framework.

The expected workflow is:

1. Make the change locally.
2. Run the local development server.
3. Run the relevant tests.
4. Commit the change.
5. Push to the assigned GitHub repository.
6. Let RevCent handle the deployment and hosting process.
7. Review the deployed change on the dev staging URL before merging or promoting it to live.

Configuration And Domains

RevCent Sites separate Site configuration from Site source code, and the Site source separates the core framework from the merchant theme.

Configuration describes which RevCent records the Site uses. Source code describes how the customer-facing ecommerce experience works.

Site Configuration

Supported Site configuration includes details such as:

• Site name,
• Site description,
• Product Group,
• Payment Profile,
• optional PayPal Account,
• collaborator list.

The EditSite operation changes supported RevCent Site configuration only. It does not edit the actual Site code.

Use Site configuration changes when you need to update the RevCent records attached to the Site. Use the GitHub repository and theme layer when you need to change design, pages, copy, layout, cart behavior, checkout presentation, upsell logic, tracking behavior, custom business rules, or storefront code.

Custom Domains

A RevCent Site can use a custom domain through a Tracking Domain.

A custom domain is useful when the merchant wants the live Site to be reachable from a branded domain rather than only a RevCent-hosted route.

The high-level process is:

1. Create or prepare the Tracking Domain in RevCent.
2. Add the A record IP provided by RevCent to the domain registrar DNS.
3. Attach the Tracking Domain to the Site.
4. Confirm the live Site is reachable at the intended domain.

RevCent handles the Site hosting and routing association. Once the Tracking Domain is attached, RevCent automatically routes the domain to the live deployment. The merchant is responsible for owning the domain and adding the provided A record IP at their domain registrar.

Removing a Tracking Domain from a Site removes the custom domain routing association. It does not delete the Site.

Operations, Events, And Deletion

Events And Logs

Site Events and Site Logs help users and AI understand what happened with a Site.

Use Site Events to review activity such as Site creation, deployment updates, catalog updates, routing changes, and status activity.

Use Site Logs for focused troubleshooting of a specific Site branch over a specific date range.

There is no single-event or single-log retrieval operation for Sites. Events and Logs are retrieved as paginated lists.

Deleting A Site

Deleting a Site is irreversible.

When a Site is deleted, Site data, routing, and content associated with that Site are removed. If DNS is still pointed at the deleted Site, that DNS will no longer reach a working RevCent Site until the DNS records are changed or removed.

If you only want to disconnect a custom domain, remove the Tracking Domain from the Site instead of deleting the Site.

Ecommerce Capabilities

RevCent Sites are designed for custom ecommerce experiences that AI can build and evolve over time.

The prepared Next.js codebase gives AI a commerce-aware foundation and a theme layer for merchant-specific customization. The merchant can then ask AI to create a complete storefront, a focused lander, a product funnel, a custom checkout flow, or a highly specific customer journey.

Full Shopping Cart Experience

A RevCent Site can become a complete shopping cart experience because the framework already includes the core ecommerce engine.

AI can help create a Site that already includes:

• home page,
• product catalog,
• category navigation,
• site search,
• product detail pages,
• cart page or cart drawer,
• coupon and discount presentation,
• shipping and tax expectations where applicable,
• checkout flow presentation,
• credit card checkout through the selected Payment Profile,
• optional PayPal checkout,
• order confirmation,
• customer trust content,
• policy pages,
• FAQs,
• supporting SEO content.

This is useful for merchants who want a real custom ecommerce store without being trapped inside a template builder or plugin marketplace.

Product Landers And Campaign Pages

A RevCent Site can also be a focused landing page for one product, one Product Group, one offer, or one campaign.

This is useful for:

• paid ad campaigns,
• influencer campaigns,
• product launches,
• seasonal offers,
• direct-response sales pages,
• lead-in pages for checkout,
• focused offer pages with minimal navigation.

The user can tell AI what kind of page to create, what benefits to emphasize, what objections to answer, what proof to include, and how the call to action should lead into checkout. AI can then implement the page inside the Site theme and the user can test it locally before pushing.

Upsells, Order Bumps, And Funnels

RevCent Sites are especially useful for upsells because AI can work directly in the theme layer on top of the ecommerce framework instead of being limited to a generic upsell plugin.

A Site can support flows such as:

• an order bump during checkout,
• a post-purchase upsell after the initial order,
• chained upsell offers,
• downsells after a declined upsell,
• subscription upgrades,
• bundle add-ons,
• accessory offers,
• replenishment offers,
• warranty or support package offers,
• paid-traffic funnels with offer-specific pages.

Example prompt:

Add a checkout order bump for the travel case.
After purchase, show a one-time upsell for the refill bundle.
If the customer declines, show a lower-priced sample pack.
Keep the page mobile-first and make the offer feel like part of the brand.

AI can use the Site theme and framework to create the pages, components, offer logic, and checkout flow. Accepted upsells and order bumps can also be marked in RevCent commerce data so reporting, events, automations, and later AI analysis can understand which Products were part of the funnel.

Search, Sessions, And Custom Logic

Search, Catalogs, And Product Organization

RevCent Sites can use Product Groups and Product metadata to organize the customer-facing catalog.

AI can create category pages, collection pages, product cards, search views, featured product sections, product comparison pages, and product detail pages that match the merchant’s brand and offer strategy.

The slug and site_categories Product metadata values help AI and the Site framework present Products with stable URLs and useful category paths.

Session-Powered Customer Journeys

The prepared Site codebase includes patterns for visitor tracking, abstracted session handling, checkout state, returning customers, saved customer information, custom session data, and commerce behavior.

This lets AI build a Site that is not just a static page. The Site can guide a visitor through product discovery, cart selection, checkout, upsells, confirmation, and follow-up activity while staying connected to RevCent commerce records.

The session layer is part of the RevCent framework. Merchants get custom ecommerce behavior without having to design their own visitor, attribution, cart, or checkout state infrastructure.

Custom Business Logic

Because a RevCent Site has a source-controlled theme layer, AI can implement custom business logic that would be difficult or impossible inside a closed visual builder.

Examples include:

• showing different page content by campaign,
• changing product presentation by category,
• building custom offer flows,
• creating a quiz or guided shopping experience,
• building specialized bundle selection,
• changing upsell logic based on the initial cart,
• adding custom validation,
• changing checkout messaging by offer type,
• building internal helper pages for campaign launches.

The merchant should still review and test all custom logic carefully before sending live traffic.

Why This Is Different

RevCent Sites are built for merchants who want the upside of custom development without the burden of managing a hosting platform.

Full Control Without Hosting Setup

Traditional custom ecommerce development often requires the merchant to coordinate developers, hosting, deployment, environment variables, server provisioning, database setup, monitoring, and ongoing maintenance.

Traditional SaaS builders solve the hosting problem, but they often limit the merchant’s control.

RevCent Sites are designed to sit between those worlds:

• AI can customize a real ecommerce theme backed by a prepared framework.
• The merchant gets GitHub source control.
• The Site can be customized beyond template settings.
• RevCent provides the prepared ecommerce framework and theme methodology.
• RevCent handles environment setup, deployment, and hosting.
• The Site runs on RevCent-managed serverless infrastructure.
• The framework includes session handling, secure API usage, browser/server security patterns, and credential protection.

For merchants searching for a custom ecommerce solution, AI-built storefront, hosted Next.js ecommerce site, custom shopping cart, AI landing page, or ecommerce site with full source control and theme-based customization, RevCent Sites are designed for exactly that workflow.

AI Instead Of A Visual Builder

RevCent Sites do not use a visual drag-and-drop Site builder inside the RevCent web app.

That is intentional. Modern AI can understand and modify real application code. Giving AI a prepared ecommerce repository with a theme layer creates far more flexibility than forcing every merchant into the same hosted page editor.

The merchant describes what they want. AI customizes the Site theme. RevCent hosts it.

AI is the theme and business logic developer.
GitHub is the source control layer.
RevCent is the commerce and hosting platform.

Review And Launch Responsibility

Because Sites provide full AI-driven flexibility, users and merchants are responsible for developing, testing, reviewing, and approving their Site changes before relying on them for live customer traffic.

This responsibility includes testing:

• product presentation,
• mobile and desktop layout,
• cart behavior,
• checkout flows,
• payment methods,
• shipping and tax expectations,
• tracking,
• legal and compliance pages,
• custom business logic,
• any changes made by AI or collaborators.

Full access is intentional. RevCent gives users and AI meaningful control over the Site because modern AI tools can create, modify, and maintain ecommerce experiences at the source level. That flexibility is powerful, but it should be handled carefully.

Sites vs Shops

RevCent Sites are separate from Shops, Third Party Shops, User Shops, and Site Shops.

This distinction is important because the names can sound similar, but they describe different RevCent concepts.

A WooCommerce store connected to RevCent is a Third Party Shop. It is not a RevCent Site.

An AI-created ecommerce deployment hosted by RevCent is a RevCent Site. It is not a Shop or Third Party Shop.

Use this simple distinction:

RevCent Site = AI-created, RevCent-hosted ecommerce experience
Third Party Shop = external ecommerce store connected to RevCent

Operations And Reference

Developers and AI clients can use the RevCent API Sites section and the RevCent Sites MCP overview for supported Site operations.

Common Site Operations

Common Site operations include:

• CreateSite
• GetSites
• GetSite
• EditSite
• DeleteSite
• AddTrackingDomainToSite
• RemoveTrackingDomainFromSite
• GetSiteEvents
• GetSiteLogs

Best Practices

Before sending live traffic to a RevCent Site:

1. Confirm the Product Group contains the correct Products.
2. Add or review Product metadata entries with name = slug and name = site_categories when the Site catalog needs stable product URLs or category organization.
3. Confirm the Payment Profile is ready for the intended payment flow.
4. Confirm PayPal only when PayPal checkout should be available.
5. Make sure collaborators have accepted GitHub invites.
6. Have AI read the repository documentation after cloning the Site repository.
7. Run the local development and testing workflow described by the repo.
8. Review checkout, tracking, mobile layout, the dev staging URL, custom domains, upsells, and custom business logic.
9. Push approved changes to the assigned GitHub repository.
10. Use Site Events and Site Logs when troubleshooting.
11. Treat deletion as permanent and confirm carefully before deleting a Site.