Elektronikos taškas: 60,000 products in one Shopify store

Elektronikos taškas, an electronics, appliance and home goods retailer, needed a single catalogue. We imported 60,000 products from eight different XML and API sources using an external application customised for the project.

Elektronikos taškas online store

Why did the import need a custom app?

Part of the product data arrived in XML files. The rest had to be retrieved through APIs. Both formats needed to feed the same Shopify catalogue. The external app brought the eight sources together for import into the store.

What happened to old product links?

Product addresses changed with the platform. We matched old URLs to the corresponding pages in the new store and imported redirects into Shopify. A shopper following an old link for a mapped product can reach its new page.

What did the client receive?

A working Shopify store with a 60,000-product catalogue, imported redirects and Paysera payments. The catalogue import, URL migration and payment setup were three distinct parts of the delivery.

What does a 60,000-product catalogue look like to a shopper?

Elektronikos taškas stocks both battery chargers and small kitchen appliances. A customer looking for a paint thickness gauge starts in automotive equipment; someone choosing a toaster starts in kitchen appliances. Both see a single Shopify store, even though the underlying product records came from eight different sources.

What should a retailer prepare before a similar move?

Start with three examples: one actual product record from each source, one working address for an old product, and one old category address. Each reveals a different piece of the project. A record shows how data arrives. An old product link helps establish where a returning customer should land. A category URL is a reminder that people also bookmark ranges, not just individual items.

The old Elektronikos taškas WordPress store had distinct address patterns for products and categories. For example, /produktas/ identified a product, while /produkto-kategorija/ identified a group. When considering a redirect, the purpose of the old page matters first. If the visitor came to compare several products, a single item does not replace an entire category.

How should you scope a catalogue migration?

The two figures in this project, 60,000 products and eight sources, answer different questions. The first describes catalogue volume. The second tells you how many separate inputs the import must bring together. Even a smaller shop can have a complex import if some suppliers deliver files and others expose their information through an API. It helps to give those two figures separately when asking for an estimate.

Agree what completion should look like to a customer. One check is to open an item from the new catalogue. Another is to reach it through its old link. A third is to continue from the product page to checkout and see the intended payment option. These are three distinct journeys that can be checked independently.

Is exporting the products to a spreadsheet enough?

A spreadsheet can help plan a one-off move. On its own it does not explain how to retrieve information from eight sources or preserve the purpose of old links. For this store, the external app handled the catalogue import, while mapping old addresses was a separate task. A retailer planning a comparable project can start with sample records and URLs before deciding where an ordinary import will suffice and where a custom solution is warranted.

Visit store

Related services

XML and API integrations · Shopify migration · Technical SEO

All projects