Stuzhuk Lab — Chemistry of Code
Chemistry of Code
1C integration and custom solutions
Reliable 1C exchanges with modern stacks: APIs, queues, idempotent sync, and reporting your ops team can trust after go-live.
Tell me the goal, stack constraints, and timeline — I reply on Telegram.
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).
Representative work
Recent deliveries include timetracking and EmploymentApproval—systems where 1c integration and custom solutions skills (1C, HTTP/REST, OData, HTTP services, TypeScript, Node.js, React, PostgreSQL, webhooks, VK/MAX/Telegram bots, dashboards, LLM) were applied end to end.
Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.
Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.
After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.
We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.
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.
Tell me the goal, stack constraints, and timeline — I reply on Telegram.
