No double entry
Site → CRM → 1C → WMS once, automatic.
Integrations · API · 1C
Custom integrations & API
I design and ship integrations — 1C, CRM, website, Telegram, marketplaces, payment and logistics APIs without double entry. REST, webhooks, queues, retry, monitoring — production-grade in 5–10 days. Fullstack Vladislav Kompaniec — Royal Rental, DryRent, Usede.ru, 130+ projects.
from 80,000 ₽ / project
5–10 days for one link or API service. Multi-system — scoped at brief.
Why pro integrations
Zapier breaks on volume and 1C. Custom exchange — your rules, error logs, idempotency.
1C expertise
CommerceML, HTTP — 130+ exchange projects.
Webhooks
Payment, shipment events — retry on 500.
Partner API
Documented REST for dealers, apps.
Monitoring
Telegram alerts, DLQ, idempotent replay.
Rental patterns
Royal Rental, DryRent battle-tested flows.
Integrations and API
1C, CRM, site, Telegram — one data flow.
Production needs retry, idempotency, monitoring — not Zapier forever. Focused bridge in 5–10 days.
Order → 1C → client status → Telegram; telephony → CRM card.
Public API: keys, rate limits, Swagger.
Brief: master data systems, format, SLA.
Integration deliverables
One integration loop in 5–10 days — spec, code, staging, docs.
Discovery
Fields, frequency, master, conflicts — doc first.
REST API
Auth, rate limit, OpenAPI.
Webhook receiver
Signature, queue, fast ACK.
1C exchange
Catalog, orders, payments.
CRM bridge
Leads, deals, statuses.
Notify
Telegram/email from events.
Marketplace API
Ozon, WB — scoped at brief.
Deploy
Docker, logs, runbook.
Solution types
Often start with one pain — orders or stock — then expand.
1C ↔ site/CRM
Orders, stock.
Payment hooks
YooKassa → CRM.
Logistics
CDEK.
Telegram ops
Alerts.
ERP custom
Rental.
BI export
To Metabase.
SSO
OAuth.
Legacy
CSV bridge.
Who it's for
When Excel glue fails.
E-commerce + 1C
No manual export.
CRM + phone
Calls to deals.
Rental
DryRent + 1C.
MP seller
MP + WMS.
SaaS
Public API.
Migration
Replace Zapier.
What we need
5–10 days, from 80,000 ₽ after mapping.
-
Systems
1C, CRM, stack.
-
Flows
Direction, frequency.
-
Master
Source of truth.
-
Creds
Staging access.
-
Errors
Alerts, SLA.
-
Volume
Peak orders/day.
Technical aspects
Reliability, security, and scale built in from day one.
Performance
DB indexes, cache, and queues keep the system fast as data and users grow. Load testing on staging before production.
Security
HTTPS, role-based access, audit logs, and API key protection. Personal data handled per your compliance model.
API & webhooks
REST and webhooks for website, 1C, Telegram, and partners — no manual re-entry. API docs included.
Mobile web
Responsive layout and PWA — most users work from phones. Native iOS/Android apps when needed.
Backups
Automated DB and file backups with verified restore on staging. Data loss in normal ops is unacceptable.
Staging
Test environment for team training and integration checks before release. Updates roll out without blocking core ops.
How we build it
-
01
Brief & scope
Scenarios, roles, integrations — MVP and estimate in 1–2 calls. We lock v1 priorities and what moves to phase two.
-
02
Prototype
Wireframes for key screens and admin — revisions before build. UX flows agreed so logic isn't rebuilt mid-project.
-
03
MVP
Working flow on your domain: core modules and test data. Your team walks through scenarios on staging before live integrations.
-
04
Integrations
Payments, 1C, Telegram, partner APIs — verified on staging. Test payments, doc exchange, and webhooks before go-live.
-
05
Launch
Deploy, team onboarding, monitoring first operations. Handover of access, docs, and support for first iterations.
FAQ
Cost?
From 80,000 ₽ one link. 5–10 days.
Zapier?
Custom for 1C, idempotency.
Which 1C?
Scoped at brief.
SLA?
Monitoring optional.
Docs?
OpenAPI, runbook included.
Order integration
Systems and flows — from 80,000 ₽, 5–10 days.
Get in touch
Pick a channel — I usually reply within a day.