Yevhen Stuzhuk - Personal Portfolio
I am a Senior Software Engineer
1C integration and custom solutions
Web layers around 1C: site and CRM sync, REST APIs, customer portals, employee workspaces, dashboards, AI assistants, and MAX or chat-bot channels.
1C is often the accounting and operations core; customers, staff, and partners still need fast web surfaces—catalogs, cabinets, approvals, analytics, and messenger channels. I build the integration layer and web UI so 1C stays the source of truth while the outside world gets a modern experience.
Typical stack: HTTP services or OData on the 1C side, TypeScript/Node.js middleware for queues, validation, and auth, React or Astro for portals and dashboards. Delivery is iterative: map entities and flows first, then ship vertical slices (e.g. catalog sync before full checkout).
FAQ
Tap a question to expand the answer.
Which 1C configurations do you work with?
Trade, ERP, Accounting, and custom configs—usually via HTTP services, OData, or file/XML exchange. The integration contract matters more than the box name.
Do you modify 1C code or only the web layer?
Both when needed: HTTP services or scheduled jobs in 1C plus TypeScript middleware and web UI. Scope is agreed up front so your 1C team keeps ownership of core accounting rules.
What access do you need to the 1C server?
A test infobase, published HTTP endpoint or VPN, and a contact on the 1C side for metadata and release windows. Production access only through agreed change process.
How do you keep sync secure and reliable?
TLS, token or mutual auth, idempotent handlers, dead-letter queues, and structured logs. No direct DB exposure from the public web—only documented APIs.
How long does a typical integration take?
A focused exchange (e.g. catalog or order status) often lands in 3–6 weeks; portals and multi-system CRM flows take longer. We ship vertical slices, not a big-bang go-live.
