
Stuzhuk Lab — Chemistry of Code
Chemistry of Code
Online store development

Ecommerce development for international teams: Shopify, WooCommerce, Magento, or a custom storefront — catalog, checkout, inventory sync, and merchant feeds.
Tell me the goal, stack constraints, and timeline — I reply on Telegram.
I build online stores that sell: catalog, cart, payments, inventory, and a handover your team can operate. This is ecommerce development, not a marketing landing with a “buy” button glued on.
For English-speaking and international teams the default shortlist is Shopify, WooCommerce, Adobe Commerce (Magento), or a custom / headless storefront (Astro, TypeScript, Storefront APIs). 1C-Bitrix stays in the mix only when you already run CIS accounting or a Russian-language catalog that must talk to 1C. I do not pretend Bitrix is the default stack for a US or EU brand.
Typical engagements: a first store for a DTC brand, a replatform off a sluggish Magento 1 / OpenCart / custom PHP shop, a B2B portal with customer-specific prices, or a catalog that must stay in sync with a warehouse or ERP. Delivery is iterative: written scope, vertical slices you can click every one to two weeks, staging that mirrors production, and a short hypercare window after go-live.
I have shipped commerce sites on CMS platforms for years and now work mostly in TypeScript, Node.js, and PHP where the accounting layer demands it. Related catalog work includes euromoskitka and ecosteks.ru. Adjacent tracks when the store is not enough on its own: marketing and corporate websites for brand pages, SEO, AEO and GEO for answer-engine structure, 1C integration for CIS ledgers, and chat bots when a messenger checkout helper is useful.
Platform choice is a business decision. Shopify wins when you want speed and a managed checkout. WooCommerce wins when WordPress content is the acquisition engine. Magento still fits large B2B catalogs. Headless fits when the storefront must be fast and the commerce engine is already an API. We pick one primary platform in discovery so you do not pay for two half-finished stacks.
Cost depends on catalog size, payment and tax rules, ERP hooks, and how much of the theme you keep versus rewrite. I do not publish fake “from $X” store packages. After a short call you get a written outline: milestones, what is in the first release, and what waits. Most first releases land in 6–12 weeks; a theme-level Shopify or WooCommerce launch can be faster; ERP-heavy or multi-store Magento work is longer.
The cluster below is the actual delivery surface: platform landings, store migration, catalog UX, checkout, inventory sync, and product SEO with merchant feeds. Start from the parent page or jump to the stack that matches your search.
Related directions: 1C-Bitrix stores, WooCommerce, OpenCart, Shopify, Magento and other platforms, custom and headless, store migration and replatforming, catalog and search, cart, payments and delivery, ERP and inventory sync, catalog SEO and merchant feeds.
FAQ
Tap a question to expand the answer.
Shopify, WooCommerce, or a custom storefront?
Shopify for managed checkout and speed; WooCommerce when WordPress content is the engine; custom/headless when themes cannot express the funnel. Magento only when B2B catalog complexity is real. We pick one primary stack in discovery.
How long does a first release take?
A focused Shopify or WooCommerce launch is often 5–10 weeks. Headless or ERP-heavy work is 8–16 weeks. I do not sell a fake two-week “any catalog” package.
Do you migrate an existing store?
Yes — that is store migration and replatforming: products, customers, orders where APIs allow, plus a redirect map. It is a project with a freeze window, not a theme swap.
Which payments do you implement?
For this audience: Stripe, PayPal, and wallets the platform supports. Tax/VAT follows the entities in the brief. CIS-specific processors are documented on the Russian pages, not as the English default.
Is 1C-Bitrix part of the English offer?
Only for CIS operations that already run 1C. It is not the default stack for a US/EU DTC brand. See 1C-Bitrix stores for that contour.
Tell me the goal, stack constraints, and timeline — I reply on Telegram.