How to manage availability texts by brand in PrestaShop without editing product by product
In a store with dozens of manufacturers, each brand has its own lead time: some ship in 24 hours, others in two weeks, and some have exceptions. PrestaShop lets you write the availability text, but product by product and in each language. With thousands of references, keeping it up to date by hand is impossible. That is why we built Available texts.
Why it is not trivial in PrestaShop
- Texts live on each product and in each language. Changing one brand's lead time means touching hundreds of product pages.
- Combinations only have their own texts from PrestaShop 8. On 1.6 and 1.7 the product's texts have to be written.
- Brand rules are not enough: part of a manufacturer's catalogue often has a different lead time.
- New or imported products must get their text without anyone having to remember.
The approach: rules, not product pages
The merchant defines one rule per brand with both texts (available now and available later) and, optionally, an HTML block, in each language. A generic rule covers brands without their own. For special cases, a brand can have exceptions limited to certain categories, with a priority when a product sits in several.
Technical decisions
Write to the native fields
The module adds no logic to the product page: it writes the texts into PrestaShop's standard fields. The theme shows them as always, with no extra cost per page and compatible with any theme, feed or integration that already reads those fields.
Applied immediately and on schedule
Saving a rule rewrites the matching products and combinations at once. A scheduled task applies the rules again to cover new or imported products, and a button does it on demand.
Each version, its own way
On PrestaShop 8 and 9 the texts of each combination are written too; on 1.6 and 1.7, the product's. Translations for 1.6, which lacks the modern translation system, are served from files generated from the same sources as the other versions.
What we learned
Many store needs do not call for a new screen but for automating what the core already has, with rules that fit the business. It is the same approach we apply to imports, supplier synchronisation or ERP integrations.
What this development demonstrates
- Extending brand management without modifying the core
- A rules engine with category exceptions and priorities
- Bulk writing to native multilingual product and combination fields
- Data model differences between PrestaShop 1.6, 1.7, 8 and 9
- Scheduled tasks to keep the catalogue consistent