Shop configuration includes the Legacy Records, Logging, Usual Cart, Cloudflare, Recommendations and Notifications tabs. To reach them, select Shop configurations in the Admin Panel menu, then select a tab.
Legacy Records tab
These rules apply to records that are no longer present in the ERP. All marked records no longer appear on the system. Each entity has its own radio group with Yes and No options.
Entity | Label on the tab |
Brand | If brand no longer exists in ERP - mark as deleted |
Category | If category no longer exists in ERP - mark as deleted |
Package | If package no longer exists in ERP - mark as deleted |
Product | If product no longer exists in ERP - mark as deleted |
Attribute group | If attribute group no longer exists in ERP - mark as deleted |
Attribute | If attribute no longer exists in ERP - mark as deleted |
Product package | If product package no longer exists in ERP - mark as deleted |
Customer | If customer no longer exists in ERP - mark as deleted |
Currency | If currency no longer exists in ERP - mark as deleted |
Special price | If special price no longer exists in ERP - mark as deleted |
Price list | If price list no longer exists in ERP - mark as deleted |
Property | If property no longer exists in ERP - mark as deleted |
Variant value | If Variant value no longer exists in ERP - mark as deleted |
Customer data | If Customer data no longer exists in ERP - mark as deleted |
ERP value | If ERP value no longer exists in ERP - mark as deleted |
Customer price list | If Customer price list no longer exists in ERP - mark as deleted |
Customer discount | If customer discount no longer exists in ERP - mark as deleted |
Customer shipping address | If customer shipping address no longer exists in ERP - mark as deleted |
Product characteristic | If product characteristic no longer exists in ERP - mark as deleted |
Product characteristic group | If product characteristic group no longer exists in ERP - mark as deleted |
Product label | If product label no longer exists in ERP - mark as deleted |
Product attribute | If product attribute no longer exists in ERP - mark as deleted |
Collection set | If collection set no longer exists in ERP - mark as deleted |
Individual product list | If individual product list no longer exists in ERP - mark as deleted |
ERP customer user | If ERP customer user no longer exists in ERP - mark as deleted |
Similar product | If similar product no longer exists in ERP - mark as deleted |
Similar product group | If similar product group no longer exists in ERP - mark as deleted |
Universal API product feed | Allow a universal-API product feed to delist more than half of its products in one run |
Universal API customer feed | Allow a universal-API customer feed to delist more than half of its customers in one run |
Allow a universal-API product feed to delist more than half of its products in one run applies to Universal API (plan 3) only. A run that would mark more than half of the feed's products (at least 10) as deleted is refused as a truncated feed, and nothing is marked. Set Yes for the one run that follows a genuine catalogue cut, then set it back to No.
Allow a universal-API customer feed to delist more than half of its customers in one run applies to Universal API (plan 3) only. A run that would mark more than half of the feed's customers (at least 10) as deleted, which also detaches their portal logins, is refused as a truncated feed, and nothing is marked. Set Yes for the one run that follows a genuine cut, then set it back to No.
Logging tab
Long-term storage of logs affects system memory.
Setting | What it holds |
Clear task logs after in days | A number field for the number of days after which task logs are cleared. |
Usual Cart tab
These settings apply to the customer-facing My Usual Cart feature, which lists products previously bought by the logged-in customer. The usual cart feed supports sorting and attribute filters. If nothing is linked to a customer's account, the page simply shows no products and no error appears.
Setting | Control | What it does |
Data fetch mode | Radio group with Live and Static. | Live fetches SKUs from the ERP on each request, which is fresh but slower. Static uses a periodically synced snapshot in the database, which is faster but can be stale until the next sync. |
Lookback window (days) | Number field. | Sets how far back, in days, the system looks at customer invoices when working out which SKUs count as usual. |
Cloudflare tab
These settings configure edge and CDN cache purge for this client's storefront zone. Secrets entered on this tab are not exposed to the storefront.
Setting | What it does |
Cloudflare Zone ID | Holds the Cloudflare zone ID for this client's storefront zone. Edge purge requires it, and leaving it empty disables purge. |
Cloudflare Purge Token | Holds a Cloudflare API token restricted to cache purge, stored encrypted at rest. Leaving it empty disables purge. |
CDN warm-up paths | Holds comma-separated origin paths that an internal request warms before a purge, to avoid a cold-render storm. |
GCP CDN url-map | Holds the name of the GCP global load balancer url-map whose CDN is invalidated before the Cloudflare purge. Leaving it empty disables GCP CDN invalidation. |
Recommendations tab
These settings cover per-customer tracking of recently viewed products and the dynamic-slider feed. Views are tracked for signed-in shoppers only; browsing without signing in leaves no trace. Viewing the same product again refreshes the existing record instead of adding another. Each signed-in customer gets their own list of products they looked at lately, latest at the top; with the feature off, that list stays empty. To show a recently viewed carousel, point a site builder dynamic slider at this feed.
Setting | Control | What it does |
Enable recently viewed | Radio group with Yes and No. | A master switch that gates both recently viewed tracking and the feed endpoint. |
Track product-page views | Radio group with Yes and No. | Counts product-page views toward recently viewed. |
Track add-to-cart | Radio group with Yes and No. | Counts a server-side add-to-cart toward recently viewed, even without opening the product page. |
Retention / look-back (days) | Number field. | Sets the look-back window, in days, for the recently viewed feed, applied at query time. |
Max items returned | Number field. | Sets the maximum number of products the recently viewed feed returns. |
Notifications tab
These settings decide where operational alerts go. Sync and system events concern the operator rather than a customer, so they are addressed here instead of to an order's contact. Such events include a failed sync task, a finished sync run, a triggered upgrade and a change in installed apps. Leaving both alert fields empty is valid, and rules bound to those events are then skipped.
Setting | What it does |
Operations alert e-mail | Holds the address that receives e-mail notification rules bound to sync and system events. |
Operations alert phone | Holds the number that receives SMS notification rules bound to sync and system events. |
Calls per hour to one external address | A number field for how many times an hour this shop may call any one external address from an automation. Leaving it blank uses the default of 500 calls per hour. A call refused by this limit is recorded as a failed step that names the address and the number. |
Saving changes
Save is unavailable when a tab first opens.
Related