Which e-commerce components for Joomla do you work with?

Most often VirtueMart and HikaShop, but other options are possible depending on the component's data structure.

How are product variations, like size or color, transferred?

The variation structure in 1C/BAS is mapped to how it's built in the specific component, this is worked out separately.

Can we sync just orders, without the catalog?

Yes, the exchange is configured around specific needs, just order transfer can be connected.

What if our store has non-standard customizations?

This is accounted for when reviewing the data structure, additional logic is added to the exchange if needed.

How much does the integration cost?

Cost depends on the component chosen, catalog size, and non-standard customizations, calculated individually on request.

1C / BAS integration with Joomla: data exchange for a VirtueMart or HikaShop store

Q: Do we have to tell you which component we use?

Yes, an exchange built for one component won't work for another without being rebuilt.

If your Joomla store runs on VirtueMart, HikaShop, or another e-commerce component, we set up catalog, stock, price, and order exchange with 1C or BAS for the specific component you’re using.

Discuss the integration Pricing on request, depends on the e-commerce component chosen and catalog size

Why isn't a Joomla exchange as simple as it sounds?

Joomla itself is a CMS with no built-in e-commerce, so a store on it always runs through a separate component, VirtueMart, HikaShop, or another one. Each component has its own data structure, its own category and attribute logic, which means an exchange built for VirtueMart simply won’t work on HikaShop without rebuilding it.

That’s why the first question we ask before starting isn’t “which Joomla version are you on”, it’s “which component do you use for your store”. The answer shapes the entire approach to the integration.

What syncs

Product catalog

Products are exported from 1C/BAS into the structure of your chosen e-commerce component, with correct category and field mapping.

Stock and prices

Regular stock and price updates from the accounting system, on a schedule, so the site catalog always matches the actual warehouse.

Attributes and product variations

If products have variations (size, color, etc.), we map the variation structure in 1C/BAS to how they're built in your component.

Orders back into 1C/BAS

New orders from the site land in the accounting system automatically, with full contents and customer data.

Customization for your component

If the component's standard logic isn't enough for correct syncing, we add the logic your specific store build needs.

The order of work

Stage 1. Identifying the component and version. We find out which e-commerce component your store runs on (VirtueMart, HikaShop, or another) and which Joomla version is in use.

Stage 2. Reviewing the data structure. We look at exactly how categories, attributes, and product variations are organized in your component.

Stage 3. Setting up the exchange. We connect catalog, stock, price, and order syncing for your specific structure.

Stage 4. Testing on a real catalog. We verify the exchange on actual products and orders before switching to permanent operation.

Why it's worth trusting us with this

Do you work with every e-commerce component for Joomla?

We most often work with VirtueMart and HikaShop as the most common options, but we consider others too, the key is understanding the data structure of the specific solution.

What if our Joomla store is built non-standard, with custom modifications?

That's a normal situation for Joomla stores, which is exactly why we always start by reviewing your specific implementation, rather than offering a generic exchange template blindly.

FAQ

Most often VirtueMart and HikaShop, but we can consider other options too, it all depends on the specific component's data structure.

Yes, that's the first thing we need to know, an exchange built for one component won't work for another without being rebuilt.

We map the variation structure in 1C/BAS to how it's built in your component, this gets worked out separately during the review stage.

Yes, the exchange is configured around specific needs, if the catalog is already handled another way, we can connect just order transfer.

This is accounted for when reviewing the data structure, we add whatever logic your specific build needs if necessary.

Cost depends on the component chosen, catalog size, and any non-standard customizations, calculated individually, on request.

Tell us about your Joomla store

Let us know which e-commerce component you use (VirtueMart, HikaShop, or another) and which 1C/BAS configuration you have, we’ll suggest an approach for your case.

1C/BAS integration with Joomla: exchange for VirtueMart and HikaShop

Joomla has no built-in e-commerce, so a store on this CMS always runs through a separate component, most often VirtueMart or HikaShop. Each has its own category, attribute, and product variation structure, which is why a 1C Joomla integration always starts with identifying the specific component, not the CMS in general.

An exchange built for a specific e-commerce component

After identifying the component, we set up syncing for the product catalog, stock, prices, attributes, and variations, as well as transferring orders from the site back into 1C or BAS. If a component’s standard logic isn’t enough for a correct exchange, we add whatever logic your specific store build needs.

Why this is our approach

An exchange built for VirtueMart won’t work on HikaShop without rebuilding the data structure, these are two different systems with their own category and product logic. That’s why, before any estimate, we clarify exactly which component your store uses, and build the technical solution around it.

If you want to understand the scope of work for your specific Joomla store, describe your component and 1C/BAS configuration in the inquiry on this page.