Prodentra Catalog Workflows Ltd

Prodentra
Prodentra
Discuss Your Content Workflow

Prodentra Catalog Workflows Ltd · Company no. 17304135

01 Services

Six pieces of work on product content operations.

Each entry states what it produces and what we need from you before it can proceed. They can be taken separately or in sequence, and the level of detail follows the size and shape of the catalogue.

01

Product Content Workflow Planning

The order in which a change travels from the moment it is raised to the moment it is live, with the conditions that let it move on.

We begin from the way updates actually run today, not from an ideal process. Each step someone already performs is written down, the points where work waits are identified, and the sequence is then set out with the conditions that allow an item to move from one stage to the next. Where two teams currently work in parallel on the same record, the plan says which of them holds it and when.

What you receive

  • A stage diagram covering preparation, review, approval, publication handover and later updating
  • Entry and exit conditions for each stage, written as checks rather than intentions
  • The route a returned item takes when a reviewer raises a query
  • A record of which stage an item sits at, and what it is waiting for

What we need from you

  • A description of how a change reaches a product page today
  • The roles that take part, in-house and outside
  • Any existing instructions, request formats or checklists already in use

02

Catalogue Content Organisation

What a product page is made of, in what order, and which of those parts are agreed as required.

A product page is treated as a set of named parts rather than a block of copy. Each part gets a definition, a purpose and a rule for how it is written, so two people preparing two products produce comparable pages. Where product types genuinely differ, the structure differs with them and the difference is written down rather than left to judgement.

What you receive

  • A page structure listing description, benefit and feature blocks, specifications and media slots
  • Field definitions with the wording rules that apply to each
  • Which elements are required, which are optional and which depend on the product type
  • Worked examples of a completed structure for a fictional product line

What we need from you

  • Examples of product pages as they stand, including ones you consider poor
  • The product types or ranges the structure has to cover
  • Any wording, terminology or house style rules already agreed internally

03

Update Process Setup

The request that starts a change, the source information it must carry and the statuses it moves through.

The purpose of a request form is to make an incomplete request visible before anyone starts work on it. The form is written so that the fields a reviewer needs are the fields the requester has to complete, and the statuses are written so that each one names the condition that ends it. The form is a working document: it can be held in whatever your teams already use, and it does not require a system from us.

What you receive

  • An update request form with the fields a reviewer needs to act on it
  • The list of source information required before a request is accepted
  • A status set, with the condition that has to be met to leave each status
  • Rules for handling a request that is incomplete, duplicated or withdrawn

What we need from you

  • Who currently raises changes, and how they raise them
  • What information is usually missing when a request arrives
  • Where the request record needs to live, so the form fits it

04

Documentation & Review Support

The written guidance contributors work from, and the checks that confirm a set is complete before it is approved.

Instructions are written per role and in the order that role acts, so a contributor reads only the part that concerns them. Review support covers whether a set is complete, whether it follows the agreed structure and whether the confirmations it depends on are present. It is a check on the content package, and it is not a technical or safety assessment of the product itself.

What you receive

  • Working instructions for each contributing role, in the sequence they act
  • Review checklists covering completeness, structure and the required confirmations
  • Media handling rules: matching to products, naming, versions and handover
  • Version records and content revision cycles, written as a schedule of reviews

What we need from you

  • The agreed page structure, or the work to produce one
  • Who reviews and who approves, by role
  • How media currently reaches the people who publish it

05

Contributor Coordination

Keeping internal teams and outside contributors working to the same agreed order, within a scope set in advance.

Coordination here means the running of an agreed process, within limits written into the order. Where a project needs images prepared, content formatted, catalogue records updated, pages built or a change implemented technically, those contributors are briefed and their handovers tracked against the same stages. We do not take over your suppliers, and we do not take decisions that belong to your approver.

What you receive

  • A responsibility table naming which role supplies, prepares, checks, approves and hands over
  • Briefing formats for outside contributors preparing images, copy or page builds
  • Handover points where work passes between contributors, and what travels with it
  • A record of open queries, who they sit with and what closes them

What we need from you

  • The list of contributors involved and what each of them does
  • The limits of the coordination you want us to carry out
  • A named approver on your side for decisions about content

06

Ongoing Operational Support

Continuing help to keep an agreed process in use, and to improve it as the catalogue changes.

A process that is written once and never revisited drifts back to whatever it replaced. Ongoing support keeps the written version and the practised version in step: where contributors work around a stage, either the stage or the working around it has to change, and that decision is made deliberately. The scope and the hours of this support are agreed for each arrangement.

What you receive

  • Regular review of how the agreed process is being followed in practice
  • Amendments to rules, forms and instructions as product ranges change
  • Support for contributors on how a stage or a request should be handled
  • Coordination of outside contributors within the scope agreed for the period

What we need from you

  • An agreed process already in place, from this work or from your own
  • A point of contact on your side who sees the updates going through
  • Agreement on the scope of the period, so both sides know what is included

Limits of the service

What this work does not include.

Stating the boundary is part of the service. A process only holds if everyone knows which decisions sit outside it.

  • No software product. Request forms, version records and approval flows are documents and rules, not a platform, and this is not a PIM, ERP or CRM system.
  • No automatic publishing, no application programming interface, no synchronisation between your systems and no storage of your catalogue on our side.
  • No confirmation of product facts. Specifications and commercial claims are confirmed by you and remain your responsibility.
  • No technical or compliance assessment of a product. Content review looks at the completeness and structure of a content package only.
  • No regulated, financial, legal, medical, cyber security or licensed services of any kind.

Fees and dates

Every engagement is priced in a written quotation sent by email before any work begins. The quotation states the full price in pounds sterling with any tax already included, and nothing is added to that figure afterwards. The same quotation names the delivery dates and the number of rounds of revision included, so both are settled in writing before anything starts.

Payment is by card or through PayPal, on a secure link in the invoice email, or by bank transfer against the invoice. Nothing is bought, paid for or downloaded on this website, and card details reach the payment provider rather than this company.

02 Contact

Tell us how a product content update runs today.

A general description is enough for a first enquiry. We reply with the questions that have to be answered before any work can be scoped, and nothing is quoted until that is clear.

Who takes part in a product content update at the moment, in-house or outside.

A general description is enough for a first enquiry.

Please keep a first enquiry general, and do not attach or paste confidential, personal or commercially sensitive material. A description in ordinary terms is all that is needed to answer.

Every field except Company is needed for a useful reply. The button writes the enquiry into a new message in your own email application, addressed and filled in; you read it over and press send there, and this page sends nothing itself.