We implement Odoo from scratch, move companies off 1C, build custom modules, accounting reports and mobile scanning apps. Manufacturing, warehousing, distribution.
First consultation, process audit and estimate — free of charge.
One product instead of a dozen disconnected systems
One database · one interface · one source of truth
Six directions covering the whole path from the first estimate to supporting a live system.
We move accounting off 1C without stopping the business: master data, balances, BOMs, open documents and a parallel run.
We configure the manufacturing perimeter: BOMs, routings, work centers, warehouse, costing and planning.
We build modules for processes the standard product lacks — designed so that Odoo upgrades do not break them.
Trial balance, reconciliation statements, aged receivables, management P&L and printable documents.
Apps for warehouse, production and field staff: handheld terminals, barcodes, offline mode and background sync.
We remove manual work: automated scenarios inside Odoo plus exchange with banks, marketplaces, EDI and telephony.
Pick a direction — we show the stages, what the client receives and how long it takes.
Migrations fail on decisions that were not made in time — what to move, what to archive, who cleans the master data. We lock those decisions down at the start.
We document the processes, mark what standard Odoo covers and what needs development, and build a 1C-to-Odoo object mapping table.
We hand over reports on duplicates, items without units of measure and dead partners. Garbage does not move into the new system.
At least three full runs on a test database. Loading is idempotent: every record has an external ID, so re-running never creates duplicates.
Stock by warehouse, balance per partner, cash, number of active items — everything matches to the cent.
One month in both systems, discrepancy triage, role-based training. After go-live 1C is switched to read-only.
Trading company — 4–6 weeks, manufacturing — 3–5 months
What exactly was built, in what time frame, and the numbers it produced.
End-of-life 1C:UPP plus a dozen Excel files. Month-end took 9–11 days and order cost was known a month after shipment.
Migrated 18,400 items, 2,700 BOMs and stock across 6 warehouses. Configured MRP, accounting exchange and a one-month parallel run.
The company grew to 40 SKUs without an ERP: orders in messengers, warehouse in a notebook. The retail client demanded lot traceability.
Deployed Odoo 18: lot tracking with expiry dates, quality control, GS1 labels, FEFO picking and a plan-vs-actual dashboard per line.
12,000 SKUs and 900 picking lines per shift. Built-in scanning failed whenever Wi-Fi dropped in the far aisles.
A Flutter app with an offline queue, wave picking and a route based on warehouse geometry, syncing with Odoo over JSON-RPC.
Reports were assembled in Excel from four entity exports. Consolidation took a week and numbers diverged between file versions.
Built a trial balance with analytics, reconciliation statements, aged receivables and a consolidated management P&L with drill-down.
Marketplace orders were re-entered by hand and stock was updated once a day, so out-of-stock items kept being sold.
Two-way exchange: orders, statuses, stock and prices every 10 minutes. Background job queue, exchange logs and failure alerts.
Sheet nesting was calculated in a separate tool and copied into orders by hand. Usable offcuts were never tracked and got lost.
A nesting module inside Odoo: layout selection, automatic receipt of usable offcuts into stock, and their effect on costing.
Fixed stages with a clear deliverable at each. You see a working system on your own data before the main payment.
We study how the business works today: interviews with process owners, current systems, bottlenecks. Output: target process description and an estimate.
We deploy Odoo with your products and a couple of real scenarios. You click through the system before paying for the bulk of the work.
Two-week iterations: configuration, development, data migration. Each sprint ends with a demo and the priorities for the next one.
Role-based training before go-live, a parallel run and on-site support in the first weeks. We triage issues and tune the reports.
An SLA contract: incident response, version upgrades through staging, backups, monitoring and new tasks from the backlog.
We show a prototype on your data in week two or three. You decide to continue while looking at the system, not at a slide deck.
Custom code lives in your repository with documentation. You are not locked in — another team can pick the system up.
Manufacturing, warehousing, distribution. We know where lot tracking, costing and accounting exchange usually break.
Stage-based estimates with a fixed sprint price. Odoo Community has no licence fees — you pay for the work only.
We work with Odoo 15–18, Community and Enterprise, deployed on your own infrastructure or in the cloud.
Capabilities that usually complement an ERP project — and work as standalone tasks.
Handling inbound requests, parsing documents, prompting sales staff — integrated straight into Odoo.
Telegram and WhatsApp: requests, order statuses, approvals and event-driven alerts from the system.
Corporate sites, online stores and customer portals connected to the ERP in real time.
Power BI and Metabase on top of Odoo data: sales, margin, production and finance in one place.
Implementation cases, engineering notes and team news.
We moved manufacturing accounting from 1C:UPP to Odoo 17 — master data, stock, BOMs and work in progress. One month of parallel run, zero data loss.
The company grew without an ERP: orders in messengers, warehouse in a paper notebook. In 10 weeks we deployed Odoo 18 with manufacturing, lot tracking and full traceability.
The stock Barcode module could not handle 900 picking lines per shift and broke on Wi-Fi loss. We built a Flutter app with an offline queue syncing over JSON-RPC.
Briefly about licensing, timelines, pricing and support.
Describe the task — we will come back with a timeline and cost estimate. The request commits you to nothing.
Minsk, Alibegova str. 28
Dubai, UAE, Business Bay
@IvanZhdaniuk_dev
We reply during business hours, usually within 2–4 hours.
