In this article · 13 sections
- What is an enterprise ecommerce platform
- SaaS, self-hosted or headless: which model fits a large business
- When a business outgrows a standard platform
- 10 criteria for choosing an ecommerce platform for large businesses
- Can one admin run several stores and countries
- How ERP, PIM and B2B connect to the store
- How to migrate a large catalog without downtime
- API, headless and an AI assistant: what the IT team gets
- Security and access control
- Who is accountable when something breaks
- How much does an enterprise ecommerce platform cost
- How to choose a platform for a large online business: 6 steps
- Frequently asked questions
In short: an enterprise ecommerce platform is ecommerce software that handles a large catalog, several markets and live connections to ERP, PIM and B2B systems without manual retyping. In CloudCart, a 51,000-product catalog updated every night runs on the same platform as a 300-product store. Above all plans sits Unicorn, with terms negotiated for your business, a dedicated team and contractual limits.
This guide is for owners and managers of online stores with revenue in the hundreds of thousands of euros, several markets or business customers, who need to know whether their current platform will hold for the next 3 years. It is written for companies selling in or from Bulgaria and for EU sellers shipping across borders. It compares requirements with solutions, criterion by criterion. The examples and limits come from CloudCart, the Bulgarian ecommerce platform, and are taken from the pricing page and the Enterprise page.
What is an enterprise ecommerce platform
An enterprise ecommerce platform is online selling software built for a business where the store is one part of a larger system: warehouse, accounting, suppliers, physical shops, distributors and several countries. What separates it from a standard platform is everything around the storefront: where the data comes from, how many systems exchange it and how many people work in the admin.
The English-language rankings for "enterprise ecommerce platform" are mostly vendor lists written for the US and Western European markets, with quote-only pricing. For a business selling in Bulgaria, Romania and Greece, the criteria are different: the local couriers and payment methods in each market, Ordinance N-18 (Bulgaria's rules for recording and reporting online sales to the NRA, the National Revenue Agency), the inventory and accounting software Bulgarian companies actually use, and a catalog in each market's language. The reporting steps are in the guide to Ordinance N-18 for an online store.
SaaS, self-hosted or headless: which model fits a large business
A large online business has three platform models to choose from: SaaS, where the provider runs the servers and updates; self-hosted open source such as WooCommerce or Magento Open Source, where that is your team's job; and headless, where the storefront is separate code on top of the platform's API. CloudCart is SaaS and supports headless storefronts with Nitrogen on the same catalog and admin.
| Question | Self-hosted (open source) | SaaS (CloudCart) | Headless on CloudCart (Nitrogen) |
|---|---|---|---|
| Who maintains hosting and updates | Your team or an agency | CloudCart | CloudCart for the platform, you or your developers for the storefront |
| Security and SSL | Set up and monitored separately | Cloudflare in front of every store, SSL renews automatically | The same for the platform |
| Design | Any theme or custom code | Themes and an editor in the admin | Fully custom, up to 10 storefronts per store |
| Catalog, orders, ERP | Plugins, each updated separately | Apps in the admin, REST and GraphQL APIs | The same admin and catalog, Storefront GraphQL API |
| When it fits | You have an in-house team for servers and security | Your team focuses on sales, not servers | The brand needs its own storefront experience |
The cost of self-hosting does not show in the licence. It sits in the hours spent on updates and plugin fixes, so compare platforms by total cost over 3 years rather than by the monthly fee. How a custom storefront is built on Nitrogen is shown in the guide to designing a storefront with Nitrogen and AI.
When a business outgrows a standard platform
A business outgrows its platform when the manual work around the store grows faster than sales. The signals are specific and visible in the team's daily routine.
| Daily signal | What it means | What solves it |
|---|---|---|
| Price lists and products arrive as PDF and Excel files and are retyped | The catalog depends on one person | Scheduled import from API, XML, Excel and PDF |
| Stock is entered twice: in the warehouse system and on the site | You sell goods you do not have | A connection to the ERP or inventory software |
| Business customers order by email, Viber and phone | Wholesale orders are retyped by hand | B2B login with group prices or a B2B portal |
| Every new country is a project from scratch | Growth abroad is slow and expensive | Multistore with a shared catalog and stock |
| Descriptions are copied from brand websites | Weak SEO and incomplete product data | A PIM system for product data |
| Decisions are made by gut feeling | No report built on real data | Analysis of orders, repeat purchases and slow-moving stock |
The CloudCart team follows these six signals through a large client's processes, and every manual step gets a solution, a deadline and a price, as described on the Enterprise page.
10 criteria for choosing an ecommerce platform for large businesses
A platform for a large business is judged on 10 criteria: catalog scale, markets and languages, ERP, PIM, B2B, migration, API, security, accountability when something breaks, and price. The table shows what to check and how CloudCart covers it.
| Criterion | What to check | How CloudCart handles it |
|---|---|---|
| Catalog scale | Product and import limits, nightly updates | CC Master has unlimited products; in a tire store, 51,000 products update every night |
| Markets and languages | A storefront per country, currency, couriers, hreflang | Multistore, Multilang and Stores Sync |
| ERP and warehouse | A ready connection to your software, or an API | 16 built-in ERP and inventory connections, a custom adapter, a sync dashboard |
| Product data (PIM) | Where descriptions and attributes come from, who approves them | PIM systems built as a project: every value has a source, a person approves it |
| B2B | Group prices, a private catalog, payment by invoice, approval | Customer groups, Private Store, a B2B portal built as a project |
| Migration | Moving without stopping sales, 1:1 URLs, 301 redirects | Migration by the team, the old store sells until the switch |
| API and development | REST, GraphQL, webhooks, rate limits | REST API v2, Admin and Storefront GraphQL, webhooks, Dev MCP |
| Security | Role-based permissions, two-factor login, backups | Permissions by section, 2FA, Cloudflare, daily backups (paid package) |
| Accountability | One named contact, a visible work plan | A dedicated account manager from CC Pro up, a client portal |
| Price | A public plan price, commission on sales | Public prices up to CC Master, 0% commission, Unicorn by agreement |
Important: if you sell to consumers in other EU countries, the platform also has to support your VAT setup. Since July 1, 2021, once your cross-border B2C sales of goods across the EU exceed €10,000 a year (excluding VAT), VAT is charged at the rate of the buyer's country, and you can declare it through the EU's One Stop Shop (OSS) instead of registering in each country. A separate store per market, each with its own VAT rate, keeps this simple.
For a broader comparison of platforms used in Bulgaria, see the guide to choosing an ecommerce platform in Bulgaria.
Can one admin run several stores and countries
In CloudCart, every country is a separate store with its own admin, and you switch between them in one click, without another password. The catalog and stock are shared, while prices, couriers, payment methods, currency and VAT rate are set per market. The model is described on the multistore and languages page. The step-by-step setup is in the guide to a multilingual store and multistore.
A separate store per market is a deliberate choice. A customer in Romania expects Sameday or FAN Courier and prices in lei, and a customer in Greece expects ACS or a BOX NOW parcel locker. A single store with a language switcher does not cover these differences. In Bulgaria the store works with Econt and Speedy (DPD Bulgaria), the main Bulgarian couriers, with office pickup and cash on delivery.
Two apps in the admin handle the shared work between stores:
- Multilang (Apps → Multilang) copies products from the main store to the new market's store and machine-translates them. In each language store's settings you choose which fields are translated, a price factor and rounding, and whether each new product transfers automatically or after approval. Sync runs one way: from the main store to the language stores. Product copying and AI translation for a language version are in CC Master, according to the pricing table.
- Stores Sync (Apps → Stores Sync) matches quantities only between stores, by SKU or barcode. An order, a manual adjustment or a return in one store changes the quantity in all connected stores. Prices and orders stay with each market.
Important: Stores Sync has no master store. Every store in the group sends its changes to all the others, and when two changes happen at the same time, the last one wins. A full sync can be run once every 24 hours. If your ERP supplies stock by warehouse, that goes through the API with PUT /api/v2/store-quantity.
Multilang generates the hreflang tags between language stores automatically, and the main store gets x-default. This tells Google which store serves which language, following Google Search Central's guidance on localized versions.
How ERP, PIM and B2B connect to the store
The ERP is the source of truth for stock and prices, the PIM for descriptions and attributes, and the B2B setup decides who sees which prices. Each connects to the store differently, and you choose based on who orders and where the data comes from.
| System | What it sends to the store | How it connects in CloudCart |
|---|---|---|
| ERP and warehouse | Stock, prices, documents; receives orders and customers | An app in the admin (Microinvest, Micro.bg, SelMatic, Gensoft, Colibri and others), a custom adapter or the REST API |
| PIM | Descriptions, attributes, images from manufacturers | A PIM system built by the team as a project; every value comes with a source and is approved by a person |
| B2B in the store | Group prices, quantity tiers, a private catalog | Customer groups (Customers → Customer groups) and Apps → Private Store |
| B2B portal | An employee orders, the manager approves, the order goes into the ERP | A dedicated B2B platform built as a project, with dashboards for distributors by country |
An ERP connection does not require you to change your software. Microinvest, Micro.bg, SelMatic, Gensoft and Colibri are Bulgarian accounting and inventory programs; together with the others, 16 ERP and inventory systems are built in as apps, and if yours is not on the list, the team writes an adapter for it. In custom projects, the dashboard shows every sync and warns you when one fails. Details are on the page an online store connected to inventory software, ERP and POS.
PIM (product information management) software comes in when the catalog runs to tens of thousands of items from many manufacturers. In one CloudCart team project, 48 manufacturer files with 453,364 items were reduced to 16,846 items from 18 brand websites, every value with its source.
B2B starts with customer groups. The number of groups depends on the plan: 3 in Starter Pack, 5 in CC Pro and 100 in CC Master. Private Store locks the catalog behind a login, so only approved companies see the prices. The main ecommerce models, B2B among them, are compared in the guide to types of ecommerce and business models.
How to migrate a large catalog without downtime
A large catalog moves without downtime when the new store is built alongside the old one, and the old store keeps selling until the domain switches. URLs move 1:1 with 301 redirects, and the ERP connection and language versions are part of the same plan.
- Inventory the old store. Products, variants, customers, orders and every URL Google knows.
- Move the data. From an export (CSV, XML), through an API or from the old site. Orders are moved and kept separately.
- Map the URLs. Every old URL gets a 301 redirect to the new one. In one team project, 13,418 URLs were moved in 30 minutes, and 9 domains were merged into 1 with 4,801 redirects.
- Compare the counts. Before the switch, products, customers, orders and URLs are compared between the old and the new store. Launch happens only when the difference is zero.
- Switch and monitor. The domain moves at an agreed time, then Search Console, 404 errors and rankings are watched during the first weeks.
Google describes the same order in its guide to a site move with URL changes. A worked example with every step is the WooCommerce migration without losing SEO.
API, headless and an AI assistant: what the IT team gets
The IT team of a large store gets three APIs in CloudCart, webhooks, a command line and tools that AI assistants understand. The documentation is public at cloudcart.dev and on the developers page, and the limits are listed per plan.
| Tool | What it is for | Limit or condition |
|---|---|---|
| REST API v2 | Orders, products, customers, stock by warehouse | Starter Pack 50, CC Pro 100, CC Master 150 requests per minute, up to 800 by agreement; Baby Pack has no API access |
| Admin GraphQL API | Bulk operations on the catalog and URLs | Access with a PAT (personal access token) with selected permissions |
| Storefront GraphQL API and Nitrogen | A storefront fully to your design on the same catalog | Up to 10 storefronts, deploy from GitHub or the command line |
| Webhooks | Your system receives an event on a new order, customer or product | For example order.created |
| Dev MCP and AI Toolkit | Claude Code and Cursor write the integration against the real schema | A plugin for Claude Code, query validation |
API keys (Settings → Api keys) switch off with a toggle without being deleted, and the rate limit is shared by all keys of a store. PAT tokens (Settings → PAT tokens) are created only by the owner, with selected permissions, an expiry date and allowed IP addresses.
Why a large store gains from an AI assistant
An AI assistant connects the admin, the API and reporting in one sentence in plain English. Instead of dozens of clicks, the manager writes "Here is the new price list. Update prices by product code and show me which codes are missing", and the assistant makes the change and shows the result. The analyst can work with a read-only PAT token, and the catalog assistant with permissions on products only.
A read-only token is enough for every report in this table:
| Metric | Why it matters for a large store | What to ask the assistant |
|---|---|---|
| Revenue and order count by market | Shows which store in the multistore is growing | "Compare revenue and orders by store for the last 30 days against the previous 30." |
| Share of returning customers | A repeat purchase is the cheapest sale | "How many of September's customers had ordered before? Give me a list of those who stopped." |
| Stock with no sales | Cash frozen in the warehouse | "Which in-stock products have had no sale in 90 days? Sort them by value." |
| Low stock on best sellers | Lost sales on what sells most | "Which of the top 100 products by sales are below 5 units?" |
The difference from an admin report is the next step. The assistant goes past the table: with a token that has product permissions, it proposes the change, shows the list and makes it after your "yes".
Security and access control
Security for a large store rests on three things: who sees what in the admin, how people log in and how data comes back after a mistake. CloudCart covers all three:
- Permissions by section. Each moderator sees only the sections the owner has granted. The number of admin accounts is 1, 3, 5 and 10 by plan.
- Two-factor authentication. A code from an app (Google Authenticator, 1Password, Authy, Microsoft Authenticator) or by email at login and for sensitive actions, such as creating a moderator or restoring from a backup.
- Cloudflare and SSL. Attack protection in front of every store and a certificate that renews automatically for every domain.
- Backups. Daily copies of the whole database with full or partial restore. This is a paid package, priced by how long the copies are kept.
Domains and certificates are explained in the guide to domain, SSL and security for an online store.
Who is accountable when something breaks
In CloudCart a named person is accountable: from the CC Pro plan up, your dedicated account manager knows your store, follows the results and knows whom to bring in from the team. CC Pro and CC Master include 3 and 5 meetings with the technical team, according to the pricing table, and Unicorn has a dedicated team for the project.
Work on a large project is visible in a client portal: every topic, task and decision with a name and date, and the phases with deadlines. Reporting is every two weeks, and every release goes through testing. On every plan you can write to support@cloudcart.com.
Important: when you evaluate a platform, ask how a failed ERP sync shows up. A silent failure (stock that stops updating without anyone noticing) costs more than a visible problem, so the dashboard and alerts matter more than promises.
How much does an enterprise ecommerce platform cost
With CloudCart you pay for two things: the platform plan at a public price, and the team's project work, with a proposal in stages and a price and deadline for each stage. Plan prices are from the pricing page, billed annually, excluding VAT.
| Plan | Price per month | Six-month revenue up to | Products | Admin accounts | API requests/min |
|---|---|---|---|---|---|
| CC Pro | €83 | €249,999 | 7,500 | 5 | 100 |
| CC Master | €249 | €499,999 | Unlimited | 10 | 150 |
| Unicorn | Terms negotiated for your business | Above CC Master | By contract | By contract | Up to 800 by agreement |
Compare the price with commissions. A 1% commission on €1 million in annual sales is €10,000 a year on top of the plan. CloudCart charges no commission on sales on any plan.
How to choose a platform for a large online business: 6 steps
- Map the process from supplier to accounting. Write down every manual step: who retypes what, and where people wait.
- Check your systems against the list. ERP, inventory software, POS, couriers and payment methods in every market. Anything missing needs an adapter or the API.
- Give your IT team the documentation. The APIs, limits and schema should be public before you decide.
- Ask for a migration plan. With a URL map, a count comparison and a switch time.
- Check who is accountable. A person's name, a visible plan and how a failed sync shows up.
- Calculate the cost over 3 years. Plan, project, commissions and add-ons such as backups.
To see the admin, multistore and the AI assistant in action, open a store and go through the steps yourself.
Frequently asked questions
An enterprise ecommerce platform is ecommerce software for a large business that handles a big catalog, several markets and connections to ERP, PIM and B2B systems. What sets it apart from a standard platform is the systems around the storefront and the team that maintains them.
A business outgrows its platform when manual work grows faster than sales. Typical signals are retyped price lists, stock entered twice, wholesale orders over Viber or email, and every new market built from scratch.
In CloudCart every country is a separate store with its own admin, and you switch between them in one click without another password. Multilang copies and translates the catalog, and Stores Sync matches quantities between stores by SKU or barcode.
The new store is built alongside the old one, which keeps selling until the domain switches. URLs move 1:1 with 301 redirects, and launch happens only when the record counts match. In CloudCart, migration by the team is €0 with a 24-month contract through Dec 31, 2026.
The ERP sends stock and prices and receives orders, the PIM sends descriptions and attributes, and B2B decides who sees which prices. In CloudCart, 16 ERP and inventory systems are built in as apps, and PIM systems and B2B portals are built as projects.
Yes. With Nitrogen, the storefront is built fully to your design on the Storefront GraphQL API, while the catalog, orders and admin stay in CloudCart. One store can have up to 10 Nitrogen storefronts, deployed from GitHub or the command line.
In CloudCart, CC Master is €249/month billed annually, excluding VAT, for six-month revenue up to €499,999. Above it is Unicorn, with terms negotiated for your business, and the team's work is priced per project, with a price for each stage. There is no commission on sales.
Sources
- One Stop Shop (OSS)vat-one-stop-shop.ec.europa.eu
- Google Search Central's guidance on localized versionsdevelopers.google.com
- site move with URL changesdevelopers.google.com
