DeliveryP2Reference

Product Content & Catalogue Approvals

Full nameE-commerce Product Content and Catalogue Approvals Micro ERP

Briefs, design versions, estimates, review comments and approvals need a shared project history.

Application configurations3

Extension mappings6

LifecycleReference

About this erp

Purpose and scope

Briefs, design versions, estimates, review comments and approvals need a shared project history.

Source: ERP_Full_Hierarchy_Catalogue.html
Family: Design versions and approvals
Family ID: design
Configuration scope: Industry operations
Standalone scope: Own clients, briefs, design assets, reviewers, versions. Run product content brief, content versions, internal review, approved product assets. Maintain record history and role permissions.
Core records: Clients, briefs, design assets, reviewers, versions
ERP connections: Projects, documents, purchasing, billing
Primary workflow: Product content brief → content versions → internal review → approved product assets
Readiness: Source-defined reference configuration; runtime unverified.

AI brief

Written by Claude from this ERP's record. Check the details before you rely on them.

Connected catalog

Follow each relationship to its full catalog record.

3 linked records

Full nameE-commerce Design Studio App

Maintain briefs, submit design versions and prepare material selections.

Full nameE-commerce Design Reviewer App

Review proposed designs, estimates and readiness for client approval.

Full nameE-commerce Design Client App

Review shared proposals, request revisions and approve a final version.