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
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
Partner in Singapore · teams in Taguig City & Ho Chi Minh City
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.
Four connectors, one Odoo database
Bank lines matched to invoices and bills 38 of 41
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.
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.
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.
Six kinds of system we usually connect, and what flows between each one and Odoo.
Shopify, WooCommerce and other platforms: orders in, stock levels out, tracking synced, so the web store and Odoo never disagree.
Marketplace accounts kept in step with Odoo stock and orders, so a sale in one place isn't oversold in another.
Card and e-wallet payments on invoices and the web store, with payouts and fees reconciled against your books.
Statement feeds into Accounting for daily reconciliation; payment files out for supplier runs.
Shared inboxes, send-as addresses and calendar sync, so conversations and activities live inside Odoo.
HR systems, BI tools, POS hardware and industry software. If it has an API, it can be connected.
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
Agree which records flow, in which direction, field by field, before anything is switched on.
A standard, maintained connector wherever one exists; custom code only where none does.
Run real records end-to-end and reconcile the totals before go-live.
Cut over with error handling that alerts a person, and documentation for the next developer.
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.
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.
Only where no maintained connector exists. We prefer standard connectors from Odoo and its app store, and we document any custom code we write.
Either. We agree the direction of every flow up front, field by field, so both systems hold the version of the truth you expect.
They are captured and reconciled, so your books match what the gateway actually paid out, fees included.
Error handling alerts a person rather than failing silently, and everything is tested on staging with real records before it goes live.
On quotation, based on the systems and flows involved: request a quotation.
Tell us the store, gateway, bank or tool you need connected. We will map the flow and come back with a quotation.