Short answer: Building a Didox Odoo integration or an Asl Belgisi connector from scratch usually means months of development, testing and ongoing maintenance. A ready, tested module shortens that path: you start with code that already works and get updates from your partner when the rules change. Deep Vision, an Odoo Gold Partner from Tashkent, has ready-made Odoo modules for Didox (e-invoices) and Asl Belgisi (digital product marking).
Almost every trading or manufacturing company implementing Odoo in Uzbekistan runs into two questions: how to send electronic VAT invoices (ESF), and how to track product marking codes. For the first, most businesses use Didox; the second is handled through the Asl Belgisi system. This article compares two ways to get a Didox Odoo integration and an Asl Belgisi connection: a custom build from scratch, or a ready module. The goal is simple: to help you judge any provider's proposal on your own.
If you first want to understand what e-invoicing and marking actually are, read our guide to Didox and electronic invoices and our Asl Belgisi digital marking guide. This article is about the technology choice and the risks behind it.
What is a Didox Odoo integration and why do you need it?
A Didox Odoo integration lets you send, receive and track electronic invoices straight from Odoo sales and purchase documents, without typing anything twice.
Without it, your accountant handles every invoice in two places: in Odoo and in the Didox account. With dozens of documents a day, that means hours of work, typing errors and a painful reconciliation at month end. Asl Belgisi is the same story: if marking codes are not tied to stock moves, nobody can say which code went to which customer.
What a good integration should give you:
- each document is created once, in Odoo;
- the ESF status (sent, signed, rejected) is visible inside Odoo;
- marking codes are linked to receipts, deliveries and returns;
- accounting and warehouse data match;
- you get a reliable base for VAT accounting and reports.
What are the risks of building the integration from scratch?
Custom development is not bad in itself. The problem is that its cost does not end with the first version. A from-scratch build usually brings the following.
Time. The developer first has to learn the external API, get access to a test environment and map document formats. That learning time is billed to you.
Untested edge cases. Partial returns, corrective invoices, multiple warehouses, discounted sales, VAT-exempt lines. These cases tend to surface in live operation, exactly when a mistake costs the most.
Changing rules. Requirements for electronic documents and product marking are updated from time to time. Who rewrites code built for a single client, and at what price? Contracts often say nothing about it.
Odoo version upgrades. Odoo ships a new version every year. Custom code has to be migrated each time, and if its author has moved on, that gets expensive.
Dependence on one person. Undocumented code is understood only by whoever wrote it.
In large IT projects these risks pile up. McKinsey and the University of Oxford studied more than 5,400 IT projects and found that large ones run 45% over budget on average and deliver 56% less value than expected (McKinsey). An integration is not a large project, but the logic holds: the more unknowns, the more unplanned costs.
Why is a ready Odoo module faster and cheaper?
A ready module is code that already runs in several companies, has been tested on the common scenarios and comes with a plan for updates.
The advantages are practical:
- Shorter time to go live. The main work is installation, configuration and fitting it to your processes.
- Bugs found earlier. Problems other users hit have already been fixed.
- Shared cost. Development cost is covered by many clients rather than one, so your share is smaller.
- Updates in one place. When rules change, the module is updated once and delivered to every client.
- Knowledge stays in the team. The whole team knows the module, not just one developer.
This does not rule out custom work entirely. If your business has a genuinely unique process, it can be built as an extension of the ready module. But the foundation should be ready-made. It is the same reasoning as choosing between building an ERP from scratch and a ready system, only at a smaller scale.
How can you check a provider's integration offer?
"We have a Didox integration" does not mean much on its own. Ask the provider these questions:
- Can you demo the module live, on a real document flow rather than slides?
- In how many companies, and for how long, has this module been running?
- Which Odoo versions does it support?
- How are returns, corrective invoices and partial deliveries handled?
- How are Asl Belgisi codes accepted on receipt and written off on sale?
- Who updates the module when rules change, and what does it cost?
- Is there documentation and a user guide?
- Do you keep the right to use the module if the contract ends?
- Is the company listed in the odoo.com partner directory, and at what tier?
If the answers are vague, or you hear "we'll build whatever you need", the module probably does not exist yet and you would be paying for its development.
How does Deep Vision handle Didox and Asl Belgisi integration?
Deep Vision is an official Odoo Gold Partner. You can verify this yourself on our page in the odoo.com partner directory. Under Odoo's official requirements, Gold means 300 new Enterprise users a year, at least 6 certified people and a client retention rate of at least 80%.
The facts:
- Deep Vision has ready-made Odoo modules for Didox (e-invoices) and Asl Belgisi (digital marking);
- the team has 7 Odoo-certified experts across versions 17 to 19;
- the partner page lists 20+ client references, mostly wholesale, retail and manufacturing;
- client retention is 89%, against the Gold minimum of 80%;
- Odoo 19 includes an official Uzbekistan accounting localization, and the Deep Vision team did Odoo's Uzbek translation.
A typical engagement goes like this: we first review your processes (document volume, warehouses, which products are marked), then install and configure the ready module, test it on real documents and train your staff. Standard Sales and Inventory often go live in 6–8 weeks, and a full rollout usually takes 2–6 months. Integrations are part of that plan, not a separate project.
Tax setup matters too: if VAT and taxes in Odoo are configured wrongly, even a good integration will send the wrong numbers. That is why we review the integration together with your accounting settings. For an overview of local requirements, see Odoo in Uzbekistan.
Learn more on our Odoo implementation service page, or fill in a short brief and we will prepare a plan for your document flow.
When do you still need custom development?
A ready module does not cover everything. You may have a non-standard document route, complex intercompany trade between several legal entities, or extra links to other systems. The right approach then is to use the ready module as the base and write only what is truly different. That keeps upgrade risk low and custom code to a minimum.
Ask yourself one question: is this requirement a real competitive advantage for the business, or just an old habit? If it is a habit, adapting the process to standard Odoo is usually cheaper and more reliable.
Frequently asked questions
How long does a Didox Odoo integration take?
With a ready module, most of the time goes into configuration, testing and training. The exact timeline depends on your document volume and processes; it is usually delivered inside the overall implementation plan.
Does the Asl Belgisi module work for every product group?
That depends on which of your product groups are marked and on your processes. During diagnostics we check your specific assortment.
Another provider implemented our Odoo. Can the module be added?
In many cases, yes. We start with an audit and check that your version, custom modules and accounting settings are compatible with the ready module.
What happens when the rules change?
A ready module is updated centrally. Update terms are written clearly into the support agreement.
Does it work with Odoo Community?
It depends on the module and version. We cover the differences in Odoo Community vs Enterprise, and give a precise answer during diagnostics.
Sources
- Deep Vision in the Odoo partner directory
- Odoo partnership tiers and requirements
- McKinsey: delivering large-scale IT projects on time, on budget and on value
To get a Didox and Asl Belgisi integration plan, fill in the brief or call +998 77 093 00 07.