OpenText Information Archive - BigCommerce Integration and Automation

Common Integration Use Cases Between OpenText Information Archive and BigCommerce

1. Archive completed order and invoice records from BigCommerce for long-term compliance

Data flow: BigCommerce to OpenText Information Archive

When orders are fulfilled, invoiced, and no longer active in day-to-day operations, transaction records can be automatically archived in OpenText Information Archive. This includes order details, invoices, payment references, shipping confirmations, and customer service notes.

• Supports tax, audit, and regulatory retention requirements
• Reduces the volume of historical data stored in the commerce platform
• Improves performance and simplifies operational reporting in BigCommerce
• Provides controlled access to historical order records for finance and support teams

2. Preserve customer account and transaction history when decommissioning a legacy commerce platform

Data flow: Legacy commerce system to OpenText Information Archive, then searchable access for BigCommerce support and finance teams

During a commerce platform modernization program, historical customer, order, and product transaction data from a retired system can be archived in OpenText Information Archive. If BigCommerce becomes the new storefront, teams can still retrieve legacy records for customer service, returns, disputes, and audit requests without keeping the old system running.

• Enables legacy system retirement and lowers infrastructure costs
• Maintains access to historical commerce records without full application migration
• Reduces risk tied to unsupported platforms
• Supports continuity during platform transformation projects

3. Archive product content and digital assets no longer active in the storefront

Data flow: BigCommerce to OpenText Information Archive

Seasonal products, discontinued SKUs, and retired promotional assets can be moved from BigCommerce into OpenText Information Archive once they are no longer needed for active selling. This includes product descriptions, images, spec sheets, and campaign content tied to past catalog versions.

• Keeps the active catalog clean and easier to manage
• Preserves historical product information for warranty, support, and legal reference
• Helps merchandising and marketing teams maintain a record of past campaigns
• Supports product lifecycle governance across teams

4. Retain customer communications and service evidence related to ecommerce transactions

Data flow: BigCommerce and connected customer service systems to OpenText Information Archive

Customer emails, refund approvals, dispute documentation, and order exception records associated with BigCommerce transactions can be archived for retention and legal hold purposes. This is especially useful for enterprises handling chargebacks, returns, or regulated customer interactions.

• Creates a defensible record of customer communications
• Helps customer service teams resolve disputes faster
• Supports legal and compliance review processes
• Reduces reliance on shared inboxes or disconnected file storage

5. Store tax, payment, and fulfillment evidence for audit readiness

Data flow: BigCommerce to OpenText Information Archive

BigCommerce-generated records such as tax calculations, payment confirmations, fulfillment milestones, and shipping proofs can be archived to support financial audits and jurisdictional compliance. This is valuable for enterprises selling across multiple regions with different retention rules.

• Improves audit readiness with centralized evidence retention
• Supports finance, tax, and compliance teams with consistent recordkeeping
• Reduces manual collection of supporting documents during audits
• Helps enforce retention policies by region or business unit

6. Maintain historical catalog and pricing records for legal and commercial reference

Data flow: BigCommerce to OpenText Information Archive

Archived snapshots of product catalogs, pricing changes, promotional offers, and published terms can be retained in OpenText Information Archive. This gives legal, finance, and merchandising teams a reliable record of what was live on the storefront at a given point in time.

• Supports price dispute resolution and customer claims
• Provides evidence for promotional compliance and contract reviews
• Helps teams reconstruct historical storefront states
• Reduces the need to keep old catalog versions in active commerce systems

7. Enable controlled retrieval of archived ecommerce records for support and back-office teams

Data flow: OpenText Information Archive to BigCommerce support workflows, or via connected service tools

Archived order, customer, and product records can be made searchable for support and back-office users who need historical context while working in or alongside BigCommerce. This allows teams to answer customer inquiries without restoring data into the live commerce environment.

• Improves customer response times for older orders and returns
• Limits exposure of archived data to only authorized users
• Reduces operational burden on IT and support teams
• Maintains separation between active commerce data and long-term records

8. Support retention and disposition policies for ecommerce data lifecycle management

Data flow: Bi-directional governance alignment between BigCommerce and OpenText Information Archive

BigCommerce can serve as the system of record for active commerce operations, while OpenText Information Archive manages retention, legal hold, and disposition once records age out of operational use. This creates a governed lifecycle for orders, customer records, and related documents.

• Automates retention based on business rules and regulatory requirements
• Reduces legal and storage risk by disposing of records on schedule
• Improves data governance across ecommerce, finance, and compliance teams
• Provides a clear operational model for active versus archived data