How to Choose a 1C Integration Provider: 10 Questions to Ask
Contents
- 1. What do you need to know about our 1C before estimating?
- 2. What happens if an order is sent twice?
- 3. What happens if 1C is down for an hour?
- 4. How will we know that data sync has stopped?
- 5. Who on the team is responsible for 1C?
- 6. How do you work with Bitrix24 and MoySklad?
- 7. How do you estimate a project?
- 8. How does testing work?
- 9. What is included in post-launch support and who owns the code?
- 10. Can you show a similar project?
- Red flags
- Studio, freelancer, or 1C franchisee
- Frequently asked questions
There are many web studios and many 1C developers on the market. There are far fewer teams that combine both competencies and make sure orders reach accounting without duplicates. These 10 questions will help you understand who you are dealing with before signing a contract.
1. What do you need to know about our 1C before estimating?
Good answer: configuration, version, customizations, data volume, access to a copy. Bad answer: "send the specs, we will estimate in a day."
2. What happens if an order is sent twice?
Good answer: unique transaction key and duplicate prevention. Bad: "that never happens."
3. What happens if 1C is down for an hour?
Good answer: message queue and automatic retries. Bad: "the order will not go through, a manager will enter it manually."
4. How will we know that data sync has stopped?
Good answer: operation log, monitoring, notifications to the owner. Bad: "clients will let us know."
5. Who on the team is responsible for 1C?
An in-house specialist or partner, their experience with your configuration, and how responsibility is split between web development and 1C.
6. How do you work with Bitrix24 and MoySklad?
If you use these systems, the contractor must understand their APIs, limitations, and common issues when linking them with 1C.
7. How do you estimate a project?
Good answer: an audit or discovery phase, then phased estimates. Bad: a fixed price for the entire project after a single call.
8. How does testing work?
A test database, testing against real scenarios, data reconciliation before and after, and a pilot with a limited group.
9. What is included in post-launch support and who owns the code?
Response times, monitoring, updates when configurations change, and costs. Source code, access, and documentation must be transferred to you, with any exceptions explicitly stated in the contract.
10. Can you show a similar project?
Not necessarily with the client's name, but with an overview of the challenge, architecture, and results.
Red flags
- an estimate without any questions about your 1C;
- a promise to "finish in two weeks" for a portal with custom pricing;
- no 1C specialist on the team or among partners;
- conversations limited only to design and pages;
- no support agreement;
- reluctance to hand over code and access.
Studio, freelancer, or 1C franchisee
| Contractor | Strengths | Risks |
|---|---|---|
| Freelancer | Price, flexibility | Accountability, support, vacation, or sudden departure |
| 1C franchisee | Knowledge of configurations | Web development and interfaces are often weaker |
| Web studio without 1C | Design and interfaces | Integration becomes a bottleneck |
| Team with both competencies | The entire workflow under single accountability | Higher upfront cost |
Frequently asked questions
Do you need a contractor specifically from Kazakhstan?
Preferably: they need to know local 1C configurations, documents, and distributor business practices.
How to test a contractor on a small task?
Start with an audit: it will show the team's skill level and give you an independent result.
What if the contractor works with only one system?
Then no one is responsible for the connection between systems. This is the main source of problems in integrations.
