Stuzhuk Lab — Chemistry of Code
Chemistry of Code
1C integration and custom solutions
1C integrations with websites, CRMs, portals, analytics, and bots using explicit contracts, externalId, idempotency, and exchange logs.
Tell me the goal, stack constraints, and timeline — I reply on Telegram.
I integrate 1C with web services while keeping the accounting system authoritative for its data and preventing external interfaces from depending on the thick client. A typical setup may include an HTTP service or OData in 1C, a TypeScript/Node.js intermediary, a retry queue, and a React or Astro interface. The stack is secondary to an entity map and an unambiguous owner for every field.
Every exchange defines an external identifier such as externalId, a version or modification date, an idempotency key, and repeated-delivery behaviour. Without them, a retry can become a second order and a temporary outage can turn into manual database comparison. Structured logs must identify the object, result, attempt count, and operator action.
Scope depends on ownership of the accounting rules. It may include 1C HTTP services and scheduled jobs, an intermediary API, portal, report, or messenger adapter. Accounting-policy changes, configuration upgrades, and 24/7 server administration are separate. Acceptance uses test entities and failure cases: repeats, missing fields, unavailable peers, and recovery.
An established connector is preferable when both systems and fields are standard and the vendor maintains it. Custom integration is justified for non-standard documents, several sources, special deduplication rules, or a dedicated operations view. For commerce inventory and orders, start with 1C warehouse and order sync.
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.
