OpenText Lens - Data Visibility - BigCommerce Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and BigCommerce

1. Identify and remove sensitive content before publishing commerce assets

Flow: OpenText Lens - Data Visibility to BigCommerce

Use OpenText Lens to scan shared repositories, file stores, and collaboration platforms for product images, spec sheets, pricing documents, and marketing files that may contain sensitive or obsolete information. Only approved, current assets are then pushed into BigCommerce for use in product pages, downloadable resources, or customer-facing content.

• Reduces the risk of exposing confidential pricing, internal notes, or outdated product details
• Improves content governance before assets are published to the storefront
• Supports legal, compliance, and merchandising teams with cleaner approvals

2. Support eCommerce migration by inventorying unstructured content

Flow: OpenText Lens - Data Visibility to BigCommerce

During a BigCommerce implementation or replatforming project, OpenText Lens can identify all unstructured content related to products, promotions, policies, and customer-facing documents across legacy repositories. Teams can classify what should be migrated into BigCommerce, what should be archived, and what should be discarded.

• Speeds up migration planning and reduces manual content discovery
• Prevents unnecessary transfer of redundant or obsolete files
• Helps merchandising and IT teams prioritize high-value content for launch

3. Detect duplicate or outdated product support documents before customer publication

Flow: OpenText Lens - Data Visibility to BigCommerce

Many retailers store product manuals, warranty documents, installation guides, and compliance certificates in shared repositories before linking them to BigCommerce product pages. OpenText Lens can flag duplicate, outdated, or conflicting versions so only the correct document is attached to the relevant product listing.

• Improves customer experience by reducing confusion and returns
• Ensures product documentation is current and consistent
• Helps support and product teams maintain a single approved version of truth

4. Govern regulated product content for restricted or controlled goods

Flow: OpenText Lens - Data Visibility to BigCommerce

For businesses selling regulated items such as cosmetics, electronics, chemicals, or medical-related products, OpenText Lens can identify sensitive compliance files, certifications, and internal review documents stored outside the commerce platform. Approved compliance artifacts can then be linked or published in BigCommerce to support product eligibility, market-specific disclosures, and audit readiness.

• Reduces compliance risk when selling in multiple regions
• Supports legal review of product claims and disclosures
• Improves auditability of published commerce content

5. Clean up obsolete promotional and seasonal content before campaign launch

Flow: OpenText Lens - Data Visibility to BigCommerce

Marketing teams often maintain large volumes of campaign assets, banners, landing page files, and promotional copy in shared repositories. OpenText Lens can identify outdated seasonal content, expired offers, and redundant creative files so only active campaign assets are synced into BigCommerce for storefront use.

• Prevents expired promotions from appearing on live storefronts
• Reduces manual review effort for campaign managers
• Improves brand consistency across channels and regions

6. Improve product data governance by locating source documents for enrichment

Flow: OpenText Lens - Data Visibility to BigCommerce

BigCommerce product records often depend on supporting documents such as technical specifications, certificates, and supplier files stored across multiple repositories. OpenText Lens helps teams locate these source documents, assess their relevance, and identify the most complete and trustworthy files for product enrichment workflows.

• Accelerates product content enrichment and onboarding
• Helps merchandising teams find missing or incomplete product information
• Improves data quality before content is loaded into BigCommerce

7. Reduce risk in cross-functional content handoffs between legal, merchandising, and operations

Flow: Bi-directional

OpenText Lens can be used to discover and classify unstructured content, while BigCommerce serves as the controlled publishing destination. Legal, merchandising, and operations teams can review flagged content in OpenText Lens, approve the final version, and then publish or update the corresponding commerce content in BigCommerce. If issues are found in live storefront content, BigCommerce records can be traced back to the source repository for remediation.

• Creates a governed approval process for customer-facing content
• Improves accountability across business and compliance teams
• Enables faster correction of inaccurate or risky published content

8. Prepare for data retention and content cleanup after product discontinuation

Flow: BigCommerce to OpenText Lens - Data Visibility

When products are discontinued or categories are retired in BigCommerce, associated unstructured content such as manuals, images, and internal reference files can be identified in OpenText Lens for retention review, archival, or deletion. This helps organizations align storefront changes with broader information governance policies.

• Supports defensible retention and disposal practices
• Reduces storage costs and content sprawl
• Helps IT and compliance teams manage the full content lifecycle