Online stores
The storefront,built from your catalogue.
Said plainly first: castomUI builds the storefront, not the till. The catalogue, the category pages, one page per product, the images, the languages and the way it all looks when shared — that is castomUI. The basket, checkout and payment stay in the shop system you already run and connect to.
Where the catalogue lives.
Either in castomUI or where it already is. A dataset on MongoDB or MySQL holds products with a structure you define — name, price, description, images, colour, options, a relation to a category dataset — and records are added through a generated form. Fields can be marked translatable.
If the products already live in a shop database, connect it as an external source instead: MongoDB or MySQL directly or through castomoConnector, or OlgroupPanel for shops run on that panel. Nothing is copied by hand, and the shop stays the one place stock and prices are changed.
One template page,
every product page.
A view decides which fields and records are shown, in which order and with which filters. Connect a page to that view and it becomes a dataset page: one designed template that generates a page for every record. Two hundred products, one page to design.
Set that page's OpenGraph type to product, so a shared product link carries its own name, description and image. Product photographs come from the media library, with ALT text and titles per file and duplicates removed.
For more than one market, translatable fields and cloned pages give each language its own product page. Multilingual websites has the detail.
- 1SourceExisting shop MySQL, via castomoConnector.
- 2ViewProducts in stock, sorted by category, then name.
- 3Dataset pageOne template, a page per record. OpenGraph: product.
- 4Category pagesBlocks drawing filtered lists from the same view.
- ·Buy buttonLinks to the product in the shop's own checkout.
- 5LanguagesEN and DE, translatable name and description.
Catalogue readCheckout stays in the shop
The counter stays where it is.
The window gets a lot better.
Around the catalogue
Everything a storefront needs besides products.
Content pages
Delivery, returns, about the shop, a journal — ordinary pages and blocks in the same template as the catalogue.
SEO per product
Canonical addresses, index rules and META across generated pages, with AI to draft descriptions. See SEO and migration.
Campaigns from data
The mailing plugin drives bulk e-mail campaigns from datasets. See plugins.
Which plan
PRO, €300 a month. Datasets, external data sources and dataset pages are PRO features, and a store needs all three. Team at €500 a seat when several people look after the shop. Compare plans.
Questions
Does castomUI take payments?
No. There is no built-in basket or payment. Checkout happens in the shop system you connect, and the storefront links to it.
Do I have to move my products?
No. Connect the existing MongoDB or MySQL database, directly or through castomoConnector, or an OlgroupPanel shop.
How many product pages can a dataset page make?
One per record the view returns. Filter the view to control which products get pages.
Retail truth: nobody has ever abandoned a basket because the product page was too well organised. They have abandoned plenty because it said "Lorem ipsum" under the price.
Your website next.
Start it today.
Open the editor, describe the website, and publish the first version to a cstmui.com address.
Open castomUI See pricing