Every morning, someone copies orders into another system. Occasionally stock figures diverge and a customer buys something you no longer have. Then an offer for Shoptet Premium arrives. Will the service solve the problem, or do you primarily need a suitable connection and reliable data?
Shoptet Premium is Shoptet's top solution for large e-shops: from CZK 12,000 a month excluding VAT, up to 100,000 products, a custom design on a blank template, a private REST API and premium support. It makes sense once you can name a specific limitation of the current setup. A better banner or growing revenue alone does not determine the right choice. The required feature, its availability and the work needed to maintain it matter more.
If appearance is your main concern, start with templates versus custom design. This article addresses technical and operational capabilities.
What Premium adds
The official Shoptet Premium offer lists a private REST API, custom-design tools and premium support. On 3 October 2026, the main Shoptet pricing page lists Premium from CZK 12,000 per month excluding VAT and up to 100,000 products. This is a platform starting price, not automatically the full budget for your solution. Confirm the specific scope, implementation, integrations and ongoing maintenance in the quotation.
The private API matters when directly connecting the shop to your own systems. Shoptet describes working with orders, products, customers and stock. That does not mean every idea can be implemented with a single request. Verify the exact operations, available data and interface limitations before deciding.
Custom-design options including the blank template are platform capabilities. Designing, implementing and testing your particular solution are additional work. Ask the quotation to distinguish what is included from separately commissioned work.
Shoptet plans and where their limits end
Before looking at Premium, check whether a higher standard plan is enough. Pricing as of 3 October 2026 (excluding 21% VAT, 10% discount for annual billing):
| Plan | Monthly | Annual billing (per month) | Products | Suits |
|---|---|---|---|---|
Free |
CZK 0 |
CZK 0 |
10 |
Trying the system |
Basic |
CZK 440 |
CZK 396 |
100 |
A small shop starting out |
Business |
CZK 1,490 |
CZK 1,341 |
1,000 |
A typical e-shop |
Profi |
CZK 2,490 |
CZK 2,241 |
5,000 |
A growing e-shop with a larger catalogue |
Enterprise |
CZK 4,690 |
CZK 4,221 |
50,000 |
A large catalogue on a standard template |
Premium |
from CZK 12,000 |
by quotation |
100,000 |
Custom design, private API, sandbox |
The difference between Enterprise and Premium is therefore at least CZK 7,310 a month, over CZK 87,000 a year excluding VAT, before any design or development. According to the developer documentation, a custom design built on the blank template and a private API token are not available on standard plans. Those are the two main things you pay for with Premium.
Signals that Premium is worth considering
Consider Premium when at least two of these apply:
- Your catalogue is approaching 50,000 products, the Enterprise plan limit.
- You need a direct connection to your own ERP, WMS or B2B process that public add-ons and connectors don't cover and that requires the private API.
- Design is a competitive advantage for you and customising the default template with CSS and JavaScript is hitting limits, slowing the site or breaking after updates.
- You pay monthly for add-ons and workarounds an amount comparable to the difference between Enterprise and Premium.
- An outage or process error costs you more than the yearly difference in platform price.
When you don't need Premium
- You need one or two features that an add-on from the Shoptet add-on store or a template customisation solves.
- The problem is content, photos or the purchase journey, not a technical limit. Premium won't photograph a product or write a description.
- The only reason is growing revenue. Revenue alone doesn't define a technical need.
- You want a "nicer e-shop". A distinctive look can be built on a standard plan by customising the template; see templates versus custom design.
Start with "we need the system to…"
"We want warehouse automation" is too broad. A better requirement is: "When dispatch is confirmed in our warehouse, the shop order must update without manual re-entry." Add which system is the source of truth, how often data changes and what must happen when something fails.
Then investigate three routes:
| Route | First check | When to investigate further |
|---|---|---|
| Current settings and targeted edits | Whether content, template or data causes the problem | No new data-access capability is required |
| Existing add-on or connector | Supported operations, updates and support ownership | The vendor can demonstrate your complete scenario |
| Premium and a custom integration | Required API operations, operating design and total quote | Ready-made options are insufficient and the private API supports the requirement |
This is a verification process, not a feature matrix covering all plans. An add-on's name is insufficient: establish whether it can only read orders or also change their status, and how it handles repeated requests.
An example: two shops, different decisions
The first shop wants consistent colours, a better product page and complete dimensions. Start by checking its particular template and content quality. Premium will not photograph products or supply missing attributes by itself.
The second shop uses a bespoke warehouse system with an unusual dispatch approval process. Existing connectors do not cover it. A trial integration and verification of the necessary API operations are worth investigating. The result may support moving to Premium, but only after technical validation and a clear cost comparison.
These are illustrative situations, not stories about my clients. The difference is the requirement: one company needs content and shopping-journey improvements; the other needs a specific operating process.
Worked example: Premium: put the actual problem in the brief
ORIGINAL EXAMPLE · FICTIONAL DATA
| Situation | Concrete need | Verify first |
|---|---|---|
| Unclear catalogue | Clear categories and copy | Content and existing theme |
| Two warehouses | Stock reservation rules | Integration options and limits |
| B2B approval | Order awaits salesperson | Roles and state changes |
| Custom process | Specific order export | API, scope and support |
A higher plan alone cannot fix an unclear offer or poor product data.
Compare a full year of operation
Separate one-off implementation from recurring costs. Analysis, design, development, data transfer and testing belong in the first category. The platform, add-ons, integration infrastructure, monitoring and maintenance belong in the second.
Include your team's work: manual repairs, incident handling and data checks. Value that time using your own records. Do not assume a generic automation promise saves the same number of hours in every shop.
Compare two budgets for the same period and scope. A quote including maintenance is not directly comparable with a launch-only quote. For each projected saving, state the assumption: which manual activity must actually disappear?
Worked example: Higher plan: compare the whole year
ORIGINAL EXAMPLE · FICTIONAL DATA
| Item | Existing solution | Proposed solution |
|---|---|---|
| Licence | 12 months of current plan | 12 months of new quote |
| Integration | Current connection operations | Modified or new connection |
| Transition | No migration | Data, checks, training |
| Support | Existing agreement | Specific response and ownership |
The difference is meaningful only with identical requirements and verified prices.
How the switch to Premium works
You change a standard plan in the admin and, according to Shoptet's help, the change takes effect immediately. Premium, however, is not a plan switch; it is a separate project:
- Analysis and consultation with Shoptet Premium: what you need, which API operations and what scope.
- Design on the blank template and the integration design (source of truth, errors, retries).
- Implementation: template, connection to the ERP or warehouse, custom add-ons, data transfer.
- Testing in the sandbox, including orders, payments, shipping and error states.
- Launch outside peak season, checking redirects from old URLs so the e-shop doesn't lose search rankings (see SEO migration during a redesign).
With me, building an e-shop on Shoptet Premium starts at €8,000 and takes 6-10 weeks. It includes a custom design on the blank template, custom add-ons, a B2B module, language versions, an ERP or WMS connection and 90 days of priority support. You pay the Premium licence to Shoptet separately.
Alternatives to Premium
| Alternative | When to consider it |
|---|---|
| A higher standard plan (Profi, Enterprise) | You only hit the product limit and don't need the private API |
| Add-ons and template customisation | You're missing one or two specific features or design elements |
| Shopify | You sell mainly abroad; see Shoptet vs Shopify vs custom |
| A custom e-shop | Your process is so specific that the platform would only work around it |
What the integration supplier should demonstrate
Transferring one order successfully is a start. Also ask what happens when the other system is unavailable or the same request arrives twice. Agree how errors are traced and who owns them.
Before commissioning, ask:
- Which specific data is read and which is changed?
- Which system is authoritative when values disagree?
- How quickly must a change propagate, and how is delay detected?
- How is a failed transfer repaired or repeated?
- Who maintains the connection when either system changes?
- What is handed over when the relationship ends, and how is access revoked?
Do not order Premium as a substitute for understanding the problem. Write down a concrete scenario and compare feasible routes. Through Shoptet support, we can inspect the current setup and identify what needs a targeted change and what requires technical validation. Then choose the implementation scope.
Frequently asked questions
Does every custom design require Premium?
Wanting a distinctive appearance does not settle the question. Compare the planned design with the changes available in your current template. Premium offers additional tools, but whether you need them depends on the specific solution.
Does Premium include a working connection to our system?
Not automatically. API access enables integration; it does not prove that your connection already exists or covers your workflow. Separate the platform, integration development, testing and maintenance in the quotation.
At what revenue should we switch?
Shoptet sets no fixed revenue threshold. I recommend my Shoptet Premium package to large e-shops with turnover of roughly CZK 1 million a month and above, but technical needs decide: the private API, custom design, catalogue size. A smaller shop with a specific process may need Premium sooner than a larger shop with simple operations.
How much does Shoptet Premium cost?
According to Shoptet's pricing, the Premium licence starts at CZK 12,000 a month excluding VAT and includes up to 100,000 products, the private API, custom design and premium support. Add the one-off implementation (from €8,000 with me) and the running costs of integrations. The exact licence price is set by the Shoptet Premium quotation.
What is the difference between the Enterprise plan and Premium?
Enterprise costs CZK 4,690 a month, covers up to 50,000 products and works with standard templates and public add-ons. Premium starts at CZK 12,000, handles up to 100,000 products and adds a custom design on the blank template, a private REST API, a sandbox and premium support.
How long does the switch to Premium take?
It depends on the scope of design, integrations and how ready your data is. With me, building an e-shop on Shoptet Premium takes 6-10 weeks from the approved brief. Plan the launch outside peak season and account for redirecting old URLs.
Sources
- Shoptet: plan pricing, checked 3 October 2026
- Shoptet Developers: Premium, blank template and private API
- Shoptet Premium: pricing
- Shoptet Premium: API
- Shoptet help: changing your plan (Czech)