A delivery-data guard module for an online store

The problem

In a Bitrix online store the delivery module pulled pickup-point addresses from the carrier's public export, which occasionally contained errors — and it filtered none of them. Because of this a «fake branch» with wrong coordinates appeared on the map (the pin jumped to another city), and in some cities delivery disappeared from the options entirely. A customer in such a city didn't see the familiar delivery method and left for a competitor — a direct loss of orders.

Before

• The module blindly trusted the public pickup-point export — any error in it hit the storefront immediately.
• Wrong coordinates produced a non-existent branch, and the map pin jumped to the wrong city.
• An empty city-mapping table meant delivery wasn't shown in most towns.
• Data errors surfaced by chance — noticed from complaints rather than in advance.

What we did

• We built a separate add-on module with no edits to the third-party code — only a subscription to data-update events. Such a module survives updates of the original delivery module.
• Blacklist: known-fake pickup points don't make it into the storefront's auto-update.
• A data watchdog: every suspicious change (a coordinate shift over 2 km, a region change, new points) is logged — an error is visible right after the base updates.
• An admin dashboard, «delivery data health»: the manager runs the blacklist and sees the state without a developer.
• Auto-mapping of the carrier's cities to Bitrix cities — delivery reappears wherever pickup points exist.

Results

• Fake branches are cut off automatically — the map no longer «flies» to the wrong city.
• Auto-mapping of 120 cities brought delivery back to every town that has pickup points.
• Any future data error is caught right after an update, not from customer complaints.
• Zero edits to the third-party module and zero store downtime — the add-on ports to other sites as a single archive.