ERP, CRM, marketplaces — in one data flow
Orders, stock, prices and customers move between systems on their own: no manual exports, no lost orders, no “ask accounting”. We design the schema, write the connectors, set up monitoring.
- 1C 8.3 · ERP
- amoCRM · Bitrix24 · RetailCRM
- Ozon · WB · Yandex Market
- queues · retries · alerts
Frontbox already integrates with 1C‑Bitrix, 1C ERP and Ozon — it is part of the subscription. The standalone service is for non‑standard systems, custom APIs and complex exchange schemas.
Four things that stop eating your time
Data moves itself
Stock and prices from ERP to the site and app, orders back — no manual exports or spreadsheets.
Data arrives
Queues with retries and idempotency: if an API is down, an order is not lost, it catches up.
You see what broke
Alerts on failure and log audit — you learn before the customer does, not from a complaint.
There is documentation
Exchange schema, fields and rules are written down. A new developer figures it out without us.
What we integrate with
The path of goods and money: accounting → site and app → payment and delivery → marketplaces → CRM.
Accounting systems
Two‑way exchange with 1C: catalog, stock, price types, orders, statuses, counterparties.
- 1C:Trade
- 1C:Retail
- 1C:ERP
- MoySklad
CRM and communications
Orders and customers into CRM, statuses back to the site, triggered emails and messages.
- amoCRM
- Bitrix24
- RetailCRM
- Telegram bots
Marketplaces
Catalog, stock and price sync; marketplace orders in one interface.
- Ozon
- Wildberries
- Yandex Market
Payments and instalments
Online payments, invoices for legal entities, instalments, fiscalisation.
- YooKassa
- SBP
- Split
- online cash register
Delivery
Lead time and cost calculation, pickup points on a map, tracking, document printing.
- CDEK
- Boxberry
- Yandex Delivery
- PEK
Your own API
Custom systems, ERPs, external services — through an adapter with a contract and documentation.
- REST / GraphQL
- webhooks
- OpenAPI
From task to production — three steps
Schema and field dictionary first, code second. Launch with monitoring, not “seems to work”.
- 01
Analysis and schema
We map data, roles, failure modes and acceptance criteria. We fix who owns each field.
- 02
Development and tests
Connectors, queues, validation. Tested on a data copy, including API failures.
- 03
Launch and monitoring
Gradual switch‑on, alerts, log audit, documentation. Then support under an SLA.
One‑off task or ongoing support
We name the price after analysing the schema: it depends on the number of systems, exchange directions and data quality.
One integration
One system or one exchange direction with a clear outcome.
estimate after schema analysis
- schema and field dictionary
- connector + queue + retries
- tests on a data copy
- documentation
A full set
Several systems in one flow: ERP + CRM + marketplaces + delivery.
- single data bus
- monitoring and alerts
- staged launch
- training for your team
Integration support
A team on call: API changes, new marketplaces, incidents.
- SLA response
- connector updates when APIs change
- log audit
- monthly report
Frequently asked
Which systems do you integrate?
1C (Trade, Retail, ERP), MoySklad, amoCRM, Bitrix24, RetailCRM, Ozon, Wildberries, Yandex Market, payment and delivery services — and any documented API.
Do we have to change 1C‑Bitrix or 1C?
No. Integrations are built on top of working systems; we change only an exchange format that loses data.
What if a third‑party API changes?
Under support we update the connector. The retry queue keeps data safe while the update is in progress.
How do you guarantee data is not lost?
Queues, idempotent operations, validation of incoming data, alerts and log audit. An API failure is a routine situation, not an outage.
How long does development take?
One exchange direction — usually weeks. A set of several systems — in stages, each with its own launch.
Tell us which systems need to talk
A list of systems and what should move between them is enough for a schema and a first estimate. We reply within a day.