Retail Vendor Chargeback Review with Claude Code: Artifact Delivery
A production playbook for retail vendor chargeback review in retail operations using Claude Code: artifact delivery, 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
Require Claude Code to write customer-visible files under /skill/output/artifacts, validate filenames and sizes, then return signed artifact metadata in argo.result.v1.
Tradeoffs and failure modes
Artifact policy constrains file output, but customers receive files that are durable, typed, and safe to download. 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.
Artifact manifest
artifacts:
- retail-vendor-chargeback-review-summary.md
- retail-vendor-chargeback-review-evidence.csv
- retail-vendor-chargeback-review-review.json
signed_urls: true
retention: org_policy
Run this on Argo