Connect the systems where your team currently copies data by hand: payments, shipping, messaging, accounting and devices. Then judge each connector not by how it behaves on a good day, but by what it does when the other side is slow, wrong or offline. A connector that loses an order silently is worse than no connector.
What is worth connecting
Start with the point where staff retype things. Common places include:
- Payments. Online payments should arrive in Odoo and match the invoice, so nobody ticks them off by hand.
- Shipping. Rates, labels and tracking from couriers can come into the sales or delivery screen.
- Messaging. Order updates and notifications can reach customers by message, email or text when something happens in Odoo.
- Accounting. If part of your accounts lives elsewhere, data may need to move both ways, or your opening data may need to be brought in once.
- Devices. Barcode and label printers, and attendance devices, can feed records straight into Odoo.
- Marketplaces. Products, stock and orders may need to stay in step with a place you sell.
You do not need all of these. Pick the one that costs the most hours each week.
How to judge a connector
A connector is a small piece of software that must keep working when things go wrong. Ask these questions of any connector, whoever built it.
- Does a retry create a duplicate? If a payment message is sent twice, you must still get one payment. This property has a name, idempotency, and it is basic.
- Does it retry sensibly? After a failure it should wait and try again, with growing gaps, not hammer the other system.
- Is there a queue? If the other side is down for an hour, jobs should wait and then run, not vanish.
- Are failures kept? A failed message should be stored for review. It should not be thrown away.
- Does someone get told? Logs and alerts should reach a person before a customer complains.
- Where do the keys live? Passwords and access keys should sit outside the code, not inside it.
Real-time or scheduled
Not everything must be instant. Stock levels shown on a shop may need to be fresh. A daily accounting exchange may be perfectly fine. Choose by how stale the data can be, and then check that totals are compared, so a difference shows up quickly instead of months later.
The middleware idea
Sometimes Odoo should not talk to an outside system directly. A small service in between takes a job from Odoo, calls the other system, retries when needed and reports the result back. This keeps Odoo fast and keeps the messy parts in one place that is easy to watch.
When there is no ready-made link
Some systems offer no clean connection. Options include exchanging files on a schedule or building a small custom link. A good consultant explains the trade-offs before choosing, including what will need attention later.
Mistakes to avoid
- Connecting everything at once.
- Skipping a test with real, awkward data.
- Having no plan for what happens when the other system changes.
- Assuming a connector is maintained because it exists.
Where Teapot Techies fits
Our Odoo integrations page lists the kinds of connector we build, each available on request. Tell us which systems you use and we will explain what is involved, what we would need from you and how failures would be reported. The custom side sits with our Odoo engineering work. To talk it through, use the contact button below.