API Integration
Keep orders, payments and shipments in sync across every system.
We connect Odoo and other ERPs to your CRM, online stores, marketplaces, payment gateways, banks and carriers through REST, GraphQL and webhooks, with retries, idempotency and monitoring built in, so a failed call never becomes a missing invoice.
- REST, GraphQL and webhooks
- Retries and idempotency keys
- Shopee, Lazada, TikTok Shop
- PromptPay and bank reconciliation
- Priced per endpoint
- Odoo versions we integrate
- Price per integration endpoint
- Reply time on enquiries
- Offices: Bangkok, New York, Delhi NCR
What we integrate
Integrations built for the day an API changes
Most integrations work in the demo. The ones we build keep working when a marketplace renames a field, a carrier times out or the same webhook arrives twice.
REST and GraphQL APIs
Custom endpoints on Odoo, Node.js or Python services, with OpenAPI documentation, versioning and scoped tokens for partners and your own apps.
Webhooks and event sync
HMAC-verified webhooks in, signed webhooks out, queued and processed in order, so stock and order status update as events happen instead of in a nightly batch.
Marketplaces and online stores
Shopee, Lazada and TikTok Shop orders, stock and fees into Odoo, plus Shopify through our own published connector with two-way sync.
Payments and banks
Stripe, 2C2P and PromptPay payments matched to invoices, Thai bank statement imports, and payout reconciliation that separates gateway fees from revenue.
Carriers and logistics
Odoo's DHL, FedEx and UPS connectors configured, plus custom links to Thai carriers such as Flash Express, KEX and Thailand Post, with labels and tracking written back to the delivery order.
CRM and legacy systems
HubSpot, Salesforce and Zoho contacts and deals synced with Odoo, LINE Official Account messages linked to customers, and older systems reached through files or database views when there is no API.
Beyond Zapier
When a no-code connector stops being enough
Zapier, Make and n8n are good for light automations, and we will tell you when one is enough. As volumes grow, per-task pricing, silent failures and missing reconciliation start to cost more than a small integration service you own, with queues, retries and alerts.
- Idempotency keys, so a retried call never creates a duplicate order
- Exponential backoff and a dead-letter queue for failed messages
- Daily reconciliation reports that compare both systems
- Alerts by email or LINE when an integration needs attention
Data contract
Fields, owners, formats and failure rules agreed in writing for every endpoint.
Queue
Every inbound event is stored before processing, so nothing is lost during an outage.
Retry
Failed calls retry with backoff, and duplicates are dropped by idempotency key.
Reconcile
Counts and totals are compared daily, with every difference listed for a person to review.
Typical projects
Integrations that remove a daily manual job
Marketplace orders into Odoo
Shopee, Lazada and TikTok Shop orders arrive in Odoo with the right warehouse and marketplace fees split out, and stock is pushed back to every channel after each sale.
Payments matched to invoices
PromptPay and card payments are matched to open invoices automatically, and only the leftovers are listed for the accounts team instead of a hunt through bank statements.
Group companies on different systems
A US entity on QuickBooks, an Indian entity on Tally and a Thai entity on Odoo, consolidated through scheduled syncs with a clear owner for every record.
Industries
Integration patterns by industry
The systems change from sector to sector, but the failure points repeat. These are the connections each sector usually needs first.
- Retail & E-commerceMarketplaces, POS and the webstore on one stock ledger.
- Wholesale & DistributionBulk order imports from key accounts, customer portals and carrier booking.
- Freight & LogisticsCarrier tracking, customs data and vendor bills matched to each shipment file.
- ManufacturingMachine counts, barcode scanners and supplier portals feeding work orders.
- HotelsChannel managers, booking engines and outlet POS posting into accounting.
- Hospitals & ClinicsAppointment apps, lab systems and insurer claims linked to patient billing.
- Real EstatePayment gateways, bank feeds and CRM leads tied to units and contracts.
- Travel & ToursSupplier APIs, booking sites and multi-currency payments per booking.
How we work
Five steps from spreadsheet exports to live sync
1. Audit the systems
We list every system, who owns each record, the API limits and every place where people re-key data today.
2. Agree the data contract
Field mappings, formats, error rules and the direction of every sync are signed off before we build, and the price per endpoint is fixed from here.
3. Build with retries
Queues, idempotency keys, backoff and structured logs from the first commit, tested against sandbox accounts.
4. Run in parallel
The integration runs beside the manual process until the reconciliation report matches for a full cycle.
5. Monitor and maintain
Dashboards, alerts and a named engineer who updates the integration when a provider changes its API.
Tools and protocols
Protocols and tools we work with daily
- REST
- GraphQL
- Webhooks
- OAuth 2.0
- OpenAPI
- Odoo XML-RPC and JSON-RPC
- Python
- Node.js
- PostgreSQL
- Redis
- RabbitMQ
- n8n
- Postman
- Grafana
Our commitments
Integrations you can audit line by line
No invented uptime figures. These are the terms every integration ships with, written into the scope before we start.
Map my integrations- Webhook channels in our Shopify Odoo Connector
- Odoo apps we publish ourselves
- Written status note
- Documentation and support
FAQ
Questions clients ask first
How much does API integration cost?
Integrations are priced per endpoint once the data contract is agreed, so you know the cost of each connection before we start. The price depends on the direction of the sync, the volume and how well the other system's API is documented. Third-party API fees, if any, stay on your own account.
Can you connect Shopee, Lazada and TikTok Shop to Odoo?
Yes. Orders, stock levels, listings and marketplace fees sync with Odoo Sales, Inventory and Accounting, with each shop mapped to the right warehouse. Fees and payouts are split out, so each marketplace settlement reconciles against the bank.
What happens when the other system's API is down?
Nothing is lost. Inbound events are stored in a queue before processing, failed calls retry with increasing delays, and messages that still fail go to a dead-letter queue with an alert. Idempotency keys make sure a retry never creates a duplicate order or payment.
Should we use Zapier or Make instead of a custom integration?
For low-volume, non-critical automations, often yes, and we will say so. A custom integration earns its cost when volumes grow, when money or stock depends on the data, or when you need reconciliation and an audit trail. A common setup uses both: no-code for small tasks, owned services for orders, payments and inventory.
Can you integrate a system that has no API?
Usually. We can work with scheduled file exports in CSV, Excel or XML, SFTP drops, email parsing or read-only database views, and we explain the trade-offs in freshness and reliability. If the vendor adds an API later, the same data contract lets us switch without changing Odoo.
Who maintains the integration after go-live?
We can, under a monthly support plan, or your own team can, using the runbook and repository we hand over. Monitoring and alerts are set up either way, and when a marketplace or carrier changes its API, the fix is made against the same data contract.
Start with an audit
Tell us which systems need to talk to each other
List the systems, the records that move between them and where it hurts today. You get a reply within one business day, and after a short call, a written data contract with a fixed price per endpoint.
- Reply within one business day
- Fixed price per endpoint
- Monitoring built into every integration
Prefer to talk first? Call us or WhatsApp us.