RevCent Sites are AI-developed, RevCent-hosted ecommerce deployments for merchants who want maximum flexibility over their storefront, shopping cart, lander, product presentation, and business logic.

A RevCent Site gives you a customer-facing ecommerce experience connected to your RevCent account. Products, Product Groups, Payment Profiles, optional PayPal Accounts, Tracking Domains, sales, and customer activity can work together while the Site remains flexible enough for AI to customize deeply.

RevCent Sites are intentionally different from traditional template builders. Instead of forcing your store into a closed visual builder, RevCent gives you an AI-native path where AI acts as the developer for your ecommerce experience and RevCent hosts the Site for you.

Important: RevCent Sites are an AI-only feature. There is no RevCent web app visual site builder for customizing Sites. AI is the sole intended method for customizing a Site and implementing storefront or business logic.

Why RevCent Sites

RevCent Sites are built for users who want the power of a custom ecommerce site without being boxed into a rigid storefront system.

Traditional site builders and hosted ecommerce platforms can be useful, but they often limit how much you can change. You may be restricted by templates, app marketplaces, checkout rules, hosted themes, closed extension systems, or platform-specific limits that make deep AI customization difficult.

AI-Native Commerce

RevCent Sites take a different approach:

• RevCent hosts the ecommerce Site.
• RevCent connects the Site to your commerce data and checkout configuration.
• AI builds, customizes, and updates the Site.
• You get full flexibility over the customer experience.
• Your Site can evolve as quickly as your products, offers, funnels, and business logic evolve.

The goal is simple: let merchants use AI as the developer instead of forcing the merchant into a one-size-fits-all site builder.

Maximum Flexibility

RevCent Sites are designed for merchants who want more control than a locked-down SaaS builder can provide.

With RevCent Sites, the ecommerce experience can be tailored to the way your business actually sells. A Site can be a focused product lander, a product catalog, a cart, a campaign-specific offer flow, or a custom storefront experience that changes over time.

This is especially useful when:

• you want AI to quickly create and modify your ecommerce experience,
• you want deeper customization than a visual builder allows,
• your products or offers need custom presentation logic,
• your checkout experience needs to match a specific customer journey,
• your brand needs a storefront that does not feel generic,
• you want control over how products, content, and offers work together.

RevCent Sites are not meant to be a walled garden. They are meant to give users and AI the room to build what the business needs.

Beta Feature And Responsibility

RevCent Sites are currently a beta feature.

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.

In practical terms:

More flexibility means more control.
More control means more responsibility.

AI Is The Builder

AI is the intended builder for RevCent Sites.

When you create a Site, collaborators are invited to a GitHub repository for that Site. After accepting the GitHub invite, a collaborator can clone the repository locally and use AI coding tools to customize the ecommerce experience.

What AI Can Customize

The RevCent web app is not where the Site is visually customized. RevCent provides the Site record, commerce connections, hosting, status visibility, and supported configuration. The Site itself is customized through the Site repository using AI.

This workflow allows AI to work directly with the Site source, which means AI can help with:

• storefront design,
• landing pages,
• product pages,
• shopping cart behavior,
• checkout flow presentation,
• offer pages,
• campaign-specific pages,
• copy and messaging,
• product display logic,
• custom business logic,
• testing and refinement.

In plain language:

RevCent hosts the Site.
AI builds and customizes the Site.
The Site repository is where storefront logic changes happen.

Repository Documentation

After the repository is cloned locally, AI should read the documentation included in that repository before making changes. The repository documentation contains the detailed development, customization, and testing guidance for that specific Site.

The public RevCent Knowledge Base intentionally does not include the full repository-level implementation documentation.

Customization vs Configuration

Site configuration is different from Site code.

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 storefront source code, page templates, cart behavior, checkout business logic, offer logic, design, or custom business logic.

Use the Site repository workflow when you want to change:

• design,
• page layout,
• copy,
• product presentation,
• cart behavior,
• checkout presentation,
• offer flow,
• campaign pages,
• theme behavior,
• custom storefront logic,
• custom business rules.

Do not look for a RevCent web app drag-and-drop builder for these changes. The RevCent web app is not the customization surface for Sites.

How Sites Fit In RevCent

A RevCent Site is not an isolated webpage. It is connected to your RevCent commerce setup.

Commerce Connections

Common Site relationships include:

• Product Group: The catalog source for the Site.
• Products: The sellable items shown or used by the Site.
• Payment Profile: The credit card processing strategy for Site checkout.
• PayPal Account: Optional PayPal checkout support.
• Tracking Domain: Optional custom domain routing for the live Site.
• Campaign: Campaign context associated with Site activity.
• Sales: Purchases created when customers check out through the Site.

Before creating a Site, make sure the Product Group and Payment Profile are the right fit for the ecommerce experience you want AI to build.

Product Metadata For Site Catalogs

Each Product intended for a Site catalog can include Site catalog metadata in the Product’s metadata entries.

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.

Sites vs Shops

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

This distinction is important because these 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-developed 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-developed, RevCent-hosted ecommerce experience
Third Party Shop = external ecommerce store connected to RevCent

Creating And Managing Sites

RevCent Sites are intended to be created and managed through AI-assisted workflows, including the RevCent MCP and supported API operations.

Before Creating A Site

Before creating a Site, you should know:

• the Site name,
• the Product Group that should power the Site catalog,
• whether Products in that Product Group need slug and site_categories metadata for Site catalog organization,
• the Payment Profile that should process credit card payments,
• whether PayPal should be enabled,
• the GitHub collaborators who should be invited to the Site repository.

Collaborators are invited through GitHub. They must accept the GitHub invite before they can access or clone the Site repository.

Dev And Live

RevCent Sites support separate dev and live contexts.

The dev context is used for development, testing, and review. The live context is the customer-facing experience. AI and collaborators should test carefully before treating a change as ready for live customer traffic.

Use returned Site status, deployment status, routing status, events, and logs to understand whether the Site is ready and reachable.

Tracking Domains

A Tracking Domain can be attached to a Site when you want a custom domain to route to the live Site.

Tracking Domains are separate RevCent records. A Tracking Domain must be created and ready before it can route traffic to a Site.

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

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.

Operations And Reference

API And MCP 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 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. Test changes in the dev context.
8. Review checkout, tracking, mobile layout, and custom business logic.
9. Confirm routing before relying on a custom domain.
10. Use Site Events and Site Logs when troubleshooting.
11. Treat deletion as permanent and confirm carefully before deleting a Site.