Skip to content

Shop settings

The shop’s own settings are tabs of Catalogues → Filters → System:

TabApplies to
Admin filterThe filter bar of the administration’s lists: see Options.
Storefront filterTiming and display of the panel in the shop, per sales channel.
Value listsHow many values a list of the panel loads, for every sales channel.
CompatibilityThe product page, the node pages and the search of compatibility catalogues, per sales channel.
InsightsWhat the statistics record and name, for every sales channel.
RetentionHow long data is kept and how stalled tasks are handled, for every sales channel.
Performance, InformationSee System.

Tabs marked “for every sales channel” hold one value for all channels. Change what you like and click Save. A number field takes a whole number within the limits shown below; an empty field takes the default. On the tabs set per sales channel, the sales channel picker over the form switches between all channels and one: a channel’s empty field takes the value for all channels, and an empty value there the default.

Filters → System → Storefront filter. The settings apply to pages the shop draws after saving, and to the builder’s stage at once.

SettingEffectDefaultLimits
Loader after (ms)A value clicked and its group show the loader only when the answer takes longer than this; a quicker answer shows none.2000–2000
Loader stays at least (ms)Once shown, the loader stays this long, so it does not flicker.4000–3000
List dims after (ms)Where the skin dims the product list while it loads (Products while loading: Dim), it does so this long after the request went out.1500–2000
”Undo” after “Clear all” (ms)How long “Filters cleared · Undo” stays in the chips’ row.50001000–30000
Search in a list’s values after (ms)A list that holds only part of its values searches on the server once the shopper stops typing this long.2500–1000
SettingEffectDefaultLimits
Bars of a range’s histogramA range with Histogram on shows how its products spread across the slider in this many bars. On MySQL each bar is one query.205–50
Tiles in “Auto” up to (characters)A group displayed Auto draws tiles when no value is longer than this (sizes such as S, M, 42, XXL), else a list.41–12
Long lists scroll and load from (values)A list, radios or pills with Long lists: Auto show “Show more” in place for fewer values and, from this many, scroll in their own box and load the next values as they scroll.3010–500
SettingEffect
Remember the compatibility choice without asking for consentThe shopper’s compatibility choice goes to its cookie at once, as after consent to “Remember what my products should fit”: the next page lists what fits from the start. Off (the default): until the shopper consents, the session keeps the choice and the list follows it a moment after the page shows. Not recommended where the GDPR or similar rules apply.

See Compatibility in the shop.

Filters → System → Value lists. The settings apply to the shop’s next listings, and to the builder’s stage at once.

SettingEffectDefaultLimits
Values per listThe most values one list of the panel (and of the builder’s stage) carries at once, the ones with the most products first. A source with more values gets a search on the server and loads more as the list scrolls.20020–1000
Values a list loads by scrollingPast this many values a list stops loading more and asks for a search instead. At least as many as Values per list.100020–10000
Room for hidden valuesValues hidden in Sources → Values are read and then left out; a list asks for this many more, so the hidden ones do not shorten it.1000–1000
Values of the small property groups, togetherProperty groups with no more values in the shop than Values per list are counted together in one query. Past this many values that query stops, and their lists load the rest as a large group’s do.5000200–100000

Filters → System → Compatibility, per sales channel.

SettingEffectDefaultLimits
”Fits” tab: rows a pageHow many of a product’s fits the Fits tab shows at once; the next ones come with Show more or a search.205–200
Structured data: fits namedHow many of a product’s fits its structured data names as what it is a part or accessory for, each with its node’s page. 0 names none.100–50
SettingEffectDefaultLimits
Products a node’s page showsThe best-selling products that fit the node. The categories the page names, those whose filter offers the catalogue, lead to the rest.244–96
SettingEffectDefaultLimits
A node named in the search phraseOffer: the search suggestions and the results page offer to show only what fits the node named. Apply: the results show only what fits at once, with the bar to clear it. Off: nothing is recognised.Offer—
Shortest word that names a nodeShorter words and numbers alone name nothing; they only add to a name a longer word starts (“golf 5”).21–6
Nodes offered when a phrase names severalA phrase that names several nodes equally well applies none: the shopper picks one of this many.31–10

See Compatibility in the shop.

Filters → System → Insights, for every sales channel. The settings apply to the panel’s next reports, and to Insights at once. How long the statistics are kept is set under Retention.

SettingEffectDefaultLimits
New combinations recorded a day per sales channelChoices of the panel that found nothing, first seen that day. Past this number new ones are left out until the next day; those already recorded go on counting.50050–5000
Combinations listed in Insights › No resultsThe ones hit most in the period; the figures over the list count all of them.500100–5000
SettingEffectDefaultLimits
Share of the set’s applies below which a group is rarely used (%)Insights → Usage names the set’s own groups below this share as candidates to fold or remove. 0 names none.10–50
Applies of the set before a group counts as rarely usedWith fewer applies in the period every share is chance, so no group is named.20010–100000

See Insights.

Filters → System → Retention, for every sales channel. A daily cleanup removes what is past these numbers; the watchdog uses its minutes on its next round.

SettingEffectDefaultLimits
Days the statistics are keptHow the filter panel was used, day by day, and the choices that found nothing. Older days are deleted once a day; Insights can show no period further back.40030–730
SettingEffectDefaultLimits
Days the listing times are keptThe times of the shop’s listings and its slow requests, which System → Performance shows while measuring the traffic is on.71–60
Slow requests keptThe newest ones; older ones are deleted once a day, as are those past the days above.50050–5000
SettingEffectDefaultLimits
Days ended tasks are keptDone, failed and cancelled tasks in System → Tasks. The last check of the values and of the dashboard in each language and a set’s measurements stay as long as they are read.301–365
Measurements kept per setThe newest measurements of a set in System → Performance; a new one removes the oldest past this number.101–50
SettingEffectDefaultLimits
Versions kept per set and skinThe versions of this many last publishes of each set and skin stay in System → Versions; older ones are deleted once a day. The version the shop shows always stays. 0 keeps them all.500–500
SettingEffectDefaultLimits
Days a replaced URL name keeps leading to the new oneAn address with a filter’s or a value’s former URL name still finds the filter, as an old SEO URL does. Older names are deleted once a day; 0 keeps them for good, as the shop keeps its old SEO URLs.00–3650
SettingEffectDefaultLimits
Pick up a task silent for (minutes)A running task whose worker stopped (memory, time limit, a restart) goes on from where it stood. The watchdog looks every 5 minutes.52–120
Pick-ups per taskA task that stops on the same item again is not picked up past this; 0 never picks one up.50–20
Fail a task silent for (minutes)A task still silent this long, its pick-ups used up, ends as failed in System → Tasks, to be started again. At least a minute past the pick-up.3010–1440