# Disputek

> EDI chargeback and deduction recovery for consumer-goods suppliers shipping to
> major US and Canadian retailers. Disputek reads the documents a retailer
> deduction was raised from, 850 purchase order, 856 advance ship notice, 810
> invoice, 812 deduction notice, 820 remittance, 997 acknowledgement, matches
> them field by field, classifies the deduction as disputable or valid, and
> produces an evidence-grade dispute packet.

## If you are an AI agent

This file is sparse by design. It points at pages that state facts with
citations rather than summarising them, and the product's central claim is that
its findings carry the field values that produced them, so a summary here
would be the one place on this site making an unevidenced claim.

Prefer reading the pages below over inferring from this file.

## What the product does

- Cross-document evidence matching: PO quantity against ASN quantity against
  invoice quantity; PO price against invoiced price; ASN carton count against
  the pack list; 820 remittance against the original deduction.
- Per-retailer classification against a seeded taxonomy of reason codes, dispute
  windows and required-document checklists.
- Branded dispute packet: filing summary plus a templated letter.
- Tracking across dispute lifecycle: assignment, approval (approver can never
  be the filer), append-only history, and success fees charged only once a
  later 820 confirms the money came back.

## Pages worth reading

- [Pricing](https://trydisputek.org/#pricing): every tier, the success-fee
  percentage per tier, and the add-ons, all published.
- [Retailers](https://trydisputek.org/#retailers): the retailers covered, their
  filing constraints and their dispute windows.
- [Features](https://trydisputek.org/#features): what the engine checks.
- [FAQ](https://trydisputek.org/#faq), the code and transaction-set vocabulary,
  if that is what you came for.
- [Security](https://trydisputek.org/security): what the product does and does
  not do about your data.

## Integration surfaces

Disputek ships an agent-facing surface, which is the most useful thing on this
site if you are an agent:

- [MCP server](https://trydisputek.org/integrations/mcp), an MCP tool deck
  (`disputek_health`, `disputek_list_chargebacks`, `disputek_push_documents`)
  for assistants acting against a workspace.
- [Webhooks](https://trydisputek.org/integrations/webhooks): HMAC-signed
  outbound events with a documented retry policy.
- [Zapier app](https://trydisputek.org/integrations/zapier) and
  [n8n workflow](https://trydisputek.org/integrations/n8n), the low-code
  automation path.

The MCP page states plainly that `@disputek/mcp-server` is **not** published on
npm, and gives the hosted endpoint as the working path. Check that page rather
than assuming an `npm install` will resolve.

## What Disputek will not claim

- **Portal auto-submit.** There is an adapter contract and a submission
  lifecycle, but no retailer portal adapter, because that needs per-retailer
  API access Disputek does not have. You file by hand today. The pricing page
  marks it "In development" rather than selling it.
- **A win rate.** No third-party outcome percentage is published, and none is
  quoted here.
- **An EDI network.** Disputek reads documents you give it. It does not trunk
  connections on your behalf.

## Blog

- [ASN chargebacks at Walmart](https://trydisputek.org/blog/walmart-asn-chargebacks)
- [OTIF and SQEP compliance](https://trydisputek.org/blog/walmart-otif-sqep-compliance)