Capability · Reconciliation
Building nowStop writing off gaps you can’t trace.
Every payout lands on the order it belongs to — so the billed-vs-landed gap ties out on one record, not across three spreadsheets that never agree.
The pain today
Month-end still lives in Excel.
The order file, the marketplace payout and the COD remittance live in their own exports. Nothing shares a key — so every gap ends as a hand-matched guess.
How it will work
The payout ties to the order, not a fourth spreadsheet.
The payout lands on the order that already exists
Captured, shipped, delivered and paid out sit on one record — so every payout line has an order to tie against.
Fees, weight-diff and clawbacks net out in place
Marketplace MDR, weight-difference and RTO clawbacks reconcile on the same record — not in a fourth spreadsheet.
A short-paid line is flagged, not written off
When landed falls short of billed, the gap surfaces on the order — traceable, instead of a month-end write-off you can’t explain.
Order-only tools stop at the warehouse door. Only a record that already holds the payout can render the billed-vs-landed column.
Orders, warehouse and delivery already run on one record — the substrate every payout will tie against.
The tie-out layer — payout, fees and COD reconciled on that record. On the roadmap, not shipped.
Proof
Rated by the teams who run on it
Bring one day of orders and their payouts — we’ll walk them onto one record with you, so you see how the tie-out will read before it ships.
The honest question
“Isn’t this just another matching spreadsheet?”
No — a spreadsheet matches three files that never share a key. Here the payout lands on the order that already exists, so there is no fourth file to reconcile. The freight side ties out today at freight billing.
Be the team that never writes off an unexplained gap.
See where reconciliation is headed — shaped on your own order flow, before it ships.