Skip to content

Store settings

Everything in this group describes the store itself rather than what it sells. These are the settings a visitor experiences indirectly: the address they arrive at, the emails they get, the legal text they are shown, the places they can collect an order from.

Destination What it governs
Store The store’s own identity — the name and details that appear wherever CIQRA has to refer to your business rather than your products.
Domains Which addresses reach your storefront, and which one is the primary. The primary domain is the one every public URL is built from, so changing it changes canonical links and redirects — not just what you type in the address bar.
Emails The transactional emails your store sends: the ones triggered by an order or an account, as distinct from marketing.
Legal texts The policy texts shown to shoppers — terms, privacy, returns and the rest. These are yours, not templates we maintain on your behalf.
Store locations Physical locations belonging to the store.
Pickup points Where a shopper can collect an order in person.
External scripts Third-party scripts you choose to load on the storefront.

Of the seven, Domains is the one whose effect reaches furthest. CIQRA builds every public URL — canonical links, og:url, redirects, links inside emails — from the store’s primary domain rather than from whatever host a given request happened to arrive on. That design is deliberate: a server should not infer its own public address from the traffic it receives, because behind a proxy the address it sees is an internal one.

The practical consequence for you: changing the primary domain is a store-wide change, not a cosmetic one. Search engines will see different canonical URLs the moment it takes effect.

External scripts deserve a different moment

Section titled “External scripts deserve a different moment”

A script you add here runs on your storefront, in your shoppers’ browsers, with your store’s name on it. CIQRA does not review what a third-party script does. If you are adding one at a vendor’s request, the question worth asking them is what it collects, because under GDPR and KVKK the answer is your responsibility rather than theirs.

  • It does not give click-paths. These screens have no verified screenshot in this help centre, and steps we have not checked against the current admin are not worth printing.
  • It does not describe the legal texts themselves. What your policies must contain depends on where you sell and what you sell, and that is a question for your own counsel.
  • It does not cover consent or cookie banners. Those are configured elsewhere, and this group is only the seven destinations the admin lists under Store.