Store settings

Store settings is the dashboard's central place for managing store-wide information: owner and business basics, email addresses, search engine optimization, an optional API key for headless setups, and tools for moving data in and out (store transfer and CSV import/export).

Find it in the left navigation under Settings → Store settings. The page has five tabs: General, SEO, API key, Store transfer, and CSV import/export.

General

The General tab holds the store's and the business's core information. Most fields are required because they're used in order confirmations, emails, shipping labels, and VAT calculations.

Owner and contact info

Email vs. Support email — what each one is for

These two fields are intentionally separate because they serve different purposes.

Email (required) is the store owner's own address:

• It receives store-related notifications (trial expiry, store-closure confirmation)
• It's the sender address on Shipit shipments
• It's used as the Reply-To on customer emails only when the support email is empty

Support email (optional) is the public address visible to customers:

• It's set as the Reply-To on every customer email (order confirmation, ticket confirmation, refund, sign-in links)
• It appears in email bodies and as the contact link in the storefront footer
• It's used as the recipient of the contact form
• It also shows up in structured data (Schema.org / JSON-LD) for search engines

Business info

Storefront URL

The Storefront URL is your store's public web address — a single source of truth that several systems rely on. Getting this right matters because a wrong URL means broken links in customer emails.

The backend uses the URL to build these email links:

• Email verification links (customer registration)
• Password reset links
• Abandoned-cart reminder links
• Digital download links

In addition, the Storefront API exposes the same URL to the storefront template (with the trailing slash stripped), and the template uses it for:

• The metadata base for indexing (metadataBase)
• The base URL of the sitemap and robots.txt
• Canonical URLs in Open Graph and Twitter share cards
• URL fields in structured data (Schema.org / JSON-LD)

Logo

Drag a file in or click to upload. Supported formats: SVG, PNG, JPG, WebP. Max size: 2 MB.

The logo appears:

• In the storefront's navigation
• In order confirmation emails
• In structured data for search engines

Danger zone — closing the store

At the bottom of the form there's a red Danger zone box with a Close store button. The action:

1. Cancels the Putiikkipalvelu subscription at the end of the period
2. Marks the store for deletion in 30 days
3. Sends a confirmation email to the owner

During the 30 days you can undo the closure with the Cancel closure button that appears in the same box. After that period, all store data (orders, customers, products) is permanently deleted.

SEO

The SEO tab controls how your store shows up in Google search results, social media share previews, and structured data.

Basics

• SEO title (max 60 characters) — appears as the blue title in Google search results and in the browser tab
• SEO description (max 160 characters) — the short snippet shown beneath the title in search results

If you leave the SEO title empty, search engines fall back to the store's name; an empty SEO description means Google picks the description text on its own — usually a poorer result than your own copy.

Open Graph (social share images)

The Open Graph image is the picture shown when someone shares your storefront link on Facebook, WhatsApp, LinkedIn, or most other platforms.

Twitter / X

The Twitter / X card is shown when the link is shared on X (formerly Twitter).

Social media links

Social media URLs are shown in the storefront footer and in structured data. Fields: Instagram, Facebook, TikTok, YouTube, Pinterest, LinkedIn.

These are entirely optional — fill in only the ones you actually use.

Structured data (Schema.org)

Structured data helps search engines understand what kind of business you run.

Search engine verification

The Google Search Console code adds a verification meta tag to the site's <head>. Paste only the content attribute value that Search Console gives you — not the whole HTML tag.

API key

You only need the API key if you want to use Putiikkipalvelu in a headless way — that is, build your own frontend (e.g. Next.js, Astro, a custom React app) for the store, or integrate it with other systems. For regular users this tab isn't relevant.

Generating a key

1. Click Generate new API key
2. The key appears in a text field — copy it immediately, it won't be shown again
3. The status flips to Active

Technical details:

• The key is a 64-character random hex string (32 bytes)
• Only the SHA-256 hash of the key is stored in the database — the original is unrecoverable if lost
• A store can have only one active key at a time

Using the key

Add the key to requests in the x-api-key header. It grants access under the Storefront API tree:

Base URL: /api/storefront/v1/
Header:   x-api-key: <your key>

In the storefront template the key goes into the STOREFRONT_API_KEY environment variable, and the SDK package picks it up automatically.

Rotating the key

Click Generate new API key again. This:

• Replaces the old key with a new one
• Invalidates the old key immediately — any apps still using it stop working until they're updated with the new key
• Requires a separate confirmation in a dialog

Rotating the key is good practice if, for example, you suspect the old key has been leaked.

Store transfer

Store transfer is a one-click tool that exports the store's content to a JSON file and imports it into another store. It's especially useful when you've built things in a test store and want to move them to a production store.

Export store data

Click Download export file. The browser downloads a JSON file named store-export-YYYY-MM-DD.json (with today's date in the filename).

The file contains:

• Store settings (owner, contact details, VAT, currency, logo, storefront URL, image aspect ratio)
• SEO settings (titles, images, social links, schema.org info)
• Categories (the full tree)
• Variation types (e.g. Size, Color and their options)
• Events (ticket events with date and location info)
• Products with their variations and any ticket info
• Pages (CMS page structures with their content blocks)

Orders, customers, campaigns, discount codes, and payment integrations are not transferred — the export covers only the store's structure and content.

Import store data

1. Pick a previously exported JSON file
2. The preview shows how many categories, products, variations, pages, etc. the file contains
3. Click Import store

The import runs as a single database transaction — either everything succeeds or nothing is saved.

What happens during import

• Settings and SEO are upserted — existing values are overwritten
• Categories, products, and pages are created in the destination store as new
• Images are copied automatically in R2 storage from the source store to the destination (logo, product and variation images, SEO images, images in content blocks) — the URLs are rewritten to the destination store's paths
• A stats box at the end shows how many categories, products, variations, pages, and images were transferred

Slug conflicts

If the destination store already has a category, product, or page with the same URL slug, the import stops immediately and you get an error listing the conflicts.

The pages privacy and terms are exceptions — these are upserted on top of existing ones and don't cause a conflict.

Versioning

The file's header contains an exportVersion: 1 marker. If the version doesn't match what the system supports, the import is rejected with the error "File version is not supported".

CSV import/export

CSV import and export is well suited for bulk operations — for example, importing a thousand products at once from an Excel file. You get a ready-made template, fill it in in Excel or Google Sheets, and upload it back to the system.

Categories first, products second

Products are linked to categories by name — so categories must exist first before they can be referenced in the products CSV.

Export and Download template

Each section (Categories, Products) has two buttons:

• Export CSV — downloads a file containing the current categories or products. Use this when you want to edit existing data in Excel
• Download template — downloads an empty template with just the header row. Use when starting from scratch

Category CSV format

Product CSV format

The product CSV is wider: it covers a product's basics, pricing, stock, sale pricing, SEO fields, up to three variation types, plus per-variation fields and image URLs.

Key columns include: handle (unique identifier for a product group), name, description, price, compareAtPrice, stock, category, sku, weight, vatPercent, salePrice, saleStartDate/saleEndDate, metaTitle, metaDescription, imageUrls.

Variations live on their own rows with the same handle value — using columns option1Name/option1Value … option3Name/option3Value, plus variantSku, variantPrice, variantStock, variantWeight, variantGtin, variantBrand, variantCostPrice, variantShowOnStore, and variantImageUrls.

Download the template for the full column list in the right order.

Preview and validation

When you pick a CSV file, the system reads it in the browser and shows a preview before importing:

• A summary: how many rows will be created, updated, or skipped
• A table preview of the chosen rows
• All errors with row numbers (e.g. missing required field, unknown category, malformed price)

The Import button only appears once the preview confirms there's something to create or update.

Product import — synchronous vs. asynchronous

The import mode is chosen automatically based on whether the CSV contains image URLs:

• Synchronous — importing product data without images runs immediately and the result is shown right away
• Asynchronous — when the file contains imageUrls or variantImageUrls columns, the system creates a background job that:
  • Downloads images from the external URLs
  • Processes them (aspect ratio, optimization)
  • Updates a live progress bar (images and products tracked separately)

Import mode

The product import uses create-only mode: an existing product with the same handle is skipped during import. This prevents accidental overwrites of existing products.

Related topics

• Settings overview
• Visitor stats
• VAT report