What is hidden inside “replace the catalogue PDF”?
A catalogue update can look like one upload while involving several different kinds of work. The number of files is a poor measure when those files contain product variants, languages, unstructured tables and claims that different people must approve.
This fictional scope review follows a supplier preparing to replace a bilingual product brochure. It does not assign invented prices. It shows how to identify the work before comparing estimates and how to avoid paying repeatedly for a fragile source process.
Inspect the material instead of counting its filename
Brochure D-6 contains six products and two language sections. Three product tables are selectable text. Three are images of tables, including small dimension symbols that are difficult to distinguish at the intended display size. Two products also have variant-specific notes that are absent from the general summary page.
The website currently has six product pages, each linking to the same brochure. The proposed update is described as “one new PDF and the Bosnian version”. Inspection establishes that the PDF already contains both languages, but the web pages have independently maintained descriptions. Replacing the download will not update those twelve product-language descriptions or establish that they agree with the revised tables.
The work inventory therefore separates these items:
| Material | Review needed before publication |
|---|---|
| Six product records | Confirm identity and the approved source for changed facts |
| Twelve product-language descriptions | Check the affected meaning and responsibility for each version |
| Three image-only tables | Obtain an authoritative readable source or carefully reconstruct and verify the values |
| Two variant notes | Associate each note with the correct variant rather than the whole range |
| One shared download | Confirm file identity, language coverage and the intended current/historical treatment |
The counts describe this example. They are not a formula for every catalogue.
Distinguish transcription from approval
Text extraction can reduce retyping where the source permits it. It does not confirm that a dimension was interpreted correctly, that a note applies to every variant or that a translation uses the approved terminology.
The project team asks for the original table source. For two image tables, the supplier provides an approved spreadsheet. The third has no verified editable source, so its reconstruction requires a separate comparison by the technical owner. The team does not mark all three “automatically converted” because one extraction process produced readable characters.
Native-language review and technical approval also answer different questions. A fluent sentence may still make the wrong product claim. A correct technical value may still be placed under an unclear label. The estimate needs to identify both responsibilities without treating them as duplicate administration.
Choose a maintainable source boundary
The team compares continuing to edit the brochure and web pages independently with maintaining approved structured product facts that feed the relevant web presentation. The second option does not magically generate a fully designed or accessible PDF; it provides a clearer source for the facts that recur.
For the first release, the owner approves a limited change: publish verified web tables for the six products, associate the two variant notes precisely and retain the approved brochure as a clearly labelled download. The unverified table is held until its comparison is complete. Brochure redesign and automation of future PDF production are separate possibilities, not hidden additions to this update.
The worked result is a scope with named sources and review units. It is no longer “one upload”, but it also avoids an automatic commitment to rebuild the entire publishing system.
Include the next update in the comparison
An editor rehearses changing one approved table value and identifying the affected language descriptions and download. The rehearsal reveals whether the source boundary is usable or whether the next person will return to editing an isolated image.
Acceptance should compare the visible tables with their approved sources, check variant placement and review the downloadable material separately. Accessible presentation requires checks of the implemented content and document; putting the same information on a web page does not establish that every format is now accessible.
The recurring costs may include source preparation, technical approval, language review and document maintenance as well as software support. Each should have an owner. Pricing and scope explains how to compare those responsibilities across proposals, and supplier-catalogue development addresses the structure behind the files.