erp integration / legacy bridges
keep the erp. fix everything around it.
your erp is not the problem. the wall around it is. we work with SMEs running SAP Business One, Oracle NetSuite, Microsoft Dynamics, or a Thai-native system like Express Accounting, BusinessPlus or Formula ERP. none of them need replacing. what they need is a bridge to the systems the rest of the business already runs on: Shopify, Shopee, Lazada, LINE OA, and AI tools like Claude. replacing a working ERP is a multi-year bet most SMEs lose. integrating it is a 4 to 10 week bet that ships. we only take the bet that ships.
tell us about your integration
01 . what it is
we build the integration layer, not a new ERP. that layer speaks whatever protocol your system speaks: SOAP for SAP Business One, REST for NetSuite, SFTP or EDI for older supply-chain systems, and scheduled CSV exports where a vendor has locked every other door.
the architecture stays calm on purpose. an integration layer hosted in the region you choose, a cache and event log, jobs that retry cleanly instead of silently failing, and a written runbook for every flow we build. your ERP team keeps working exactly as they do today. nobody touches the underlying database. the bridge owns the contract, not the ERP.
for an SME running Thai-language master data, this usually means one more layer of care: customer, vendor and product records get normalised to a clean, consistent format so nothing turns into broken characters downstream, with reporting synthesised in English on top where a role needs it.
the integration spec is written and signed before a single line of code is touched: the data model on both sides, the protocol per flow, and how errors get handled. read-only flows go live first for validation, writes stay behind a feature flag until your own team says go.
02 . who it is for
archetype 01
stock and pricing need to reach Shopee and Lazada automatically, and a sales team working in LINE needs a way to check stock and take orders without calling the warehouse. a scoped integration can connect price and stock data to marketplaces, while a LINE OA workflow can support stock checks, quotes and order entry. discovery confirms what the ERP exposes before we propose the bridge.
archetype 02
a booking or property system needs to feed a guest or client workflow instead of living in its own silo, with a proper handoff into whatever the front-of-house team already uses day to day.
archetype 03
time, billing or inventory records need to feed a reporting or automation layer without opening up access to data that should stay restricted. governance and row-level access controls are part of the build, not an afterthought.
03 . what you receive
01
an integration spec, written and signed before any code is touched, covering the data model on both sides, the protocol per flow, and how errors get handled.
02
a hosted integration layer, built to run for years, with scheduled and event-driven flows kept separate and a dead-letter queue for anything that fails.
03
protocol adapters matched to your system: SOAP, REST, EDI, SFTP or scheduled CSV, including adapters for Thai-specific tools like Express Accounting and BusinessPlus.
04
master data normalisation, to validate Thai-language customer, vendor and product records before they reach downstream systems.
05
a handover package: full documentation, a deployment runbook, and code that sits in your own repository from day one. you own all of it.
06
90 days of post-launch care, with a bug-fix window and two tuning passes after go-live.
04 . timeline
phase 0
scoped within the 4 to 10 week project
we map your data model, agree the protocol per flow, and write the technical spec. fixed fee, credited to the build.
phase 1
after discovery
the integration layer goes up, adapters get scaffolded, and the first read-only flow goes live for validation before anything writes back to your system.
phase 2
the middle stretch
flows land in priority order, read-only first, writes behind a feature flag, with a working demo on a fixed cadence.
phase 3
cut-over, then 90 days of care
production cut-over with a written rollback plan, training for your team, and care starting the moment we go live.
05 . pricing
ERP integration starts from USD 16,500, fixed price per phase, published up front rather than quoted after a sales call. timelines run 4 to 10 weeks depending on how many flows are in scope and how the ERP side behaves. a short intake call comes first, and a transparent quote follows within 48 hours.
06 . proof
07 . questions
we integrate, always. the bridge sits between your existing ERP and the modern tools around it, so your ERP team keeps working as they do today and we never touch the underlying database. replacing a working ERP is a multi-year bet. integrating it is a 4 to 10 week bet that ships.
yes. these systems typically expose data through CSV exports or SFTP, occasionally a REST endpoint. discovery maps what is actually available per data domain, then we build the adapter around it. Thai-language master data comes out normalised to a clean, consistent format, with English reporting synthesised on top where needed.
we have scoped this exact pattern, a SOAP bridge into a 30-year-old on-premise ERP, for Hottlet Foods (epic.be), a 75-year-old IFS-certified food importer whose trilingual platform we already built and ships live today. the bridge itself is mapped and ready to build as the next phase. we bring the same integration discipline to a new engagement from day one of discovery.
4 to 10 weeks from discovery to production, depending on the agreed flows and ERP complexity. phase dates are fixed during scoping. 90 days of post-launch care follow go-live.
ERP integration starts from USD 16,500, fixed price per phase, with pricing published up front rather than quoted after a sales call. the exact number depends on how many flows and systems are involved. a short intake call comes first, then a transparent quote follows within 48 hours.
this can be a suitable integration pattern, but it must be scoped against the SAP Business One version, available APIs and marketplace requirements. we begin read-only, document the data contract and only enable writes after validation.
08 . further
ready to scope it
send us one paragraph: what ERP or accounting system you run, and what needs to talk to it. we reply with a call slot, and a transparent quote follows within 48 hours of that call.
