JoomShaper Arino - Joomla Template

How to Set Up JoomShaper Arino for a Joomla Online Store

JoomShaper Arino is not just a visual skin for a Joomla page. It is a ready-made store framework where the storefront design, catalog structure, cart, promo blocks, and page editing all work together. In this guide, we will look at how to approach the template as a real working project: what to check before installation, which package to choose, where to configure the header and modules, how to build the homepage, how to review product pages, and what to do if the demo does not match the preview.

This guide is written for a site owner, webmaster, or editor who is already considering the template and wants to understand whether it is a good fit for a real store. We will not repeat the short product summary that already appears above on the page. Instead, we will walk through the practical path: from a test installation to configuring the logo, menu, product areas, demo content, responsive behavior, troubleshooting, and comparing alternatives.

Special attention is given to the details that often get lost in standard reviews: the difference between Quickstart and the regular template package, the role of SP Page Builder Pro, Joomla module positions, EasyStore, demo images, updates, and safe edits through the built-in Helix Ultimate fields. If a feature depends on a specific package version, use this guide as a validation map, and check the exact version numbers and compatibility details in the developer's official sources.

What Arino Is Designed to Do and Where It Stands Out

Arino is primarily built for stores where product presentation matters just as much as the cart itself. The template gives Joomla a ready-made storefront: multiple homepage variations, product collections, promo sections, search, categories, cart, blog, and pages like checkout. This is useful when you need more than an empty theme and want a demo store you can study and then replace with your own products.

The template's strength comes from how it combines three layers. Helix Ultimate controls the site's core shell: logo, header, grid, menu, typography, and custom code. SP Page Builder Pro handles visual editing for pages and sections. EasyStore powers the commerce side: products, variants, orders, discounts, shipping, payments, and other store features. If what you need is a storefront with ready-made shopping logic, Arino gives you more than a typical general-purpose template.

Visually, the template is designed for a catalog with prominent product imagery. The included preview shows a store header, SKU search, categories, featured blocks, cart, large hero slider, product grids, and promotional sections. That layout works well for fashion, accessories, electronics, furniture, gifts, cosmetics, and similar niches where shoppers scan collections first and then move to the product page.

Arino is less convenient if you need a strict B2B catalog with no visual promotions, a marketplace with many vendors, a complex discount system, a separate vendor dashboard, or custom order logic. In those cases, the template can still work as the front-end storefront, but the business logic needs to be validated at the EasyStore level, through third-party extensions, and against your technical requirements.

Who This Template Fits and When Another Approach Makes More Sense

Before installing anything, it helps to define honestly what role the site needs to play. Arino works especially well when a store launches from a ready-made design and is then gradually filled with products, blog content, and promotions. If the team is prepared to replace the demo data with its own products and images, the template speeds up the launch and saves you from designing the store structure from scratch.

Good-fit scenarios

• A small or mid-sized Joomla store that needs ready-made storefront, catalog, product page, and cart layouts.
• A catalog where products should be presented through large images, curated collections, sliders, promotions, and new arrivals blocks.
• A project where the editor will update homepage sections through a visual builder instead of manually editing template files.
• A site where the header matters: search, categories, cart, account access, and a short marketing message all need to work together.
• A test launch where you first want to see a complete demo store scenario, then replace it with your own products and settings.

When to be more cautious

Arino does not solve every store requirement on its own. It gives you the design, page layouts, store-system integration, and a set of ready-made blocks, but it does not replace planning for logistics, taxes, payment methods, inventory management, or legal content. If your store depends on uncommon shipping methods, complex pricing rules, or integration with an external accounting system, first check whether EasyStore or separate extensions can handle that.

The template can also be overkill for a simple site with only a few products and a quote request button. In that type of project, a standard Joomla template, a few articles, and a contact form may be easier. Arino makes sense when you truly need a store storefront: categories, filters, product pages, cart, promotions, blog, and ongoing catalog management.

What to Check Before Installation: Server, Package, Demo, and Images

Preparation matters because Arino can be installed in two very different ways. Quickstart deploys a complete site with Joomla, demo data, the template, and extensions. The regular Template Pack installs only the template, without demo pages, modules, or store components. That difference shapes the entire workflow that follows.

Environment check

Start by reviewing the Joomla requirements and the JoomShaper documentation for your server: supported PHP version, MySQL, memory limits, execution time, upload size, cURL, and folder permissions. This is especially important for Quickstart because the package includes not just the template, but also demo content, extensions, and settings. If the server is underpowered, the installation may stall while creating tables or fail the system requirements check.

Practical minimum checklist before you begin:

• Set up a separate staging site or subdomain, especially if the store is already live.
• Create a fresh database or use a separate table prefix so the demo content does not mix with your existing site.
• Check folder permissions and make sure you can access the admin panel after installation.
• Create a backup of the files and database if you are not working on an empty project.
• Confirm which package you actually have: Quickstart, Template Pack, or a template update.

Quickstart or Template Pack

Choose Quickstart when you want a site that closely matches the demo and then plan to replace the content. It is the best way to study the Arino structure: where the header lives, which modules are used in the top bar, how the homepage is built, which pages were created in SP Page Builder, and where the store logic is connected. But Quickstart cannot be installed as a normal extension inside an existing Joomla site through the Extensions Manager because it contains an entire Joomla installation.

Choose the Template Pack for an existing site, but do not expect it to build the demo store for you. After installation, you will need to assign the template style manually, create or migrate pages, configure modules, positions, menus, products, categories, and store extensions. If you are not fully sure how the template is structured, install Quickstart on a staging site first and use it as a settings reference.

An important note about demo photos

JoomShaper's documentation specifically notes that demo photos may not be included in the package because of licensing restrictions. That is normal for commercial templates: instead of polished visuals, you may see placeholders. So do not assume the installation is broken just because the demo images differ from the preview. Prepare your own product photos, banners, logo, and promo graphics in advance.

Your post-installation check should include more than just the homepage appearance. Replace at least one demo product with your own product and a real image. That will immediately show whether Arino's grid works well with your image style, proportions, and title lengths.

Installation and the Initial Review Without Unnecessary Risk

The safest working path is to deploy Quickstart in a test environment first, study the structure, and then decide whether to move that build to the primary domain or recreate the settings inside an existing Joomla site. This reduces the risk of breaking a live store and helps you identify which modules are actually needed.

Installing Quickstart on a clean site

1. Download the latest Quickstart package from the developer's official source.
2. Extract the archive locally and upload the contents to the future site folder via SFTP or your hosting file manager.
3. Create a database and a user with full privileges for that database.
4. Open the domain or subdomain in a browser and go through the standard Joomla installer.
5. Do not use an obvious super user login. Set a unique username and a strong password.
6. After the installation completes, remove the installation folder, confirm access to the admin panel, and enable SEF URLs if that is part of your launch plan.
7. Open the front end of the site and check the homepage, menu, cart, search, a few product pages, and the blog.

After that, go to System and review the system information, folder permissions, and the list of installed extensions. If Joomla offers core or extension updates, do not click through everything blindly on a working site. Create a backup first and test updates on a staging copy, because the storefront depends not only on the template, but also on the builder, EasyStore, and modules.

Installing the Template Pack on an existing site

The standard template is installed through System - Install - Extensions. After installation, you need to assign it as the site style, review the Helix Ultimate settings, create menus, and publish modules into the proper positions. In this setup, do not expect ready-made catalog pages and demo sections. You will need to build them manually or copy them from a test Quickstart installation.

The initial validation looks like this:

• Check whether the correct template style is assigned as the default for the site or for specific menu items.
• Confirm that the homepage opens without PHP errors or a blank white screen.
• Check whether CSS and JavaScript are loading properly and whether the header and icons display correctly.
• Make sure the required modules appear in the header, menu, lower content area, and footer positions.
• Verify that the store pages, cart, and product pages work after EasyStore is enabled.

Post-Install Settings Map: Where to Go in the Admin Panel

After installation, do not start by changing every color, font, and section. First, understand which layers control the site. Arino has a Joomla layer, a Helix Ultimate layer, an SP Page Builder layer, and an EasyStore layer. If you mix them together without a plan, it is easy to end up in a situation where a product exists but does not display, a module is enabled but not assigned to menu items, or the header looks right on the homepage but breaks on internal pages.

Level one: Joomla template and style

In Joomla, check System - Site Templates and Site Template Styles. The key here is to confirm which Arino style is assigned by default and whether any individual menu items are still using another style. If the homepage looks fine but the product page looks different, the cause is often a style assignment or menu-based module assignment.

Level two: Helix Ultimate

In the Helix Ultimate settings, you typically review the logo, base colors, typography, presets, header options, menu, custom code, and style compilation. This is especially important for Arino because of its complex top area: logo, product search, categories, account, cart, and promo text all need to function as one coherent block.

Level three: SP Page Builder

Arino's homepage and key pages are built with SP Page Builder Pro. The documentation states that the Home Page uses addons in the component area rather than modules. That means some sections need to be edited in the page builder interface, not in the Joomla Module Manager. If you are looking for a banner or product block as a module and cannot find it, check the relevant page in SP Page Builder.

Level four: EasyStore

EasyStore handles products, variants, discounts, orders, shipping, payments, analytics, languages, and checkout logic. The template displays that data beautifully, but the products and business rules still need to be configured inside the store system. That is why setting up Arino without checking EasyStore is incomplete: the visual layer may be ready while the real purchase flow is still untested.

Header, Search, Categories, and Cart: What Matters Most in Arino

Arino's header is more than basic Joomla navigation. According to JoomShaper's documentation, it is built as a custom Top Bar and Header: the logo is changed through Helix Options, position top1 is used for EasyStore product search, top2 contains the login and cart modules, menu-left is reserved for EasyStore categories, the main menu uses Helix Ultimate MegaMenu, and menu-right can display a short message such as shipping terms.

Because of that, after installation you need to check more than the general Menu area. In a real store, the header controls the shortest path to a product: the customer searches by SKU, opens a category, checks the cart, goes to the account area, and sees a promo message. If even one of those elements is not assigned to the correct position, the top bar loses its purpose.

Practical header review

1. Open the Helix settings and replace the logo with a test file that has a reasonable height.
2. Check the product search module in position top1 and make sure it searches real products rather than demo placeholders.
3. Check position top2: the login module should not overlap the cart, and the cart should open after a product is added.
4. Review menu-left with the EasyStore categories and confirm that the categories lead to real pages.
5. Review the main MegaMenu. It is usually better to remove or hide unnecessary demo items before launch.
6. Replace the promo text in menu-right with a real store message or disable the block if the offer details are not ready yet.

After each change, clear the Joomla cache and your browser cache if you are still seeing the old header version. For testing, open the homepage, a category, a product page, the cart, and the blog. The header should feel consistently managed across all key store pages, otherwise customers may lose access to search or the cart at an important step.

Homepage and Product Sections: How Not to Break the Demo Logic

Arino's homepage is built around a retail rhythm: a large hero slider, featured products, top viewed items, promo tiles, new arrivals, curated collections, deals, and other store-focused sections. The official description lists homepage variations for a general store, fashion, electronics, furniture, and organic products. These are not just different visuals. They represent different selling scenarios.

Before editing, choose one variation as your base. A common mistake is to mix sections from different home variations without understanding what products and modules they were designed for. A fashion-style layout may depend on bold promotional graphics and a social gallery, while electronics may center on gadgets, categories, and newsletter signup, and furniture may rely on large cards and a product slider. If you move blocks around mechanically, the page becomes visually noisy and harder to maintain.

How to edit the homepage safely

1. Make a copy of the page or create a test menu item for experiments.
2. Open the page in SP Page Builder and rename the sections with clear internal labels.
3. Start by replacing the images and text in the hero block without changing the grid.
4. Then replace the product sources: featured, trending, deals, and category sections should pull from real products.
5. Check product title length, price, old price, discount display, and the call-to-action button.
6. Remove demo sections that do not match your actual catalog.
7. After saving, check desktop, tablet, and mobile widths, because product blocks often break lower on the page rather than in the first screen area.

If you need a quick way to understand why a block is not showing products, go from data to output: the product is published, the category is assigned, the image is uploaded, the price is set, the module or addon points to the correct source, the page is saved, and the cache is cleared. That sequence is faster than changing the design at random.

How to choose product sections

For a store with a limited catalog, it is usually better to keep fewer blocks but make them meaningful: a hero with the main offer, featured products, categories, one promo zone, and a blog. For a store with frequent updates, you can add top viewed items, trending products, new arrivals, and multiple homepage scenarios. The key is that every section should answer a shopper's question: what is new, what is a good deal, what is popular, and where should I go next?

Catalog, Filters, Product Page, and the Checkout Scenario

For a shopper, the template is valuable not because it has many settings, but because it makes products easy to find and the next step obvious. Arino is positioned as an eCommerce template with a dedicated product listing page, filtering, product pages, product view variations, offer popup, deals, and a ready-made cart flow. These pieces need to be checked as one connected chain, because a polished homepage does not guarantee a working store.

Catalog and filters

Start with a product category. Check whether products appear in the listing, whether filters by price, category, and brand work, and whether you get empty results in places where products should exist. If a filter shows nothing, first verify the product data itself: category, brand, price, publication status, stock, and availability. Only after that should you look for a template-level issue.

Product page

The product page should display the title, images, price, variants, description, add-to-cart button, and supporting blocks. In your test product, intentionally use a long title, multiple images, a size or color option, and a medium-length description. That will show how Arino behaves with real data rather than ideal demo content.

Cart and checkout

Test the path from product to checkout manually. Add a product from the catalog, then from the product page, open the cart, change the quantity, apply a test discount if one is configured, go to the checkout page, and review the fields. You do not need to connect live payment methods on a staging site right away, but you do need to confirm that the checkout design holds together, required fields are clear, and validation errors are visible to the user.

Also test different product types. One item may be simple, while another may include size, color, or package variants. If your store includes different shipping rules, limited stock, or discounts, create one test product for each case. That will show where the template's role ends and where store-system configuration begins. Arino is responsible for presentation and flow, but accurate pricing, stock, shipping, and order status depend on the store engine and its rules.

Do not ignore empty states. In a real store, a shopper may open an empty category, apply an overly narrow filter, remove an item from the cart, or make a mistake in a required checkout field. Each of those states should show a clear message rather than a blank screen. If a system message feels out of place for your store, update it through Joomla language overrides or extension settings, not by editing files directly.

A good Arino test for a store is not a homepage screenshot. It is a complete trial path: category -> filter -> product page -> cart -> checkout -> result message.

Practical Example: Building a Storefront for an Accessories Shop

Let us walk through an example that can be adapted for fashion, electronics, gifts, or home goods. The goal is to create a homepage with a clear header, a hero promotion, product selections, working categories, and a verified cart path. This does not replace full store configuration, but it gives you a practical minimum after which the template can already be judged against real data.

Goal

You need to set up a starter storefront for a small accessories shop: bags, glasses, watches, and shoes. The homepage should lead shoppers quickly to categories, showcase several products, offer a seasonal promotion, and keep the cart accessible on internal pages.

Preparation

• Quickstart is installed, or the Template Pack is prepared with the required extensions.
• Three to four product categories and at least eight to twelve test products with images have been created.
• EasyStore has a base currency, prices, and product availability configured.
• A logo has been added in Helix, and the header height has been checked.
• A test copy of the homepage has been created in SP Page Builder.

Steps

1. Choose the homepage variation that is closest to your catalog. For accessories, the fashion variation is a good starting point because it is built around visually driven collections.
2. Replace the hero image and text with a specific promotion. Do not use generic wording. Name a category or a seasonal collection.
3. Check the All Categories block in the header and match it to your EasyStore categories.
4. Configure featured products to show the items that should appear first on the storefront.
5. Keep one deals block only if you have real discounts, or disable it for now so you are not promising a promotion that does not exist.
6. Check one product page: image, price, add-to-cart button, description, and the path back to the category.
7. Add a product to the cart and confirm that the cart indicator in the header updates.
8. Open the checkout page and make sure the form does not conflict with the template width or hide important fields.

Review

Open the site as a guest and repeat the shopper journey. First find a product through a category, then through search, then through featured products on the homepage. If a user can reach the product in three different ways and sees a consistent header, cart, and product page each time, the basic storefront is configured correctly.

A useful detail

If a product block on the homepage looks empty, do not change the design right away. Check product publication status, category, stock, the addon or module data source, the menu item, and the cache. In most cases, the cause is not that the template "doesn't work." It is that a specific section points to a different product set or the demo data has not been replaced yet.

Practical Use Ideas for Different Store Types

The same template can be used in very different ways if you do not copy the demo literally. Below are several scenarios based on confirmed Arino capabilities: multiple homepage variations, product collections, filters, product pages, deals, popup features, blog, a search-driven header, and EasyStore. This is not a decorative list. These are workable storefront patterns.

Fashion and accessories store

Use a fashion-oriented rhythm: a large seasonal hero, a new arrivals selection, a wishlist/deals block, visual category cards, and a blog with curated collections. The test is simple: within two clicks, a visitor should be able to move from the hero or featured products to a product page and add the item to the cart.

Electronics store

Put the emphasis on search and categories. For gadgets, SKU, filtering, price, brand, and quick access to popular products matter. Use the hero slider not for an abstract banner, but for one clear promotion: a bundle, a category, or a new product line.

Furniture and home goods

For furniture, large images, a card slider, and a category grid work well. Do not overload the homepage with too many small products. It is better to show two or three strong zones where the shopper sees the style, size, material, and the path to the category. Check the mobile version carefully, because long furniture names and wide photos often need additional adjustment.

Organic products or cosmetics

For organic goods, trust and repeat purchases matter. Use a softer color scheme, featured and trending blocks, a blog with recommendations, and clear shipping terms in the header. If the demo includes Instagram or a gallery, do not leave it empty. It is better to hide the block temporarily than to show irrelevant placeholders.

Safe Improvements: CSS, Text, Positions, and Rollback

Arino allows careful improvements without editing the Joomla core, the template itself, or the extensions. The official documentation notes that Helix Ultimate and SP Page Builder include visual settings, while custom CSS, JavaScript, meta tags, and tracking code can be added through built-in custom fields. In practice, that means small changes are best made through template settings rather than by editing package files.

A small CSS tweak for a promo section

The example below is safe because you first add the class arino-promo-strip yourself to the needed section or module in the builder settings, if that field is available in your version. The CSS does not modify the core and does not affect the whole site. It only makes the buttons inside the selected promo section more noticeable.

.arino-promo-strip a,
.arino-promo-strip .sppb-btn {
  border-radius: 3px;
  font-weight: 700;
  letter-spacing: 0;
  padding: 12px 22px;
}

.arino-promo-strip a:hover,
.arino-promo-strip .sppb-btn:hover {
  transform: translateY(-1px);
}

Paste this snippet into the custom CSS field in Helix Ultimate settings or into whichever built-in CSS area your site uses. After saving, clear the cache and review only the section where you assigned the class. If the result is not right for you, remove both the CSS and the section class. That is a complete rollback.

Language and text changes

Text such as the promo message in the header, menu item names, and section labels is best changed through modules, menus, SP Page Builder, or Joomla language overrides. Do not edit strings directly inside template files if they can be replaced through built-in tools. File-level edits are easy to lose when the template is updated.

Module positions and menu assignments

If you need to show an extra block only on the catalog page, use Joomla's built-in module assignment by menu item. This is especially useful in Arino: the same module may make sense on a product category page but feel unnecessary on the checkout page. Always review the position, module order, access level, language, and the menu assignment tab.

Reviewing the Result Before Launch

Before publishing the store, it is not enough to visually inspect the homepage. A store template should be judged by the full chain: the design loads correctly, products display, filters work, the cart keeps items, checkout shows the correct fields, the mobile header does not cover content, and demo images have been replaced with properly licensed assets.

Front-end review

• The homepage opens without visual jumps or empty demo areas.
• The header keeps search, categories, account access, and cart visible on all key pages.
• The catalog shows real products, and filters do not return empty results without a reason.
• The product page handles long titles, multiple images, and product variants properly.
• The cart updates quantities and does not lose items when moving between pages.
• The checkout does not contain unnecessary demo fields and displays correctly on mobile.
• The blog or informational pages do not look like an unrelated design inserted into the store.

Admin-side review and support readiness

Make sure the editor understands where to update the homepage: which sections live in SP Page Builder, which blocks are Joomla modules, where EasyStore products are managed, and where the header is configured. A strong launch is not only a polished site, but also a clear operating guide for the person who will update products and promotions after handoff.

Also review updates. JoomShaper's documentation recommends checking the changelog and making a backup before major updates. That is especially important for a store: changes to the template, page builder, or store component can affect checkout, product pages, and module display.

Multilingual Setup, SEO, and Performance: Checks Worth Doing Before Publish

Arino is described as translation ready and retina ready, and EasyStore includes multilingual capabilities. But that does not mean a multilingual store appears automatically. In Joomla, language is tied to menus, modules, articles, products, aliases, and system strings. If you are launching the store in two languages, configure the language structure on a staging copy first, and only then start copying pages and products.

Multilingual storefront

Do not check only the translated text on the homepage. For a store, product titles, categories, checkout fields, emails, URLs, the search module, cart, error messages, and blog content all matter. If one language shows a correct product page while the other leads to an empty page, the cause is often a menu issue or a language-specific module assignment. In Joomla, multilingual behavior should always be tested through the full customer journey in each language, not through a single translated section.

What to check first

• Each language has its own menu items and a correct default home item.
• The header, category, search, and cart modules are assigned to the right languages, or to all languages if that is the intended setup.
• Products, categories, and promo sections do not mix languages inside the same block.
• Checkout shows clear messages and does not leave demo strings in places where the customer enters data.

SEO review without making ranking promises

A template can help with structure, speed, and clean markup, but it does not guarantee search visibility. Before launch, check the basics: page titles, meta descriptions, SEF URLs, alt text on product images, the absence of empty demo pages, correct canonical URLs if your site uses them, and indexation for important categories. For the blog, it helps to choose several topics in advance that support the products: collections, tutorials, comparisons, care guides, sizing, materials, and answers to common buyer questions.

Do not turn the homepage into a pile of repeated keywords. Arino works better with a clear structure: the first screen explains the offer, categories lead into the catalog, featured blocks show real products, the blog answers questions, and the technical SEO setup does not compete with the shopping experience.

Performance and image weight

A visually rich store is easy to overload with banners and product cards. Before publishing, check hero image sizes, product photo compression, lazy loading, Joomla cache, minification conflicts, and slider behavior. If filters, the cart, or interactive elements stop working after optimization is enabled, roll back the questionable setting and re-enable optimization one group at a time: images first, then cache, then CSS and JS.

How to test without creating chaos

1. Capture a baseline state without aggressive optimization.
2. Optimize product and banner images.
3. Enable caching on a staging copy and test the cart, search, filters, and checkout.
4. Only after that should you try file combining or minification, if your site uses it.
5. After each step, verify the result both as a guest and as an administrator.

For a store, the most dangerous situation is when the homepage gets faster but the cart or checkout starts showing stale data. That is why performance testing needs to happen alongside functional testing. Optimization is only successful when the customer journey still works end to end.

If Arino Looks Wrong: Common Symptoms and How to Diagnose Them

Joomla template issues often look similar: the page is blank, a module does not display, the header is broken, products disappear, or the demo does not resemble the preview. But the reasons are different. Below is a practical troubleshooting guide for this specific type of setup: Quickstart, Helix Ultimate, SP Page Builder, EasyStore, modules, and positions.

Quickstart hangs or fails to install

Symptom: the installer gets stuck for a long time while creating tables, shows a server requirements error, or never reaches the final message. A likely cause is insufficient PHP limits, a weak environment, database issues, or unsuitable local server settings.

Check the PHP requirements, memory, execution time, upload size, and database settings. If you are installing locally, make sure Apache and MySQL were restarted after changing the parameters. If you do not manage the server yourself, send the requirements to your hosting provider and do not try to work around the error by editing random files.

The demo installed, but the photos are missing

Symptom: the structure looks like the demo, but the polished images have been replaced with placeholders. The reason is usually not a failed installation. The developer explicitly notes that demo photos may be excluded from the package because of licensing.

The solution is to replace the images with your own assets. Check the hero area, product cards, promo tiles, blog, and gallery. If you do not have content yet, temporarily hide sections where placeholders hurt trust in the store.

The header does not show search, categories, or cart

Symptom: the logo is there, but search, cart, categories, or promo text is missing. In Arino, this is most often tied to module positions: top1, top2, menu-left, menu-right, and the main Helix menu.

Check whether the modules are published, assigned to the correct menu items, set to the right language, visible for the right access level, and placed in the correct position. If a module appears on the homepage but disappears on the product page, review the menu assignment tab.

The homepage is not edited where you expect it to be

Symptom: you change modules, but the hero or product section does not change. The Arino documentation states that the Home Page uses addons in the component area rather than modules. That means part of the content has to be edited in SP Page Builder.

Open the relevant page in the builder, find the section by its text or images, make a small change, and check the result on a staging copy. If the change does not appear, clear the Joomla cache, clear the browser cache, and confirm that you are editing the page assigned to the current menu item.

Products do not appear in featured or deals blocks

Symptom: the block is there, but it shows no products or the wrong ones. A likely cause is the section's data source, product publication status, category, stock, price, filtering, cache, or demo settings that have not been replaced yet.

Follow the chain: the product is published, the category is assigned, the image exists, the price is set, the product is available, the section points to the correct category, the page is saved, and the cache is cleared. If the same product appears in the catalog but not on the homepage, the issue is almost certainly in the configuration of that specific section or its data source.

The page layout changes after an update

Symptom: after updating the template or extensions, spacing, cards, the header, or checkout changes. Before updates, you should always create a backup and review the changelog, because Arino depends on several layers: Joomla, Helix Ultimate, SP Page Builder, and EasyStore.

If the problem has already happened, compare the staging copy with the working version, disable custom CSS, check overrides, cache, and extension versions. Roll changes back only from a backup, not by manually deleting files, unless you clearly understand which layer changed.

Arino Video: What to Watch Before Recreating the Settings

JoomShaper provides a video tied to Arino and shown on the product page. It is useful not as a standalone promo piece, but as a visual reference for which blocks should appear in the demo: homepage variations, product sections, store pages, and the overall storefront layout. Watch it after installing Quickstart and compare it with what you see on your staging site.

While watching, keep a checklist nearby: header, hero, featured products, categories, deals, product page, cart, checkout, and responsiveness. If the video shows a block you do not have, first check the demo package, the page in SP Page Builder, published modules, and whether the demo content was replaced. Do not treat the video as a guarantee that a specific feature exists in your version. Verify exact details against the documentation and changelog.

When JoomShaper Arino Is a Strong Choice

Arino is worth using if you need a Joomla store template with ready-made visual logic: a header with search and cart, product collections, multiple homepage variations, product pages, deals, blog, checkout pages, and editing through the JoomShaper stack. It is especially useful when you are ready to start from Quickstart, understand the demo structure, and then replace it with your own products, images, and store terms.

If the project requires unique business logic, complex integrations, a non-standard checkout, or complete design freedom without a built-in eCommerce structure, compare Arino with alternatives first and validate the store component on a staging site. But for launching a visually rich storefront on Joomla quickly, the template gives you a clear starting foundation.

Once your staging site, backup, product list, and review plan are ready, you can download JoomShaper Arino and deploy it in a safe environment. After installation, walk through the full shopper journey: homepage, category, filter, product page, cart, and checkout. That path will show whether the template fits your store, not just whether the first screen looks good.