Loading page
Three stages, no dates. Anything that is waiting on something names what it is waiting on — a credential, a decision, an environment. Nothing appears here before it is real enough to describe honestly, and nothing is for sale until it is finished.
Available today.
Shopify orders, stock, shipments, refunds, cancellations and Shopify Payments payouts, through a queue that retries safely and never confirms an order whose totals it cannot reproduce.
The stock and shipping bridge for the connector: locations, stock without overselling, and deliveries sent as fulfillments with tracking. No price of its own.
Facebook and Instagram Lead Ads into Odoo CRM, with every webhook verified, one lead per leadgen id however many times Meta retries, and a backfill for anything missed.
Free. The ETA connection and code mappings e-Invoice and e-Receipt share, so each filing module is bought on its own.
Card payments in Egypt through Paymob current Intention API, with callbacks verified before they are believed and retries that cannot confirm an order twice.
Point-of-sale receipts in the Authority documented v1.2 structure, with a per-till chain that halts rather than warns when a receipt is skipped.
File customer invoices and credit notes with the Egyptian Tax Authority, with a 202 recorded as received rather than filed and rejection reasons shown in the Authority own words.
Two-way WhatsApp on the official Meta Cloud API: readable keyword rules, the 24-hour service window enforced before the send, and five safety rules that cannot be configured away.
Customer statements whose closing balance reconciles, aged from the due date rather than the invoice date, bilingual in English and Arabic.
Every IP Office call logged in Odoo and matched to the contact and opportunity, with a spooling listener that makes an Odoo restart cost delay rather than calls.
Thirteen checks on database size, failing scheduled actions, mail delivery and your own integrations, with unknown reported as its own severity rather than rounded down to green.
Multi-level approvals for sales orders and invoices: conditions picked from dropdowns rather than typed as code, records locked while a decision is pending, and a decision history that cannot be edited afterwards.
Activity, sensitive-field changes, exports, sessions, access changes and a weighted security score, in one Odoo application.
Effective permissions after group inheritance and record rules: what one account can reach, who can reach one model, and how two accounts differ.
A dunning ladder you define once — one email per customer, an activity in someone’s diary, and a record of every reminder sent.
Scheduled backups to local disk or SFTP, each archive re-opened and verified, with mail only when a run fails.
Delete, export, print, archive and duplicate restricted per model, with your own refusal message and a log of every blocked attempt.
Your own label layouts, EAN-13, Code 128 and QR, starting at any cell on a part-used sheet.
Visa, permit and certificate expiry with per-type lead times, two reminders and a missing-document view.
Ask questions of your Odoo in plain language, answered with the asking person’s own access rights. Nothing is exposed on install, every read is logged, and a simulated provider means it can be evaluated with no API key from anybody.
One endpoint that lets Claude, or anything else speaking the Model Context Protocol, ask questions of your Odoo. A token is bound to one person, and every call appears in the same audit trail as the questions asked inside Odoo.
Save a report over any model, share it with a team, and have it arrive by email every Monday — read with each person’s own access rights, and with schedules that run as a named person rather than as the system.
Your saved reports become Power BI tables over a native OData feed. Get Data, OData feed, paste — no custom connector, no Power Query, and each token returns its own person’s rows.
Odoo attachments filed into SharePoint automatically, in folders somebody can navigate a year later, with a log of where every document went — and the Odoo copy removed only once Microsoft has confirmed the file.
Days in stock and days since last shipment as two separate measures, across six ageing bands.
A company’s own listed-share investments in a ledger that cannot be quietly rewritten, with broker statement import, reconciliation and draft journal entries as companion listings that come with it. Odoo 19, English and Arabic.
Built and tested: a button on the contact form that opens WhatsApp with the number already correct, and hides itself when the number is not usable. LGPL-3, no account, no API, nothing recorded.
Code exists and is being worked on. It is not for sale until it is finished.
Screenshots are done — 26 captures across seven modules, on the product pages and the Odoo Apps Store listings. A demo video per flagship is the remaining half.
Built and tested: a message channel with the provider behind an interface, a delivery log, templates, retry with backoff, and delivery states that move only when the provider reports them. 80 tests, all against a simulated provider — no Meta account needed to install it, configure it or see what it would send.
Waiting on: Not on the Odoo Apps Store yet — it goes up with the first module that depends on it. Licensable direct in the meantime. Live sending needs Meta WhatsApp Cloud API credentials; everything else works without them.
Most of the catalogue is already listed for Odoo 19 on the Apps Store; each product page says which series it is listed for. The rest have 19.0 builds and are being registered one listing at a time.
Waiting on: The Apps Store registers a limited number of new branches per account per day.
Decided and specified. No date, because a date we have not earned is not information.
The first paid module on the channel, extending the existing dunning engine rather than duplicating it: the same escalation ladder, delivered over WhatsApp instead of email.
Waiting on: Meta WhatsApp Cloud API credentials for live sending.
Audit Log & Security Center, Access X-Ray and Restrict Delete & Export sold together — the past, present and future tense of the same question.
Waiting on: A bundle cannot be sold on the Odoo Apps Store, so it needs checkout on this site, which needs a payment provider.
Community, Professional, Business and Enterprise tiers, each defined by a response time and an hours allowance rather than the word “priority”. Modules keep working whether or not a subscription is live.
Waiting on: A payment provider.
The WhatsApp button is the first. Free apps are how a new vendor earns downloads, stars and a first review — and they are built to the same standard as the paid ones, with the same documentation and the same tests.
Odoo events posted into a Teams channel over Microsoft Graph. The document half of Microsoft 365 shipped first because Odoo already has Outlook mail and calendar; this is the part it does not have.
Waiting on: An Entra app registration.
Editing a printed document layout without a developer: fields, headers, totals, conditions, multi-company and multi-language. Distinct from the Advanced Report Builder, which is about tabular reports rather than printed forms.