This glossary explains terms you see in the Snomi panel and in the help docs. If you find a term that is missing here - write to hello@snomi.app and we will add it.
Organization and account
Organization (company account) - a company or agency in Snomi. One organization means one billing account, one team, a shared AI credit pool, and shared store limits. All team members work within one organization.
Store (project) - a separate product catalog within an organization. It maps to one online store, campaign, or dedicated feed. Examples: “Main store”, “Outlet”, “Test feed”. The number of stores depends on the plan.
Role - a user's permission level in the organization. From highest: Owner (OWNER), Administrator (ADMIN), Member (MEMBER), Viewer (VIEWER). The role decides who can edit products, invite teammates, manage billing, and change settings.
Trial - a free 7-day trial available once per organization, with no card required. After it ends, the account switches to read-only mode.
Read-only mode - the account state after the trial ends or a subscription expires. You can browse the catalog and export XML, but editing, AI generation, and import are blocked. A banner with a link to billing appears at the top of the panel.
Feed and import
Source feed (source) - an XML file with product data from the store, imported into Snomi. It is stored as a set of source values - a baseline you can always return to.
Output feed (output) - an XML file with current values after editing and optimization. This is the feed that goes to Google Merchant Center - via file download or a permanent URL.
Supplemental feed - an extra data set (CSV, TSV, or Google Sheet) layered on top of the source feed. If you already have a supplemental feed in Google Merchant Center with manual fixes, Snomi loads it so audit and optimization see the real catalog state, not only the base feed. Supplemental values override source values - the same way they do in Merchant Center.
Source vs current - on the product card (Attributes tab) you see both values side by side: where a value came from (store feed / extra source / Snomi) and what it is now. That way you always know what changed and who changed it.
Synchronization - automatic catalog refresh from the source feed on a schedule. Snomi fetches the new feed, compares it with existing data, and updates the catalog. Sync history (last 30 days) is on the import page.
Anomaly - a situation where Snomi detects something wrong in the imported feed (for example a sudden drop of more than 5% in product count). The import is paused, and a banner appears at the top of the panel with “Approve” and “Reject”. Without a decision within 48 hours, the import is automatically rejected - the catalog stays unchanged.
Product - one item in the feed, identified by a unique feed ID (id / g:id). A product in Snomi matches one item in the store catalog.
AI optimization
AI credit - the billing unit for AI usage in Snomi, assigned to the organization on a monthly cycle. Generating a proposal for one attribute of one product uses credits - how many depends on how many proposals you requested (see: proposal) and whether you enabled custom AI instructions. The base proposal pool (set in the organization) fits in the price of one credit; each extra proposal beyond that pool costs an extra credit. Credits renew every month and do not roll over.
Proposal - an AI-generated attribute variant (for example three different title versions to choose from). You set the number of proposals per attribute in the organization - more proposals mean more choice, but use more credits. A proposal needs your acceptance before it is saved.
AI queue - the view where you review, edit, and accept generated proposals. Proposals are split into tabs: Pending, Needs attention, Ready, Errors, Saved. Bulk accept (“Accept all”) covers only proposals marked as correct; those with warnings need a single decision.
Optimizer Agent - bulk gap-filling across the catalog, attribute by attribute. You pick an attribute (for example descriptions), and the agent generates one proposal for each product that is missing it. Before you start, you see a credit usage estimate. Available on paid plans; blocked in the trial.
Custom AI instructions - an option (from the Growth plan) that lets you describe how AI should write: style, length, structure. Applied to the whole catalog. Enabling instructions adds a credit surcharge to every generation.
Conversational attributes - feed fields designed by Google for conversational search (AI Mode, Gemini). Snomi generates three of them with AI: question-and-answer pairs (question_and_answer), product highlights (product_highlight), and technical details (product_detail). Other conversational attributes (for example related_product, item_group_title) are filled from feed data, not by AI.
Export and limits
SKU (in the export context) - a single product in the output feed. The export limit (for example “up to 1,500 products / store”) applies to the number of SKUs in one output feed per store. This is not the same as AI credits - the SKU limit caps the size of the exported feed, while credits cap generation volume. Both limits work independently.
Permanent URL - the address where Snomi serves the current output feed. You connect it in Google Merchant Center as a supplemental feed - Google fetches a fresh file on every sync, with no manual export.
Custom label (0-4) - optional segmentation labels in the feed, used to split products in Google Ads campaigns. You can set them manually, in bulk, or force them in output feed settings.
Locks and protection
Lock (field lock) - protection that stops an attribute value from being overwritten from outside. When a field is locked, neither store feed sync, nor supplemental, nor AI will change it. Available locks: Lock title, Lock description, Lock MPN, Lock custom labels. To overwrite on purpose, unlock the field first.
Catalog protection (anomaly) - see: anomaly. The mechanism pauses import when it detects a sudden change (for example a large share of products disappearing), before a bad feed reaches Google.
Audit and quality
Quality dashboard - a catalog score view across three dimensions: GMC completeness (whether products have required fields), data quality (how you compare to Google thresholds), and AI readiness (coverage of conversational attributes). Together they make up the overall score as a percentage.
Google thresholds (benchmarks) - reference values from official Google Merchant Center reports (for example “97% of products should have a title longer than 30 characters”). Snomi compares your catalog to those thresholds - the result is how close you are, not a pass/fail check.
Strategic AI audit - a deeper PDF report generated by AI from catalog data. It costs 100 AI credits from the organization pool, charged only after a successful generation.
Frequently asked questions
How do AI credits differ from the export SKU limit? They are two independent limits. AI credits cap how much content (proposals) you can generate in a given month. The SKU limit caps the size of the output feed per store. You can use all credits and still export the feed - and the other way around.
What happens if I lock a field (Lock) and then change the store feed? Nothing - that is the point. Lock protects the value in Snomi from being overwritten on sync. The new value from the store feed is ignored for that field until you remove the lock.
What are “source” and “current” on the product card? Source is the value from the latest store feed import. Current is the value that will go to the output feed now - after edits, AI, or supplemental. You see both side by side so you always know what changed.
What is a proposal and when does it use credits? A proposal is an AI-generated attribute variant (for example a new title). Credits are used when generation runs - not on accept or save. If you reject a proposal, credits are not refunded.