Integrating 1C with Mobile Apps via REST API
We constantly face a situation: a B2B client keeps accounting in 1C and needs to "just" connect a mobile app. The typical request: "Make orders from the mobile app automatically land in 1C, and update stock levels in real time." Simplicity is deceptive — the zoo of configurations (Accounting, Trade Management, ERP, UNF, Payroll) turns a routine task into a project with hidden pitfalls. Each configuration has its own data structure, and what works in Trade Management 11 does not work in ERP 2.5. Let's dive into technical solutions and common pitfalls. Experience shows that a properly designed integration of 1C with a mobile client pays for itself within a few months. In this article, we'll cover what problems we solve, how to choose the integration method, and what to focus on during implementation. Our team has completed dozens of projects linking 1C with mobile apps on iOS and Android, including offline warehouses, courier services, and retail point-of-sale networks. With over 50 successful integrations and 8 years of expertise, we offer a detailed work plan and documentation at each stage.
What Problems We Solve
Synchronizing catalogs. A product database of 50,000 items — full export every time is unacceptable. Solution: an HTTP service with a modified_since parameter that returns only changed items. Implementation on the 1C side uses ThisObject.DateModified. Frequency: catalogs every 30-60 minutes, prices on document opening. A proper implementation saves staff time and reduces manual entry errors. Businesses using our integration save up to $20,000 annually in data entry errors.
Retrieving stock balances. A query to the accumulation register via OData: GET /odata/standard.odata/AccumulationRegister_TovarыNaSkladах/Balance?$filter=... — slow on large databases. Optimization: an HTTP service with SELECT + GROUP BY, cache in middleware with TTL 2-5 minutes.
Creating documents (orders, waybills). Transaction on the 1C side: HTTP POST → 1C creates an object, posts it, returns the number. If there is an error, a meaningful response is needed (not just 500). Agree on the error format with the 1C developer upfront.
Which Integration Method to Choose?
1C HTTP Services — a native option for modern configurations. Business logic stays inside 1C, no third-party components. Downside: requires a 1C developer, limited performance (1C is not optimized for high concurrency). OData Interface — publishes objects without code, but limited (expand one level, not all filters). Middleware (recommended) — a Node.js/Go/.NET service calls 1C via HTTP services or OData, caches, transforms, and returns concise JSON to the mobile client. This is faster and more flexible: middleware processes requests 10 times faster than direct 1C calls.
| Criteria | HTTP Services | OData | Middleware |
|---|---|---|---|
| Flexibility | High | Medium | Maximum |
| Performance | Low (single-threaded) | Medium | High (multi-threaded) |
| 1C Specialist Required | Yes | Partially | No (only middleware) |
| Development Speed | Medium | Fast | Depends on scope |
1C documentation: HTTP Services — the foundation for implementation.
How to Ensure Data Transfer Security?
1C supports Basic Auth out of the box. For production, HTTPS and a technical user with minimal rights are mandatory. OAuth 2.0 — only via an external IdP (Keycloak) with mapping in middleware. On the mobile client, credentials are stored in Android Keystore + EncryptedSharedPreferences or iOS Keychain. Never use SharedPreferences or UserDefaults. Proper authentication protects against financial loss. Our solutions are tested and conform to industry security standards.
Offline Warehouse on Android: Integration with 1C
A typical task: a mobile handheld scanner on Android in a warehouse area with poor WiFi. The operator scans barcodes, creates an inventory — data is saved locally in Room. When network appears, a batch is sent to 1C in one request. The 1C HTTP service accepts an array of items, creates an inventory document, and returns the result. On mobile: status "queued" → after confirmation "sent", local copy marked as synchronized. Delta-sync of catalogs via the modified_since parameter — only changed records. This significantly reduces infrastructure costs. Typical integration cost for a medium business ranges from $8,000 to $15,000 depending on complexity. Contact us if you need offline mode implementation.
| Sync Type | Description | Latency |
|---|---|---|
| Online (direct request) | App calls 1C API in real time | Instant |
| Periodic | Pull catalogs on schedule | 30-60 min |
| Offline (batch) | Local accumulation, batch sending | When network available |
Typical Mistakes When Integrating 1C with a Mobile App
- Publishing 1C on IIS without SSL — all data transmitted in plain text.
- Ignoring user rights — using a technical user with admin rights. Violates the principle of least privilege.
- No timeout on 1C requests. A heavy query can take 30-60 seconds. Set
timeout: 15son middleware, return 504 to client with a retry button. - Caching without invalidation — stale stock levels. Use TTL or versioning.
Process of Work
- Audit of 1C configuration — determine data structure, version, ability to publish HTTP services.
- API design — define methods, request/response formats, authentication scheme.
- Implement HTTP services in 1C — development and testing (usually 1-2 weeks).
- Develop middleware (if needed) — caching, transformation, error handling.
- Integrate with mobile client — configure REST client, handle offline mode.
- Testing — load testing (simulate peak requests), functional, edge cases.
- Deploy — publish on web server, configure HTTPS, TestFlight/Google Play.
Our certified 1C specialists with 8+ years of experience guarantee integration stability and provide SLAs.
What's Included in the Work
- API documentation (OpenAPI/Swagger specification).
- Code for 1C HTTP services (or middleware).
- Deployment and access setup instructions.
- Training for your developers (1-2 hours online).
- Technical support for 30 days after launch.
Timelines and Cost
Audit of 1C configuration and API design — 3-5 days. Basic integration (reading catalogs and stock levels, creating documents) via HTTP services — 3-6 weeks. Full offline support, delta-sync, error handling — plus 2-3 weeks. Cost is calculated individually, depends on the 1C configuration and customization scope. Typical integration cost for a medium business ranges from $8,000 to $15,000. Get a detailed plan — contact us.
Our experience shows: a properly designed integration pays for itself. Contact us to evaluate your project.
Trusted by 50+ companies. Guaranteed results.