1C integration and custom solutions

1C and Website Integration

A 1C website integration transfers catalogues, prices, stock, requests, or statuses without re-entry.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

A 1C website integration transfers catalogues, prices, stock, requests, or statuses without re-entry. I centre the exchange on externalId and explicit field ownership so retries cannot create a second entity.

Scope may include an HTTP service or OData, intermediary adapter, schedule or webhooks, idempotency, and logs. Acceptance covers create, update, delete or archive, repeated batches, and one invalid row among valid ones; one bad product must not stop the batch, and operators can locate it by externalId. Full commerce should use warehouse and order sync.

Acceptance criteria

Done when

  • Agreed entities sync with externalId and no duplicates on retry
  • Exchange journal shows object, result, and attempt
  • Failure paths are visible to operators
  • Catalog or order statuses match on a sample of SKUs/docs

Deliverables

  • API/contract notes + mapping table
  • Staging exchange runbook

Out of scope

  • 1C accounting-policy changes
  • Production 1C upgrades without change windows

Assumptions

  • Test infobase and a 1C contact for metadata

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Ballpark estimate

Scope size
Extras

FAQ

Tap a question to expand the answer.

Must the exchange be real-time?

Only when the process requires it. Catalogues often suit schedules, while order statuses can be event-driven.

What is the source of truth?

It is defined per field—for example, price in 1C and marketing copy on the website. Uncontrolled two-way editing causes conflicts.

Discuss this directionContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

View full service page