Change validation
Access from: Catalog → Products
Before saving a change to a product, Epinium checks it against the rules Amazon publishes for its product type and marketplace. That way, what is left pending to publish is something Amazon can accept, and you learn about a problem when you save, not days later when publishing fails.
The check is the same wherever you change a product from: the Properties tab, quick editing in the table, bulk editing, AI generations and tasks.
What is checked
| Rule | Example |
|---|---|
| Maximum length | A bullet point cannot go over the character limit of its category |
| Format | A price start date has to be a valid date |
| Allowed values | A list field only accepts the options Amazon offers |
| Data that go together | If you state that the product includes batteries, Amazon also asks for the battery type and number |
| Price rules | The price has to be between the minimum and the maximum you have set |
When a change is blocked
Not every place blocks the same things. It depends on whether you can see and fix the field from there.
| Where you change it from | Problems your change introduces | Problems the field already had from Amazon |
|---|---|---|
| Properties tab | Not saved | Not saved: fix the whole field |
| Quick editing, bulk editing, AI and tasks | Not saved | Saved anyway |
A product that already comes from Amazon with a problem does not hold up a bulk edit or an AI optimization: the change is saved and published as usual. If publishing then fails because of that old problem, you fix it from Properties, which is where every problem of each field is shown.
What you see if a change is not saved
Whatever does not pass the check does not touch the product and is not left pending to publish.
| Where you change it from | Where you see it |
|---|---|
| Properties tab | The problem summary, next to the save button, with a shortcut to each field |
| Quick editing in the table | A warning in the window itself, which stays open |
| Bulk editing | In Catalog → History (see the page), the Failure column counts the products that were not saved |
| AI generation | The warning "Some suggestions were not accepted"; the suggestion stays pending review |
| Tasks | The task item keeps the reason why it was not applied |
Fixing a product from Properties
- Open the product and go to the Properties tab.
- The side index marks the groups that have problems with a number. Open the group.
- Fix the field. If something is missing when you save, the summary says so and takes you to the first missing field.
- Save as pending and publish from Publish changes.
Vendor Central products
- Changes to a vendor product are always saved in its Vendor Central data.
- The description of a vendor product is a different field from the seller one, and Epinium uses the right one for each.
- The price of a vendor product is not edited from Epinium.