Skip to main content

Store settings

Plans: Starter ✓ · Growth ✓ · Pro ✓ · Agency ✓ (some cards are platform-specific — Schema Injector on BC only, theme-app guidance on Shopify only)

Each connected store has its own Settings page. Open the store from the sidebar, then click Settings.

The page is divided into cards:

  • General settings — display name, store URL, storefront type, storefront URL.
  • Credentials — view + update API token, BC store hash, etc.
  • Schema Injector (BigCommerce only) — install / uninstall / preview the storefront script.
  • Branding — per-store "Powered by Clione" badge toggle.
  • Danger zone — schedule store deletion.
  • API Keys (below the cards) — generate/manage embed widget API keys for this store.

General settings​

FieldWhat it is
NameDisplay name in your dashboard sidebar. Pick something that helps you tell stores apart (e.g. EgoShoes EU, EgoShoes US).
Store URLThe canonical URL of your store admin / API. For Shopify this is your-store.myshopify.com; for BigCommerce it's the platform API path.
Storefront typeClassic (Stencil / Liquid theme) or Headless. The dashboard uses this to bifurcate flows (e.g. the Schema Injector card hides on headless because there's no theme to inject into).
Storefront URLThe public-facing URL shoppers see (e.g. https://shop.example.com). This is what Clione fetches during Verification and what the Pulse extension scores.

Click Save to apply changes. Changes take effect immediately for new operations.

Credentials​

The Credentials card lets you rotate or replace the platform API token without re-creating the store.

BigCommerce​

  • Access token — the BC API access token (from your BC API Account).
  • Store hash — the alphanumeric hash from the BC API Path (e.g. abc123xyz from https://api.bigcommerce.com/stores/abc123xyz/v3/).

When you save, Clione merges with existing credentials — supplying only the access token won't wipe the store hash. This was a bug fixed in #28 — earlier versions would clobber unrelated fields on a partial save.

Shopify​

  • Access token — the Admin API access token from your Shopify custom app (shpat_...).

The store URL is set per-store, so this card only takes the token.

Credential validation​

Saved credentials are validated lazily on the next operation that needs them (next sync, next propagation). If validation fails, the offending operation surfaces the error and the credentials card shows a yellow warning chip — you can re-paste and re-save without losing your work.

Schema Injector (BigCommerce only)​

See Install the Schema Injector. This card is hidden on Shopify stores.

Branding card​

Per-store override for the "Powered by Clione" badge that appears in widgets (FAQ accordion, public Pulse pages, branded summary footers).

The toggle:

  • Is enabled on Growth, Pro, and Agency.
  • Is disabled and forced on for Starter and during trial. The disabled state shows a tooltip explaining why.

The badge is enforced via the API itself, not just the UI — flipping the toggle in the DB directly won't bypass it on Starter. This is a deliberate enforcement of the Terms of Service.

There's also an org-level brand setting under Org → Brand that covers logo, accent color, and custom domain. The per-store toggle is the only thing that lives in the store-level Settings page.

Danger zone​

Schedule deletion​

Clicking Schedule deletion starts a 7-day grace period during which:

  1. The store remains usable.
  2. A confirmation email is sent to the org owner.
  3. The Danger zone card shows a banner with the scheduled purge date and a Cancel deletion button.

If you don't cancel, the store and all its enriched data are permanently deleted on the scheduled purge date.

Cancel deletion​

Click Cancel deletion any time before the purge date to abort. The store returns to its normal state immediately.

Resend deletion email​

If the owner missed the confirmation email, click Resend email on the banner to re-send.

API Keys panel​

Below the settings cards is the API Keys section, used for embed widget integrations.

  • + Generate key — creates a new key with a scope (products:read by default), an optional store filter, and an allowed-domains whitelist.
  • Each key shows: name, last-used timestamp, scopes, allowed domains, active status.
  • Per-row actions: edit domains, revoke (deactivates without deleting), reactivate, delete (permanent).

When you generate a new key, the secret is shown once in a modal — copy it immediately. Clione stores only a SHA-256 hash and cannot show the secret again. If you lose it, generate a new key.

See FAQ editor and FAQ widget install for what to put in data-api-key=.

Internal keys (auto-provisioned)​

You'll see keys prefixed with __ (double underscore) that you can't edit or delete. These are auto-provisioned for internal use by the Schema Injector — they're hidden from the user-facing list. If you need to see them, you can spot the count in the page footer or via the admin API.

Per-platform notes​

Most settings are platform-agnostic. The two exceptions:

  • Schema Injector card — BigCommerce only. Shopify uses the theme app block instead, configured in your Shopify theme editor.
  • Credentials fields — BC needs access token + store hash; Shopify needs only the access token.

Multi-currency configuration​

If your store is multi-currency (BC Channels with separate price books, or Shopify Markets with per-country prices), the Settings page surfaces the Default currency the propagator should use for JSON-LD priceCurrency. Today this is a single value — the request-aware multi-currency JSON-LD (offers as array) is on the roadmap.

BigCommerce​

  • Click Channels to see the channels Clione has detected. Pick the default channel for propagation.
  • The price book associated with the default channel's currency is what propagates into the JSON-LD price.
  • If you have multiple channels with different currencies, only the default channel's prices are propagated. Other channels show their own meta tags via BC's native multi-currency theme support — Clione doesn't override these.

Shopify​

  • Click Markets to see the Markets Clione has detected via the Markets API.
  • Pick the primary Market.
  • The primary Market's currency is what's used in JSON-LD.
  • Secondary markets (e.g. Germany, Japan) get their currency-appropriate price tags from Shopify's native Markets feature.

Sync schedule​

Sync currently runs on-demand only — there is no automated daily sync built into the Settings page. The roadmap includes a per-store sync schedule (daily / weekly / hourly). For now, run a manual sync from Store → Sync after any catalog change you want Clione to pick up.

Webhook health​

Clione subscribes to platform webhooks during the connection flow:

  • BigCommerce — store/product/updated, store/category/updated, store/cart/converted, store/order/created.
  • Shopify — products/update, collections/update, orders/create, app/uninstalled.

The Settings page has a small Webhook health chip showing the last received webhook timestamp per type. If a chip is stale (no webhook in >24h), open it for details — usually the webhook subscription got deregistered in the platform admin and you need to reconnect to re-register.

Troubleshooting​

"Failed to save: no changes" — You clicked Save without changing any field. The dashboard tracks dirty state to avoid empty PATCH requests.

Schema Injector card shows "checking" forever — Network issue or BC API timeout. Hard refresh. If it persists, your BC API token might have lost the Content scope (see Connect BigCommerce).

Deletion email didn't arrive — Check spam. Click Resend email on the deletion banner. If still nothing, ping support — Resend deliverability is a known watchpoint (task #76).

Credentials saved but next sync still says "no credentials" — Hard refresh and retry. Credentials are cached in the API for 60 seconds.

"Storefront unreachable" toast when validating a new Storefront URL — The URL you entered returns 4xx / 5xx. Try opening it in a private browser tab; if it loads for you but not for Clione, your storefront may block our datacenter IP — contact support to whitelist.

Phantom stores re-appearing after deletion — Known bug (#79). Stores named "Starter Shopify Store" or "Store to Delete" sometimes regenerate after deletion. Workaround: delete via Superadmin path (if you're a superadmin) or contact support.

BC store hash field shows wrong hash after editing access token — Known bug fix from #28. Update by clearing both fields and pasting both fresh. If the wrong hash persists after refresh, log out and back in to force a session re-fetch.

Shopify access token rejected with "Invalid API key" — The token format must start with shpat_ for Admin API. If you accidentally pasted the Storefront API token (shpsa_), it won't work — Clione needs Admin scope. Re-issue the Custom App token.

Audit log per store​

Every store action is logged. Visible under Store → Audit:

  • Credential updates (token paste, store hash change).
  • Sync runs (start, finish, error).
  • Enrichment runs.
  • Propagation runs.
  • Schema Injector install / uninstall.
  • Branding badge toggle.
  • Store-level setting changes.
  • Member assignment to / removal from the store (Agency).

Retention follows the org-level retention setting — 90d on Growth, 180d on Pro, 365d on Agency.

Reconnecting after a token rotation​

If you rotate your BC token or Shopify Custom App token on the platform side, Clione's next operation will fail with 401. To reconnect:

  1. Generate the new token on the platform (same procedure as the initial setup).
  2. Open the store in Clione → Settings → Credentials.
  3. Paste the new token.
  4. Click Save and validate. Clione makes a quick test call to confirm the token works.
  5. If validation succeeds, the next sync will pick up the new token automatically. Webhooks remain subscribed.

If validation fails with the new token, the prior token is restored. You'll see a clear error message.