From end-of-life Magento 1 to a connected, modern store

A-Shop is a consumer retailer running true omnichannel commerce — online sales tied to physical store availability and self-pickup, with a large, frequently changing catalog driven by 1C ERP. Its platform isn't a standalone webstore: catalog, stock, orders, store locations and pickup points all flow between Magento and 1C, while a heavily customized frontend carries merchandising, marketing and analytics. That tight coupling makes the business efficient — and means even a small sync or checkout fault can ripple into catalog visibility, order processing, pickup, SEO or analytics. When the partnership began, all of this still ran on Magento 1, which had reached end of life and was no longer receiving security or functional support — so the platform first had to be migrated to Magento 2 before it could be modernized further.

A-Shop's platform had to keep many moving parts in agreement at once — website, ERP, physical stores, payments and marketing — on a catalog that changes constantly. But it was doing all of this on Magento 1, a version that had reached end of life: no more security patches, mounting technical debt, and a hard ceiling on performance and new functionality. In a connected setup like this, small faults don't stay small — they surface where customers and revenue are.

• An end-of-life platform that couldn't move forward. The store ran on unsupported Magento 1 — no security updates, accumulating technical debt, and no safe path to add the features the business needed. Re-platforming to Magento 2 was the prerequisite for everything else, and it had to happen without losing the heavily customized frontend, the 1C integration, or live retail operations.
• Deep 1C dependency on a high-churn catalog. Catalog imports, stock sync, order exports, category structures, product attributes and store/pickup data all ran through 1C. Any integration error could distort catalog visibility, stock accuracy or order processing across the whole store.
• Checkout had many ways to break. Delivery selection, self-pickup, promo codes, gift packaging, cart updates and LiqPay payment confirmation each added a failure point — and any one of them could block an order at the moment of purchase.
• Omnichannel and discovery had to stay trustworthy. Store availability, pickup flows, search, filtering, indexing and SEO URLs all had to stay accurate, while the platform needed ongoing upgrades and security response — including reaction to live compromise risks — without disrupting daily trade.

Encomage began by migrating A-Shop from end-of-life Magento 1 to Magento 2 — then stayed on as the long-term engineering partner, keeping the customized retail platform stable, measurable and commercially effective. Each workstream protects a part of the connected operation.