Context
Mespi.sk is a multi-market commerce environment where we designed and continue to develop the public buying journey and internal workflows for products, orders, warehouse work, pricing, marketing and content.
Project case study
In-house project
Mespi.sk
A multi-market store with its own product, warehouse, pricing, marketing and operational workflows.
Delivery preview
The project on desktop and mobile
Keep commercial and internal data usable across markets.
The parts cannot behave as isolated exports. Product changes affect the store, feeds and marketing, while orders affect warehouse and downstream processing.
What was designed or delivered
Connected areas across the store and internal team
Multi-market storefront and catalogue
Categories, products, variants, media, availability, pricing and localised content follow shared rules across market versions.
Product imports and data quality
Supplier imports map identifiers, descriptions, attributes, categories, prices and media. Batch state and faulty inputs remain inspectable.
Feeds, advertising and reporting
Product exports for comparison and advertising channels are checked for required fields, category mapping and delivery readiness.
Pricing intelligence
Competitor price tracking separates run state, results and margin boundaries so pricing decisions remain controlled.
Orders and warehouse
Internal tools support receiving and dispatch, warehouse locations, EAN or SKU scanning, picking, labels and change history.
Content and automation
Editorial and operations tools connect briefs, content production, review, publishing, scheduled runs, live logs and safe retries.
Verified scope
Verified scope
- Publicly accessible store
- Product, warehouse and pricing workflows confirmed by internal project material
- Marketing and editorial tools separated from the customer website
Important decisions
Important decisions
- Separate the public buying journey from internal permissions.
- Preserve stable identifiers through imports and downstream processing.
- Expose automation state, output and a controlled retry path.
What this experience contributes to Torevo work
This experience transfers to Shopify projects where the store depends on warehouse work, feeds, pricing data or internal workspaces.
Current state
Actively developed project. The profile was last reviewed against the public website and internal material.
Last updated
Related services
Areas where the experience is transferable.
Projects
Working with a similar commerce or data system?
Send a short description of the users, data sources and the step currently handled manually.