Direct answer
To add one extra information tab to a WooCommerce product, save a short title and safe content on that product, then add one uniquely keyed entry through WooCommerce's native product-tabs filter. Return the original tab array unchanged when either field is empty or the key already exists. Do not copy the product template, create a JavaScript tab system, or rewrite Description, Additional information, or Reviews.
StoreFixKit's One Extra Product Tab for WooCommerce uses that narrow model. Free adds one product-specific tab. Pro reuses one shared tab by category or tag.
Why one tab is often enough
Many merchants need a predictable place for one block of information: care instructions, ingredients, shipping notes, specifications, compatibility, downloads, or a warranty summary. They do not necessarily need a tab library, drag-and-drop editor, conditional engine, or theme builder.
WooCommerce's commercial Tab Manager serves a broader job with reusable tabs and more complex organization. A focused helper should not claim that larger feature surface. Its value is that a beginner can answer two questions, save the product, and know exactly what changed.
Use the tab system WooCommerce already owns
The product template already decides how native tabs look, respond, and fit the theme. Adding one entry to the existing woocommerce_product_tabs array lets the theme keep that ownership.
Copying a WooCommerce template into a plugin creates a second version that can drift when WooCommerce or the theme changes. Injecting markup later with CSS selectors or JavaScript is also brittle because selectors differ across themes and block templates.
The safe boundary is simple: if the active product template exposes the native tabs filter, add one entry. If it does not, render nothing rather than forcing a second interface onto the page.
Never overwrite an existing tab key
Every tab entry needs a key, title, priority, and callback. A plugin should use a namespaced key such as sfk_extra_information and check whether it is already present.
If another component occupies that key, StoreFixKit returns the original array. Choosing silence over replacement prevents one plugin from deleting or changing content another plugin owns.
Empty means no tab
A title without content produces a confusing empty panel. Content without a title creates an inaccessible or unexplained control. Both fields should contain valid values after sanitization before the entry is added.
That rule also makes rollback easy. Clearing either setting removes only the optional tab from future renders; it does not alter the product description or create placeholder content.
Sanitize saved content and escape output
The title is plain text and should be length bounded. Content can use the safe HTML WordPress normally permits for post content, while scripts, unsafe attributes, and disallowed elements are removed.
The callback should output only the stored safe content for the current resolved tab. It should not execute arbitrary PHP, fetch a remote page, run shortcodes by default, or load a page-builder document into a product request.
What public support complaints teach
WordPress.org support threads include reports such as one custom tab not appearing, tabs not shown on a product, and a created tab not being shown. These reports come from different products and do not identify one universal bug.
They do show the recurring failure surfaces: partial settings, assignment rules, cache, theme templates, duplicate identifiers, and broad tab managers with many interacting states. A one-tab plugin can remove several of those states by refusing to manage core tabs or templates.
Product-specific content should win
If a merchant writes a tab directly on a product, that is the clearest instruction. A reusable category or tag rule should not silently replace it.
Pro therefore uses the shared tab only when there is no valid product-specific Free tab. An explicit product exception can also suppress the shared assignment. This precedence is visible and reversible:
- valid product-specific tab;
- otherwise a matching shared tab that is not excepted;
- otherwise no StoreFixKit tab.
Display order without reordering everything else
WooCommerce and other extensions supply their own priorities. Pro can set a priority only for the StoreFixKit entry. A lower number generally places it earlier, but the plugin does not normalize, rewrite, or sort every other tab.
The default of 50 is deliberately ordinary. A merchant should change it only after testing the real theme with all active tab-producing extensions.
What this plugin should not do
It should not remove Reviews, rename Description, hide Additional information, replace templates, change product search, index tab content independently, or add conditions based on cart, customer, order, or payment state.
It also should not become an unlimited content-management system. One shared Pro tab plus finite assignments preserves the same beginner mental model as Free.
Safety and resource boundaries
The plugin adds no frontend JavaScript or stylesheet. It creates no custom table, cron event, telemetry, public remote request, storefront write, or product query. It reads the current product's two bounded meta values and, when needed, one bounded Pro option.
Missing WooCommerce, empty settings, a duplicate key, an absent native filter, or unavailable Pro should leave the original page behavior unchanged. The plugin never changes product descriptions, excerpts, attributes, reviews, revisions, orders, prices, or stock.
The One Extra Product Tab documentation contains the exact installation, setup, troubleshooting, rollback, and uninstall workflow.
Beginner test checklist
Valid title and content
The product should show one extra tab and its content.
Empty title
No StoreFixKit tab should appear. Existing tabs should remain.
Empty content
No StoreFixKit tab should appear. Existing tabs should remain.
Existing core tabs
Description, Additional information, Reviews, and every third-party entry should keep their original titles, priorities, and callbacks.
Shared category or tag
A matching product without its own tab should show the shared Pro tab. An unrelated product should not.
Product-specific override
A matching product with valid Free content should show that content instead of the shared tab.
Explicit exception
An excepted product should not show the shared tab.
Missing WooCommerce or custom template
WordPress should keep loading. The plugin should not inject a replacement interface.
Update and rollback
Downgrade and return to the current version. Owned settings should remain while product content and existing tabs remain untouched.
Security and support evidence
Only users allowed to edit products should change product-specific fields, and only users who manage WooCommerce should change shared rules. Writes require capabilities, nonces, sanitization, bounds, and escaped output. WordPress's common plugin issues guide summarizes those directory-review expectations.
For support, capture the product ID, theme, template or builder, title, whether content is product-specific or shared, assignment and exception IDs, tab priority, plugin versions, and screenshots. Do not send credentials, customer data, private content, or full license keys.
Rollback boundary
Keep the current and previous Free and Pro ZIPs plus a database backup. Deactivate both, install the previous versions, activate Free before Pro, and test product-specific, shared, excepted, and native Reviews tabs. Since the plugin never rewrites core tab or product content, rollback should not require repairing WooCommerce data.
FAQ
Can it remove the Reviews tab?
No. It adds one tab only and preserves existing entries.
Does it replace my product template?
No. It uses WooCommerce's native product-tabs filter.
Can I add unlimited tabs?
No. Free adds one product-specific tab and Pro adds one bounded shared tab.
What if my theme does not show native tabs?
The plugin renders nothing. It does not inject markup through theme-specific selectors.
What happens when Pro expires?
Product-specific Free tabs continue working. Shared Pro assignments become unavailable without changing product content.
Focused plugin
Use the one-job implementation.
Add one extra information tab to a WooCommerce product through the native tab system without replacing templates or changing existing tabs.