checkout-management

Debug Saleor checkout state lifecycle across client and server contexts.

1.5k|875|Updated Aug 20, 2021
One-click install
npx skills add https://github.com/saleor/storefront --skill checkout-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkout-management
Source: https://github.com/saleor/storefront/tree/main/.claude/skills/checkout-management
Command: npx skills add https://github.com/saleor/storefront --skill checkout-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand and troubleshoot the lifecycle of checkout sessions in the Saleor storefront, reducing time to diagnose issues such as hydration mismatches or stale checkout data.

Core Features & Use Cases

  • Checkout state anatomy: explains how checkout IDs are created, stored, and persisted in both cookies and URLs.
  • Debugging workflows: provides a structured approach to reproduce and diagnose failures like CHECKOUT_NOT_FULLY_PAID.
  • Operational guidance: outlines best practices for validating live checkout data before payments and for creating new checkouts when needed.

Quick Start

Identify the current checkout state in the UI and reproduce the issue to gather the relevant IDs for debugging.

Frequently Asked Questions about checkout-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Saleor checkout fail with a CHECKOUT_NOT_FULLY_PAID error during payment?

A CHECKOUT_NOT_FULLY_PAID error occurs when live checkout data is not validated before payment. You must verify the current checkout state and outstanding balance on the server before submitting the payment transaction.

How do I debug a hydration mismatch in a Saleor checkout storefront?

To debug a checkout hydration mismatch, reproduce the issue in the UI to gather relevant checkout IDs. Diagnose how checkout state is persisted across page reloads using cookies and URLs to find the client and server mismatch.

How is checkout state persisted across page reloads in Saleor ecommerce?

Saleor checkout state is persisted across page reloads by storing the checkout ID in both browser cookies and the URL. This dual approach maintains session continuity between the client and server during the ecommerce lifecycle.

What is the best way to troubleshoot stale checkout data in a Saleor storefront?

The best way to troubleshoot stale checkout data is to identify the current checkout state in the UI and gather the relevant IDs. Follow a structured debugging workflow to inspect the checkout lifecycle and create a new checkout if needed.

Can I create a new Saleor checkout if the existing session has invalid payment data?

Yes, you can create a new checkout when the existing session has invalid data. Operational guidance requires validating live checkout data before payments and creating a fresh checkout session if the current state is unrecoverable.