Integration Audit for a 1C-Bitrix Website
Integrations are the most fragile part of a Bitrix project. The 1C data exchange fails silently at 3 a.m., the payment system stops working after an API update on the provider's side, and a marketplace integration creates duplicate orders. Without monitoring and documentation, these problems are only discovered through customer complaints or the next crisis. An integration audit is an inventory of all external system connections and an assessment of their reliability.
Integration Map
The first step of the audit is to compile a complete list of integrations. A typical Bitrix site has 5–15:
| Type | Examples | Mechanism |
|---|---|---|
| ERP / accounting | 1C: Enterprise | CommerceML, REST |
| Payment systems | Sberbank, YooKassa, Stripe | sale.payment modules |
| Delivery | CDEK, Boxberry, Russian Post | API modules |
| CRM | Bitrix24, amoCRM | REST API |
| Marketing | SendPulse, GetResponse | SMTP, REST |
| Analytics | GA4, Yandex.Metrica | JS tracking codes |
| Marketplaces | Wildberries, Ozon | REST API |
| Call tracking | CoMagic, CallTouch | JS + webhooks |
Reviewing the 1C Exchange
The 1C data exchange is the most problematic integration. We check:
Exchange log. In Bitrix: Desktop → 1C-Bitrix → Data Exchange. Review the latest synchronization dates and errors in the log. The log is stored in files under /bitrix/modules/sale/sync/ and in the database — table b_catalog_import_log.
Data integrity. Spot-check: compare 10–20 random products between the site and 1C by price, stock level, and availability. Discrepancies indicate a mapping problem or data loss in transit.
Schedule. Verify the exchange cron job: is it running on time, are there any stuck processes (ps aux | grep import)?
CommerceML format. When parse errors occur — inspect the XML files in /bitrix/catalog_import/. Common causes: invalid characters in product names, PHP memory limit exceeded when importing a large file.
Reviewing Payment Integrations
For each payment system:
- Date of the last successful transaction (from
b_sale_order_payment) - API key validity (expiry date, rotation)
- Webhook URL configuration for payment confirmation — the URL must be reachable from the internet
- Error handling: what happens when the payment gateway is unavailable
What Is Checked During the Audit
- Complete list of active integrations (some are often undocumented)
- Dates of the last successful synchronizations for each integration
- Presence and quality of error handling (retry logic, alerts on failure)
- Currency of API keys, certificates, and tokens
- Logging — is it possible to reconstruct the history of operations
- Documentation — are integration parameters and partner support contacts described
Final Report
For each integration: status (working / working with issues / unknown), date of last check, identified risks, recommendations. Separately — a list of integrations with no monitoring in place (failures will only be discovered manually).
What Is Included in the Integration Audit
- Compiling the complete integration map for the project
- Log and status review for 1C, CRM, and marketplace exchanges
- API key and certificate validity check
- Reliability assessment: error handling, monitoring coverage
- Spot-check of data integrity in transmitted records
- Final report with risk mitigation recommendations