Separate information by its rate of change: stable specifications in a product reference, prices in an approved dated commercial source, and availability in a system or explicit confirmation process. Do not make a static PDF look like a live stock feed. Choose a maintenance model your team can operate, then design the catalogue around it.
A cover date helps, but does not by itself explain the validity of every price or when availability was confirmed. Readers need to know what a figure represents, when it was updated and how to obtain an offer appropriate to their request. Your team needs an owner who can withdraw an obsolete version.
Choose a maintenance model
| Model | Useful when | Maintenance responsibility |
|---|---|---|
| Specification catalogue without prices | Pricing changes or depends on the request | Product updates and a clear quotation route |
| Catalogue plus separate price list | Specifications change less often than prices | Correct item-code relationships across both |
| Catalogue with dated prices | Scope and usage period can be defined | Reissue and withdrawal of previous copies |
| Digital channel using an approved data source | Frequent updates justify the workflow | Permissions, review, publishing and connection tests |
Do not choose a connected channel merely because it appears sophisticated. Without price ownership and update rules, it may distribute mistakes faster. A product catalogue can remain a useful specification and comparison tool while pricing is handled separately.
Define what price and availability mean
The commercial owner should approve currency, sale unit, whether a figure covers an individual item or pack, and conditions necessary to interpret it. Relevant specialists should review contractual or tax-related wording rather than leaving it to the designer. Do not copy old conditions simply because they fit the page.
For availability, distinguish an item included in the range from an item currently available and one requiring confirmation. Catalogue inclusion does not establish warehouse stock at the moment of reading. Avoid a green availability indicator if the file is not connected to a reliable, tested update source.
Keep the language equally precise in Arabic and English. “Available to order” and “in stock” can lead to different expectations. Select wording that reflects the actual process and have its owner approve it.
Worked hypothetical: a distributor separates specifications and prices
Imagine a distributor with forty catalogue items. Some prices change during the selling cycle while specifications remain comparatively stable. The quantity is illustrative. The team chooses a versioned specification catalogue, a separate price list with approved dates and conditions, and a route to confirm quantity and delivery requirements.
Three prices change. The owner creates a new price-list release without redesigning forty product pages. Review checks the three item codes, sale units and relevant period before approval. The catalogue changes only when a specification, image or range item changes.
Later, one item is discontinued. The owner updates the product reference, catalogue and related price list. Removing only its price would leave the catalogue suggesting that it remains part of the orderable range.
A link points to the team's controlled location for the current list. Internally, the team recognises that previously downloaded files do not update themselves. Salespeople receive the release notice and stop reusing old attachments. A customer needing a specific order receives an approved quotation for that request rather than an assumption that an old list remains valid.
Maintain a release register
Record output name, language, version, approval date, owner, distribution location and reason for change. Connect each request to affected item codes and identify whether it changes wording, imagery, pricing or links. Filenames such as “final-new-latest” do not establish reliable status.
Use a few understandable states: draft, in review, approved for distribution, superseded and withdrawn. Retain earlier releases according to the organisation's policy, but keep them away from the active sales folder. A material error may require immediate withdrawal without waiting for a whole-document redesign.
Distinguish correction from scheduled improvement. A wrong ordering code may block use of a page, while a preferred photograph can wait for the next planned release. Give the responsible owner a way to make that decision explicitly.
When a CMS becomes useful
Multiple channels, editors and frequent changes may justify CMS development with defined fields, permissions and Arabic–English workflows. A CMS does not automatically include live inventory or pricing integration. Define and verify those sources and connections separately where required.
If the challenge is mainly editorial, a controlled reference and approver within content strategy and production may be sufficient. Test the process manually before commissioning a larger system: can the team identify who approves a change and every affected output? If not, resolve ownership and definitions first.
The right acceptance test follows a realistic change from source to distribution. Modify an approved test item, review both languages, generate the output and confirm that users obtain the correct release. This reveals gaps that a demonstration of an editing screen alone may miss.
Maintenance acceptance checks
- Item codes connect catalogue and pricing without ambiguity.
- Prices, sale units and conditions have accountable approval.
- Static outputs do not imply live inventory.
- Every release has a date, status and owner.
- Shared information changes are reviewed in both languages.
- Links or access codes are tested in the actual distributed output.
- The team knows how to withdraw a wrong version and notify internal users.
Frequently asked questions
Should prices always be removed from catalogues?
No. Decide from the sales process, frequency of change and maintenance capacity. Useful prices can remain where scope and conditions are clear and release control is practical.
Is a QR code enough to provide current prices?
It is only a route to information. Its destination still needs an owner and maintenance, and readers need to know whether the information is general or requires a specific quotation.
Does an emailed PDF update after distribution?
A downloaded attachment remains an independent copy. Replacing a file in your own location does not automatically replace a copy saved on a recipient's device.
What should we send LAB first?
Share the catalogue, price list, data sources and actual pattern of changes. Those inputs help choose a realistic maintenance model and the appropriate design, content or system scope.