Migrate to Standard Cart APIs

The structured migration process involves these phases. This approach ensures a seamless transition to Standard Cart APIs by validating changes in a Sandbox environment before deploying them to Production. Users can follow this phased approach, to minimize risks, enhance system performance, and leverage advanced features for improved efficiency and scalability.

Evaluation Phase
Implementation Phase

Evaluation Phase

The evaluation phase is critical for understanding the benefits of transitioning to Standard Cart APIs and ensuring compatibility with existing functionalities. This phase involves assessing performance improvements, available features, and designing an implementation strategy tailored to specific business needs.

Understand the Value of Standard Cart APIs

Migrating to Standard Cart APIs offers these advantages.

Better Performance and Thresholds: Standard Cart APIs are optimized for efficiency, offering improved response times, scalability, and handling higher transaction volumes without performance degradation.
Exclusive Features and Roadmap: Standard Cart APIs provide access to advanced capabilities and continuous enhancements, ensuring alignment with future technological advancements and platform updates.

Evaluate Feature Compatibility

Before proceeding with migration, it is essential to assess the compatibility of existing features with Standard Cart APIs:

Check Supported Features: Identify which current functionalities are supported by Standard Cart APIs and determine whether any modifications or alternatives are required. See Check Feature Compatibility and Known Limitations. Product attachments on cart line items are not supported with Standard Cart APIs or LWC Cart.
Identify Standard vs Classic APIs: Only the APIs listed in Standard Cart APIs run on the Standard path. Other Cart APIs continue to run on Classic Apex. See Cart APIs vs Standard Cart APIs.
Future Roadmap Considerations: Evaluate upcoming enhancements and new capabilities in Standard Cart APIs to align with long-term business objectives and avoid potential rework.

Design and Estimate

A well-structured migration plan ensures minimal disruption to business operations:

Identify Relevant Standard Cart APIs: Determine which APIs are applicable for the use cases specific to the business. See Standard Cart APIs Usage Examples.
Evaluate Benefits and Feasibility: Assess the expected gains in terms of performance, scalability, and ease of maintenance to justify the migration effort.

Implementation Phase

The implementation phase is divided into these two major stages.

Sandbox Migration Steps: For initial testing and validation.
UAT/Production Migration Steps: For final deployment and production rollout.

Sandbox Migration Steps

Enable JSON Attribute V2 Schema (prerequisite).

Ensure that JSON Attribute V2 Schema is enabled before proceeding with further changes. See JSONAttribute v2 Schema Upgrade Considerations.
Review interfaces and implementations.

Analyze and update implementation class names and interfaces that are compatible with Standard Cart APIs. See Interfaces and Implementations.
Update Attribute-Based Pricing

Modify the existing pricing logic to align with the attribute-based pricing model in Standard Cart APIs. See Set up Attribute-Based Pricing.
Handle changes to response

Ensure that any modifications in API response formats are accounted for in dependent systems to avoid integration issues. See Changes to Response.
Move customizations

If there are any custom hook implementations, make the necessary updates.
- Use Field Mappers to add and manage custom fields, ensuring they are properly integrated.
- Update any existing hook implementations using the CPQ Cart Document to align with Standard Cart APIs.
- Because not all APIs have migrated to the Standard Cart framework, custom implementations must accommodate both Classic and Standard Cart flows and switch dynamically based on context.

Enable Standard Cart APIs

Activate the necessary Standard Cart APIs to replace legacy implementations. See Enable the Standard Cart APIs.
Execute the administration tasks.

Complete the required configuration updates and administrative tasks to support the migration. See Execute the Administration Tasks.
Validation

Conduct thorough testing in the Sandbox environment to verify that all functionalities work as expected before moving to production.

UAT or Production Migration Steps

Enable JSON Attribute V2 Schema (prerequisite).

Ensure that JSON Attribute V2 Schema is enabled in the production environment before proceeding. See JSONAttribute v2 Schema Upgrade Considerations.
Deploy Sandbox/UAT changes in Production.

Migrate the tested configurations and changes from Sandbox/UAT to the production environment through the existing deployment process.
Enable Standard Cart APIs.

Activate the Standard Cart APIs in the production environment. See Enable the Standard Cart APIs.
Execute the administration tasks.

Complete the required configuration updates and administrative tasks to support the migration. See Execute the Administration Tasks.
Validation

Conduct thorough testing in the Production environment to verify that all functionalities work as expected before moving to production.