VX fields on product pages

A product can carry VX fields like any other post: specifications, materials, care instructions, a downloadable spec sheet, a related-products relation. This is how to get them onto the page and how to edit them.

First, attach a fieldset to the product post type in VX. Nothing here does anything until a product actually has VX fields.

Showing them on the store's own template

VX Modules → Settings → FluentCart (or WooCommerce).

Setting	What it does
Show VX fields on product pages	Whether they show on the store's own single product template at all
Heading	The heading above the list. Leave empty for no heading
Fieldsets to show	Which fieldsets. Empty means every fieldset attached to products. With more than one, each gets its own subheading
Where it goes	WooCommerce only — see below
Show empty fields	Off hides a field the product left blank

Where it goes — WooCommerce

Choice	Position
Under the price and meta	In the product summary, below the add-to-cart area
In a tab of its own	A new tab beside Description and Reviews
Below the product, with the upsells	After the summary, in the related-products region

FluentCart has one position: under the content on its own single product template.

How each field renders

Not as raw values — each type renders as itself:

Field type	On the page
Text, textarea, rich text	Text
Number, date, time	Formatted with the site's formats
Select, radio, checkboxes	Their labels
Switch	Yes or no
Image	The image
Gallery	The images
Video, audio	A player
File	A link
URL	A link
Relation	Links to the related posts
Group	Its sub-fields, labeled
Repeater	One block per row

The shortcode

For a custom template, or a position the settings do not offer:

[vxm_product_details]
[vxm_product_details id="123"]
[vxm_product_details heading="Specifications"]
[vxm_product_details fieldsets="specs,care"]

Attribute	Default
id	The current post
heading	The heading from Settings. Pass an empty string for none
fieldsets	Comma-separated keys. Empty falls back to the setting, and an empty setting means all

The shortcode works whether or not the automatic placement is on, so a custom template can turn the setting off and place the list itself.

Building your own layout instead

The settings put the whole list on the page. When you want the fields laid out your own way — a spec table, an accordion, a chart — bind them individually with the VX picker in Elementor or Bricks, and turn the automatic placement off.

The product's VX fields are on @post(…) like any other post's, because a product is a post. @product(…) is for the store's own data — price, stock, variations. The two work side by side on the same page.

Editing a product's VX fields

WooCommerce

WooCommerce products are WordPress posts edited in WordPress's own editor, so VX's field panel is already there. Nothing extra is added and nothing extra is needed.

FluentCart

FluentCart has its own product editor. The module adds a VX fields card under FluentCart's own cards, editing the product's fieldsets in place:

Field type	In the card
Text, number, date, color	Edited directly
Choices and switches	Edited directly
Media	Through the media library
Related posts, users, terms	Through a search box
Repeaters and groups	Shown read-only, with a link to the full editor

The card mounts itself because FluentCart's editor has no seam for adding a section, and re-attaches when the app redraws. The module also adds a VX fields tab to FluentCart's product header — a FluentCart route beside Upgrade Paths and Integrations — which opens the same card on a page of its own. Go there if the card ever fails to mount.

Colors follow FluentCart's light and dark themes.

Writes go through the same path the Sheet uses, so VX's validation and publishing rules apply exactly as they do everywhere else.

In bulk

Products are a post type, so the Sheet and bulk edit work on them too — which is usually the fastest way to fill in a field you added after the catalog was built.