“It Has No API” Is a Scoping Answer, Not an Engineering One

By Dissai Pindatisha, Founder, Simply & Fine Solutions · Published 10 Oct 2026 · Updated 10 Oct 2026

The situation

A packaging manufacturer came to us running WinSpeed for accounting. They wanted Odoo for operations, with accounting data flowing between the two. No API. No documented integration path. No vendor appetite to build one.

We built the integration anyway — from scratch, at billion-baht transaction scale.

The decision, not the technique

The obvious alternative was to rip out WinSpeed and migrate everything to Odoo. Cleaner architecture, much bigger project, and it would have put the client's finance function through a full system change they hadn't asked for.

Integration was the smaller, less elegant, correct answer. The client's accounting team kept working the way they already knew. Operations got the system they needed. Nobody had to be retrained on two things at once.

The engineering instinct is to consolidate onto one platform. Sometimes the business answer is to leave the working thing alone and build the bridge.

Simply & Fine Solutions — Odoo implementor, Bangkok. ISO/IEC 29110 certified. More insights