Enterprise · Custom change reports
Compare observed carrier signals across available snapshots. Identify merchants for account review and build a scoped research list for logistics sales and retention teams.
Reports compare available snapshots. A change in detection is a reason to investigate, not confirmation of a supplier switch or customer churn.
Synthetic example — proposed report format
Domain: merchant.example
Earlier snapshot: DPD and DHL detected
Later snapshot: DPD detected; DHL not detected
Snapshot dates: included in the agreed report
Observation dates: included where available
Interpretation: review the detected difference
Commercial relationship: not verifiedDefine markets, platforms, categories and the providers or technologies to compare. Historical availability and coverage must be checked for that scope.
Agree before/after values, snapshot dates, available observation dates and merchant context. Source URLs are included only where available and explicitly agreed; a URL documents an observation, not a commercial contract.
Use the agreed file to prioritize account research. Missing observations, website changes and detection coverage can affect differences between snapshots.
For custom datasets, we agree the available fields, scope, price, permitted use and delivery date before purchase. Coverage varies by field and market. A missing payment or carrier signal means we did not detect it, not that the merchant does not use it.
A logistics team compares detected carrier signals for a chosen merchant segment. Where a previous signal is missing, it checks the merchant site and its own account records before deciding whether a retention or sales conversation is appropriate.
This describes a possible workflow, not measured customer results.
We rebuild the searchable index typically every 2–4 weeks. Observation dates vary by source and field; a rebuild does not mean every website was observed again. Delivery dates and any recurring schedule are agreed separately for your project.
No. A missing observation can reflect a page change, a failed observation or a detection gap. Verify candidate changes before treating them as a supplier switch or churn.
Custom change reports require an Enterprise agreement. We confirm historical availability, fields, format, permitted use, price and delivery before purchase.
No. These reports compare observed website signals and available history. They do not verify purchases, checkout availability, parcel volumes or provider contracts.