Nucleo PIM

Getting started

Open the PIM from the workspace selector after signing in, or switch to it at any time from the sidebar. The PIM workspace is organized around a few areas:

• Home — your landing page, with key metrics and an ask bar to query Atomo.
• Catalog — Products, Categories and Promotions.
• Inventory — stock on hand across your locations.
• Insights — catalog analytics.
• Configuration — general settings, attributes, attribute sets, SEO rules, markets, languages, locations, integrations, imports and exports.

Everything you see is scoped to your workspace: your catalog, your attribute model, your markets and channels. What you can edit depends on the role assigned to you by an administrator — viewers can browse, editors can change products, and configuration is reserved for admins.

Catalog & products

Catalog → Products is the master list of everything you sell. It is built for large catalogs: search, filters, sorting and pagination all live in the URL, so any view you build can be bookmarked or shared with a colleague and they will see exactly the same slice.

Search and filters

The command bar at the top combines free-text search with filter tokens. Click the bar to pick a dimension — Status, Brand, Category, Attribute set, price range or stock range — then choose the values. Most filters support both "is" and "is not", so you can exclude as easily as you include. Active filters show as inline tokens you can edit or remove one by one.

Saved views

Once you have a filter combination you use often, save it as a view: it stores the filters, the sort order and the search text together. Views appear in the switcher on the left of the command bar, so jumping between "everything", "drafts to review" or your own slices takes one click.

Columns

Show, hide and reorder the list columns — SKU, product type, gender, price, channels, stock and status — from the columns control. Your layout is remembered per browser.

Bulk actions

Select one or more rows and the toolbar switches to bulk mode. From there you can set the publication status, assign a product type or brand, or delete the selection (with a confirmation step). Bulk actions respect your permissions.

1. Open Catalog → Products.
2. Type in the command bar to search, or click it to add filters.
3. Click Save view to keep the current combination for later.
4. Click any row to open the product editor, or select rows for bulk actions.

The product editor

Every product opens in a two-column editor. The left column holds the content — images plus six tabs: Info, Attributes, Variants, Pricing, SEO and Translations. The right rail holds the operational controls: the publishing engine, the completeness score and the activity history, always visible while you scroll.

Images

Upload product images directly in the editor (JPG, PNG and WebP), drag to reorder them (the first image is the cover) and remove the ones you no longer need.

The Info tab

• Core fields — title, rich-text description and the SKU, with inline rename, server-side uniqueness validation and copy-to-clipboard.
• Primary attributes — attributes flagged as "visible in product page" (like Brand) are edited as first-class fields here, in the order defined in Configuration.
• Base pricing — the product-level Price, Discounted price and Cost; per-variant and per-market pricing lives in the Pricing tab.
• Compliance and customs — VAT class, HS code (customs tariff), country of origin and weight in the workspace weight unit.
• Category assignment — assign the product to one or more nodes of the category tree via an expandable tree with chips, without leaving the editor.

Creating a product

1. Click Add product in the catalog list.
2. Enter the product name — the SKU is generated automatically, and you can rename it later from the Info tab.
3. Pick the attribute set the product belongs to and fill its attributes.
4. Generate variants, set prices, then save.

Variants & SKUs

Products are sold as variants — one row per concrete combination of options, typically size. The Variants tab has two parts: a generation panel on top and the table of persisted variants below.

1. In the generation panel, tick the option values that apply to this product (for example the sizes it actually comes in), optionally marking a primary axis.
2. Click Generate: the PIM creates one variant per combination, skipping any that already exist.
3. Adjust individual rows — SKU, barcode and available stock are editable inline, with a running total of available units. Stock entered here is written to your default location.
4. Click Save changes to persist every edited row in one go.

Variant SKUs are seeded from the product's base SKU plus the option values, following the SKU pattern defined at workspace level — separator (underscore, hyphen, dot, slash or none) and casing (as entered, UPPERCASE or lowercase), with a live preview — so codes stay consistent across the whole catalog.

Attributes & attribute sets

Attributes are the reusable dimensions that describe your products — color, material, gender, season, size scales and anything else your business needs. You manage them once in Configuration → Attributes and reuse them across the catalog.

• Dropdown — a single choice from a predefined option list.
• Multi-select — several choices from an option list, shown as toggle chips.
• Swatch — color choices rendered as swatches.
• Text, Number and Yes/No — free-form values.

Attribute properties and option values

• Each attribute has a name, a unique code, a Required flag and a "Visible in product page" flag that promotes it to a first-class field on the Info tab.
• For option-type attributes, a value matrix manages the value code, the swatch color, one label column per active language, drag-and-drop ordering, and value creation and deletion.
• Attribute and value labels are maintained per language, and can additionally be overridden per sales channel — a different label on your storefront than internally.
• System attributes (like Brand or VAT class) are managed centrally; administrators decide whether store-level roles may edit their option lists.
• The attribute registry shows, for every attribute, which sets reference it, product counts and variant-axis usage — deletion is blocked while an attribute is still referenced.

Attribute sets

An attribute set bundles the attributes a family of products needs (a footwear set and an apparel set will differ). Per set, attributes can be marked as variant axes — the axes drive variant generation. On the product's Attributes tab you pick the set, and the editor renders one dedicated control per attribute; attributes used as variant axes are managed in the Variants tab instead. Attributes marked as required in the set drive the completeness score, so the team always knows what is still missing.

Categories

Catalog → Categories manages the category tree: a searchable, collapsible explorer on the left and the editor for the selected node on the right. Create, move and delete nodes directly from the tree; search auto-expands the matching branches so you never dig manually.

Editing a category

The right pane edits the selected node: name, rich-text description and status (Active, Draft or Hidden), plus per-category SEO — meta title, meta description and URL slug. Products are assigned via a searchable pick list with removable chips, and assignments can also follow a smart rule — the same rule builder used for promotions — so a category can populate itself from product data, alongside or instead of manual picks.

Per-channel category trees

The canonical tree is the Global one. Switch the channel selector to see the effective tree for a sales channel: any field you change on a channel tab is stored as an override on top of Global, and untouched fields keep inheriting. "Reset to Global" drops the whole override for that node.

Channels & per-channel overrides

Your catalog feeds more than one destination — an e-commerce storefront, B2B feeds, marketplace exports. In the PIM each destination is a sales channel, and the product editor is channel-aware.

Global is the master record: every field is editable there and it is the single source of truth. Switching the editor to a channel puts it in override mode — you edit only the fields that must differ on that channel (copy, attributes, prices), and everything else inherits from Global, shown read-only. Clearing an override makes the field inherit again.

• Content overrides — name, description and attribute values per channel.
• Price overrides — channel-specific prices on top of the canonical price lists; empty a price to fall back to Global.
• CSV feed channels are flat exports: per-size pricing without the market grid, with their own editable SEO.

Markets & price lists

Configuration → Markets models where you sell. A market groups one or more countries that share a currency and a language fallback; VAT is edited per country inside the market, since rates differ even where everything else is shared.

1. Create a market and give it a name.
2. Add the countries it covers — each comes with a standard VAT rate you can adjust.
3. Pick the market's currency, default language and any additional locales.
4. Attach one or more price lists to the market.

Prices live per variant and per price list, and price lists belong to a market — a price list is created automatically with each market, in the market's currency — so the product's Pricing tab groups the price grid by market, one sub-tab each. Per variant the grid carries five fields: Price, Discounted price, a computed Discount %, Sale start and Sale end, so discount windows can be scheduled at variant level.

The workspace's currencies and languages are managed alongside markets in Configuration — add currencies, set the default, remove unused ones — and everything you set here feeds the pickers across the app.

Publishing

The publishing engine sits in the product editor's right rail and answers one question: where is this product live, and where should it be?

• Status — Active, Draft or Archived, settable globally and per channel (with an explicit "inherit from Global" state). Archived is the terminal state for retired SKUs.
• Channel sync — one toggle per sales channel decides whether the product syndicates there.
• Scheduling — each channel can carry a publish and a de-publish date (shown as "Scheduled / Until" indicators), so a launch goes live and a capsule retires on the right days without manual intervention. Individual markets can carry their own schedule window.
• Scope — inside a channel you refine where the product appears: by market, and for storefront channels also by physical retail location.
• Tags — free-form product tags with suggestions from the tags already used across the catalog.

The activity feed below records what changed and when, so handovers between teammates need no archaeology.

Completeness

A PIM's job is to get every product ready to syndicate — completeness makes that measurable. Every product gets a 0–100 score, computed across four weighted dimensions:

• Info — name, description and a publication status are set.
• Media — at least one product image.
• Attributes — every required attribute of the assigned set is filled. This is the heaviest dimension: it is the core enrichment signal.
• SEO — meta title, meta description and handle present and within length limits, plus translation coverage across your enabled languages.

In the editor the score updates live as you type, with a per-dimension breakdown and the exact list of what is still missing. The catalog list shows the same score per row, so "almost ready" products are easy to hunt down — and easy to ask Atomo about.

Promotions

Catalog → Promotions manages discount campaigns with the same list experience as the product catalog: search, filters, saved views and bulk actions over the promotion status. Each row shows the status (Active, Scheduled, Draft or Ended), the discount, how many products are covered, the validity window and a market/channel coverage summary with detail on hover.

Creating a promotion

1. Click Add promotion and name the campaign.
2. Choose the discount type — percentage off or fixed amount — and its value, and set the campaign window (start and end).
3. Pick the scope: All catalog, or Custom rule to target a subset.
4. Choose where it runs: promotions reuse the product publication rail, so status, channels, per-channel markets and scheduling windows work exactly as they do on products.

Scope rules

The custom-rule builder decides which products the discount applies to. Combine conditions on category, attribute values, product status, gender and SKU ("is one of") with AND/OR logic, nest groups for complex targeting, and mix operators freely — AND binds tighter than OR, so flat expressions read the way you expect. A live counter shows how many products currently match, and an option auto-applies the promotion to future products that match the rule.

Inventory

Inventory shows stock on hand across your whole network in one matrix: one column per location — warehouses and points of sale, each with its own icon — and a sortable network total per product. KPI cards on top summarize network-wide units on hand plus units and stocked SKUs per location.

• Expand any product row for the per-size breakdown, with each size split across locations and reconciling to the product total.
• Search, attribute filters and saved views work exactly as in the catalog list.
• Each row opens the product editor — stock quantities are maintained at variant level there, keeping a single point of truth.

Locations

Stock locations are managed in Configuration → Locations: each has a name, an address and capability flags — Ships orders, Physical store (POS) and Default location. Locations feed the inventory matrix, the variant stock in the editor and the POS module.

Insights

Insights is the module's analytics page — a read-only overview of how the catalog is performing and where it needs attention.

• KPI overview — a strip of five north-star metrics with period deltas: Revenue, Conversion, Average order value, Sell-through and Returns.
• Attention feed — severity-ranked operational alerts spanning catalog, commerce, channel, translation and SEO issues, each deep-linking to the affected area.
• Bestsellers — top products with rank, thumbnail, units sold month to date, revenue, week-over-week delta and a 30-day trend sparkline.
• Customer pulse — repeat purchase rate, 12-month customer lifetime value and a cohort retention snapshot.

Translations & SEO

Translations

Enable the languages your catalog speaks in Configuration → Languages; one of them is the workspace default. On the product's Translations tab, the default language is the master copy (managed on the Info tab), and every other locale gets its own title and description, edited inline and saved with the product.

SEO rules

Instead of hand-writing meta tags for thousands of products, you define SEO rule sets in Configuration → SEO Rules. A rule is a pattern built from chips — literal text plus tokens that pull from product fields and attributes — for each of meta title, meta description and URL handle.

On the product's SEO tab you pick the rule set (the first one compatible with the product's attribute set is preselected) and the three fields resolve live from the product's real data, with length checks inline. Need an exception? Toggle Override on a single field and hand-tune it without breaking the others. A search-result preview and a social preview show exactly what will ship.

CSV import

Configuration → Imports brings data in bulk from CSV files. Import types cover products, locations, markets, attribute values, channel status and translations (both product copy and attribute value labels).

1. Pick the import type and upload your CSV file.
2. Map the file's columns to the destination fields — the PIM auto-maps recognizable headers, and you can set any column to Ignore.
3. Review the validation preview: blocking errors (unknown SKUs, values that do not fit the field) must be fixed, warnings (like overwriting existing copy) are yours to accept.
4. Confirm — rows are imported in batches and each run is tracked, so you always know what was loaded and when.

• Templates — every import type has a downloadable CSV template, so files start from the right columns.
• Error reports — each run produces a downloadable error report listing exactly which rows were skipped and why.
• History — the import log keeps every past run with file, type, result (completed, completed with skipped rows, failed), applied/total counts, timestamp and author.

Exports

Configuration → Exports produces a CSV per data type, one click each. Exports come in two flavors:

• Round-trip exports — Products, Inventory, Markets and Locations use the exact same headers as the corresponding import template. Export, edit in a spreadsheet, re-import: columns map back 1:1 with no remapping.
• Reference exports — Currencies, Languages, Sizes, Price lists, Attributes and Categories are informational snapshots of your configuration.

The inventory export includes one row per variant and location with the available stock — handy for reconciliations and for sharing a stock snapshot outside the PIM.

Integrations & channel sync

Configuration → Integrations manages the platforms your catalog syndicates to. Two kinds are available: an API connector for your commerce platform (Shopify) and a scheduled CSV file export delivered over SFTP (host, port, credentials, remote path and optional filename timestamping). Each platform can be enabled or disabled independently.

Sync scheduling

For API connectors, each data stream — Products, Inventory, Prices, Translations and Media — has its own schedule row with a mode: Real-time, Scheduled (cron expression), Manual or Off, plus last-run visibility. CSV exports run on a single cadence, scheduled or manual.

Attribute mapping

Each attribute is mapped towards the channel's data model — a Shopify metafield (namespace and key), a tag template, or excluded from sync — with a coverage indicator showing how many attributes are mapped ("N of M mapped").

Workspace settings

Configuration → General holds the workspace defaults that shape the whole module: default language, time zone, weight unit, default currency and date format (DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD or D MMM YYYY).

Feature access

Admin-only capability toggles gate sensitive actions for the entire workspace: manual price editing, SEO editing, product creation and product deletion. Turning a capability off makes the corresponding surfaces read-only for every user, regardless of role.

Atomo on the catalog

Atomo is the Nucleo AI assistant, and in the PIM it knows your catalog. Open it from the top bar and it slides in as a right-rail panel next to whatever you are doing — it never takes you away from the page.

Atomo answers in real time, streaming, and is scoped to your workspace: it sees your products, your completeness scores and your channels, and nothing else. When you open it fresh, it suggests prompts contextual to where you are. On the catalog, typical asks are:

• "Show me the Draft products with completeness above 60% that are ready to publish."
• "Find the SKUs below 40% completeness and tell me what is missing."
• "How many products are active on each sales channel?"
• "Draft three description variants for a new capsule collection."