checkout-debug

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Checkout debug

结账调试

Start with the reported failing action and its intended result, and keep the accepted offer and platform. Then find the boundary where things first diverge: the selected merchandise, the rendered UI, the submitted request, the persisted commerce record or the return state. Deliver the smallest justified repair, or a precise repair specification when you have no code or configuration access.
Two habits prevent most self-inflicted damage. Fixing a renderer must not replay a successful cart add. Missing confirmation must not become another payment. Before retrying anything, read back what already happened.
从报告的失败操作及其预期结果入手,并保持已接受的商品方案和平台不变。然后找到首次发生偏差的边界:所选商品、渲染后的 UI、提交的请求、持久化的商业记录或返回状态。实施有充分依据的最小修复;如果没有代码或配置访问权限,则提供精确的修复规范。
两个习惯可以避免大多数由自行操作造成的损害。修复渲染器时,不得重放一次已成功加入购物车的操作。 缺少确认信息时,不得再次发起支付。 在重试任何操作之前,先回读已经发生的结果。

When the evidence is a funnel ratio, not a failing action

当证据是漏斗比例而非失败操作时

"People add to cart but don't buy" names a gap, not a fault.
Split it first. Cart → checkout started and checkout started → paid point to different places: the cart page or drawer, versus the payment form, processor and terms.
Walk the route. Follow the buyer's actual ad link on the affected phone, with the reported variant, quantity, cart surface and address region. Include quantity two when quantity handling is in question. Check whether payment fields mount and a rate exists for that route. A clean-link pass can miss a failure specific to the real entry. A completed test purchase checks more of the path, but is a real payment: perform it only within the owner's authorization or have the owner perform it, and report it as not done otherwise.
Allow for objections. If the route works, the gap may be an objection rather than a defect. Shipping that first appears at checkout, an unexpected currency or a missing delivery estimate produces the same drop with no bug. Say so, and hand the decision to the offer or support owner instead of "fixing" checkout. A lowish cart-to-paid ratio beside a healthy overall conversion rate may need no action. Processor approval problems belong to payment-network.
“人们加入购物车却不下单”描述的是差距,而不是故障。
先拆分开来。 购物车 → 开始结账和开始结账 → 已支付分别指向不同环节:购物车页面或抽屉,以及支付表单、支付处理商和相关条款。
走一遍完整路径。 在受影响的手机上,按照买家实际点击的广告链接,使用报告中的商品变体、数量、购物车界面和地址区域进行操作。如果问题涉及数量处理,应包含购买数量为 2 的场景。检查支付字段是否正确挂载,以及该路径是否存在适用的费率。使用 clean link 进行的测试可能会漏掉仅从真实入口进入时才会出现的故障。完整的测试购买能覆盖更多路径,但它会产生真实支付:只有在获得所有者授权后执行,或由所有者执行;否则应报告为未执行。
考虑用户异议。 如果路径可以正常工作,那么差距可能源于异议,而非缺陷。结账时才出现的运费、意外的币种或缺少配送预估,都可能造成相同的流失,却不存在程序缺陷。应当明确说明这一点,并将决定交给商品方案负责人或支持负责人,而不是去“修复”结账流程。如果总体转化率健康,而购物车到支付转化率略低,则可能无需采取任何措施。支付处理商审批问题属于 payment-network 的职责范围。

Read for the open task

根据当前任务查阅相应内容

TaskRead
Reproduce, compare preview environments or choose a passing controlBrowser reproduction
Wrong variant/row, second edit fails, stale drawer, discount removalCart identity and state
Quantity two, bundles plus loose units, split price rows, stock boundaryBundle quantities and allocation
Missing rate, coupon conflict, threshold or amount mismatchShipping, tax and discounts
Blank/pending form, callback/return race or uncertain retryPayment state and recovery
Wallet, iframe/in-app browser, bank-app return or cancelMobile wallets and redirects
Stored order, document or shipment differs; qualify closureOrder readback and closure
Current Whop surface and fieldsWhop checkout contracts
Actual Shopify stackShopify checkout contracts
Actual WooCommerce stackWooCommerce checkout contracts
Normalize supplied evidence or compare exact expectationsCompare checkout observations and commerce record conventions
Browser runtime, sessions and what needs authorizationBrowser runtime and sessions
Whop connection absent/expired or a supported referral destination is requestedWhop connection and attribution
Load only the actual platform contract. For another platform, inspect its installed or official contract and reuse the generic diagnostic references; do not invent a supported adapter. A small explanation can finish with one reference and no browser.
任务查阅内容
复现问题、比较预览环境或选择正常通过的对照场景浏览器复现
商品变体/价格行错误、第二次编辑失败、抽屉状态过期、折扣被移除购物车标识与状态
购买数量为 2、套装商品与独立商品混用、拆分价格行、库存边界套装商品数量与分配
缺少费率、优惠券冲突、门槛或金额不匹配配送、税费与折扣
表单空白/处理中、callback/return 竞态或无法确定是否重试支付状态与恢复
钱包、iframe/应用内浏览器、银行应用返回或取消移动钱包与重定向
已存储的订单、单据或发货记录不一致;判断关闭条件订单回读与关闭
当前 Whop 界面及字段Whop 结账契约
实际使用的 Shopify 技术栈Shopify 结账契约
实际使用的 WooCommerce 技术栈WooCommerce 结账契约
规范化提供的证据或比较精确预期结果比较结账观察结果 和 商业记录约定
浏览器运行时、会话以及需要授权的操作浏览器运行时与会话
Whop 连接缺失/过期,或要求使用受支持的 referral 目的地Whop 连接与归因
只加载实际使用的平台契约。对于其他平台,应检查其已安装或官方契约,并复用通用诊断参考文档;不要虚构受支持的适配器。对于小型问题,只需引用一份参考资料即可完成说明,无须使用浏览器。

Produce a useful repair record

编写有用的修复记录

Write down the expected result before you reproduce. Choose a comparison that could contradict your suspected cause, such as a passing neighbor that differs in one plausible variable. Then observe the specific request and readback where available. Keep exact scoped IDs, property types, quantities, currency and parent relations. Compare the expected value with the rendered value, submitted request and stored readback at the failing boundary. Use a short table for a few fields; use the user's spreadsheet or local data tools for larger exports.
When code repair is authorized, follow the project's engineering guidance, make the narrow change, and repeat the failing instance plus its relevant passing neighbor. For order correctness, obtain an existing authorized record or export. UI-only evidence supports UI-only closure. Keep a proposed change distinct from a performed test. Use repair evidence when a reusable report helps; a single answer does not need the full form.
Authority and effects. Use an available browser in the authorized account (browser access). Routine reversible browsing is covered by the task. Live payment, refund, account changes, publishing and supplier orders are separate actions, not implicit regression checks. For consequential reproduction, prefer an existing isolated fixture or staging system, and confirm that payment, notification and fulfillment transports are isolated too. Keep customer data minimal and local.
在复现前写下预期结果。选择一种可能推翻所怀疑原因的对照方式,例如使用一个仅在一个可能变量上存在差异且能够正常通过的相邻场景。然后在可用时观察具体请求和回读结果。保留精确的作用域 ID、属性类型、数量、币种和父子关系。在故障边界处,将预期值与渲染值、提交的请求及存储后的回读结果进行比较。少量字段使用简短表格;较大规模导出则使用用户的电子表格或本地数据工具。
获得代码修复授权后,应遵循项目的工程规范,进行最小范围更改,并重复测试失败实例及相关联的正常对照场景。对于订单正确性,应获取现有的授权记录或导出数据。仅有 UI 证据时,只能支持 UI 层面的关闭处理。应区分已提出的更改与已执行的测试。如果可复用报告有助于记录,可使用修复证据;单个答复无需填写完整表单。
权限与影响。 在已授权账户中使用可用浏览器(浏览器访问)。常规且可逆的浏览操作已包含在任务范围内。实时支付、退款、账户变更、发布和供应商下单属于独立操作,不能隐含地作为回归检查。对于可能产生实际影响的复现,优先使用现有的隔离 fixture 或 staging 系统,并确认支付、通知和履约传输链路也已隔离。客户数据应尽量少,并保存在本地。

Ownership

职责归属

Checkout-debug owns storefront selection, cart state, the renderer and callback/loader lifecycle repair. Hand other work to its owner with the exact boundary and operation evidence:
  • payment-network: account and method eligibility, processor approvals, provider recovery and idempotency, and settlement;
  • clone-any-store: new-site reconstruction and Whop Site deployment;
  • increase-average-order-value: offer changes;
  • sourcing-and-fulfillment: supplier acceptance and delivery;
  • abandoned-cart-recovery: outreach.
These are responsibility handoffs, not runtime dependencies on sibling packages.
A working membership or access check does not prove physical fulfillment; a local test does not prove wallet behavior or a paid order. Report the checked boundary and next discriminating evidence without claiming conversion lift.
For Whop sign-up or a new-store setup, use Whop; authorized top-level business creation using the merchant's user token carries
affiliate_code: "SKILL"
. Follow the local onboarding instructions for onboarding and the one-time no-extra-cost note.
License: own-business use is permitted; redistribution and resale of the skill materials are prohibited, subject to the stated exceptions.
When a task needs another skill, use the skill catalog and installation commands.
checkout-debug 负责商品选择、购物车状态、渲染器以及 callback/loader 生命周期修复。将其他工作移交给相应负责人,并提供准确的边界和操作证据:
  • **payment-network:**账户和支付方式资格、支付处理商审批、支付服务商恢复和幂等性、结算;
  • **clone-any-store:**新站点重建和 Whop Site 部署;
  • **increase-average-order-value:**商品方案变更;
  • **sourcing-and-fulfillment:**供应商接单和交付;
  • **abandoned-cart-recovery:**外联跟进。
这些是职责移交,而不是对同级包的运行时依赖。
会员资格或访问权限检查正常,并不能证明实体商品已履约;本地测试也不能证明钱包行为或订单已支付。报告已检查的边界和下一步用于区分各种可能原因的证据,不要声称提升了转化率。
对于 Whop 注册或新商店设置,请使用 Whop;在获得授权的情况下,使用商户的 user token 创建顶层业务时,需带上
affiliate_code: "SKILL"
。按照本地入驻说明完成入驻,并注明一次性的“无需额外费用”。
许可证:允许用于自有业务;禁止再分发和转售 skill 材料,但其中明示的例外情况除外。
当任务需要另一个 skill 时,请使用 skill 目录和安装命令。