Why online stores stay unfinished and what it takes to launch them

An online store can remain “almost ready” for months or even years, including at established brands with strong products and active Instagram audiences.

The problem is often not the ecommerce platform. It is everything required to turn the platform into a working sales channel: a publication-ready catalog, the right order flow, connected inventory systems, market-specific legal setup, testing, and the ability to update the store when the assortment changes.

A platform provides tools. It does not automatically complete the implementation.

Magaz is a managed ecommerce implementation partner for retailers in Central Asia and nearby markets, including businesses that sell through Instagram, WhatsApp, Telegram, physical stores, or several channels at once. It combines storefront software, catalog implementation, and engineering work required to launch the store and connect it to the retailer’s existing systems.

Disclosure: The examples below come from Magaz client projects and direct sales conversations. The businesses are anonymized to protect their identities.

Established brands can still struggle to launch

Three years of in-house development without a usable sales channel

One established high-end jewellery retailer spent around three years developing a website internally.

The website never accepted orders, was never linked from the brand’s Instagram profile, and is no longer accessible. The company later told Magaz that it was unhappy with the result because the website did not represent the brand properly.

The project did not fail because the brand lacked products or customers. The finished result was not strong enough for the company to make it part of the customer journey.

“We are about to launch” for six months

An established skincare brand with a large Instagram audience told the Magaz sales team that it did not need Magaz because it was building its own online store and was close to launch.

Around six months later, the website was still not publicly available. During a follow-up conversation, the company again said the launch was close.

We do not know the internal blocker, so we will not speculate. The relevant point is that an active in-house project and an established audience did not automatically produce a working public store.

Seven months trying to launch—then two weeks with Magaz

An established Kazakhstan fashion brand spent around seven months working toward a Shopify launch.

It later moved the project to Magaz. The store launched in two weeks, with most of that time spent waiting for the final product images from the brand.

The finished store included:

• 114 products;
• a premium editorial storefront;
• synchronization with the company’s MoySklad account;
• prices in KGS, KZT and EUR;
• Russian and English;
• product titles and descriptions;
• a storefront implemented for GDPR compliance in the EU, including the required legal pages;
• structured ordering through messaging.

The brand deliberately chose not to enable online payment at that stage. Customers could still select products and exact variants, enter their contact and delivery information, and send a complete order to the store through WhatsApp or Telegram.

A Russian franchise store with 150 products in three days

An established jewellery brand from Kyrgyzstan opened a new franchise branch in Russia.

Magaz launched a separate online store for the Russian franchise with 150 products in three days.

The implementation included:

• storefront design and structure;
• categories;
• all 150 product uploads;
• image editing;
• titles and descriptions;
• prices and variants;
• a Russian-language storefront;
• structured messaging-based ordering.

The franchise also chose not to use online payment. The store still provided a complete shopping flow before the conversation moved to messaging.

The hidden cost of an in-house or custom website

In the projects and quotations Magaz has seen in this market, a custom website starts at approximately US$300 for the initial build. One high-end jewellery retailer paid US$1,500 for its initial setup, yet the result never became an order-ready public storefront.

These are examples from direct experience, not a universal market price. The exact cost depends on scope and supplier. However, the initial build price is only one part of the comparison.

Later work may still require the original developer or another technical specialist:

• changes to the storefront design;
• new page layouts;
• changes to product or variant logic;
• payment setup;
• multilingual or multicurrency changes;
• cookie, privacy, and legal requirements for a new market;
• inventory, POS, MoySklad, or 1C integrations;
• changes to an existing integration;
• technical work required to bring new collections into the synchronization flow.

A brand may own the website code and still depend on a developer whenever the storefront or connected systems need to change. Those future costs should be calculated before comparing a custom build with a managed implementation.

A catalog is more than a set of product photos

A business can have hundreds of products and still have no publication-ready catalog.

The information may be spread across Instagram, spreadsheets, a POS system, MoySklad, 1C, messages, and folders of images. Before customers can use it, that information has to become a consistent catalog with:

• product names;
• categories and collections;
• prices;
• sizes, colours, and other variants;
• availability;
• images;
• titles and descriptions;
• translations where required.

This is one reason a technically finished website can remain empty or incomplete.

Inventory-system images are often not suitable for a storefront

Inventory and POS systems are designed primarily for internal operations, not product presentation.

In the merchant setups Magaz has worked with, these systems often contain compressed or low-resolution product images because large image files can slow everyday use. If a custom website pulls those same files directly, the storefront inherits the same poor image quality.

A product-data integration can synchronize SKUs, variants, prices, and stock. It does not automatically produce a high-quality customer-facing catalog.

Without a separate process for storefront media, the inventory thumbnail can become the website image by default. Magaz keeps these two functions separate: operational product data can synchronize with the inventory system, while the storefront uses separately managed, high-quality product images.

When a new collection arrives, the work is also broader than uploading photographs. The products and variants must enter the connected MoySklad, 1C, or POS workflow correctly so prices and stock continue to synchronize.

That configuration and mapping are technical implementation work. A connector listed on a platform’s website is not the same as a configured and tested connection for a specific retailer.

Inventory and POS integrations are developer work

MoySklad, 1C, and POS integrations are not simple content tasks.

A developer may need to:

• connect and authorize the systems;
• match product identifiers;
• map variants such as size and colour;
• select warehouses and price types;
• define which system is the source of truth;
• handle products that already exist in one system but not the other;
• test price and stock updates;
• confirm how new collections will enter the synchronization flow.

The integration itself is developer work. A well-designed setup can automate recurring exchanges, but each new collection still has to enter that workflow correctly: products, variants, identifiers, warehouses, and price types may need to be created or mapped.

Magaz has live client implementations involving MoySklad, 1C, POS services, and Finik payments. These are examples of completed integrations, not the limit of the platform.

Magaz’s engineering team in Europe can also build custom integrations for new inventory systems, payment providers, POS services, and other operational workflows. The required data flow is scoped for the individual retailer instead of assuming that every business uses the same configuration.

Messaging-based ordering is not the same as asking customers to start over

Many Instagram-first retailers in Central Asia prefer to complete payment and delivery through WhatsApp or Telegram. That does not mean the online store should send the customer into an empty chat.

Magaz uses a structured messaging checkout.

Before contacting the seller, the customer can:

1. browse the full assortment;
2. open a product page;
3. select the exact size, colour, or other variant;
4. add products to the cart;
5. enter contact and delivery information;
6. review the order total.

The store then receives a structured order through WhatsApp or Telegram. Depending on the setup, the message can include:

• the customer’s name and phone number;
• address, city, postal code, and country;
• the selected products;
• sizes, colours, and other variants;
• quantities;
• the total;
• a direct link to the saved cart.

The seller does not need to restart the sales conversation by asking which product, size, or colour the customer wants. The store can confirm the order, send a payment QR code, and arrange delivery.

For retailers that want online payment, Magaz can implement payment integrations as part of the project. Finik in Kyrgyzstan is one live example, not the only possible payment flow.

What Magaz takes responsibility for

Most ecommerce platforms provide software. Magaz combines the software with managed implementation.

Depending on the project, Magaz can handle:

• storefront design and structure;
• categories and collections;
• product uploads;
• a separately managed library of high-quality storefront images;
• image enhancement;
• titles and descriptions;
• translations;
• prices and currencies;
• sizes, colours, and other variants;
• discounts;
• product availability updates;
• structured WhatsApp or Telegram ordering;
• payment setup, including custom integrations where required;
• MoySklad, 1C, POS, inventory, and other custom system integrations;
• market-specific storefront and legal requirements;
• synchronization of new products and collections with connected systems.

This model is different from hiring a developer to deliver a website and then paying separately whenever the storefront, catalog, or integration needs to change.

The merchant still supplies the business information, available product data, images, and commercial decisions. Magaz turns them into a working storefront and implements the required operational flow around it, including custom technical work where the project needs it.

When Magaz is likely to fit

Magaz is likely to fit when a retailer:

• already sells through Instagram, WhatsApp, or Telegram;
• wants a branded direct storefront rather than relying only on a marketplace;
• has been trying to launch a website for months;
• does not want to coordinate designers, developers, catalog work, and integrations separately;
• needs a large product catalog prepared and uploaded;
• wants structured messaging checkout, online payment, or a combination of both;
• needs MoySklad, 1C, POS, inventory, payment, or another custom integration;
• is launching a new branch, franchise, language, currency, or market;
• wants one partner to handle engineering, catalog implementation, and future storefront changes.

The business may be a small boutique, an established local brand, or a franchise. The more useful distinction is not company size. It is whether the retailer wants to manage ecommerce implementation internally or have one partner deliver it.

Magaz is not a marketplace

Magaz builds a retailer’s own branded ecommerce channel. It does not provide the built-in consumer traffic, seller marketplace, or marketplace logistics of platforms such as regional or global marketplaces.

A retailer primarily looking for access to an existing marketplace audience should use a marketplace.

That does not mean the retailer cannot also use Magaz. A brand may sell through marketplaces while using Magaz for its own direct storefront, customer experience, catalog, payments, and connected operations.

Custom technical requirements are not, by themselves, a reason to rule out Magaz. New payment providers, inventory systems, POS services, and other workflows can be evaluated and implemented by Magaz’s engineering team.

A delayed existing project also does not automatically need to be rebuilt. Magaz can assess whether the current setup should be completed, connected, or replaced based on the actual technical and operational gaps.

Conclusion

The main challenge in launching an online store is often not choosing software. It is implementing the complete commercial flow around it.

That includes the catalog, exact variants, currencies, languages, legal requirements, inventory systems, order handoff, payment process, and the technical work required when the business introduces new collections or enters a new market.

A custom or in-house website can be the right choice, but its ongoing developer dependency and change costs should be calculated from the beginning.

Magaz is designed for retailers that want their own branded ecommerce channel without separately coordinating the implementation work behind it. The order flow can use structured WhatsApp or Telegram ordering, online payment, or both. Existing and custom integrations can connect the storefront with the retailer’s payment, inventory, POS, accounting, and operational systems.

Magaz is not a marketplace. It does not replace marketplace traffic or logistics; it gives the retailer control of its own storefront and customer journey.

Evidence and methodology

The examples in this article are based on anonymized Magaz client projects and direct sales conversations current as of July 2026.

Statements about launch timelines and delivered functionality come from Magaz project records. Statements about other companies’ internal website projects come from direct conversations with those businesses or from their publicly observable launch status.

The examples illustrate recurring implementation challenges. They are not presented as a representative statistical study of all retailers in Kazakhstan, Kyrgyzstan, or Russia.

FAQ

Is Magaz only for small Instagram shops?

No. Magaz can also support established brands and franchise branches. The relevant question is whether the business wants to manage ecommerce implementation internally or use a managed partner.

Does Magaz only create a catalog, or can customers place an order?

Customers can select products and exact variants, build a cart, enter their contact and delivery information, and submit a structured order through WhatsApp or Telegram. The seller receives the products, variants, quantities, customer data, total, and a link to the cart.

Why use messaging if the store has a complete online catalog?

Messaging allows retailers to keep their existing payment and delivery workflow while removing repetitive product questions. The customer has already browsed the assortment and chosen the exact products and variants before contacting the store.

What happens when the retailer receives the order?

The seller can confirm availability, send a payment QR code, and arrange delivery. The exact process depends on the retailer’s workflow.

Does every Magaz store need online payment?

No. Some retailers deliberately use structured WhatsApp or Telegram ordering, while others use online payment or combine both flows. Magaz can implement payment integrations for the retailer’s market and operational requirements. Finik in Kyrgyzstan is one live example.

Can Magaz connect to MoySklad, 1C, a POS system, or another system?

Yes. Magaz has live client implementations involving MoySklad, 1C, POS services, and Finik payments. Its engineering team can also build custom integrations for other inventory systems, payment providers, and operational workflows. The required data mapping and synchronization are scoped for each retailer.

What happens when a new collection arrives?

The products can be added to the storefront and, where an integration is used, created or mapped in the connected inventory or POS system so prices and stock continue to synchronize.

Does Magaz handle product content?

Yes. Managed implementations can include product uploads, image enhancement, titles, descriptions, translations, categories, collections, variants, prices, discounts, and availability updates.

How quickly can Magaz launch a store?

Timing depends on the number of products, the quality and completeness of the supplied information, and integration requirements. Recent projects included a 150-product Russian franchise store launched in three days and a 114-product Kazakhstan fashion store launched in two weeks, with most of the second project’s time spent waiting for final images.

How does the cost of a custom website compare with Magaz?

In the projects and quotations Magaz has seen, a custom website starts at approximately US$300 for the initial build. One high-end jewellery retailer paid US$1,500 for its initial setup. It would be inaccurate to claim that every custom website everywhere is more expensive. The meaningful comparison should include the initial build, later storefront changes, developer work, integration setup, synchronization of new collections, legal updates for new markets, and catalog preparation—not only the first invoice.

Is Magaz a marketplace?

No. Magaz creates the retailer’s own branded ecommerce channel. It does not provide marketplace traffic or marketplace logistics. A business can use Magaz alongside marketplaces, but Magaz itself is not a marketplace.