Incep Digital
GuidesIncep Platform owner guide
Get started4 min read

What kind of site is this?

Incep Platform started as a store builder, and it still builds excellent stores. It is no longer only that. Selling, bookings and the blog are each optional capabilities, so the same platform runs a plain business website with no cart anywhere in it.

Which capabilities are on decides what you see. Half the admin disappears on a site that does not sell, and that is deliberate rather than a fault.

The three capabilities

/admin/settingssaved to Store.featureFlags
Ecommerce
Products, cart, checkout, orders, payments, shipping and tax. On by default.
Bookings
Services sold as appointments rather than shipped goods. Paid bookings still run through the same cart and order pipeline.
Blog
Posts, categories and comments, under a URL prefix you choose.

Every existing deployment behaves exactly as it always has. A store with no stored preference is treated as an ecommerce store, so nothing changed underneath anyone.

Ecommerce, bookings and the blog are flags. Switching one off removes its admin areas and its storefront routes.

What switching ecommerce off actually does

/admin/settings
The admin
Catalog, orders, customers, payments, shipping and tax leave the sidebar, and their routes refuse to load rather than sitting there half working.
The storefront
Shop, product, cart, checkout, wishlist and compare routes return a not found page. The header drops its cart and wishlist icons.
The page builder
Blocks that only make sense for a store are hidden from the library, so you cannot place a product grid on a site with no products.
AI setup
Business briefs skip catalog sections, leave /shop out of the navigation, and do not build a product page template.
Note: Bookings and ecommerce overlap. Services are products underneath, and a paid booking flows through the same cart, checkout and order pipeline, so Products, Orders, Customers and Payments stay available whenever bookings are on even if ecommerce is off.

Choosing at setup

The provisioning wizard asks whether to enable ecommerce when a new deployment is created, and seeds a business navigation and homepage rather than a shop when the answer is no.

Tip: You can change your mind later. Turning ecommerce on brings the catalog and checkout back with your data intact.