---
title: Add Product Tabs to Selected BigCommerce Products
description: "Create one reusable product-information tab, select the BigCommerce products that should receive it, and publish it without copying the same content into every product description. A product tab is a **content item** with **Insert as a tab** enabled. It can…"
url: "https://prikid.app/docs/how-to-add-a-new-tab-next-to-the-product-description-tab-on-particular-product-pages-in-a-bigcommerce-store/"
updated: "2026-10-13"
category: Creating and Targeting Content
tags:
  - tab
---

# Add Product Tabs to Selected BigCommerce Products

Create one reusable product-information tab, select the BigCommerce products that should receive it, and publish it without copying the same content into every product description.

A product tab is a **content item** with **Insert as a tab** enabled. It can contain specifications, care instructions, sizing information or another shared layout. Changes to that item apply to the products assigned to it when saved.

Before you start, install PRIKID.APP in your BigCommerce store and check that its storefront script is available. Automatic tab insertion depends on a recognized product-page tab or accordion structure. Custom themes and modified templates need individual verification. These steps do not establish native multi-storefront or headless/Catalyst support; ask support to confirm the intended storefront and integration first.

Click or tap any screenshot to enlarge it. Use the viewer’s zoom and pan controls for small labels. Sample names, products and content illustrate the controls; replace them with your own values.

## 1. Create a reusable content item

1. Open PRIKID.APP and select **Size charts and content items** on the dashboard.
2. Click **Add new content item**. To update a reusable tab, open its existing item instead.
3. The editor follows **Selection rules → Content → Display options**. A product tab uses this workflow rather than the separate Popups tab.

[![Current PRIKID Size charts and content items dashboard with Add new content item, Specification tab, Published and Products count columns.](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-dashboard-current.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-dashboard-current.jpg)
Current content-items dashboard and Add new content item. The saved Specification tab has a Published checkmark but zero matching products; publication alone does not prove storefront display.

## 2. Select the products and check matching

In **Selection rules**, choose the product, category, brand or text conditions that identify the intended products. Click **Preview** and check the actual product names and SKUs. Confirm that intended products are included and unintended products are excluded before publishing.

[![Specification tab Selection rules using a category or a product-name AND group, with Preview, AND and OR controls.](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-targeting-current.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-targeting-current.jpg)
Current rules for the sample Specification tab. The category is one OR branch; the two name conditions form an AND group. Its Preview currently returns no products, so this is a configuration example rather than a working-match demonstration.

For condition choices, AND/OR groups, category handling and stale catalog checks, follow [doc #6381: Target BigCommerce Products with Rules and Conditions](https://prikid.app/docs/creating-rules-to-filter-products-according-to-conditions/). An empty Preview needs a targeting or catalog check before theme troubleshooting. Matching Preview does not test whether the theme can insert or open a tab.

## 3. Build the tab content

1. Open **Content**. Add the blocks you need: **Text & Video**, **Image**, **Table**, **Divider** or **Google Sheet**. You can also start with an example layout.
2. Replace sample text, images and measurements; remove unused blocks. Keep the content appropriate to every product selected by the rules. Create a separate item when a different product group needs different information.
3. Use the Content editor’s **Preview** to inspect the layout. Check image clarity, readable tables and links, then continue to **Display options**. This Preview checks the content, not live tab placement or theme interaction.

[![Current content editor with sample table, text and image blocks, all five content-block icons, Examples and Preview controls.](https://prikid.app/wp-content/uploads/2026/10/prikid-content-editor-loaded-icons.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-content-editor-loaded-icons.jpg)
Reused current content-editor screenshot with all five block controls loaded. The sizing table and image placeholder are examples; a product-information tab can use the same blocks for other content.

## 4. Choose tab display and its shopper-facing title

1. Enter a useful **Content item name**, such as “Care instructions — cotton products.” This is the internal dashboard name.
2. Under **Display mode**, select **Inject the content item directly into a product page**.
3. Enable **Insert as a tab**, then enter the shopper-facing **Tab title**, for example “Care instructions” or “Specifications.”

[![Current tab Display options with Content item name Specification tab, Publish enabled, direct injection mode, Insert as a tab, Tab title Specification, --last-- placement and Save & Publish.](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-display-current.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-display-current.jpg)
Current Display options for an existing tab: direct injection, Insert as a tab enabled, shopper-facing Specification title, Publish? and Save & Publish. These saved controls were inspected without changing the item.

**Use both modes** can combine the injected tab with a link/button that opens the same content in a popup; keep Insert as a tab enabled for the injected part. The popup-only mode does not create a product tab. With Insert as a tab off, direct injection follows the inline-content placement workflow instead. Use [Display a Size Chart Directly on a Product Page](https://prikid.app/docs/how-to-inject-a-size-chart-into-a-product-page-content-directly/) for that setup and custom placement details.

On a compatible responsive theme, the same content may appear as an accordion section on mobile. Verify the actual desktop and mobile presentation; the app setting alone does not guarantee a particular theme layout. If several matching items use the same Tab title, their content can be combined into one tab. Use distinct titles when you need separate tabs, and inspect overlapping rules when unexpected content appears together.

## 5. Choose where the tab appears

Use **Insert before a tab with a matching title** to position the new tab relative to the theme’s existing tabs. This field controls tab order, not an arbitrary location elsewhere on the product page.

[![Close view of Insert as a tab enabled, Tab title Specification and Insert before a tab with a matching title set to --last--.](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-position-current.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-tabs-tab-position-current.jpg)
Close view of the current tab-title and placement controls. The sample uses the literal `--last--` value; keep the double hyphens when entering a predefined value.

- `--last--`: append the new tab at the end of the recognized tab set. This is the simplest starting point.
- `--first--`: insert it at the beginning. Insertion order does not guarantee it will be the initially active tab.
- **An existing title**, such as `Reviews`: insert before a tab whose title matches that text. Use the title actually visible in your theme and storefront language. Title matching can use part of a title, so ambiguous text needs a live check.
- **A number**, such as `2`: insert before the tab at that position, counting from 1. Theme layout and other injected items can affect the resulting order.

The suggestion `[Another Tab Title]` is a placeholder, not a real target title. If title matching finds no suitable existing tab, the standard insertion path appends at the end; a theme-specific integration may behave differently. If order is wrong, first try `--last--` and verify the actual tab set, then use a real title or position. Do not use this field to repair a missing tab container.

## 6. Save, publish and verify on the storefront

1. With **Publish?** off, the action is **Save as draft**. A draft does not display on the storefront.
2. When content, targeting and display settings are ready, enable **Publish?** and click **Save & Publish**. Resolve any validation or publishing-limit message shown by the app.
3. Reopen the saved item and confirm its rules, content, display mode, Insert as a tab, title and placement. Review Selection rules → Preview again. The dashboard’s Published and Products count columns are useful checks, but a nonzero count still does not prove theme insertion.
4. Open the actual URL of a matching product on the intended storefront and reload it. Find the new title, click it and confirm the expected content becomes visible. Switch to the original Description and Reviews tabs and back to check that they still work.
5. Repeat at desktop and mobile widths. On mobile, check the tab or accordion heading, tap interaction, images, links and table overflow. Test another included product and an excluded product. For Use both modes, also test the popup link/button separately.

Saving without publishing, an unsaved display change, matching Preview and Content Preview are separate states. None replaces a real product-page test. For secondary storefronts, confirm the destination URL rather than assuming a Preview link targets the correct channel; ask support to verify catalog/channel coverage and script integration.

## 7. If the tab is missing: checks you can do yourself

- **Saved configuration:** confirm the correct item has content, is published, uses direct injection or both modes, and has Insert as a tab enabled with a meaningful title. Check any publishing message.
- **Matching:** confirm the exact product appears in Selection rules → Preview. If it does not, use [doc #6381](https://prikid.app/docs/creating-rules-to-filter-products-according-to-conditions/) before changing the theme.
- **Storefront:** check the correct product URL, store and active theme. Compare a working product with the affected one; different product templates can have different structures.
- **App enablement:** open **App → Settings → Main settings** and confirm **Enable the app?** is Yes. Link/button default settings below it do not control the product-tab title or order.

[![PRIKID Main settings showing Enable the app and default link title, button appearance, CSS classes and inline style.](https://prikid.app/wp-content/uploads/2026/10/prikid-placement-settings-current-1.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-placement-settings-current-1.jpg)
Reused current Main settings screenshot. Enable the app? controls storefront availability; the Link/button defaults below it belong to the popup trigger, not tab placement.

Open **App → Settings → Script installation** and review the installed script in BigCommerce Script Manager. The app normally installs it automatically; the current tab offers **Reinstall the script** if it is absent. Check first and avoid duplicate scripts. If a script is present but blocked or failing, record the error and ask support instead of repeatedly reinstalling.

[![Current PRIKID installation guidance with the Script Manager illustration, explanation of automatic installation and Reinstall the script control.](https://prikid.app/wp-content/uploads/2026/10/prikid-placement-script-installation-current-1.jpg)](https://prikid.app/wp-content/uploads/2026/10/prikid-placement-script-installation-current-1.jpg)
Reused current Script installation guidance and Reinstall the script control. The embedded Script Manager picture is the app’s own illustration, not a fresh capture of today’s BigCommerce admin navigation.

Reload the live page after a saved change. A consent tool, script blocker, stale theme assets or a script error can prevent the widget from running. Ask a developer to check execution if needed; a script tag present in the page, especially one rendered as a non-executing type, is not proof that it loaded successfully. Do not disable consent or security controls as a troubleshooting shortcut.

## 8. Theme structure, hidden tabs and blocked clicks

### No recognizable tab or accordion structure

Automatic insertion extends a recognized existing tab/accordion structure and its content area. A customized theme can remove the containers, rename classes, change nesting, hide the whole section or replace the usual interaction code. A description displayed as a plain block is not automatically a tab set. Some late-rendered structures also need specific integration. Changing the Tab title or order cannot create a missing theme structure.

Support history includes themes without a usable tab container and later store-specific adjustments that displayed content. Those cases do not establish universal compatibility for that theme, or prove that a separate interactive tab was created in every case. Send the current theme/version and product URL for assessment. Follow [Custom Size Chart Placement and Theme Troubleshooting](https://prikid.app/docs/how-to-place-a-size-chart-link-elsewhere/) for the detailed placement/theme checks instead of copying a generic theme snippet here.

### The tab exists but is hidden or cannot be clicked

- If the title or panel is hidden, inspect its parent containers and responsive CSS as well as the tab itself. Hidden visibility, zero opacity, collapsed height, overflow and mobile-only rules can conceal otherwise inserted content.
- If the title is visible but clicks do nothing, check for an overlapping element, even an invisible one. Historical support identified a social-widget overlay covering tabs. The current cause must be reproduced; removing a social widget is not a general fix.
- A theme developer can inspect stacking, pointer-events, click handlers and browser errors. Check whether the original theme tabs also fail and whether the problem changes on mobile. Avoid broad z-index or site-wide tab/button CSS changes.
- If a CSS change appears ineffective, inspect the active stylesheet actually loaded by the storefront and its cache. Saving a theme source file alone does not prove the browser received the rule.

When the saved configuration and matching are correct but insertion, visibility or interaction still fails, contact PRIKID support or your theme developer. A custom integration may need assessment, a compatible theme structure, scoped CSS or script work. An inline-content placement or popup can be an alternative after review; these are different presentations, not proof that automatic tabs work. Confirm feasibility and any adjustment scope or cost with support.

## What to send support

Use **Contact PRIKID support** in the app or [open a support ticket](https://support.prikid.app/new-ticket). Include the store and affected product URLs, item name, product name/SKU, theme name/version and customizations, intended title/order, matching Preview and Display options screenshots, and desktop/mobile screenshots. Say whether the tab is absent, hidden or visible but unclickable, whether original tabs work, and which products/storefronts are affected. Include the time and relevant browser error if available. Do not send passwords or API keys.