Retail Vendor Chargeback Review with Claude Code: API Runtime Pattern
A production playbook for retail vendor chargeback review in retail operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Retail operations and supplier teams
The problem
Retail operations and supplier teams need retail vendor chargeback review to run repeatedly against chargeback notices, POs, shipment records, routing guides, and dispute evidence. In retail operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the retail vendor chargeback review instructions as a skill, send chargeback notices, POs, shipment records, routing guides, and dispute evidence as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For retail vendor chargeback review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=retail-vendor-chargeback-review
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo