EShop Import Pro - Joomla Extension

A Practical Guide to Using and Configuring EShop Import Pro for a Joomla Store

EShop Import Pro is not about polishing product descriptions. Its real job is much more practical: loading a prepared catalog into EShop from a spreadsheet so you do not have to build categories, manufacturers, products, images, options, and attributes by hand. In this guide, we will walk through a careful import workflow: preparing the site, assembling the file, running a test import, checking the results, and figuring out where to look when something goes wrong.

This article is written for a Joomla store owner, webmaster, or content manager who already uses the EShop component and wants to bulk create or update product data. It does not cover purchasing, activation, or any kind of license bypass. The focus here is strictly on how the extension works in practice, how to prepare data safely, and how to verify the result after import.

The biggest risk in any bulk import is not the button itself, but the quality of the source spreadsheet. If the file contains mixed-up categories, manufacturers, identifiers, images, or product variants, the extension may process the file exactly as instructed, yet the store will end up with the wrong catalog. That is why this guide is built around the chain file - import - EShop relationships - public storefront result - troubleshooting.

What the Extension Actually Solves Inside EShop

The official description of EShop Import Pro comes down to a simple idea: the extension imports data from an Excel file into EShop and can handle several types of data in a single file. For the user, that means catalog preparation shifts away from manually filling product cards and into spreadsheet-based work, where it is easier to review hundreds of rows, copy values, sort the assortment, and spot missing data.

Based on the product descriptions available, the extension works with categories, manufacturers, products, images, options, and attributes. One important detail is that these entities are not just flat lists inside EShop. Categories drive navigation and menus, manufacturers help group and filter products, options affect what the buyer can choose, attributes describe product properties, and images need to be attached to the right product card. That makes EShop Import Pro especially useful when the store already has a clear catalog structure, or when that structure can be assembled cleanly in a spreadsheet first.

The extension is especially relevant in three situations. First, when you are filling a new store for the first time and need to add a large number of products quickly from a supplier price list. Second, when you are migrating inventory from an older system and can reshape the data into the required spreadsheet format. Third, when you regularly update part of the catalog, such as prices, stock levels, images, or specs, assuming your version and import scheme support that safely.

EShop Import Pro does not replace catalog planning. It speeds up the import of prepared data, but it will not automatically fix inconsistent naming, multiple versions of the same category, duplicate SKUs, broken image links, or incorrect relationships between options and products. If the source file is bad, a bulk import will simply move those errors into the store faster.

Which Data Needs the Most Care

For EShop, the product name and price are only part of the picture. In a real store, the customer sees a full structure: category, product card, image, selection parameters, specifications, availability, manufacturer, related products, and page layout. Because of that, your spreadsheet should not contain disconnected fields. It should model the future catalog.

• Categories. Check for consistent naming, clear hierarchy, and no duplicates such as Shirts, shirts, and T-Shirts if they actually refer to the same group.
• Manufacturers. Use a single spelling for each brand. Otherwise, filters and product pages may end up with multiple nearly identical manufacturers.
• Products. Keep a stable identifier such as SKU or model so you can later tell the difference between updating an existing item and creating a new one.
• Images. Check links, filenames, and image order before the import. A one-character mistake often shows up as an empty gallery.
• Options and attributes. Do not mix up what the customer chooses with what simply describes the product. For clothing, size is usually an option, while material is an attribute.

Bottom line: the extension solves the problem of bulk data entry, but the best outcome comes not after clicking Process Import, but after calmly preparing the file and testing it on a small sample first.

Who This Import Method Fits, and When Another Tool Makes More Sense

EShop Import Pro makes the most sense for sites where the main commerce system is EShop by Ossolution Team. It is not a universal importer for every Joomla component, and it is not a complete site migration tool. Its strength is that it is built around EShop structures: categories, manufacturers, products, images, options, and attributes. If your store already runs on EShop, that narrow focus is usually more convenient than a general-purpose spreadsheet tool for database work.

The extension works well for a store owner who receives inventory in Excel, maintains supplier pricing in spreadsheets, migrates a catalog from another system, or wants to populate a store faster before launch. It is also useful for agencies: you can prepare the file together with the client, agree on the structure, run a test import on a copy of the site, and only then repeat the process in production.

But there are cases where EShop Import Pro should not be your first choice. If you need scheduled synchronization from multiple outside sources, API-based workflows, remote database connections, complex migration profiles, or imports into multiple Joomla components, more universal solutions such as vData may be a better fit. If you have not chosen your store platform yet and are comparing shopping cart systems, you should evaluate more than import features alone. Look at checkout, shipping, payments, SEO, templates, filters, reporting, and support.

When the Product Is Especially Useful

In practice, EShop Import Pro is most valuable not because it "builds a store," but because it removes the monotonous manual step. Picture a catalog with several hundred products, multiple manufacturers, several categories, and a set of product specs. Manual entry creates two problems: it takes a long time, and it almost always introduces inconsistent naming for the same entities. A spreadsheet lets you see the catalog from above, and the extension transfers that structure into EShop.

• You are launching a new EShop store and already have a supplier price list.
• You are migrating products from an older catalog where the data can be exported to Excel or reshaped into an Excel-style structure.
• You regularly add seasonal collections and want a repeatable preparation process.
• You want to verify categories, manufacturers, images, and options before publishing.

When Bulk Uploading Is Not Worth the Risk

If the store is already live and taking orders, do not import a large spreadsheet directly into the production database. Even a correct import can change public pages, filters, images, and product selection variants. On a live site, the safer path is a site copy, a database backup, and a short test file. Bulk import without a rollback plan is especially risky when products have complex options, different pricing by variant, many images, or existing SEO value.

Practical rule: if you cannot explain in 10 minutes which field the extension should use to distinguish a new product from an existing one, you are not ready for a large import. Start by sorting out the identifiers and run a test on 3 to 5 products.

What to Check Before Installation and Before the First Import

Import preparation does not begin inside EShop Import Pro. It starts in Joomla and in EShop itself. You need to make sure the site is ready to accept data, that the main store component is installed in a current compatible version, that you have a backup, and that you understand which parts of the catalog will be created or changed.

In Joomla, extensions are installed through the admin panel, usually via System - Install - Extensions and the package upload tab. After installation, components, modules, and plugins may need to be enabled or configured separately. For EShop Import Pro, the key prerequisite is simple: confirm that the main EShop component is already installed and working, because the importer only makes sense when there is an actual store to receive the data.

Technical Checklist Before You Start

• Create a full backup of the site files and database before the first real import.
• Confirm that EShop opens in the admin panel, products can be created manually, and the storefront displays product pages without errors.
• Verify that your Joomla, PHP, and EShop versions are compatible with the importer version according to the developer's official sources.
• Check the server's file upload limit if the Excel file or images may be large.
• Avoid risky experiments on the live site: start with a copy or test section, then move to the main catalog.
• Make sure the admin user has permission to install extensions and work with the EShop component.

Joomla ACL can limit access to components and administrative actions. If the import is handled by a content manager rather than a Super User, verify permissions in advance. Otherwise, what looks like an extension problem may just be a user who cannot access the required component or system action.

Preparing the EShop Structure

Even if the import creates categories and manufacturers, it still helps to decide in advance what the store structure should look like. If some categories already exist, their names and aliases should match the logic of the file. If categories will be created by import, it is better to test them on a small sample first and make sure hierarchy, ordering, and menu display do not require manual cleanup.

Take a separate look at images as well. EShop supports multiple product images and image size settings in the main component. So before importing, decide how you will prepare the files: use links, upload images into the media library ahead of time, normalize filenames, or organize them by SKU. The more stable the system, the less manual cleanup you will have after upload.

How to Prepare the Excel File Without Hidden Errors

The quality of the spreadsheet determines the quality of the result. In Excel, it is easy to create a file that looks clean but still contains hidden problems: trailing spaces, multiple versions of the same brand, numbers in scientific notation, empty required fields, broken links, merged cells, or unexpected date formats. For the importer, appearance does not matter. Structured values do.

Start small. Create a separate test file and include several product types: a simple product without options, a product with an image, a product with a manufacturer, a product with an option, and a product with an attribute. That kind of sample is far more useful than importing 100 identical rows because it tests the relationships between entities.

Fields You Should Keep Under Control

The exact set of columns depends on the examples and documentation for your version of the extension, so do not invent the structure from scratch. Use official examples if they are available, or export test data from EShop if that fits your workflow. What matters is not what you call a column for yourself, but what the importer expects.

After filling the table, do a manual review in a text editor or value-only view if you save the file into an intermediate format. Do not rely on how Excel looks on screen alone: the editor may hide separators, reformat long numbers, and automatically change cell formats.

How to Avoid Duplicates and Wrong Relationships

The most common logical mistake is thinking of each row as an independent product. In a store, a product is connected to a category, a manufacturer, images, options, and attributes. If those relationships are described ambiguously in the spreadsheet, the importer cannot guess what you meant. For example, ACME and Acme may look identical to a person, but to the system they can be different values.

Create a separate sheet for reference lists: categories, manufacturers, options, and attributes. Then reuse those values in the main sheet instead of typing them manually each time. That reduces typos and makes it easier to spot missing relationships. If the Excel file must be strictly single-file, you can still use reference sheets during preparation and copy only the required structure into the final file according to the documentation rules.

Testing on a Small Sample

Put together 3 to 5 test products that cover different scenarios. One product without options will verify the basic product card. A second product with multiple images will show how the extension attaches the gallery. A third with a manufacturer and attributes will test the reference data. A fourth with options will show whether variant choices are mapped correctly. The fifth can be intentionally more complex, but do not use it first.

Result check: if you cannot explain and verify the test set manually, the full file will be even harder to validate. First, get a predictable result on a short spreadsheet.

Installation and the First Check in Joomla

Installing the extension in Joomla should be straightforward: upload the package through the system installer, confirm the success message, then open the component or its menu item in the admin panel. If you do not see the expected menu entry after installation, check whether the package actually installed rather than being rejected by the server because of size, permissions, or incompatibility.

Do not start the first import immediately after installation. Open EShop first, make sure existing products and categories are visible, then locate the EShop Import Pro interface and review which fields and buttons are available. Product sources mention selecting an Excel file and starting the process with Process Import. Interface labels in your version may differ, so rely on the documentation and the actual screen in the installed extension.

First Run Without Putting the Catalog at Risk

1. Prepare a test Excel file with a few products and a clearly understood expected result.
2. Open the EShop Import Pro interface in the Joomla admin panel.
3. Select the file through the upload field, and do not use the full production catalog on the first run.
4. Start the import and wait for the process to finish without refreshing the page unless necessary.
5. Open the lists of categories, manufacturers, and products in EShop and compare them to the test spreadsheet.
6. Check the public product page: name, price, images, options, attributes, and category.

If the test import produces an unexpected result, do not use manual edits in the product pages as your main fix. Find the root cause in the file first, because the same mistake will repeat dozens or hundreds of times in the full catalog. Manual cleanup after every import quickly destroys the value of automation.

What to Do Right After Installation

After installation, it helps to define a simple working procedure for the team. Who prepares the file, who reviews the reference lists, who runs the import, who checks the public result, and who decides whether a rerun is needed. Even if only one person manages the site, that process reduces the chance of uploading an old spreadsheet version or mixing up the test file with the production file.

Bottom line: installation is a short phase, but the first validation step is the main filter for errors. Do not judge the extension by the fact that it installed. Judge it by how predictably your test data turned into EShop categories, products, images, options, and attributes.

Configuring the Import Workflow: From Spreadsheet to EShop Relationships

There is no such thing as universal "best settings" for EShop Import Pro across every site. The best settings are the ones that match your catalog structure and do not create unnecessary duplicates. So after installation, configuring the process is not just about choosing a file. It means defining the rules: which data gets created, which data gets updated, which relationships are required, and how you validate the result.

According to the product description, the extension imports different data types separately and then assigns products to the corresponding categories, manufacturers, options, attributes, and images. That is convenient, but it requires discipline: reference lists must be written consistently, and product rows must point to them in a predictable way.

A Setup Order for a Typical Store

Start by deciding what the import should create. For a new store, you may allow the extension to create categories and manufacturers from the file, as long as the structure is clean. For an existing store, it is usually safer to align the file with the names that already exist so you do not end up with duplicates. Then decide how products should be handled: add only new items, or update existing ones too. If update behavior in your version depends on a specific key, test it on a small sample first.

• Categories and manufacturers. Normalize the reference data first, then import the products.
• Products. Use a stable identifier that does not change when the product name changes.
• Images. Check file availability before import and verify which image becomes the primary one.
• Options. Test customer choices on the public product page, not only in the admin area.
• Attributes. Check whether specs appear in the correct place in the EShop template.

Which Parameters to Enable Carefully

If your version's interface includes update, overwrite, or remove-missing-data modes, enable them only after testing. Bulk creation is usually less dangerous than bulk overwriting. Deleting or clearing values is the riskiest type of operation, because a mistake in the file can remove data that was omitted by accident.

For a live store, the safest approach is step by step: first import new products in an unpublished or hidden state, if that workflow is available in your EShop version; then review the product pages; then publish them. If that mode is not confirmed in your importer version, use a test copy of the site and do not rely on the idea that you will "fix it quickly after import."

Validation After Saving the Settings

After each change to the import process, compare three places: the original row in Excel, the record in the EShop admin area, and the public product page. If the data matches in the admin area but not on the site, the cause may be the template, cache, output settings, permissions, or menu structure. If the data is already wrong in the admin area, the problem is almost always closer to the file or the import rules.

How to Roll Back a Questionable Setting

The best rollback is restoring a backup of the test database or deleting the test products before the production import. If data has already been imported into the live store, do not manually mass-delete database tables. Use EShop's built-in tools, restore from backup, or involve a developer. Manual SQL fixes without a precise understanding of how products, categories, images, and options are related can leave you with broken product pages.

Practical Example: Importing a Small Product Collection

Let us walk through a realistic scenario: an EShop store is adding a new accessories collection. The spreadsheet includes categories, a manufacturer, products, images, color as an option, and material as an attribute. The goal is to import the products so the store administrator sees them in the catalog, while the customer can open the product page, select a variant, and view the specs on the storefront.

Goal and Preparation

The goal of this example is not to show every possible field, but to demonstrate a safe workflow. First, create a short file with a few products and verify the relationships. Then scale up the spreadsheet. Before you start, Joomla, EShop, and EShop Import Pro should all be installed. The EShop storefront should open correctly, and the template should display a normal manually created product without issues.

Initial Sample Set

• Category: accessories.
• Manufacturer: one test brand with a single consistent spelling.
• Products: 3 items with unique SKUs.
• Images: one primary image and one secondary image per product, if your file scheme supports that.
• Option: color, for example black and blue.
• Attribute: material, for example leather or textile.

Import Steps

1. Create a test spreadsheet based on the documentation example for your version of EShop Import Pro.
2. Fill in categories, manufacturers, and products without leaving required values empty.
3. Check that SKUs are unique and that images are reachable through the specified paths or URLs.
4. Save the file in the format expected by the extension, and do not change the column structure before the run.
5. Open the import interface, select the file, and start processing.
6. When the process finishes, open EShop and review the created categories, manufacturers, and products.
7. Open each public product page and compare it to the original spreadsheet row.

Expected Result

After a successful test, the EShop admin area should show products assigned to the correct category and manufacturer. On the public side of the site, each product page should have the correct name, price, image, color choice option, and material attribute. If the product page opens but some data is missing, compare the EShop display settings and the template: sometimes the data was imported correctly but is hidden by configuration or not rendered in the current layout.

A Common Problem That Gets in the Way

The most frustrating error in this scenario is when the import creates the product, but the relationship to the category, manufacturer, or option does not match expectations. At first glance it looks like "the import is broken." In reality, the cause may be a space, different capitalization, a different separator, or an ambiguous name. That is why after a test run you should review not only the number of created products, but every relationship as well.

Example takeaway: a correct test import should produce more than just rows in the product list. It should produce a complete, usable product page on the site. Only after that is it worth scaling the file to the full catalog.

Checking the Result: Admin Area, Product Page, Menu, and Cache

After import, it is important to separate two questions: did the data reach EShop, and is that data displayed correctly on the site? Those are different layers. In the admin area, you check records, relationships, and fields. On the site, you check the template, menu, cache, images, and the customer journey. A problem at any of those levels can look like a failed import even when the import itself worked.

What to Review in the Admin Panel

Open the product list and check several items from different categories. Do not stop at the first product. Compare the name, SKU, manufacturer, category, images, options, and attributes. If the import was supposed to update existing products, review an older product and a newly imported one separately. That will help you see whether the process is creating duplicates instead of updating existing entries.

Then open the category and manufacturer reference lists. If duplicates have appeared there, do not continue with the full file. Duplicates almost always point to a problem with value normalization or a mismatch with the structure that already exists.

What to Review on the Public Side

On the site, open the category page, the product page, and the purchase flow up to the point where the user chooses product parameters. You do not need to place a real order, but you do need to verify that the option is available, the image is visible, the price makes sense, the attributes are shown, and the product link does not lead to an error. If the product does not appear in its category, check publication status, access, menu settings, filters, and cache.

Joomla can cache pages, views, and modules. If the data is correct in the admin area but the public page still shows the old result, clear the cache using Joomla's built-in tools and review the system cache settings. Do not disable caching permanently just because of the import, but during validation it is important to understand that cache may delay what you see on the front end.

SEO and Search Visibility Caution

A bulk import affects more than the storefront. It also affects future indexing. If the import creates new URLs, names, meta descriptions, or categories, check that pages did not end up with identical titles or empty descriptions. Do not assume search engines will sort it out on their own. For a large catalog, it is better to prepare names, aliases, and descriptions in advance at least for the key product groups.

If the store is already indexed, be especially careful when updating existing products. Do not mass-change aliases or category structure without a redirect plan and link checks. EShop, as the main store component, has its own SEO settings, but EShop Import Pro only transfers data from the file. The meaning and quality of that data remains the site owner's responsibility.

Importing Images, Options, and Attributes: The Important Details

Images, options, and attributes are what separate a useful product import from a simple list of names. They are also where errors happen most often, because they depend on relationships: an image must belong to the right product, an option must connect to the correct choice, and an attribute must describe a spec the visitor can read or use for comparison.

Images: Check Availability and Order

Images in an EShop catalog are highly practical. They affect trust, click-through behavior, and ease of choice. Before importing, make sure the images are not too small, do not contain supplier watermarks, do not fail to load, and do not require authorization. If you use URLs, make sure the site server can actually fetch those files. If you use local filenames, verify exactly where EShop expects to find them.

For testing, it helps to create one product with two images and see which one becomes the primary image. If order matters, define it in the spreadsheet according to the documentation rules rather than relying on how files happen to be sorted in the folder.

Options: Do Not Mix Customer Choices with Product Specs

An option is something the customer chooses: size, color, bundle, packaging. An attribute is something that describes the product: material, density, country of origin, surface type. If you mix those up, the product page becomes harder to use. The customer may see a spec where they expected a dropdown, or the opposite.

When importing products with options, do not just check whether values exist in the admin area. Test the actual buying scenario. Open the product page, select a variant, and see whether the price or image changes if that is supported by your EShop configuration. If the option is visible but does not affect the choice, it may have been imported as a spec instead, or it may not be attached to the product correctly.

Attributes: Consistency Matters More Than Quantity

A large list of specs looks convincing only when it is organized. If some products use Material, others use material, and still others use Material, comparison and filtering become less useful. Before importing, create an attribute dictionary and use it across all rows.

Do not try to import every supplier spec without filtering. Users need the properties that help them choose a product. Internal supplier codes, service fields, and repeated marketing phrases are better kept out of the public product page, or stored only where the store team genuinely needs them.

How to Organize Repeat Imports Without Creating Chaos

One successful test import does not mean the process is ready for routine use. A store changes over time: suppliers send new price lists, some products disappear, images change, new brands appear, and content managers edit descriptions manually. If you do not agree on the rules for repeat imports, after a few cycles it becomes unclear which source is authoritative: the spreadsheet, the product card in the admin panel, or the manual edit made after publication.

With EShop Import Pro, it makes sense to treat import as a managed process. The spreadsheet should not be a random attachment from an email. It is better to store it as a working source with a version, a preparation date in the filename, and a short note about what changed. The dates do not need to appear in the article itself, but they matter in your internal workflow because they make it easier to see which file was uploaded before an error appeared.

Separate Initial Import from Ongoing Updates

The initial import and updating an existing catalog are two different tasks. During the initial import, you are building the structure: categories, manufacturers, products, images, options, and attributes. During updates, you need to preserve the already published logic and change only the fields that should change. If you mix those modes, you can easily create duplicates, overwrite descriptions, lose images, or restore old values that had already been corrected manually.

A practical approach is to keep separate working files for different kinds of operations. One file for adding new products, another for updating prices and stock, a third for fixing images or specs. Even if your version of EShop Import Pro expects one unified format, you can still prepare the data separately and assemble the final file before import according to an approved scheme. That way, the team knows exactly what each run is supposed to change.

What Counts as the Source of Truth

Decide in advance which fields always come from the spreadsheet and which can be edited manually in EShop. For example, SKU, manufacturer, primary category, and price can live in the file, while SEO text, extra descriptions, and manual page-level improvements can live in the admin area. If you later re-import an older file with an empty description, it should not accidentally wipe out useful manual work. If your version's overwrite behavior is not clearly confirmed, test it on a copy of the site first.

• Data from the file. Information that changes often at the supplier level or should stay consistent across many products: SKU, base price, stock availability, manufacturer, and category assignment.
• Data from EShop. Information the site team improves after import: SEO text, extra tabs, manual recommendations, refined images, and related products.
• Data that requires review. Fields that should not be overwritten automatically without inspection: options, attributes with mixed measurement units, complex images, and URL aliases.

This type of rulebook feels unnecessary only when the catalog is very small. As the catalog grows, it saves hours of manual cleanup and prevents arguments about why a product page suddenly reverted after the latest import.

Supplier Scenario: How to Accept Someone Else's Price List

If a supplier sends you an Excel file, do not upload it as-is. The supplier's price list was built for their system, not for your EShop store. It may contain internal categories, shortened names, non-public codes, images behind a private login, inconsistent units of measure, and marketing fields that do not belong on the product page. The content manager's job is to turn that price list into a file that matches the logic of your store.

1. Copy the original file and do not edit the source directly, so you can return to it if a dispute comes up.
2. Identify a stable product key: SKU, model, or another code that does not change when the name changes.
3. Map the supplier's categories to your EShop categories instead of creating new sections automatically without review.
4. Normalize manufacturers and brands, especially if the supplier uses abbreviations.
5. Select images that can be shown publicly and verify file availability.
6. Separate options from attributes: customer choices in one place, technical specs in another.
7. Build a test import and show the result to the responsible person before the full run.

After that kind of preparation, EShop Import Pro becomes the final step in the process rather than the place where you try to fix someone else's spreadsheet. That distinction matters. The importer is good at transferring prepared data, but it should not be asked to act as the editor of catalog logic.

How to Keep an Import Log

The log does not need to be complicated. It is enough to record the filename, the purpose of the run, the row count, who prepared the spreadsheet, who ran the import, what was checked after upload, and which problems were found. This is especially useful for agencies and for stores where several people work with the catalog.

Bottom line: repeat import should not be a habit of "upload the latest price list." It should be a controlled cycle. Prepare the file, understand the goal, validate a small sample, run the import, compare the result, and record the outcome. That is when EShop Import Pro helps you scale the work instead of turning the catalog into a pile of random corrections.

Limitations and Safe Improvements Without Touching Core Files

Every importer has boundaries. EShop Import Pro is built around a prepared Excel file and the EShop structure. If you need automatic daily synchronization from multiple XML feeds, complex data transformation, API integration, or import into multiple Joomla components, do not force this tool to solve a different problem. It is better to choose a more suitable tool or build a separate data preparation workflow.

Safe improvements here are not about modifying the extension's code. They are about organizing the process. Do not edit Joomla core files, EShop files, or EShop Import Pro files. Do not change database tables directly just to "clean things up quickly." Use backups, a test copy of the site, built-in EShop settings, Joomla permissions, and careful file preparation.

Language Overrides for Team Convenience

If the admin panel or extension messages are not fully clear to the team, Joomla language overrides are usually safer than editing the extension's language files directly. That does not change the import logic and does not break updates. The exact string key should be found through Joomla's built-in language override mechanism or the documentation for your version.

1. Open language overrides in the Joomla admin panel.
2. Find the required interface string by its English text, for example a button label or message.
3. Create an English override for the administrative area.
4. Check the EShop Import Pro screen after clearing cache if the old string is still visible.

Rollback is simple: remove the override you created. This approach is safer than editing extension files because an update will not unexpectedly overwrite your change.

Access Permissions for the Importer

If the import is not performed by the site owner, restrict access to only the people who actually need it. In Joomla, permissions can be configured through user groups and access levels. Bulk import does not justify giving broader rights than necessary. At the same time, restrictions that are too strict will create a different kind of problem: the user may be able to see the component but not perform the required action.

A practical setup is a dedicated administrative role for catalog work, a test run under that role, and a team activity log. If the import changes thousands of rows, it matters to know who ran the file, when it was prepared, and what result was validated.

Why an Import Can Go Wrong and How to Diagnose It

Import problems are best analyzed by symptom. Do not begin by reinstalling the extension, and do not run the same full file several times in a row. First, determine where the problem actually is: the file will not upload, the process never finishes, records were not created, relationships are wrong, images are empty, or the public side did not update.

The File Is Not Accepted or the Import Will Not Start

Symptom: the file is selected, but the process does not begin, the page returns an error, or the upload breaks off. Possible causes include an unsupported format, an oversized file, server upload limits, temporary folder permissions, or package incompatibility. Joomla documentation for extension installation mentions upload limits and alternative installation methods for large packages. The same logic applies here: the server must accept the file before the importer can process it.

Check the file size, format, extra sheets, and possible corruption, then try a short test file. If a small file works, the issue is not the extension itself, but the size, structure, or data in the full file.

The Import Finishes, but No Products Appear

Symptom: the process appears to complete, but the product list does not change. Check whether the file imported only categories or manufacturers first without actual product rows, whether products were created in an unpublished state, whether they landed in a different category, or whether a list filter is hiding them. Then compare the file's required fields to the documentation example.

If the test file does not contain a stable product identifier or a required product name, the extension may skip rows or process them differently from what you expected. Do not add more rows yet. First, get one simple product to appear.

Duplicate Categories, Manufacturers, or Products Appeared

Symptom: after import, EShop shows nearly identical categories or brands. The cause is often capitalization, spaces, different separators, translations, or old values in the file. Review the source reference list and compare it with the entries that already exist in EShop.

The fix is to normalize the spreadsheet and repeat the import on a clean test copy. On a live site, remove duplicates carefully, because products may already be attached to them.

Images Do Not Show on the Product Page

Symptom: the product is created, but the image is empty or the gallery does not match the file. Check the path, URL, file extension, image availability without authorization, filename capitalization, and EShop image storage rules. Just because the image opens in your browser does not prove the site server can fetch it from the same address.

For diagnosis, use one product with one image. If that works, add a second image and check the order. If even one image does not work, the problem is with the path, access, or format.

Options and Attributes Ended Up in the Wrong Place

Symptom: a spec appears as a customer choice, or an option does not show up on the product page. Check how your file structure separates options from attributes. In EShop, options and attributes serve different purposes, so they cannot be mixed just because it is more convenient in the spreadsheet.

The fix is to separate the reference data and run a new test on one product. If the product is complex, temporarily remove images and other fields so you can test only the options and attributes relationship.

Everything Looks Correct in the Admin Area, but the Site Still Shows Old Data

Symptom: the data is visible in EShop, but the public page does not change. Check Joomla cache, module cache, template settings, product publication status, the category menu item, and access permissions. Joomla may cache the page, the component view, or a module, so after large changes you may need to clear cache and check again.

If the product page still does not change after clearing cache, open the product through its direct admin link or through the category itself. That will help you understand whether the problem is in the product page or in the menu, module, or filtering layer.

When EShop Import Pro Is the Right Choice

EShop Import Pro is worth using when you already have an EShop store, a clear catalog structure, and a prepared Excel file that needs to become categories, manufacturers, products, images, options, and attributes. In that scenario, the extension saves time and reduces manual routine, but it still depends on careful data preparation.

If you are still choosing a store platform, evaluate EShop itself first along with its full feature set: checkout, payments, shipping, templates, SEO, languages, reports, and support. If EShop is already your platform, the importer becomes a practical tool for faster catalog population. Before a real run, create a backup, run a test on 3 to 5 products, verify the public product pages, and only then scale the file up.

Once the test workflow is clear, you can download the installation package and move on to careful validation on your Joomla site. Do not rush into importing the full catalog: one well-verified test import is more valuable than a thousand rows you will later have to clean up by hand.

The final rule of thumb is simple: the extension is a good fit for people who want to manage a catalog through a prepared spreadsheet and understand the EShop structure. If your data comes from multiple sources, requires complex transformations, or must be synchronized automatically, do not try to solve everything with one Excel import. In that case, it is better to design a separate data workflow and choose a tool built for it.