A WooCommerce shop often needs to display changing products in a consistent, useful layout. Editing every product listing separately is not a practical way to manage an archive, especially when products belong to several categories or the catalogue changes regularly. Elementor provides a reusable approach through its Product Archive templates.
An Elementor WooCommerce product archive template controls the shared presentation of groups or categories of products, while WooCommerce supplies the product information shown in that design. The workflow involves preparing the store, creating the archive layout, assigning display conditions, configuring the product listing and testing the result. It is also important to distinguish an archive from an individual product page, because the two templates serve different purposes.
What an Elementor WooCommerce Product Archive Is
An Elementor Product Archive template is a reusable Theme Builder site part for groups or categories of WooCommerce products. Instead of designing one fixed page for one fixed product, you create a layout that can be applied to relevant archive contexts, such as the shop or product-category views.
WooCommerce provides the changing product information, while Elementor controls the shared layout and styling. The archive should therefore be built around dynamic WooCommerce information. Product values can change from item to item, but the structure of the listing remains consistent. This makes the template suitable for repeated product content rather than a page representing one specific product.
WooCommerce must be installed for Elementor’s WooCommerce product and WooCommerce widget features to be available. The archive is a presentation system, not a guarantee that every third-party extension, theme or filtering setup will behave identically. The final result needs to be checked in the actual store environment.
Archive templates and dynamic WooCommerce information
When creating the reusable design, avoid treating product titles, prices, images or other values as fixed text belonging to a single item. The purpose of the template is to let WooCommerce provide the relevant information for each product appearing in the archive.
This distinction also helps with maintenance. A shared archive design can serve multiple products, groups or categories, while the content displayed in those positions changes according to the WooCommerce data and the archive context. Elementor supplies the visual structure; WooCommerce supplies the product-specific information.
Before You Create the Template
Begin by reviewing how the store is organised. Identify the shop and product-category contexts that need an archive design, then decide whether one broad template is sufficient. A single reusable design may be appropriate when the relevant archives should share the same presentation. Separate, narrower templates should be considered only when a genuinely different archive context requires a distinct design.
Prepare a backup or use a staging site before changing archive templates, display conditions or product-listing queries. An incorrect condition can affect shop and category pages site-wide. This is particularly important when the store also uses filtering, multilingual, membership, variation-related or other WooCommerce features. The available documentation does not establish a complete compatibility matrix for every possible combination, so the target site stack should be tested rather than assumed to be compatible.
Define the archive scope first
Write down which archive contexts the design is intended to cover before opening the builder. Consider whether the shared layout should apply to the shop, product categories or another relevant product taxonomy context. This makes condition assignment easier to review later and reduces the risk of creating several overlapping templates without a clear purpose.
The scope should describe where the layout belongs, not which individual product was used while designing it. Keep that distinction in mind when preparing sample content and when checking the finished archive.
How to Create a Product Archive Template in Elementor
In Elementor, begin from Templates > Theme Builder > Product Archive. This is the area used to create or manage the archive site part. Build the layout around the way products should be presented in a listing, using dynamic WooCommerce information instead of entering fixed product content directly into the reusable template.
Plan the repeated listing structure first. Product cards or repeated entries need a consistent visual arrangement, but the information in those entries should come from the relevant WooCommerce products. Supporting archive elements can be arranged around the listing so that the page remains clear across the contexts where the template will be used.
Keep this workflow focused on archive presentation. Do not use the archive as a substitute for widgets and content intended to design one individual product page. Once the layout has been reviewed in the builder, save or publish the template and then assign the conditions that determine where it becomes active. Avoid publishing broad conditions before checking the design in the relevant store context.
Build the reusable listing structure
Treat the archive as a shared design for multiple products. The visual loop should accommodate changing product information, while the overall structure remains stable. Dynamic data is especially important because fixed content would make the template appear to describe one product rather than a group or category.
At this stage, check the archive conceptually as well as visually: the listing should represent multiple products, and individual-product content should remain separate. Any assumptions about third-party features or compatibility must be verified on the actual website rather than transferred from Elementor’s documented template concepts.
Assigning Display Conditions Correctly
After designing the Product Archive template, use its Edit Conditions control to open Elementor’s Display Conditions editor. Select the intended shop, product-category or other relevant taxonomy scope. These conditions determine the archive contexts in which the design will appear.
Assigning conditions makes the site part live. A template without conditions remains a draft, so saving the design alone does not make it active across the store. A practical workflow is to start with the broadest scope that genuinely matches the intended design. Add narrower category or taxonomy-specific templates only when those contexts need a distinct layout.
Conditions should be treated as deployment settings, not as a minor final detail. Broad or overlapping conditions can cause an unexpected template to appear on an archive. Review the affected pages after assigning them, especially when more than one archive template is managed in the same site.
Verify scope and instances after publishing
Use the live or draft status as an initial indication of whether conditions have been assigned. Then check the Instances label in Elementor’s Products Archive management screen. It shows the specific instances where a product archive template is being used.
If an archive displays the wrong design, return to the conditions and compare the intended scope with the instances shown. Test the shop and relevant category pages before considering the deployment complete.
Product Archive Template vs Single Product Template
A product archive template controls a listing or archive view for a group of products. It can apply to a shop or product-category context and uses repeated, dynamic product information. Its purpose is to provide a common structure for multiple product entries.
A single-product template serves a different purpose: it designs the page for one individual WooCommerce product. Elementor’s documented single-product widgets include the product title, price, rating, short description, stock, add-to-cart, product metadata, product data tabs, images, upsells and related products.
The distinction is practical. Changing or assigning an archive template should not be treated as changing the individual product-page layout. Both page types need to be checked after an archive is published so that the listing appears in the intended places and individual products retain their separate template.
Use the right template for the page type
Use an archive template when the page must present repeated product listings for a shop, category or related archive context. Use a single-product template when the page must present one product’s information and purchase-related layout.
If a product page appears to have been replaced by an archive-like layout, inspect the template conditions and confirm that the individual product template still has its intended scope. These are separate workflows and should be tested separately.
Using Loop Grid for WooCommerce Product Listings
Loop Grid separates the repeated visual template from the query that determines which items appear. When the grid should display individual WooCommerce products, choose Products as the template type. When it should display product categories or other product taxonomy items, choose Product Taxonomy.
The selected template type must match the content being displayed. A product listing and a category listing are not the same content, even if both use a grid. After choosing the correct type, configure the available controls for columns, items per page and query settings according to the store’s catalogue and design requirements.
There is no universal number of columns or products per page established by the documentation. Treat these as store-specific choices to test. Query behaviour should also be checked with the site’s filtering, caching, theme and product setup. If the expected items do not appear, review both the query and the selected Loop Grid template type.
Products versus Product Taxonomy
Choose Products for individual product entries in the listing. Choose Product Taxonomy for product categories or other taxonomy items. This choice determines the kind of content the grid is expected to display.
Keep the visual loop template and the query as separate decisions. A suitable visual design cannot correct a query configured for the wrong content type, and a correct query does not by itself determine whether the archive presentation fits the store.
Pagination and Front-End Testing
Loop Grid provides pagination controls for the product listing. The documented options include numbered pages, Previous/Next, Numbers plus Previous/Next, Load on Click and Infinite Scroll. Loading can use a full-page reload or AJAX.
These are configuration choices, not universal performance or conversion recommendations. Test the selected mode with the store’s theme, plugins, hosting, filters, caching and product volume. Do not assume that AJAX or Infinite Scroll will improve the result without site-specific testing.
After publishing, check the shop archive, product-category archives, product-tag archives if used, and search or filtered results where relevant. Also open individual product pages. Test desktop and mobile presentation, product-card links, prices, stock or purchase controls, pagination behaviour and the absence of an unintended single-product replacement.
A practical archive QA checklist
Use the following checks before treating the archive as complete:
- Confirm that the intended archive template appears in every assigned context.
- Review the Instances information for unexpected or overlapping assignments.
- Confirm that the Loop Grid query displays the intended products or taxonomy items.
- Check that columns, items per page and pagination behave as configured.
- Verify product-card links, prices, stock or purchase controls where they are intended to appear.
- Open individual product pages and confirm that their separate layout remains active.
- Repeat the main checks on desktop and mobile.
Creating an Elementor WooCommerce product archive is a process of separating reusable presentation from changing product data. First define the archive scope, then build a dynamic Product Archive template in the Theme Builder. Assign display conditions deliberately, use the correct Loop Grid type, configure listing and pagination settings as store-specific choices, and verify every relevant front-end context.
The archive template manages groups of products; the single-product template manages one product page. Keeping those roles separate prevents many layout and condition errors. Because themes, extensions, filters and product setups vary, the final configuration should be tested on the target store rather than treated as universally compatible. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.