AP-004
A client rarely arrives at an agency asking for a better catalogue.
They ask for something specific.
A new range needs to be uploaded. Product descriptions need rewriting. Attributes need standardising.
Those are real client requests, and they need to be scoped, assigned and delivered clearly.
From the agency’s point of view, it makes sense to treat them as tasks.
But once the work is complete, the client does not simply have rewritten descriptions or a corrected set of attributes.
The catalogue itself is different.
Information may follow a more consistent structure. Similar products may now use the same conventions. A range that previously looked disconnected may now sit more coherently within the rest of the catalogue.
The client asked for a task.
What changed was the catalogue.
Agency work needs boundaries.
A client asks for 200 new products to be added. The agency needs to know which products, what information is available, what has to be prepared and what will count as complete.
A request to rewrite product descriptions needs the same clarity. Which products are included? What is changing? What will remain untouched?
Tasks make delivery manageable.
They allow the agency to estimate effort, assign responsibility, track progress and show the client what has been delivered.
That is not a limitation of agency practice. It is part of delivering work professionally.
The problem begins only when the task becomes the only way the result is understood.
If 100 descriptions have been rewritten, the agency can report that 100 descriptions are complete.
If a category has been reorganised, the agency can say the category work is done.
Those statements describe the deliverables accurately.
They do not necessarily describe what became better for the client.
Consider a client asking an agency to standardise specifications across a range of products.
The brief may define the agreed scope: review the products, correct the fields and make the specification format consistent.
That is what the agency has been asked to deliver.
But the completed task changes more than a list of fields.
Products that previously presented the same information differently may now follow one convention. Shoppers may be able to compare similar products more easily. Future products have a clearer precedent to follow.
The task has a defined beginning and end.
The effect of the task sits inside the catalogue after the work is finished.
Catalogue work is often divided because different activities require different skills.
A copywriter may improve descriptions.
A merchandiser may reorganise categories.
Someone else may correct attributes or supplier information.
Operationally, these can be separate jobs.
The catalogue does not keep them separate.
The description sits beside the specifications.
The attributes help determine filtering and comparison.
The category affects where the product appears.
Supplier information can shape the product data the agency has available to work with.
Each activity enters the agency through its own brief, workflow or person.
Each one changes the same catalogue.
That matters because a client can commission several apparently unrelated pieces of work and still receive one combined result: a catalogue whose overall condition has changed.
There is no need to remove those divisions.
Agencies still need specialists, scopes and responsibilities.
A content project does not become a taxonomy project simply because both affect the same catalogue.
The distinction is useful when deciding who should do the work and how it should be delivered.
It becomes less useful when deciding what the client ultimately gained from the work.
A client may have approved three separate scopes over six months: rewrite a group of product pages, correct missing attributes and reorganise two categories.
On paper, those are three jobs.
Inside the store, they have collectively changed how products are described, structured and found.
The jobs remained separate.
Their changes accumulated in one catalogue.
A completed task tells the agency that the requested work has been done.
It does not always tell the agency what has improved.
Suppose 80 product descriptions have been rewritten.
The task can be closed when the agreed descriptions are finished and approved.
But whether the work improved the catalogue depends on what changed.
Perhaps the descriptions now answer questions that were previously missing.
Perhaps they now follow a more consistent structure across the range.
Perhaps they simply use different wording without making the products clearer.
The number of completed items tells the agency how much of the agreed scope was delivered.
It does not by itself describe the quality of the result.
The same applies to specification corrections, attribute work or category changes.
A task can be completed exactly as scoped while producing a narrow improvement.
Another task of similar size may resolve a problem that affected an entire range.
The task can look the same even when the catalogue-level result is different.
This is where “better catalogue” needs discipline.
It cannot simply mean that work happened.
Nor should every catalogue task be treated as strategically important because it touched product information.
The improvement has to be identifiable in the condition of the catalogue.
Products may become more consistent.
Important information may become clearer.
Comparable products may follow the same structure.
The precise improvement depends on the task.
What matters is that the agency can identify the difference between the catalogue before the work and the catalogue after it.
Without that distinction, a catalogue service can easily be described only through activity.
A single task may affect only a small part of a catalogue.
That does not make it unimportant.
It simply means the improvement should be understood at the right scale.
Correcting specifications across ten products improves those ten products.
Standardising the same specification across an entire range creates a broader consistency.
Applying the same convention across more of the range extends that improvement.
Over time, separate pieces of work can begin to reinforce one another.
Descriptions follow a clearer pattern.
Attributes become more dependable.
Categories become more coherent.
Older products are brought closer to the standard used for newer ones.
No single task has to create the whole improvement.
When separate tasks bring different parts of the catalogue toward clearer, more consistent conventions, their improvements can accumulate across the catalogue.
That is different from treating every completed task as an isolated success.
The task disappears from the queue.
The catalogue retains whatever the task changed.
That is an important difference for agencies.
A completed ticket may be archived.
The improved product information remains in the store.
A content project may finish.
The clearer descriptions remain part of the products shoppers see.
An attribute clean-up may have a fixed delivery date.
The resulting structure becomes part of the catalogue the agency will work with next time.
The result therefore sits less in the record of completed work and more in the condition of the catalogue that remains.
Clients still commission individual tasks in a very real sense.
They approve scopes, budgets and deliverables.
They expect the agency to complete what was agreed.
Nothing about understanding catalogue-level improvement removes that responsibility.
But the task is the unit through which the work is commissioned.
It is not always the best unit for understanding what the client ultimately receives.
When catalogue work is successful, the result is a catalogue that is better in some identifiable way than it was before.
The client may have commissioned description work, attribute work or category work.
Those are the activities the agency performed.
The catalogue is the asset those activities changed.
That distinction explains why catalogue work can be understood too narrowly when it is described only through the jobs completed.
The work may be fragmented.
The improvements can still accumulate in the catalogue.
Agencies do not need to stop scoping catalogue work as individual tasks.
Clear deliverables remain essential.
What changes is the way those deliverables are understood and communicated.
If an agency rewrites 80 descriptions, it should be able to say not only that 80 descriptions were completed, but what became better about that part of the catalogue.
If attributes are standardised, the agency should be able to identify what became more consistent or dependable as a result.
If a category is reorganised, the agency should be able to explain what has become clearer or more coherent as a result.
This is not about turning every task into a grand strategic claim.
It is about connecting the work performed to the catalogue condition improved.
That gives the agency a more complete way to understand its own catalogue work.
The client may commission the work one task at a time.
The agency should still be able to see the catalogue those tasks are building.