Skip to main content

Overview

A product does not appear in the Store just because it exists. It has to be active, sellable, visible to the portal, and priced — and a few extra fields control how its tile looks. This page covers each requirement and each optional touch.

What a Product Needs to Appear

The Store and the Product page apply the same eligibility test, so a product reachable by a direct link is always one the grid would also show. Every condition below must hold.
The Store loads at most 1,000 eligible price book entries. A catalogue larger than that needs the business-unit filter in Store Settings, or a custom Store Data Provider Class.

Set Product Visibility

Product Visibility uses the Visibility Settings global value set:
Staff is the default on every product, so a newly created product is invisible to the Store until you change it. This is deliberate — nothing reaches your storefront by accident.

Product UUID

The Store addresses products by Product UUID (FCORE_PAY__Product_UUID__c), not by Salesforce Id, so storefront links stay stable and reveal nothing about your org. A product with a blank UUID is filtered out of the Store entirely.
If products you expect are missing and everything else checks out, check the UUID first — it is the least obvious of the requirements.

Dress the Tile

These fields are optional and affect only presentation.
Store Image Badge doubles as a translation key: if a Custom Label exists whose name exactly matches the badge text, the label’s translated value is shown instead of the raw text. That is how you get translated badges without per-language product records.

Limit Quantity Per Line

Max Quantity Per Item (FCORE_PAY__Max_Quantity_Per_Item__c) caps how many units may sit on a single line item.
  • Set it to 1 to sell one unit per line — the cart then shows a remove button rather than a quantity stepper.
  • Leave it blank for no limit.
  • Set it to a number, and a shopper who adds more than that gets additional lines, each capped at the same limit. Ten units with a limit of four become lines of 4, 4, and 2.
This field is currently honored by the portal Store only. Staff-side order entry does not enforce it.

Categories

Shoppers filter the Store by category, and the Product page can show which categories a product belongs to.
1

Make the category visible to the portal

On each FCORE_PAY__Product_Category__c record, set Product Category Visibility (FCORE_PAY__Product_Category_Visibility__c) using the same Visibility Settings values — Portal or Staff and Portal for a category shoppers should see.
2

Add products to it

Link products to the category with Product Category Item records, as you would for any other use of categories.
3

Check the pill count

The Store page shows category pills inline up to Max Visible Category Pills on the component (default 4, maximum 8); the rest collapse into a More dropdown.
Only portal-visible categories appear in the filter and in the Product page’s categories line — a category set to Staff is invisible to shoppers even when its products are on sale.

Products That Need a Choice First

Some products cannot go straight into the cart — a subscription needs a plan chosen. fusionCore resolves what to ask by the product’s System Category, reading the Product Configurator Class on the matching FCORE_PORTAL__Portal_Product_Config__mdt record. See Product Config Metadata Fields. Behavior follows from how many options exist:
Subscriptions added from the Store do not ask the shopper for a start date. The Subscription Start Date Updater sets it.

Limitations and Common Pitfalls with Store Products

  • A new product defaults to Staff and will not appear in the Store until Product Visibility is changed.
  • A blank Product UUID silently hides a product, from both the grid and its own detail page.
  • The price must be on the standard price book and active. A product priced only on a custom price book does not appear, even though staff can sell it.
  • Tax products never appear, regardless of visibility.
  • Short Description and Description are not interchangeable — Short Description is the tile, Description is the detail page. Filling only one leaves the other surface bare.
  • Badge color without badge text does nothing. The color applies only when text is set.
  • Max Quantity Per Item splits lines rather than blocking the shopper. If you meant to cap the total a shopper may buy, this field does not do that.
  • A category set to Staff disappears from the filter even when its products are on sale, so shoppers can reach those products only by search.