> ## Documentation Index
> Fetch the complete documentation index at: https://docs.readyforcommerce.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Ready for Commerce is an ecosystem that currently contains two products, PIM and Repricer, standing on one shared foundation: one identity, one organization, one team, one bill. Do not call it a platform with features, and never hint at an unreleased product.
> PIM connects to Shopify, Amazon, Square, Google Merchant Center and BigCommerce. Repricer connects to Amazon, Walmart, Shopify, BigCommerce, eBay and Square. The two products do not share one list, and each integration is authorized separately inside each product. The roster grows on purpose, so describe what the product does and let a table carry which integrations do it today, instead of counting them or writing that only one does something.
> Integration is the word this product uses, and it is the default in the documentation: the connection, the account, the Integrations screen, the per-account settings and the sync state are all integrations. Channel is reserved for the narrow sense of a destination where a listing lives, as in a product being live on a channel or archived on the channel.
> Newegg is not a supported channel. Do not describe it.
> On Amazon, PIM manages the offer only: price, availability and condition. It does not publish listing content such as titles, descriptions, images or specifications.
> Sign-in is passwordless: a single-use code emailed to the user, or Google. There are no passwords anywhere, so never describe a password, a sign-up with a password, or an email confirmation link.
> There is no public API for customers and no customer-facing webhooks. There is no organization-wide activity feed and no audit export, but the PIM does keep version history on products, brands, categories, tags and specifications, with who changed what and a restore, so never write that changes are not recorded or that an edit cannot be undone. Do not describe capabilities that are not documented here.
> Never write that the products have no AI, and never write that anything is AI-powered. Both are wrong. The PIM's image Optimizer runs AI-backed transforms the seller starts on purpose: Upscale, Remove background, and the region selection behind Refine. The Repricer reads competitor prices off web pages on the server. No control, badge or tooltip in either product names AI, and the seller never writes a prompt, so describe what the buttons do in the app's own words instead of reaching for the word.
> A PIM product, brand, category or variant can be switched off per connected integration account. Hover the channel badge and the switch is beside the account name in the card that opens. It carries no visible caption, so never call it the Sync switch: Sync is only its accessible name. On a variant-grained provider, Amazon today, the switch moves into the variant editor. On a product it asks whether to delete it from the channel, archive it there, or leave it live. Disabling stops publishing, not reading. There is still no per-field sync toggle.
> The PIM's image Optimizer replaced a feature called Squarify, which no longer exists. It resizes to an aspect ratio or to exact dimensions, removes backgrounds, upscales, trims the transparent margin around a cutout and re-centers it, pads, fills and re-encodes, and it always publishes a new asset instead of changing the original. Nothing crops into the picture: the subject is always contained whole.
> The PIM has no repricing engine and never reacts to a competitor's price. It does build the price it publishes to each integration account from the seller's own fields, configured in that account's settings, so do not write that the PIM has no pricing rules.
> Neither product has an in-app notification center, bell or inbox. Notifications are delivered by email only.
> Billing is per organization and per product, and only the organization owner can see or change it. Team members are free and uncounted, so never describe seats or per-user pricing.
> The seller never picks a plan. Each product has twelve price tiers assigned automatically from usage: the PIM from catalog product count, which includes drafts and archived products, and the Repricer from trailing 30-day sales. Nothing is feature-gated by plan and exceeding a tier never blocks work, so never write that a feature requires a higher plan.
> A subscription that is past due or paused makes the product read-only, which stops repricing and blocks edits without deleting data. Only a canceled subscription locks the seller out. Nothing is ever charged without a payment method on file.
> Pages containing the text 'This page has not been written yet', or its Spanish equivalent 'Esta página todavía no está escrita', are placeholders. Do not treat their headings as documented behavior.
# Saved views
> A saved view remembers how you set a table up, so the list you rebuild every morning comes back with one click and can be shared with your team.
A saved view is a table setup you keep. You filter, sort or search a table until it shows exactly the rows you care about, then save that setup under a name. From then on, you bring the whole thing back by picking the name from a list.
Most people save a view for a check they repeat: draft products that still have no price, imports that failed this week, assets no one has assigned yet. Instead of rebuilding the same filters every morning, you build them once. You can also share a view, so your whole team reads the same list the same way.
The control for all of this is in the header bar at the top of the app, between the page title and the search. Eleven tables have it: products, brands, categories, tags and the three specification tables under `Catalog`, your [asset library](/pim/assets), and the imports, exports and data sources tables under `Uploads`. On most tables it stays hidden until you change something or save your first view. Products is the exception, because you start with three views there, and a section further down explains them.
## How to save a view
From `Catalog`, select `Products`, or open any other table from the list above. Filter, sort or search until the table shows what you want. The [filters](/pim/filters#how-to-filter-a-table) page explains how the filter panel works.
As soon as you change something, the control appears in the header bar, between the page title and the search. It reads `Unsaved View`.
Click `Save`, the button beside the control. A dialog called `Save View` opens over the page with one box, `View name`. Type a name of up to 30 characters and click `Save`.
That is the whole flow. The control now shows your view's name, and the view stays on that table until you delete it. To bring it back on any later visit, click the control and pick the name from the list that opens.
Everything below explains the control, the buttons and the dialogs one at a time. You do not need any of it to save and reuse a view.
## Every option in detail
The control is a dropdown in the header bar, and the actions are a row of small buttons beside it. Which buttons you see depends on what the control reads, and on whether the view you are on is yours.
### What the control tells you
The text on the control is a status. It tells you whether you are on the plain table, on a saved view, or on something you have not saved yet.
| The control reads | You are | Buttons beside it |
| --- | --- | --- |
| `All Products`, or that table's own version of it | On the plain table, nothing changed | None |
| `Unsaved View` | On a plain table you have filtered | `Reset` and `Save` |
| A view's name | On a saved view, exactly as saved | `Set as Default`, plus `Rename`, `Share` and `Delete` on your own views |
| `Unsaved Changes` | On a saved view you have changed | `Reset` and `Save As`, plus `Save` on your own views |
While you have nothing saved and nothing changed, the control hides itself, so a header with nothing in that spot is normal. On products it is always there, because of the three views you start with.
| Table | First entry in the list |
| --- | --- |
| Products | `All Products` |
| Asset library | `All Assets` |
| Brands | `All Brands` |
| Categories | `All Categories` |
| Tags | `All Tags` |
| Specification groups | `All Groups` |
| Specification definitions | `All Definitions` |
| Specification values | `All Values` |
| Imports | `All Imports` |
| Exports | `All Exports` |
| Data sources | `All Data Sources` |
### Switching views and going back
Click the control in the header bar and a list opens. The first entry is always `All Products`, or the matching name on another table, and picking it returns you to the plain table. Below it are your own views and every view shared with you, in the order they were created.
Two small badges appear in this open list, and only here: `default` on the view your table opens with, and `shared` on a view someone else shared. The closed control shows the name alone.
Pick a name and the table changes immediately: the view's filters, sort and search replace whatever was on screen.
`Reset` is the way back when you have changed something. While the control reads `Unsaved View`, clicking `Reset` clears your changes and returns you to the plain table. While it reads `Unsaved Changes`, clicking `Reset` throws away your changes and puts the view back the way it was saved.
### What a view keeps
| Kept in the view | Left out on purpose |
| --- | --- |
| Every filter condition | The page you were on |
| Whether your filters combine with and or with or | How many rows per page |
| Whatever is in the search box | Which rows you had selected |
| The sort | How your columns look |
A view keeps what decides which rows you see and in what order. Where you happened to be at one moment is left out. A view that put you back on page 7 would be a nuisance every time you opened it.
Your columns are the other deliberate exclusion, and they have a section of their own at the end of this page.
A view stays on the table you built it on. A view saved on products never shows up on brands, and the same name can exist on both tables without colliding.
### The three views you start with
Everyone who joins an organization gets three personal views on the products table: `Active`, `Draft` and `Archived`. Each one filters products to one status and sorts them by most recently updated, so `Draft` is your list of products to finish from the day you arrive.
They are normal views that come ready made. They are yours alone, not shared, so you can rename them, change what they show, or delete them, and no one else's copies move. None of them is a default: products still opens on `All Products` until you set one yourself.
The three names stay in English whatever language you use the app in. A view's name is stored data, like a product title, so the app never translates it.
### Changing a view you saved
Everything here starts the same way: click the control in the header bar and pick the view's name, so you are on the view. The view also has to be yours. What you can do with someone else's view is covered under sharing, below.
**To rename it**, click `Rename` beside the control. The `Rename View` dialog opens with the same `View name` box, already filled in. Type the new name and click `Rename`.
**To change what it shows**, change the table: add a filter, clear one, sort differently, type a search. The control flips to `Unsaved Changes`. Click `Save` beside it and the view is overwritten right away; no dialog opens and nothing asks you to confirm. Everyone who uses the view gets the new version from then on.
**To branch a copy instead**, click `Save As` beside the control while it reads `Unsaved Changes`. The `Save View` dialog opens, you give the copy a name, and the original is left alone.
A name has to be unique among the views you can see on that table, your own plus the shared ones, and capitalization does not count as a difference. The dialog rejects a repeat with `A view with this name already exists`. Two people can each have a personal view with the same name, because neither can see the other's.
### Sharing a view with your team
`Share` is beside the control in the header bar while you are on a view you created. Click it and the view becomes visible to everyone in your organization, on that same table. The button then reads `Unshare`, which is also how you recognize your own shared view, because the `shared` badge is only shown to the others.
Sharing has nothing to do with roles. Every role can save views, share them and use shared ones. What you can do with a view depends on who created it, not on your role.
**Only the person who created a view can change it.** Rename, overwrite, share, unshare and delete are all the creator's. Everyone else can apply the view, set it as their own default, and take a copy with `Save As`. The copy is the intended route when a shared view is nearly right but not quite. If you change the table while you are on someone else's view, the buttons you get are `Reset` and `Save As`. There is no `Save`, so you cannot overwrite it even by accident.
Click `Unshare` and the view leaves everyone else's list at once. Anyone who had made it their default loses that default in the same moment, and that table simply opens plain for them again.
Ownership outlives membership. When the person who created a shared view leaves the organization, the view stays in everyone's list and stays shared. But no one can rename, overwrite or delete it anymore, because those actions are the creator's and the creator is gone. `Save As` is the way past it: take a copy of your own and use that.
### Making a table open the way you want
A default is a view your table applies on its own, every time you open it. It is personal: you set yours, each teammate sets theirs, and no one's choice touches anyone else's screen.
Pick any view you can see from the control in the header bar, your own or a shared one, then click `Set as Default` beside the control. From then on the table opens on that view for you. The view shows a `default` badge in the open list, and a shared view you made your default shows both badges side by side. To go back to opening plain, open the view and click `Unset Default`.
You get one default per table, so setting a second one replaces the first. A link beats your default. If you open the table from a link that already has filters in it, say one a teammate sent you, you get what the link says.
### Deleting a view
Open the view from the control in the header bar, then click `Delete`, the red button beside the control. A dialog called `Delete View?` asks you to confirm. Click `Delete` there and the view is gone, with no undo.
Deleting a shared view removes it for the whole organization, and anyone who had it as their default loses that default.
One thing surprises people: deleting the view you are looking at does not clear the table. Its filters stay on screen and the control flips to `Unsaved View`. Click `Reset` if you want the plain table, or `Save` if you want the same setup back under a new name.
### Limits
| What | Limit |
| --- | --- |
| A view's name | 30 characters |
| Defaults per table, per person | 1 |
| Views on one table | No limit |
### What a saved view cannot do
| You cannot | What to do instead |
| --- | --- |
| Save your column layout in a view | Nothing to do. Your columns stay as you arranged them, on every view |
| Edit someone else's view | Take your own copy with `Save As` beside the control |
| Share with one person only | Sharing covers your whole organization on that table |
| Set a default for a teammate | Each person sets their own |
| Give a view to a new owner | A copy made with `Save As` is owned by whoever made it; ownership never moves |
| Use a view on a different table than it was saved on | Rebuild the filters there and save a second view |
## What stays on your computer
A view decides which rows you see. How the table looks around those rows is a personal preference, and it is stored in your own browser instead of in the view. That covers which columns are visible, the order you dragged them into, how wide each one is, which ones you pinned, and how dense the rows are.
**Switching views never rearranges your columns.** That is a decision, not a gap. Your column arrangement is a habit you build over weeks, and a view that snapped it back to someone else's layout would cost more than it gave.
The consequence is easy to picture. Two people open the same shared view and see exactly the same rows in exactly the same order, each laid out in their own columns. The rows are shared, the layout is not.
Because these preferences are in the browser and not on your account, they do not follow you to another computer. Clearing your browser data puts the table's own layout back. Your views come through both, because they are stored with your organization.
## When something goes wrong
### Error messages
Saving, renaming, sharing and deleting can each fail and tell you so in a small message. None of them leaves half a change behind.
| Message | What to do |
| --- | --- |
| `A view with this name already exists` | The name is taken among the views you can see, ignoring capitalization. Pick another |
| `Failed to load saved views` | The list could not be fetched. Reload the page |
| `Failed to save view` | Nothing was saved. Try again |
| `Failed to update view` | The rename, share or overwrite did not go through, and the view is unchanged. Try again |
| `Failed to delete view` | The view is still there. Try again |
| `Failed to set default view` | Your default did not change. Try again |
| `Failed to clear default view` | Your default is still set. Try again |
### When a view disappears or changes on its own
Three changes can happen to you with no message at all, because each one is the creator of a shared view doing something to it.
| What you notice | What happened |
| --- | --- |
| A view is gone from your list | The person who created it unshared it or deleted it |
| A table that opened on a view now opens plain | Your default was a shared view, and unsharing or deleting it cleared your default |
| A shared view shows different rows than yesterday | The creator changed its filters and saved |
If a shared view you rely on keeps changing under you, take your own copy: open it, change anything, and click `Save As` beside the control.
## Where to go next
The filter panel, the conditions, and the search that a view keeps.
Acting on the rows a view brings back.
The table your three starter views are on.
The header bar the control is in, and the rest of the screen.