Marketplace Fee Reconciler
Finds what the marketplace charged wrongly, and what it owes you
- 8hard rules
- Things it must never do, enforced in every run
- 5handover rules
- Conditions where it stops and gives the work to a person
- 8output fields
- A structured result, not a paragraph you have to re-read
- ≤6steps per run
- Bounded work: at most 4 tool calls, enforced by the runtime
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Overview
Selling through a large marketplace means accepting a settlement statement with dozens of fee types per order, computed by the marketplace from its own records, with no line a seller can verify without rebuilding the calculation.
Mostly it is right. At scale the exceptions are worth a great deal, and they run one way.
Fulfilment fees are charged by the size and weight band the marketplace measured, and a mismeasured item is billed in a higher band on every unit sold, indefinitely. A referral fee is charged at a category's rate, and an item filed in the wrong category pays the wrong rate forever. Inventory gets lost, damaged in the warehouse, or disposed of without instruction — reimbursement exists but must be claimed. A customer is refunded and the item never comes back. A return is received and never restocked.
Every one has a claim window, usually short, and none appears as a problem in any report the marketplace provides. The seller sees a net deposit and no reason to question it.
This agent rebuilds the settlement against your own catalogue and shipment records and reports every discrepancy with its deadline and the evidence a claim would need. It files nothing: claims go through the marketplace's own process under your account, and an automated claim run is how a seller account gets flagged.
Benefits
Money back that was already yours
Nothing sold, nothing negotiated.
The recurring errors fixed
A wrong size band stops costing you on every future unit.
Deadlines met
Which is the whole difference between a finding and a recovery.
What it does
Checks the size and weight band
A mismeasured item is billed one band too high on every unit sold, indefinitely. Nothing in any report shows it.
Verifies the category rate
An item filed in the wrong category pays the wrong referral rate on every order, forever.
Finds inventory lost or damaged in their warehouse
Reimbursement exists and must be claimed. Nobody is going to offer it.
Matches refunds against returns received
A customer refunded and the item never came back. At volume this is the largest category.
Every finding has its claim deadline
Windows are short. A discrepancy found late is worth exactly nothing.
Files nothing
Claims run through the marketplace's own process under your account, and an automated claim run is how a seller account gets flagged.
What this changes
What this changes about your week
- It takes over
- Rebuilding marketplace settlements against your own catalogue and shipments.
- Done today by
- Nobody. The seller sees a net deposit and no reason to question it.
- How often
- Must be monthly — claim windows are short.
- Typical manual effort
- Dozens of fee types per order, computed by the marketplace from its own records.
Why E-commerce in particular. A mismeasured item is billed one size band too high on every unit sold, indefinitely, and nothing in any marketplace report shows it. Reimbursements exist and must be claimed; nobody offers them.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Marketplace Fee Reconciler has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-sonnet-5 with automatic fallback
- 3Toolsextract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Demo
Demo dataIllustrative sample output, abridged.
Input
{
"period": "Q3 2026",
"currency": "USD",
"claimWindowDays": 60,
"settlementLines": []
}Output
{
"escalate": true,
"findings": [
{
"sku": "SKU-4412",
"type": "wrong-size-band",
"charged": 5.94,
"claimBy": "2026-10-14",
"daysLeft": 42,
"expected": 4.11,
"reference": "Fulfilment fee, all orders",
"unitsAffected": 3140,
"evidenceNeeded": "Your packed dimensions and weight, with a photograph of the item on a scale.",
"perUnitDifference": 1.83,
"annualisedIfUnfixed": 22980
},
{
"sku": "Various",
"type": "refund-without-return",
"charged": 0,
"claimBy": "2026-09-11",
"daysLeft": 9,
"expected": 0,
"reference": "88 orders",
"unitsAffected": 88,
"evidenceNeeded": "Order identifiers and the marketplace's own return-window dates for each.",
"perUnitDifference": 0,
"annualisedIfUnfixed": 0
}
],
"disclaimer": "A reconciliation of settlement reports against your own records. No claim has been filed, no seller account accessed, no marketplace or customer contacted, no listing changed, and discrepancies where your own record could equally be wrong are reported as unresolved rather than as overcharges.",
"stillAccruing": [
"SKU-4412 is still selling in the wrong size band. Every unit shipped from today costs 1.83 more than it should, and that continues until the measurement is corrected."
],
"totalIdentified": 41200,
"escalationReason": "9,400 of identified claims expire within 9 days, and a recurring size-band error is still accruing on a product that is still selling.",
"expiringWithin14Days": 9400,
"unresolvedDiscrepancies": [
"Two SKUs where your recorded weight and theirs differ by under 30g. Either record could be right, so these are reported as unresolved rather than as overcharges."
]
}Requirements
Integrations
No integrations required.
Before you start
- Marketplace settlement and fee reports
- Your own catalogue with dimensions, weights and intended categories
- Shipment records: what you sent in, what was received
- Refund and return records
- Requires the All-Access plan or higher
Use cases
Monthly settlement review
Every statement rebuilt against your own records.
After a fee change
Whether the new rates were applied correctly to your catalogue.
High-volume fulfilment
Where a small per-unit error is a large annual number.
Before a period closes
Claims identified while their windows are still open.
Pricing
All-Access
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Does it file claims?
No. Claims go through the marketplace's own process under your account, and automated claim submission is a good way to get a seller account flagged. It gives you the case and the evidence.
Does it need marketplace API access?
No. It works from settlement reports and your own catalogue and shipment records — exports you can already download.
What if the marketplace's measurement is right and ours is wrong?
Then it is not a finding, and it says so. Where the two disagree and neither can be confirmed, it reports the discrepancy as unresolved rather than as an overcharge.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent