ce-cart-checkout

To implement two-way token sync for Commerce Engine hosted checkout, you establish a binding mechanism between your storefront and the checkout environment using provided auth modes. This ensures session continuity and consistent cart state across redirects.

Building a custom checkout with multiple payment integrations requires orchestrating cart APIs, address linking, and fulfillment payloads. Pattern-driven implementation guides manage multi-payment orchestration and order creation across SPA and SSR frameworks.

Yes, the skill provides cart mutation patterns and session recovery mechanisms. It handles cart creation, item management, and order status polling to maintain cart state consistency during the storefront checkout experience.

Commerce Engine checkout patterns apply to both SPA and SSR frameworks. The implementation guides cover cart, checkout, and payment workflows with example code tailored for single-page and server-side rendered storefront architectures.

Address collection and fulfillment in a custom checkout utilize specific cart API payload patterns. The skill provides reference-guided patterns to link addresses, configure fulfillment options, and manage payment data securely.

Hosted checkout relies on redirecting to a pre-built environment with token sync and auth modes, while custom checkout uses direct cart APIs to build a fully tailored experience. The choice depends on your required level of UX control and integration complexity.