BIR noticeCAS and CBA users register their 2026 computerised books online through ORUS by 30 January 2027 (calendar-year taxpayers).Computerised books: register in ORUS by 30 Jan 2027.

CAS set-up in Odoo
TechNext

Odoo Ready PartnerPartner in Singapore · teams in Taguig City & Ho Chi Minh City

Connect Odoo to the tools you keep.

Odoo replaces a lot, but not everything. Banks, payment gateways, online stores, carriers and specialist tools stay, and talk to Odoo 20 over standard connectors or its API, so orders, stock and payouts flow across without anyone re-typing between systems.

  1. 1Discovery
  2. 2Training
  3. 3Integration
  4. 4Support
Connections to OdooSample data

Four connectors, one Odoo database

  • Bank feedStatement lines in38Synced
  • Payment gatewayPayment events in12Synced
  • MarketplaceOrders in, stock out6Synced
  • Online storeWeb orders to sales orders4Synced
Your Odooone database

Bank lines matched to invoices and bills 38 of 41

Synced today
1,240
Retries
0
Duplicates blocked
0
  1. Bank feed 38 statement lines imported
  2. Gateway payout of 12 payments matched
  3. Marketplace 6 orders in, stock levels out

At a glance

Phase
Step 3 of 4
Connects
Stores · payments · banks · email
Method
Standard connectors first, API where needed
Goal
No re-keying between systems
Team
Singapore HQ · Philippines · Vietnam

In one paragraph

Odoo integration connects the systems you keep to your Odoo database: banks, payment gateways, online stores such as Shopify and WooCommerce, marketplaces, carriers and specialist tools. TechNext uses standard connectors or the Odoo API, so orders, stock levels and payouts flow across without anyone re-typing them between systems.

Odoo integration you can watch: webhooks, scheduled jobs, retries and a dead-letter queue.

A TechNext Odoo integration is more than a connector. Webhooks push events in seconds, scheduled jobs sync in batches, every message carries an idempotency key so nothing is booked twice, and failures retry with exponential backoff before a person is alerted. Take a connector down and watch the retries, the backlog and the recovery.

Integration sync mapSample connectors · 09:00:00 · timings sped up
Your OdooOne database · 0 keys seen
Bank feedsStatement lines in
Payment gatewayPayment events in
Marketplace connectorOrders in, stock out
CourierLabels out, tracking in
InvoiceNowPeppol access point
BI / data warehouseExtracts out
Legacy WMSPicks out, confirmations in
  • Webhook: pushed in seconds
  • Scheduled job: batch on a timer
  • Failing, retrying

Connected to Odoo: bank feeds (statement lines, on a schedule), a payment gateway (payment events by webhook), a marketplace connector (orders by webhook, stock levels on a schedule), a courier (labels out, tracking by webhook), InvoiceNow through a Peppol access point (e-invoices out, delivery status polled), a BI or data warehouse (scheduled extracts) and a legacy WMS (polled for picks and confirmations).

Reliability: each message carries an idempotency key, so a re-delivered event is recognised and ignored instead of creating a second order or payment. A failed call is retried with exponential backoff, 1, 2, 4 then 8 seconds in this demo; after the last try it moves to a dead-letter queue and a person is alerted. When the connector recovers, the backlog drains and dead letters can be replayed safely.

Sample traffic with timings sped up. Real schedules, retry limits and alerting are agreed per connector when the data is mapped.

The systems around your Odoo.

Six kinds of system we usually connect, and what flows between each one and Odoo.

Online stores

Shopify, WooCommerce and other platforms: orders in, stock levels out, tracking synced, so the web store and Odoo never disagree.

  • Orders in
  • Stock out
  • Tracking

Marketplaces

Marketplace accounts kept in step with Odoo stock and orders, so a sale in one place isn't oversold in another.

  • Orders in
  • Stock out

Payment gateways

Card and e-wallet payments on invoices and the web store, with payouts and fees reconciled against your books.

  • Payments in
  • Payouts and fees

Bank feeds

Statement feeds into Accounting for daily reconciliation; payment files out for supplier runs.

  • Statements in
  • Payment files out

Email and calendar

Shared inboxes, send-as addresses and calendar sync, so conversations and activities live inside Odoo.

  • Shared inboxes
  • Calendar sync

Internal systems (API)

HR systems, BI tools, POS hardware and industry software. If it has an API, it can be connected.

  • HR
  • BI
  • POS hardware

In the Philippines, integration keeps your BIR books current.

Bank lines that reconcile every day keep the books behind your BIR reports (SLSP, SAWT, QAP and the 2550Q) current, and 2307 certificates come from the vendor bills you post with withholding tax. Odoo has no built-in connection to the BIR's EIS, and TechNext has not built one. If you are covered, we assess the options with you and quote any connection separately.

Where it touches the BIR Philippines

  • Bank feedsStatement lines matched to invoices and bills every day, so the books stay current between filings.
  • Payment gatewaysPayouts and fees reconciled, so the books match what the gateway actually paid.
  • BIR EISOdoo has no built-in connection to the BIR's EIS, and TechNext has not built one. If you are covered, we assess the options with you and quote any connection separately. Covered taxpayers must issue e-invoices by 31 December 2026.

Standard connectors first, custom code last.

  1. Map the data

    Agree which records flow, in which direction, field by field, before anything is switched on.

  2. Choose the connector

    A standard, maintained connector wherever one exists; custom code only where none does.

  3. Test on staging

    Run real records end-to-end and reconcile the totals before go-live.

  4. Go live and monitor

    Cut over with error handling that alerts a person, and documentation for the next developer.

Systems that agree with each other.

Odoo and its app store already cover most connections. We only write code where no maintained connector exists, and we document it so the next upgrade stays predictable.

  • 6kinds of system on the map
  • 1Odoo database
  • APIonly where needed
Integration checklist12 / 12
  • Field-by-field mapping agreed before anything syncs
  • Direction of each flow defined: one-way or two-way
  • Store and marketplace order, stock and tracking sync
  • Payment capture with payouts and fees reconciled
  • Bank statement import and outgoing payment files
  • Email and calendar connected to Odoo
  • Standard connectors used wherever maintained
  • Custom API code only where no connector exists
  • Tested on staging with real records
  • Error handling that alerts a person, not just a log
  • Documentation so upgrades stay predictable
  • A reconciliation check before go-live

Integration, answered.

Will Odoo replace our online store?

Only if you want it to. Otherwise we connect your existing Shopify, WooCommerce or marketplace store so orders and stock stay in step both ways.

Do you build custom connectors?

Only where no maintained connector exists. We prefer standard connectors from Odoo and its app store, and we document any custom code we write.

One-way or two-way sync?

Either. We agree the direction of every flow up front, field by field, so both systems hold the version of the truth you expect.

What about payment fees and payouts?

They are captured and reconciled, so your books match what the gateway actually paid out, fees included.

What happens if a sync fails?

Error handling alerts a person rather than failing silently, and everything is tested on staging with real records before it goes live.

How is integration priced?

On quotation, based on the systems and flows involved: request a quotation.

Stop re-typing between systems.

Tell us the store, gateway, bank or tool you need connected. We will map the flow and come back with a quotation.

Set up meeting Ask Nexi
Services catalogue