Kharkiv Master: Online Store for Tactical Footwear
We relaunched the e-commerce store so customers can quickly find the right model and place an order in 2–3 minutes. We migrated the catalog from the old .NET site with all attributes and variations intact, and added filters, LiqPay payments, and a content layer.
About the Project
A relaunch of an online store for a tactical footwear manufacturer. The old site was slowing down purchases and had to be replaced with a new store focused on conversion: fast model selection and a fast checkout. The project included rethinking the catalog structure, UX/UI, content blocks for "cold" visitors, the technical implementation of the store, migration of products from the old .NET system, and payment integration.
About Customer
Kharkiv Master is a manufacturer of tactical footwear for military, law enforcement, and security personnel, as well as models for outdoor activities. Demand and reputation are strong, but the online store's shortcomings were costing the company customers. If users couldn't quickly filter for a model, didn't see key specifications on the first screen, or got confused during checkout, orders simply never reached payment.
Buying without a manager
The key scenario is self-service selection and fast checkout. Any extra step (additional page transitions, excess text, unclear parameters) would hurt conversion.
A feature-rich catalog
This is a product where the decision depends on details: material, season, sole, intended use, height, membrane, size chart, care instructions, and more. Users needed to be able to narrow down options with filters and immediately see the result of their choice on the product page.
Filters and listings
Filtering had to be useful without turning the search into an endless process.
Migration from .NET
We needed to preserve categories, attributes, variations, names, descriptions, photos, and the URL structure (where possible), and move them to the new store so that the team would not have to manually check hundreds of items.
"Hot" and "cold" audiences
The hot audience wants to buy quickly and needs filters, sizes, availability, delivery, and payment. The cold audience needs information and persuasive arguments.
Checkout and payment
Any error in payment or order confirmation means direct losses. The project required predictable statuses, control messages, and basic anti-failure UX.
Proposed Solution
We built the store as a fast headless e-commerce platform: Directus as the managed catalog and content layer, Node.js as the API and business logic (prices, variations, stock, orders), and Next.js as a conversion-focused frontend. We carried out the migration from the old .NET site as a controlled ETL process with attribute mapping and data validation, and connected payments through LiqPay as a separate payment loop with predictable statuses.
Headless architecture on Directus + Node.js + Next.js
We separated responsibilities: Directus manages the catalog, content, reference data, and admin processes. Node.js handles business operations (cart, orders, prices, variations, availability). Next.js delivers a fast catalog and checkout experience.
Catalog model for attributes and variations
We defined the entities "product," "variations," "attributes," "values," and "media" so that filters, product pages, and migration all run on the same logic.
Filter system
We implemented indexed attributes, faceted search, clear defaults, and hints with smart limits on combinations, so users don't get confused whichever combination they choose.
Migration from the old .NET site
We built a field-mapping table, wrote an import/sync process, and ran validations (duplicates, broken photos, misordered variations, incorrect attributes). We then produced a report and a mechanism for re-running the import.
Checkout as a short flow
We built a minimal form with autofill, clear states, validation, and a clear confirmation, so that purchases don't fail because of small UX mistakes.
LiqPay payment system
We set up the payment flow via redirect/callback/webhook, with transaction statuses, protection against duplicate payments, correct order states, and clear messages for the user.
Content layer in Directus
We moved buying guides, care information, video reviews, FAQs, and trust blocks into Directus, so marketing can update them independently and quickly.
We started by auditing how people actually buy on the old site. We entered the catalog from search and ads and tried to find a model by its parameters. We went through the path to the cart and checkout on both desktop and mobile. We recorded where users get lost in categories, where attributes are missing, and where they abandon checkout. As a result, we knew exactly what to show in the listing, what to put on the first screen of the product page, and how to shorten the order path to 2–3 minutes.
Results
1 week
the relaunch investment paid for itself
2–3 min
typical checkout time, from search to purchase
0 catalog losses
after migration from the old .NET site
1 clear path to purchase
thanks to a managed catalog
Ready for paid traffic
with payments, solid navigation, a product page that sells, and content for new users