Skip to content

Platform · Grid View

Everything you do in the spreadsheet, on the catalog itself.

Thousands of products, every attribute a column, and the values the agent could not settle marked in the cell. You fix them where they are, and export the view exactly as you built it.

The CommerceClarity grid: a catalog of products with their attributes as columns, values the agent flagged in amber, and a status bar counting issues and missing values.

Views and export

Build the view once, export it as it is

A view is a job: the columns it needs, the families it covers, the filter that finds its rows. Save it under a name, duplicate it for the next channel, and export it as it is, in the column order you set.

Named, duplicated, updated
A view is yours to keep, rename, and hand to someone else.
One view per channel
The online store and the marketplace each get their own columns.
The export is the view
Same columns, same order, ready to send.
The grid with the view switcher open: saved custom views, all products, errored products, and save as new view.

The columns

Every attribute you have, the few this job needs

The picker searches your attribute model, and the model is not flat: Size on sneakers and Size on apparel are two attributes, so they are two columns. Show the ones this job needs and hide the rest.

Search instead of scrolling
Type the attribute you are working on and it is on screen.
Per family, not per catalog
Different families, different attributes, different columns.
Show only, or hide all
One attribute across every product, or a clean screen to start from.
The attribute picker open over the grid, with attributes scoped by family and the show only, show all and hide all controls.

Review

Every problem is already marked

An issue can be a value two sources disagree on, or a description that does not sound like you. The panel names the rule it breaks, shows the rewrite in your tone, and lists what it read to decide. Accept it or keep what you had, then on to the next one.

Your rules, checked
The agent is scored against your tone of voice on every value it writes.
The rewrite, ready
The panel shows the sentence it would publish instead.
What it read to decide
The sources are on the panel, so you can check the call it made.
The review panel beside the grid: the current short description, the rule it breaks, the suggested rewrite, and the related attributes.

At catalog scale

A thousand rows in one gesture

Filter to the products that share a problem, select them, and act on all of them at once: run an agent, move the status, tag them, build a parent from the variants. The cells are typed, so a choice list edits as a choice list.

Filters that hold a condition
Status, category, code, tag, date, combined and kept.
Typed cells
Text, number, boolean, single and multi select, rich text, images.
Run an agent on the selection
The grid is where the work starts, and where it comes back.
The selection toolbar over the grid: six products selected, run agent, and the more menu.

How it gets set up

Configured with you, then yours

Your attribute model, your families, the sources each attribute may read from, the threshold that decides what waits for a person. We set it up with you, and your team changes it from then on, without opening a ticket.

Questions

Questions we get asked

Is this just a spreadsheet with a different name?
It does what a team already does in a spreadsheet, on the catalog itself rather than on a copy of it. Cells are typed, the rules are checked as you work, and the work is already in the catalog when you are done.
We have hundreds of attributes. Do we see all of them?
Only the ones the job needs. Columns are searched rather than scrolled, chosen per family rather than per catalog, and a view can show only a handful or hide everything else.
Does the export match what we see?
Yes. The export is the view: the same columns in the same order you built. Views are named, duplicated and updated, so the file a channel gets always comes from a saved view.
How do we find the products that need attention?
You walk the problems instead of hunting for them. Values that failed a rule are marked in the cell, the suggested rewrite is ready, and what the agent read to decide is one click away.
Can we act on thousands of rows at once?
Yes. A filter holds a condition instead of a one-off search, the selection stays as you work, and you can run an agent on it in one gesture.

Open it on your own catalog

Bring one category and the attributes you never got to fill. Half an hour in the grid tells you more than a deck.