When you outgrow Shoptet — and when to keep it

A paid order that cannot ship

Consider an illustrative order from a Slovak store. This is a model scenario, not a record of a particular Planet Ayurveda order.

A customer buys three products for €89.90 on Shoptet and pays through Comgate. The store confirms the order, transfers it to POHODA and prepares shipment data for Packeta. During packing, the warehouse discovers that one item is missing. The last unit sold through another channel before stock information caught up.

Someone checks the order in Shoptet, the stock and document in POHODA, the payment in Comgate and the shipment in Packeta. After agreeing a replacement, partial shipment or partial refund with the customer, they must update the affected systems and verify the result.

Each application may have done its own job correctly. What is missing is a shared view of the exception and ownership of its resolution. Replacing the storefront will not automatically close that gap.

At Planet Ayurveda we operate Shoptet in Slovakia and Czechia alongside our own Medusa-based solution in Poland and Hungary. That gives us a view of both the store and the systems handling an order after checkout.

When I would keep Shoptet

If orders reach dispatch reliably and the team spends little time on manual intervention, start with a specific weak point. It could be an unreliable integration, a configuration issue or unnecessary copying of data.

Migration affects the catalogue, URLs, search visibility, analytics, payments and everyday work. It needs a clear justification: a limitation you cannot reasonably remove and a benefit that outweighs implementation and ongoing operating costs.

Seven signs to investigate behind the store

Count one point for each recurring issue and record the time spent dealing with it. This is a discussion aid, not a validated assessment. One serious failure can matter more than several minor inconveniences.

1. Every market adds exceptions

Currencies, carriers, payment methods and selling entities can differ. When the correct process depends on what an experienced colleague remembers about each market, important rules are no longer captured by the store alone.

2. Finding an order means opening several tools

Shoptet, POHODA, Comgate and Packeta can all be appropriate choices. The problem begins when switching between them is the only way to discover where an order stopped. Tool count alone says little about operational quality.

3. The real status sits in messages

The customer changed an address, the warehouse is waiting for stock and accounting is fixing a document. The order status does not explain those open tasks. The team needs the agreements and pending actions as well.

4. People check every automatic transfer

Daily comparisons of orders, invoices and shipments may reveal a silent integration failure. Investigate error alerts, outcome checks and safe retries. Connecting applications is only one part of supervising a process.

5. Every delayed order requires an investigation

The reason for a delay, the next action and its owner should be visible together. A few minutes of searching can consume substantial time when repeated across many exceptions.

6. An experienced colleague cannot be replaced

If only one person knows when to hold a shipment or verify a payment, absence exposes the weakness. Document the rules before deciding which ones to automate.

7. Nobody owns the resolution

A payment provider knows the payment and a carrier knows the shipment. Your team still needs someone to bring the exception to a verified close. Relying on whoever happens to notice it is fragile.

What to do with the result

0–2 points: Address individual weak spots first. A better integration or alert may be enough. Prioritise serious failures even if the total is low.

3–4 points: Keep an exception log for two weeks. Record what happened, how it was discovered, who handled it, which systems they opened and how they verified completion. Use this evidence to distinguish platform limits from integration and process issues.

5–7 points: Investigate shared order management across systems. Shoptet may still be a good place for customers to buy. Decide whether an OMS is justified by the workload, impact and implementation costs, rather than the score alone.

What Myslio OMS does today

OMS means Order Management System. We already use Myslio OMS in Planet Ayurveda operations to centralise orders from multiple stores. We are gradually moving additional processes into it from separate administration interfaces and connected systems.

Our aim is to preserve the context of an order and progressively take responsibility for steps that currently require manual checking. The storefront, accounting system and carrier continue to serve their respective purposes.

Exception detection, alerts and follow-up workflows describe the direction of development. The model scenario above does not imply that the OMS already resolves every variation automatically. Coverage depends on the specific integration and process.

When a different store platform makes sense

A demonstrable limitation in checkout, product modelling, B2B sales, pricing or business rules can justify a new foundation. First check what configuration and available extensions can solve.

Our Medusa-based stores in Poland and Hungary give us direct experience of the alternative, including development, integration and operating responsibilities. They do not make migration the right answer for every business.

If most effort is spent after checkout, a new customer-facing site may leave the same manual checks for payments, stock, invoices and shipping behind it.

Trace one difficult order

Pick an exception from last week and answer:

1. Where did the order originate and which systems received it?
2. Where did it first depart from the normal process?
3. How was the problem discovered and who took ownership?
4. What required a manual decision or update?
5. How did you verify that it was resolved?

Before discussing migration, identify where time, information or responsibility is being lost.

Show me the order journey

Send an anonymised account of the expected outcome, what happened, the systems involved and the eventual resolution. Leave out customer names, addresses and other personal information.

We can examine the gap and whether it has anything to do with Shoptet.

Show us a problem order →