Jan Mikoláš
Sales flow
From product to fulfilled order
- Product, variant, price, and currency
- Availability and inventory reservation
- Order, payment, and delivery
- External states, return, or claim
Back to skills
Domain expertise
E-commerce and marketplaces
E-commerce is not just a catalogue and a cart. I develop solutions over the long term where products, pricing, inventory, orders, multiple sales channels, and daily operations meet.
The connection between commerce, data, and operations matters most.
In an online-store solution, product variants, prices, currencies, inventory availability, and the order process are interconnected. A change in one part often affects many others — administration, warehouse, delivery, accounting, or a marketplace.
I have experience developing and evolving e-commerce solutions over the long term, including a multistore platform, inventory connections, and marketplace integrations. This means I look beyond an individual feature to the full lifecycle of an order and its data.
Not familiar with a term? Read a concise explanation in the glossary.
What an e-commerce solution needs
From a product catalogue to a fulfilled order.
-
Catalogue
Product variants, prices, and currencies
Product information needs to work across administration, the online store, and external channels. I therefore address variants, pricing, currencies, and data quality so that change is controlled and traceable. -
Inventory and logistics
Availability, reservations, and the real stock state
Inventory data affects what can be promised to a customer. Reservations, order changes, fulfilment, and synchronisation must be handled so availability does not diverge between systems. -
Order
A process that does not end when an order is placed
The order process includes payment, delivery, status changes, customer communication, and subsequent claims and returns. Each step needs traceability, as does matching states from external services. -
Multistore and marketplaces
Multiple stores and sales channels from one foundation
Multistore architecture combines central administration with different domains, languages, currencies, catalogues, or store-specific rules. Marketplaces add further contracts, states, and data synchronisations. -
Long-term operations
Problems that appear only in production
A long-running online store deals with incomplete data, delayed synchronisations, changing external-service rules, and historical orders. Alongside new features, monitoring, exception repair, and safe data changes matter.
Flows that need to stay connected
E-commerce is a system of connected processes.
Design cannot focus only on the storefront. The catalogue, inventory, orders, administration, and external channels have their own responsibilities, yet they need to share a consistent state and predictable interface.
I choose the concrete system split according to company size, number of stores, order volume, and integration scope. Clear ownership of data and states matters more than the number of services.
Multistore flow
Central administration and different channels
- One administration
- Domains, languages, and currencies
- Rules for a particular store
- Marketplaces and integration synchronisations
Relevant e-commerce experience
A multistore platform and a large online store
Amiatex — multistore platform
I co-founded and developed a platform for managing multiple online stores, domains, language versions, and currencies from one administration, including marketplace integrations.
Sportisimo — e-commerce development
Experience with daily development in a larger e-commerce environment where catalogues, availability, orders, and long-term application operations meet.
Areas I work in
E-commerce as a connected whole
- E-commerce
- Marketplaces
- Multistore
- Warehousing & logistics
- REST API
- RabbitMQ
- PostgreSQL
- Elasticsearch
Need to evolve an online store and its operational foundation?
I can help with a new feature, integration, or long-term evolution of an e-commerce solution — from data design to reliable operations.