# Which metrics to watch in FMCG before a chargeback or a rejected ASN costs you the account

date: 2024-11-22

> The metrics that actually predict your risk in FMCG — cost per transaction, cycle time, and error rate — and how to read them to decide where to strengthen your retail integration before a rejected ASN turns into a chargeback.


In FMCG you operate at a volume where a small error doesn't stay small. A rejected ASN turns into a chargeback; an EDI feed that goes down at peak demand turns into a chain of lost orders. Measuring well isn't a dashboard exercise: it's how you see the problem **before** the retailer bills you for it.

Without hard data, you decide on gut feel — and at scale, gut feel gets expensive. These are the metrics worth watching, and more importantly, how to read them.

### The three metrics that predict your risk
1. **Cost per transaction**: what it costs to process an order. The revealing number isn't the average — it's the exceptions: every order that gets touched by hand costs several times more than one that flows through on its own.
2. **Cycle time**: how long a process takes end to end. In FMCG, a slow cycle doesn't just delay you; it opens the window in which a price or stock change can get your shipment rejected.
3. **Error rate**: the most ignored metric and the one that hurts most. A rejected ASN, a quantity discrepancy, a malformed document — each one is a chargeback in the making. If you don't measure it, you pay for it.

With a platform like **Kontext** you can centralize and monitor these numbers in real time, so an error shows up while it's still a warning — not once it's already a penalty.

### How to read the numbers to decide
A single metric tells you nothing; the pattern does. Before investing in any improvement, cross-reference all three:

- High error rate **and** long cycle time → the problem is integration, not your people.
- Cost per transaction spiking on exceptions → you're paying for manual rekeying, not for volume.
- Errors concentrated on one trading partner → the risk lives in that feed, not across your whole system.

Read this way, the metrics stop being a report and become a map of where to reinforce first.

---

Measuring is step one; step two is closing the gap where errors turn into cost. If you want to see how document exchange with retail gets automated — ASNs, confirmations, and labels — with no room for rejection, check out our [labels and documents solution](/en/solutions/labels/) and compare it with your current process.