Rate Deck Change Detector

Compare two carrier rate decks by destination prefix and get every added, removed, and changed rate as a row — with the currency change called out separately from the rate change.

What it does

Carrier rate decks are large and versioned constantly. This compares an old deck against a new one, matches destinations by prefix, and classifies each one as added, removed, unchanged, rate-changed or currency-changed. The currency case matters: a rate that looks unchanged in absolute terms can still move materially if the currency behind it changed, so the two are reported separately.

Output fields

Field	Description
prefix	The destination prefix this row covers.
status	added, removed, unchanged, rate-changed or currency-changed.
oldRate	The rate in the previous deck.
newRate	The rate in the new deck.
oldCurrency	The currency in the previous deck.
newCurrency	The currency in the new deck.
absoluteChange	The absolute change in rate.
percentChange	The change as a percentage.

Sample output

{
  "prefix": "4412",
  "status": "rate-changed",
  "oldRate": "0.0120",
  "newRate": "0.0140",
  "oldCurrency": "GBP",
  "newCurrency": "GBP",
  "absoluteChange": "0.0020",
  "percentChange": "16.67"
}

Use cases

• Reviewing a carrier's repricing before it reaches customers.
• Checking a new deck for destination prefixes that quietly disappeared.
• Catching a currency change hiding behind an apparently stable rate.

Pricing

Pay per event: charged per changed destination row written, plus a near-zero start event.

FAQ

What formats does it accept?

Supplied rate deck files. Read the input schema for the exact shape expected.

Why separate currency changes?

A rate can hold its number while its currency moves. Reporting them together would hide a real price change.

Does it tell me which change is material?

No. It reports the change precisely and leaves materiality to you — that is a commercial judgement, not a data one.

Related Actors

• Route Margin Report
• Invoice Aging Report

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Rate Deck Change Detector declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Rate Deck Change Detector include oldRate, newRate, oldCurrency, newCurrency, absoluteChange and percentChange.
• Rate Deck Change Detector needs no API key, login or account of any kind before its first run.
• Every one of Rate Deck Change Detector's 2 inputs is optional, so it runs with no configuration at all.
• Every number published about Rate Deck Change Detector is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Rate Deck Change Detector is filed under business and developer tools so that it is found by the people looking for that job, not by its internal name.

Limitations

• Rate Deck Change Detector reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.