The chargeback shouldn't have hit. Defend it with the data that proves it.
A chargeback is a claim filed by the marketplace, not by you. The defense is the same: attach the evidence, walk the lifecycle, win or learn. Robnu ties chargeback evidence to the ship that was the source of the dispute — automatically, with no email digging.
- Chargebacks are first-class Adjustments with type=chargeback. The dispute lifecycle reuses the return_claims state machine.
- Defense evidence is the same document pipeline output that shipped the original order — slip, invoice, manifest, AWB.
- Won defenses write a recovery Adjustment back to MarketplacePayout. Lost defenses log the reason so the discrepancy taxonomy can adapt.
What you get.
Evidence comes from the original ship
When a chargeback hits an order, Robnu already has the document trail — packing slip, customer invoice, vendor invoice, manifest. The defense packet builds itself from those StorageObject rows.
Marketplace-specific dispute templates
AJIO chargeback disputes follow a template. Robnu fills the template from the order data; you review the language and submit. Per-marketplace dispute templates ship as new marketplaces light up.
Outcome closes the loop
Win → recovery Adjustment writes back to MarketplacePayout. Lost → loss is recorded with reason, feeding the deduction taxonomy so future similar disputes have an honest expected-recovery rate.
When a chargeback hits, Robnu does this.
- Detect — payout-sync ingests the chargeback as an Adjustment of type=chargeback.
- Categorise — discrepancy taxonomy assigns a reason (SLA-miss, slip mismatch, etc.).
- Build — evidence packet pulls slip, invoice, manifest, AWB from StorageObject.
- Draft — dispute template populates from order data.
- Review — you review and edit the dispute language.
- File — POST /v1/claims/:id/file submits the dispute.
- Track — return_claim_events log every transition.
- Close — won writes recovery Adjustment; lost logs the reason for the catalog.
Practical answers.
Not by default. Auto-file is on the agents roadmap (see /ai/agents) and requires explicit opt-in plus the mutation guard. Defaults are propose-and-approve.
Adjustments where the dispute window has passed are flagged 'window_closed' and routed to accept-loss with the reason logged. They still feed the discrepancy taxonomy so you know the cost.
Per-tenant template overrides ship in the settings surface. Until then, the default templates are honest, factual, and reference-attached.
More inside this pillar.
Try it inside your own dashboard.
Free during early access. No card. Forever free under 25 orders/day.