Talk to an engineer
RECOSYNC

The marketplace money that quietly never arrives

Sell through Amazon, Flipkart and a dozen other channels and a slice of every settlement goes missing - a fee charged at the wrong rate, a return that was never credited, a parcel billed at the wrong weight. RecoSync reconciles what should have been paid against what was, and files the claim.

A free revenue audit sizes the leakage before anything is committed; the paid plans are usage-based on order volume.

Book a demo on RecoSync ↗See pricing ↗

Built by Crenspire. Registered under JK Traders, which sells and supports it.

RecoSync has its own site at www.recosync.ai - pricing, plans and signup live there.

Why we built it

The loss is small per order and large per quarter
No single mis-charged fee is worth chasing on its own. Ten thousand of them across a quarter is a line item, and by the time it surfaces in the accounts the claim windows have closed.
Every marketplace settles differently
Different rate cards, different return policies, different claim formats, all changing without notice. A spreadsheet that reconciles Amazon correctly is wrong about Flipkart, and both go stale the next time a rate card moves.
Detection without a claim is just bad news
Knowing revenue leaked does not recover it. The work that gets the money back is evidence, the platform’s own dispute format, and filing inside the window - which is the part that does not fit in a spreadsheet.

What it does

Sync, without file uploads
Orders, returns, rate cards and settlements pulled from every channel, plus the webstore, the 3PL and the ERP.
  • Amazon, Flipkart, Myntra, Meesho, AJIO and more
  • Shopify, Adobe Commerce, BigCommerce
  • ShipRocket, Blue Dart, Delhivery, Tally, SAP, NetSuite
Reconcile against the policy that applied that day
Rate cards are synced and dated, so a fee is checked against the rate in force when the order shipped rather than the rate today.
  • 22+ leakage scenarios detected
  • Fee, commission and weight-handling audits
  • Three-way match across OMS, RecoSync and ERP
Recover, and post the result
Leakage is classified, packaged into the marketplace’s own dispute format with evidence, filed, and tracked to settlement.
  • Flagged, Recoverable or Not Recoverable, each with a reason
  • Platform-compliant claim files
  • Audit-ready journal entries posted back to the ERP

Where the AI actually sits

Reconciliation is a matching problem long before it is a language problem, so the model is used where the rules run out.

RECONCILIATION
Policy-aware detection
Leakage judged against the rate card and return policy that applied on the order’s own date, not the current one - which is what stops a rate change from generating a quarter of false positives.
RISK
Anomaly and fraud signals
Risky pincodes, weight drift and negative-settlement SKUs surfaced early, where a rules engine would need someone to have predicted the pattern first.
RECOVERY
Claim classification
Every finding sorted into flagged, recoverable or not recoverable with the reason attached, so the disputes team works a queue rather than a report.

Nine modules across the pipeline

Auto-Sync
Multi-channel ingestion with no manual files.
Dynamic rate card
Platform rate cards synced, every overcharge flagged.
AI reco engine
Date-specific, policy-aware detection across 22+ scenarios.
Claims automation
Platform-compliant recovery files, filed on time.
3PL & webstore reco
Lost shipments, freight overcharges and weight disputes.
SKU-level profitability
Net-settled profit, COGS and margin per SKU and order.
Three-way reconciliation
Orders, returns and settlements across OMS, RecoSync and ERP.
ERP posting
Settlement, tax, claim and recovery deltas as journal entries.
Fraud & anomaly detection
Risky pincodes, weight drift, negative-settlement SKUs.

Every module on www.recosync.ai ↗

Find out what the marketplaces kept

RecoSync is sold and supported as a product, with its own pricing and onboarding. The audit runs against your own settlement data.

Book a demo ↗Talk to us about building one