Skip to main content

asao-erp

Odoo Community from Python, through a verified command line. Read, group, page, print PDFs and browse the operation catalog, for notebooks, scripts and staff statistics, and review a period's books for mistakes, duplicates and signs of fraud.

from asao_erp import Client, ops, to_frame

erp = Client(profile="my-odoo")          # odoo-cli and its local profile
monthly = erp.group(ops.sales.quotation_list, by=["date_order:month"],
                    aggregate=["amount_total:sum"], filter=[["state", "=", "sale"]])
to_frame(monthly)

Odoo is a registered trademark of Odoo S.A. This project is not affiliated with or endorsed by Odoo S.A.

Install

pip install asao-erp            # or: pip install 'asao-erp[pandas]'

asao-erp holds no credential and never calls Odoo itself: every call goes through a command line, so the catalog's checks, readiness rules and refusals apply exactly as on the command line. Install the command line too, either of:

  • odoo-cli, for an Odoo you configure locally: Client(profile="my-odoo"). Set the profile up once with odoo-cli profile set; the credential stays in the environment or the OS keyring, never in your notebook.
  • The governed asao CLI, for an ASAO organization: Client(organization="...", connection="..."). Calls then act with the caller's ASAO login, within the permissions their role grants: reads, and, with a domain's write key, the verified writes. A high-risk one (posting, payments, rates) runs only after a colleague approves the exact request (asao aerp approval request, then approve); deletes and prints stay with odoo-cli.

Name a binary that is not on PATH with binary= or ASAO_ERP_CLI.

Use

Call Does
read(op, filter, limit, offset, order, id) One page of records of a read operation
iterate(op, filter, page) Every record, page by page
group(op, by, aggregate, filter) Groups computed by Odoo: "date_order:month", "amount_total:sum"; each group has count
print(op, id, to) A document's PDF (ops.finance.invoice_print)
operations(domain), describe(op) The catalog, and one operation's contract
execute(op, id, values) Any operation. A write runs only with Client(..., allow_writes=True)
to_frame(rows) A pandas DataFrame, with relations as names

ops lists every operation by domain, so the editor completes them (ops.finance.invoice_list). A failure raises ErpError with the command line's code, message and remediation.

Review the books of a period

review() runs odoo-cli review run (odoo-cli 0.10.0 or later) and returns the report it computes: bills or payments entered twice, duplicate partners, a supplier paid into an employee's account, orders split under an approval threshold, sales below cost, refunds after payment, expense claims twice or on leave, valuable scrap, overdue receivables, and the period's figures month by month.

report = erp.review("2026-07-01", "2026-09-30", params={"O01": {"window_days": 10}})
to_frame(report["findings"])   # check, severity, title, why, formula, thresholds, the records behind it
report["checks"]               # which checks ran, and why any did not
report["figures"]              # revenue, margin, purchases, cash in and out, by month

It only reads. A finding is a sign to look at again, never a verdict. The formulas live in odoo-cli, not in the SDK, so a script, a notebook and an agent read the same findings; odoo-cli review checks lists each check's formula and thresholds. It runs on a profile (Client(profile=...)); the governed asao CLI has no review yet.

What is verified, and what is not

The catalog's operations are verified on the stock Odoo Community image: 1285 on 19.0, and 1170 on 20.0, a candidate series that runs only with allow_unverified=True until it is supported. A public conformance run checks them again every week. Before each call, the command line checks the Odoo it reaches:

  • Is it Odoo, and which series?
  • Are the needed modules installed?
  • Is it customised where a write acts?

A write on a customised Odoo is held back (AERP_ENVIRONMENT_UNVERIFIED). It runs only with allow_unverified=True.

Odoo Online and Enterprise. The SDK reaches them through odoo-cli and the JSON-2 API (an API key of scope RPC; Odoo Online offers the external API on its Custom plan only). Reads run there, marked unverified, and group() works there as on Community; see odoo-cli's page on them.

Customised Odoo is not guaranteed. On an Odoo changed beyond the stock image (Enterprise, third-party or in-house modules, Studio, automations, fields added by hand), operations cannot be verified, and nothing guarantees that they work as described or without error. What you accept there runs at your own risk.

Develop

python -m unittest discover -s tests     # a fake command line, no network

examples/vscode/ is a sample VS Code workspace with a statistics notebook.

This repository is exported from the ASAO monorepo (see SOURCE.md). Issues and pull requests are welcome. An accepted change is applied in the monorepo and arrives with the next export.

License

Apache License 2.0. See LICENSE and NOTICE.

Tiếng Việt

asao-erp cho phép làm việc với Odoo Community bằng Python: đọc, gộp nhóm, phân trang, in PDF và tra catalog. Thư viện hợp cho notebook và cho nhân viên làm thống kê. Mọi lệnh đi qua odoo-cli (profile cục bộ) hoặc asao (theo tổ chức ASAO). SDK không giữ mật khẩu.

ASAO chỉ kiểm chứng trên bản Odoo chuẩn. Với Odoo đã tuỳ biến, ASAO không bảo đảm thao tác chạy đúng; dùng allow_unverified=True trên Odoo đó là tự chịu rủi ro.

Từ bản 0.2.0, review() rà soát sổ sách một kỳ qua odoo-cli review run (odoo-cli 0.10.0 trở lên): hoá đơn hay khoản chi nhập hai lần, đối tác trùng, trả tiền nhà cung cấp vào tài khoản nhân viên, chia nhỏ đơn dưới ngưỡng duyệt, bán dưới giá vốn, công nợ quá hạn, và số liệu từng tháng. Mỗi phát hiện là dấu hiệu cần xem lại, không phải kết luận, và kèm công thức, ngưỡng cùng chứng từ. Công thức nằm trong odoo-cli, không nằm trong SDK.

Metadata

Release files for asao-erp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for asao-erp 0.2.0
File Size Uploaded Provenance
asao_erp-0.2.0.tar.gz 34.1 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for asao-erp 0.2.0
File Interpreter ABI Platform
asao_erp-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 62.0 kB

Release files / asao_erp-0.2.0.tar.gz

Download URL asao_erp-0.2.0.tar.gz
Size 34.1 kB
Tags Source
SHA-256 checksum
How to use checksums
b02902bab93c7c2e58fb11706794d67fa65aec73784897ad3e08f14833a986e9
BLAKE2b-256 checksum
How to use checksums
3fd9031bab298149248f93e46a1e8db273c106ad28d5cb8cd0905d633035a911
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Release files / asao_erp-0.2.0-py3-none-any.whl

Download URL asao_erp-0.2.0-py3-none-any.whl
Size 27.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5087a8948928c6d529f00b3347972413b20592cd4fd3146ef5dea066e069960c
BLAKE2b-256 checksum
How to use checksums
b5c96f290b221ea62e0632f8e6ab717a1e066fb84aa1fabdb1997b6586b3ceee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

Security for asao-erp 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for asao_erp-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page