Upload your decisions to your network

Deciding a row in AffCheck records a decision in your own workspace. Getting it to the network is a separate, deliberate step that you take. This page is where each network accepts declines, amends and corrections, and what it expects to receive.

AffCheck never uploads anything

No decision, no file and no API call leaves AffCheck for a network. That is a product rule, not a missing feature: a tool that could decline commission on its own would eventually decline the wrong thing on its own.

Awin: batch validation file

On Awin Classic: Commission → Validate → Batch Process Commission → Manual Upload, using the Accepted, Declined and Amended templates Awin provides on that page.¹ On the new Awin platform there is no batch upload: you approve or decline per row, or multi-select, in the pending list.

What Awin's documentation says about the file:¹²

• Accepted and Declined carry Order Reference, Transaction Date, Status and Status Note; for a decline the Status Note is one of the reasons listed in the template.
• Amended carries Order Reference, Transaction Date, Status Type (AMENDED), Status Note, Sale Amount, Sale Breakdown (for example DEFAULT:15.00) and Currency.
• Save it as .csv. "Do not use formulas. All fields must be hard-coded values."
• Use the date format of your programme's locale.
• On upload, select Contains column headings and Remove duplicates, and clear Leave amended commissions as pending.

Failed rows are in Batch Process History → report icon → results file, filtered to Failed. The causes Awin lists are locale formatting, missing required columns, formulas in cells and headings left in the file.¹

CJ: correction data

CJ takes a correction data import, which CJ Support sets up for your account. Once it exists, files can go by CJ SFTP, your own FTP/SFTP or HTTP, email, or Web Upload in the Account Manager.³

The file is delimited (comma, tab or pipe) or XML. Each record carries a reason code, the transaction id and the order id, plus the new amount for a partial correction. Reason codes include RETRN for returned merchandise and DUPO for a duplicate order, and they are case-sensitive.⁴

The alternative is the Tracking API's cancelOrders and restateOrders mutations.³ Either way, it has to arrive before the transaction locks — see deadlines.

impact.com: batch modifications

Batch modifications and reversals go in as CSV or XML built from impact's own templates, uploaded by FTP/SFTP or email, or sent through the API.⁵

An order-level row carries the action id (or the order id plus the action tracker id), the new Amount — 0 for a reversal — and a required Reason code such as ITEM_RETURNED. impact recommends fewer than 10,000 rows per FTP file, and an action can be modified at most 1,000 times.⁵

Rakuten, Webgains, Partnerize, Tradedoubler

We have not been able to verify the advertiser-side upload path for these four, so this page will not invent one.

• Rakuten Advertising — cancellations are reported inside the transaction update window; the advertiser help centre is not public.
• Webgains — transactions are cancelled or adjusted inside the validation period; the platform help is behind a login.
• Partnerize — conversions are set to rejected with a reason; the documented route is the brand API's bulk conversion update, up to 100,000 items.⁶
• Tradedoubler — transactions are reclassified as invalid; batch processing from a CSV file is listed on the Grow plans, without a published layout.⁷

If you have an advertiser account on any of them, send us a redacted export or a screenshot of the upload screen and we will document it here properly.

Any other network

Every network that lets you decline in bulk wants the same three things: which transaction, what to do with it, and why. Take the full CSV of flagged rows, keep the columns your network's template asks for, and put the evidence sentence in its reason field.

Where there is no bulk upload at all, work the queue as a worklist: the review queue filtered to declines, in deadline order, with Copy reason for each row.

If a publisher asks why

Every file has an evidence pack: a page listing each declined or amended transaction with the reason AffCheck gave it, the Shopify facts behind that reason, the transaction as your network reported it, and who confirmed the decision and when. Open it from the Evidence pack button next to a file on the Exports screen, or from one row's evidence drawer in the review queue.

It is a page, not a stored file: print it, or use your browser's "Save as PDF", and send that. Nothing is kept on our side, so the link always rebuilds the pack from your own decisions. It carries order references, transaction ids and amounts — never a customer's name, email or address, because AffCheck never holds those.

After you upload

Import the network's export again on your next cycle. Rows that were declined or amended come back settled, and AffCheck uses them for the "did auto-validation catch it?" figure instead of suggesting anything about them. That is also the cheapest way to confirm that an upload was actually accepted.