FAQ
Can I run multiple fully separated shops for different clients in a single TYPO3 instance?
Can I run multiple fully separated shops for different clients in a single TYPO3 instance?
What does “multi‑client” mean?
Multi‑client (also called multi‑tenant) means you operate several independent shops within one TYPO3 installation. Each shop has its own data, settings, pages, and processes — without affecting the others.
In short: yes, you can run multiple, completely separated shops in one TYPO3 — cleanly and efficiently.
How it works in the TYPO3 Shop
The TYPO3 Shop supports a multi‑client setup by scoping all shop data per site branch. You define a dedicated data container for every site tree. Each branch behaves like its own shop: products, categories, orders, customers, and settings are kept separate.
1 shop per site tree: one page branch → one data container → one fully isolated shop.
What is a “data container” here?
A data container is the storage PID (or set of PIDs) where the shop records live: products, categories, orders, etc. By assigning a distinct container to every site branch, you isolate the data between shops.
Typical setup
- Create a page tree per client (one site per client).
- For every site tree, configure its own data container/storage folder.
- Point the Shop plugins and TypoScript to that container via site configuration.
- Optional: separate domains (e.g., client‑a.example.com, client‑b.example.com) and design variations per site.
Benefits for your business and marketing
- Independence: teams work in their own shop without interfering with others.
- Clean data: products, orders, and customers are scoped to one client.
- Faster workflows: no noise from other assortments or orders.
- Branding freedom: each shop can use its own theme, content and tone.
- Growth ready: add new client shops by adding a new site branch and container.
Best practices
- Keep a strict per‑site configuration for storage PIDs and TypoScript includes.
- Separate media folders per client for neatness and permissions.
- Use consistent content elements and templates to speed up rollouts.
- Plan domains and SSL certificates per site early.
- Define a clear admin model: global admins vs. client‑specific editors.
Getting started
- Create the site branches (one per client).
- Create a storage folder (data container) for each branch.
- Configure the TYPO3 Shop to use the container of the respective branch.
- Add products, categories and settings per shop — all stays separated.
Conclusion
Yes — the TYPO3 Shop is multi‑client capable. Define one data container per site branch and operate multiple shops in parallel, cleanly separated, without teams getting in each other’s way — and each with its own invoice numbering cycle.
More frequently asked questions
- Wie löse ich den Fehler „FPDF error: All fonts must be embedded in PDF/A“ bei der PDF-Erstellung?
- How is VAT calculated? Horizontally or vertically?
- How can I adjust the sorting of variants in the variant filter?
- How does the session behave for logged‑in and non‑logged‑in frontend users?
- Why can products not be added to the shopping basket?
- Why are images missing in the product list?
- Why does the product click counter not work?
- Which PDF files can the shop create?
- Why does my PayPal redirect not work?
- Can I use the TYPO3 Shop as a jeweler and automatically import my jewelry — e.g., from the Opal ERP system?
- Can I run multiple fully separated shops for different clients in a single TYPO3 instance?
- Can I use BMEcat 2005 to import and synchronize my products with the TYPO3 Shop?
- Was ist der Unterschied zwischen Storno und Retoure (Return)?
- Beim Klick auf den Warenkorb wird nichts angezeigt obwohl das Plugin richtig platziert wurde, woran kann es liegen?
- Bei mir werden im Produkt im Backend einige Felder nicht angezeigt, woran liegt es?
- Beim Aufruf von AJAX-Requests via JSON-API kommt nur ein 200 zurück, aber keine JSON-Daten – woran kann das liegen?
- The checkout view doesn't have any country items to select - why?
TYPO3 Shop by coding.ms
An extensive shop for TYPO3 for realizing Webshops, Online-Shops or Payment-Subscriptions, comparable with tt_products, Cart or Aimeos. It includes PayPal, PayPal-Checkout, Klarna, Stripe, Bookmarks, UPS-API, invoice generation, a backend module, compare feature, graduated prices, plus product variants, filters, and tax and shipping logic for practical shop operations.