Glossary
Short explanations of the terms plinth uses, from activation code to white-label.
This page explains the terms you meet in plinth, in alphabetical order. The terms are written the way they appear on screen. Your team may keep a glossary of its own with shop terms in the area Knowledge.
Terms
Accent color
The color used for highlights such as buttons and active entries. You choose it under Appearance. If you choose none, the company color applies. See The basics.
Access
The area where people, roles, sign-in and security are managed. See Access.
Activation code
A one-time code that a new person uses to set up an account of their own. It is valid for 24 hours, works once and is handed over in person, never by email. See Signing in.
AI feature
One task the AI can do, for example writing product texts. Each feature can be switched on or off and has its own model. See AI settings.
AI key
The company's own API key for the AI. Without it, plinth works with rules only. It is stored encrypted and never shown again. See AI settings.
Approval
A second person checks a change before it takes effect. Jobs that wait for this show Awaiting approval. External accounts also need an approval. See Workflow and Access.
Area
A part of plinth with its own entry in the sidebar, for example Prices or Images. Which areas a shop has is set per shop. Some screens call an area a module.
Audit log
The record of who changed what and when, with sign-ins and exports. See Audit log.
Authenticator app
An app on your phone or in your password manager that keeps showing a fresh 6-digit code. The code is your second factor when you sign in. See Signing in.
Background job
See Job.
Budget
The monthly amount the company allows for AI. Warning levels show when a share is reached. With a hard stop, new AI requests are rejected once the budget is used up. See AI settings.
Company
The organisation one or more shops belong to. Some settings apply to all shops of a company, for example the AI key and the white-label look.
External account
An account for an agency or a service provider. It sees only the modules chosen for it, has an end date and needs an approval by a second person. See Access.
Finding
A defect that a check found in the product data, for example a missing image. The search lists findings under Issues. See Quality.
First import
The first loading of the shop data after a shop was connected. It is started in the wizard. The statistics load last. See Onboarding wizard.
Hard stop
A budget setting. When it is on, new AI requests are rejected once the monthly budget is used up.
Integration
The technical access plinth uses to reach a shop in Shopware. It consists of an access key ID and a secret access key. The wizard creates it, or you enter the keys of an existing one. See Onboarding wizard.
Job
Work that runs in the background, such as a sync, an import, a scan or a bulk change. You can keep working while it runs. See Jobs.
Local account
An account of its own with password and second factor, independent of Shopware.
Model (AI)
Which AI model a feature uses: Haiku, Sonnet, Opus or Fable. Larger models are more accurate but cost more. plinth always uses the newest version of the chosen model. See AI settings.
Owner
An account with every permission, regardless of roles. It is meant as emergency access. Only owners create and change owner accounts.
Passkey
A way to sign in with fingerprint, face or a security key instead of typing a code. See Signing in.
Permission
One single right, for example Manage people. Permissions are bundled in roles. See Access.
Read-only account
An account that may only view, not change anything. Shown as Read only.
Read-only shop
A shop that plinth only reads. Changes are refused, and jobs that could write fail. The top bar shows Read-only. See Onboarding wizard.
Recovery code
A one-time code for signing in when your phone or passkey is not available. You get the codes when you set up your account. Keep them in a safe place.
Role
A set of permissions, for example Editorial or Team lead. The role decides what a person may do. A role is assigned for one shop, for all shops of a customer or for all shops. See Access.
Run
One execution of a change over many entries, for example a price change. A run has a result and can usually be undone. See Prices.
Sales channel
A way of selling in Shopware, for example the online shop (storefront). In the wizard you choose the storefront sales channel that checks and product tools use.
Saved view
A list with its filters and sorting, stored under a name. You can share a view with the team or make it the default. See The basics.
Scan
A job that reads data from the shop and checks it, for example a quality scan. A scan changes nothing in the shop.
Sensitive permission
A permission that exposes money, people or bulk data. Every use is logged. In the role editor it is marked sensitive.
Setup place
One place where a shop is set up, for example the AI key or the text style. The page Setup lists all of them with their state. See Setup.
Shopware account
An account that signs in through Shopware. Name and password come from there.
Sign-in plugin
An optional Shopware plugin. With it people open plinth straight from the Shopware administration. See Onboarding wizard.
Snapshot
The stored values from before a change. plinth saves a snapshot before it writes many entries, so the change can be undone. See Bulk editing.
Suggestion
What the AI or a rule proposes. A suggestion never changes anything by itself. A person accepts or rejects it.
Two-factor authentication
A second proof in addition to the password: a code from an authenticator app, a passkey or a recovery code. See Signing in.
Undo
Taking back the changes of a job or run. The earlier values are restored from the snapshot. The job then shows Undone. See Jobs.
White-label
The look of plinth for a company: product name, accent color, domain and logo. It applies to every shop of the company.