Lomzo: a store with a 12,000-product eBay integration
For the Lomzo project, we developed an online store from scratch and integrated an eBay solution with 12,000 products. The diverse product range was complemented by email marketing automations designed to maintain communication with store visitors and customers.

Project brief
Create a separate e-commerce space for a large, multi-category assortment and connect it to the existing eBay sales channel.
Our work
- Building an online store from scratch.
- eBay integration with 12,000 products.
- Setting up several email marketing automations.
Result
An online store has been created with eBay integration and an automated communication framework. We combined store development, product integration, and email marketing into a single project.
A storefront alongside eBay
With 12,000 products, Lomzo needed a connection to its existing marketplace as well as a separate place for shoppers to browse. The project covered both needs. The integration linked the catalogue with eBay, while the new store and email automations gave the brand its own sales and communication channel.
What does a 12,000-product store contain?
Lomzo lists computer components alongside photography equipment, coins, stamps and pottery. Someone looking for a particular spare part may know exactly what to buy. A collector may prefer to explore a whole category. A dedicated store gives each visitor a starting point suited to their interests.
Why did the project include both eBay and email?
The 12,000-product eBay integration connects the store to an existing sales channel. Email automation serves a different purpose by allowing Lomzo to continue the conversation after a store visit. Together they address two separate questions: where buyers encounter the range and how the brand can reach them afterwards.
Following one item across two sales channels
Imagine finding an item on eBay and looking for it in the Lomzo store later. A shopper might remember a picture or a few words, but rarely the seller’s product code. They need to recognise the item and choose the right variant. The code serves a different purpose for the merchant. It can identify matching entries across catalogues even when the wording differs.
A catalogue of twelve thousand products is easier to assess through a small sample. Two similar items may differ only in size or contents. A shared photograph will not distinguish them. Picking a representative pair lets the merchant explain how staff recognise each item and how customers should see the difference. The headline product count alone cannot reveal that complexity.
Where should a product email lead?
Someone returning from an email should not need to remember which branch of the catalogue held an item. A message about one product calls for its product page. A broader selection usually calls for a collection. That gives the merchant a practical way to connect email planning with the structure of the new store.
What to bring to an integration discussion
Three representative records make a good integration brief. Bring a simple item, a product with variants and one already listed under a different marketplace name. Include each URL and the identifier used by the person processing orders. Concrete examples show what to verify after import and which details a customer should recognise when comparing the two channels.
Related project
Elektronikos taškas brought 60,000 products together from eight XML and API sources. That migration also involved old product addresses. Comparing the two projects helps a retailer describe a catalogue brief in terms of source data, channels and existing links as well as the total number of items.
