# Can’t save a product sheet in the PrestaShop back office

> Logging into the back office works, the product sheet opens, but saving it fails or throws an error: this specific symptom points the diagnosis towards one particular tab or module, not a general server problem. Three causes come up most often.

- Source canonique : [https://allaux.fr/en/prestashop/problemes/fiche-produit-enregistrement-echoue](https://allaux.fr/en/prestashop/problemes/fiche-produit-enregistrement-echoue)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Go through every tab of the product form language by language using the language switcher: one required field left empty in an active language blocks the whole save without showing anything on the visible tab. If every product fails, set _PS_MODE_DEV_ in config/defines.inc.php and read var/logs/ — a module hooked on actionProductSave is then to blame.

## A required field left empty on a tab that isn’t shown

The product sheet is split across several tabs: Information, SEO, Associations, Prices, Combinations, and others depending on configuration. A multilingual field left empty for a language that’s still active on the storefront can block saving the whole form, even if the currently displayed tab shows no error.

It’s one of the most common traps: the user stays on the Information tab, sees nothing wrong, while the block actually comes from an SEO field or another language never checked for that product.

## A module hooked into the product save

Hooks such as actionProductSave or actionObjectProductUpdateAfter run every time a product sheet is saved. If a module hooked into one of these hits an error, it can block the entire save, even for fields that have nothing to do with that module.

This case is often recognisable because the block affects every product, or appears right after installing or updating a particular module.

## A description that’s too long can also block saving

> A very long description, or one with complex HTML, can, depending on the database configuration, exceed a field’s size limit and make the save fail without a clear message.

## How I isolate the cause

1. **Check every tab, including secondary languages** — I go through each tab in turn, especially required fields in every active language, to spot an empty field blocking things silently.
2. **Disable modules one by one** — On a test copy, I disable recently installed or updated modules, especially those hooked into the product save, to isolate the one causing the block.
3. **Check the error logs** — Back office or server logs often give the exact name of the module or class at fault when saving fails.
4. **Check the length of text fields** — For a very long description, I test whether shortening the content allows the save to go through, which confirms a database field size limit.

## Related pages

- **PrestaShop back office inaccessible** — If it’s the login itself that fails, invalid token or a login loop, the diagnosis is different from a save that fails. ([/prestashop/back-office-inaccessible](/prestashop/back-office-inaccessible))
- **500 error or blank page on PrestaShop** — When a module erroring during a save triggers a 500 error rather than a simple silent block. ([/prestashop/erreur-500](/prestashop/erreur-500))
- **Custom PrestaShop module development** — For fixing a module or override blocking the save without breaking the rest of its features. ([/prestashop/module-sur-mesure](/prestashop/module-sur-mesure))

## FAQ

### I log into the back office with no trouble, but can’t edit a product: are these related?

No, these are two different problems. Access that works but a save that fails points towards a product sheet tab or a module, not a login issue.

### Why do I see no error at all when saving fails?

Because the error often happens on a different tab from the one displayed, especially an empty required field in a secondary language nobody checked.

### How do I know if it’s a module causing the block?

By disabling, on a test copy, recently installed or updated modules, especially those hooked into the product save, one at a time, until saving works again.

### The block only affects one product, is it the same cause?

Often not: a block on a single product points more towards a field specific to that sheet, an overly long description, an empty multilingual field, while a block affecting every product points towards a module.

### Is fixing a module that blocks the save configuration or development?

It’s development: the faulty line of code needs identifying inside the module or an override, and fixing without breaking the rest of its features.