Search and take stock
Your assistant finds your products and shows, for each slot, how many of your families have at least one published file.
MCP AI Tools — built into the platform
AI SKU Management
Manage SKUs, product data, and digital assets by talking to your AI. SSMS connects Claude or another MCP-compatible assistant directly to your catalog, with governed access scoped to your organization.
AI ClientMCPYour Catalog
How many of my families have a published hero image?
get_slot_coverage
Hero image7 of 9 families (78%)
Assign demo-a-hero.jpg as the hero image for the Family A products.
preview_bulk_assignPreview
DEMO-A-0012+ demo-a-hero.jpg
DEMO-A-0019+ demo-a-hero.jpg
DEMO-A-0027+ demo-a-hero.jpg
Nothing is written until it's confirmed.
AI Access
What is AI SKU management?
AI SKU management is operating your product catalog through an AI assistant instead of screens and spreadsheets: the assistant searches live SKU data, audits completeness, stages bulk changes, and ingests assets. Product edits, deletions, bulk changes and imports take two steps: a preview, then a confirmation that applies exactly what the preview showed. SSMS writes none of them without that confirmation.
With SSMS this is not a bolt-on integration: the platform exposes its catalog to your own AI through the open Model Context Protocol, with OAuth 2.1 security, access limited to your workspace, and an audit trail.
AI Client
MCP
Your Catalog
Tools your AI can call
How it works
Connect your assistant
An admin enables AI Access and connects Claude or another MCP-compatible assistant over OAuth 2.1 — scoped to your organization, revocable anytime.
Ask in plain language
"Show me the SKUs in family A." The assistant calls the catalog directly — live data, not a stale export.
Preview, then confirm
Product edits, deletions, bulk changes and imports take two steps: a preview, then a confirmation that applies exactly what the preview showed. SSMS writes none of them without that confirmation. Every change the assistant makes lands in the audit log.
Capabilities
What your AI can do in SSMS
Safe bulk operations
Assign assets or update fields in bulk. Product edits, deletions, bulk changes and imports take two steps: a preview, then a confirmation that applies exactly what the preview showed. SSMS writes none of them without that confirmation.
Spreadsheet imports
Hand the assistant a spreadsheet and let it map columns, validate rows, and stage the import — with a dry-run preview before commit.
Asset ingestion
Give the public web address (https) of a product image you have the right to use, up to 100 MB: the platform fetches it and registers it in your library.
Attribute hygiene
Fix values, add missing options, and keep each family's attributes in order.
Exports & distributor links
Generate SSMS exports on demand, and the list of your products' permanent links, which always point to the current version.
Enterprise governance, not an experiment
AI access to your catalog is a governed surface: OAuth 2.1 credentials scoped to your organization, per-credential rate limits, audit logs, and an explicit admin data-egress acknowledgment before anything is enabled. Your assistant sees your catalog and nothing else.
AI ClientOAuth 2.1Revoke
Audit log
09:43:30preview_bulk_assignDemo
09:44:02commit_bulk_assignDemo
AI SKU management — FAQ
AI SKU management means operating your product catalog — SKUs, attributes and digital assets — by instructing an AI assistant instead of clicking through screens. The assistant searches, audits, and stages changes against live catalog data. Product edits, deletions, bulk changes and imports go through a preview before they're confirmed.
Claude, which AI Access is tested with, and other assistants that support the Model Context Protocol (MCP) and its OAuth sign-in. You bring your own AI account: SSMS has no lock-in to a model or vendor.
For product edits, deletions, bulk changes and imports, SSMS requires a preview, then a confirmation that applies exactly what the preview showed. Your assistant shows you the preview and asks for your approval: set it to ask every time. Some actions are written directly, with no preview: creating a family, an attribute, an attribute option or a folder, renaming a file, adding a file. Every change lands in the audit log, and each credential is rate-limited.
Yes, with the one you connect. When an admin enables AI Access, the catalog data your assistant requests is sent to it, and so to the AI provider you chose. What that provider does with it, training included, is governed by your agreement with them. Nothing flows before an admin's acknowledgment, and each connection can be revoked. On our side, our own AI tools (Anthropic) see your catalog data only to fix a specific problem, never your personal information, and that data isn't used for training.
An admin enables AI Access in SSMS, then adds the SSMS connector in the assistant. Authentication is standard OAuth 2.1, with no API keys to copy around.
AI Access is part of the SSMS platform. You pay your AI provider separately, since you bring your own assistant.
Get started