Home | Connectors | Azure Blob Storage | Azure Blob Storage - Centric Integration and Automation
Data flow: Centric ? Azure Blob Storage
Centric users can publish large supporting files such as technical drawings, 3D renderings, spec sheets, and prototype images to Azure Blob Storage for scalable retention and distribution. This reduces load on the PLM environment while giving teams a reliable repository for large assets that need to be shared across design, sourcing, and manufacturing.
Business value: Improves file accessibility, reduces storage constraints in Centric, and supports faster collaboration across product teams.
Data flow: Centric ? Azure Blob Storage
Approved product documents from Centric, such as line sheets, compliance packs, care instructions, and launch materials, can be exported to Azure Blob Storage for controlled distribution to regional teams, suppliers, and partners. Azure Blob Storage can serve as the delivery layer for downstream systems, portals, or secure download links.
Business value: Speeds up document sharing, ensures consistent access to approved content, and reduces manual file handling.
Data flow: Centric ? Azure Blob Storage
When product styles, seasons, or development cycles are completed in Centric, historical files and superseded versions can be archived in Azure Blob Storage for long-term retention. This helps preserve audit trails, design history, and regulatory documentation without overloading active PLM records.
Business value: Lowers operational storage costs, supports compliance retention requirements, and keeps active Centric workspaces cleaner and easier to manage.
Data flow: Azure Blob Storage ? Centric
Suppliers, factories, or design agencies can upload large batches of files to Azure Blob Storage, which Centric then ingests into the correct product, style, or season records. This is useful for artwork, sample photos, measurement files, and technical packs coming from external contributors.
Business value: Simplifies external file submission, reduces email-based exchanges, and accelerates onboarding of supplier content into product workflows.
Data flow: Centric ? Azure Blob Storage ? downstream consumers
Once product content is approved in Centric, the final files can be pushed to Azure Blob Storage for consumption by e-commerce, PIM, DAM, or partner portals. This creates a controlled handoff from product development to commercial operations and ensures only approved assets are distributed.
Business value: Shortens launch timelines, reduces version errors, and improves consistency across customer-facing channels.
Data flow: Bi-directional
Centric can maintain product context and approvals while Azure Blob Storage hosts the underlying large media files. Teams in merchandising, sourcing, quality, and marketing can access the same file set through governed links or synchronized references, avoiding duplicate copies and conflicting versions.
Business value: Enhances collaboration, reduces file duplication, and improves governance over shared product assets.
Data flow: Centric ? Azure Blob Storage
Critical product files managed in Centric can be replicated to Azure Blob Storage as part of a backup or disaster recovery strategy. This provides an additional layer of protection for design files, specifications, and launch documentation in case of system outages or data loss.
Business value: Strengthens business continuity, protects intellectual property, and reduces recovery risk for product development operations.
Data flow: Centric ? Azure Blob Storage
Centric can publish approved product assets to Azure Blob Storage containers organized by brand, region, or business unit. Local teams can then retrieve only the files relevant to their market, such as localized packaging artwork, translated instructions, or region-specific compliance documents.
Business value: Improves content governance, supports localization workflows, and reduces confusion caused by broad file access.