Each module is a separate part that works within the whole but can also be licensed and deployed on its own. Status is stated honestly — anything still in development is marked.
Orders from every shop in one place, kept current by webhooks.
A local copy of your orders maintained by shop webhooks — always current, no waiting for a nightly import. Filters by market, status and period, with a direct link into the shop admin.
Product records, code registry and the history of every movement.
Products with variants, EAN and HS codes, minimum levels and a movement history with exact origin — a sale, a manual edit, or automatic reconciliation between shops. Prices and identifiers can be written back to the shop.
Packing with scanning, labels and tracking for multiple carriers from one place.
Packing with item verification, bulk label printing, pickup booking and unified tracking. Connected carriers: Packeta, DHL Express, SPS, UPS, Slovenská pošta, GLS, DPD and Česká pošta. Every shipment has one clear status, whatever the carrier calls it. The picker scans with a phone camera — either inside the app, or by using the phone as a wireless scanner for the computer: a QR code appears on the monitor, the phone reads it, and from then on items are ticked off at the shelf. No scanner, no install and no signing in on the phone.
The same goods across several shops share one count.
A sale on one domain reduces availability on the others. This addresses the most common cause of cancelled orders when selling across multiple markets.
A case with status, deadlines and full communication history.
Each case has a status, an owner and a deadline. The customer gets updates from one place, not from three inboxes.
Install MitoOps on your phone and choose what it tells you about.
MitoOps can be added to a phone home screen as an app — no app store, no install. Push notifications tell you when an order is ready to pack, when an automation fails or when stock runs low; you choose what you want to hear about. The picker no longer watches the shop or the inbox — a notification arrives and taps straight through to packing.
Rules of the form "when this happens, do that" over orders and shipments.
A rule has a trigger, conditions and actions. Typically: mark an order shipped once packed, send a reminder after three days without payment, add a note on delivery. Ready-made templates switch on with a single click.
An assistant over your own data, a website chatbot and a copywriter.
Three separately licensable parts over a shared core: an assistant that sees live system data; a chatbot for shop visitors; and a copywriter for product copy and translation. You choose the model and see usage in credits, per module and for the whole billing period.
A partner programme with its own portal, discount codes and statements.
Partners get their own portal on your domain, a performance overview and payout records. Discount codes are created directly in the shop.
Monthly and custom reports from real data, not manual exports.
Reports as a spreadsheet, document or PDF, built from system data and connected traffic and search measurement. The template is configurable.
One place where a product is edited for every market.
Descriptions, prices and identifiers for all connected shops at once, with a record of who changed what. Product reviews are included.
Shop invoices, search and PDF download.
Automatic invoice sync, full-text search across numbers, customers and line items, and PDF download without logging into the shop.
One field that finds an order, a product or an invoice.
Search across the whole system from any screen. Finds records by number, name, code or EAN.
Who sees what — including separating financial data.
Roles with precisely separated access, custom permissions at the level of individual actions, and a record of who did what. Warehouse staff do not see margins.
The system tells you when something breaks — before the customer does.
Alerts for sync failures, a broken carrier connection, low stock or a failed automation.
One layer for custom integrations and AI — a REST API and MCP over the same data.
Your own program, a reporting tool or an AI application reads orders, products, stock, shipments, analytics and reports from every store through one interface: a REST API for your code, the open Model Context Protocol (MCP) for AI applications (Claude.ai verified) and OAuth 2.1 for connecting without copying keys. Reading only with the scopes and store selection you decide; sensitive data such as purchase prices only with explicit permission. Outbound webhooks send your systems a signed event about an order, shipment, stock, invoice or claim. Available from the Start plan.
Not every module differs from what you are used to. In these four the difference is what the system can see — and therefore how much work is left to you.
Usual setup
Usual setup
Usual setup
Usual setup
Usual setup
We compare ourselves with a usual set of tools, not with a named product. Every point on the right can be shown in the application.
Real screens from the system, not illustrations. The data in the screenshots is sample data — names and orders are made up, the system is real.
We connect your first shop with you — 14 days free, no card required. And if you would rather talk first: twenty minutes, no commitment, and we say plainly what MitoOps handles and what it does not.
