Short answer: System integration is priced per data flow: about NT$30,000–60,000 for a one-way flow and NT$80,000–150,000 for two-way sync, plus 12–20% a year for maintenance. Once you run 4 or more systems with more than 6 data flows, a central middleware layer usually brings 3-year total cost down by 20–30%.
A 35-person food wholesaler runs 5 systems: its own online store, a marketplace store, POS, an ERP and accounting software. The accountant spends 3 days a month importing orders, and last quarter they oversold 40 orders. Vendor A quoted NT$460,000 to wire up 8 data flows individually; Vendor B quoted NT$520,000 to build middleware first. Is the one NT$60,000 cheaper really cheaper?
Busting Industry Myths
Bottom line: the expensive part is the next 3 years of maintenance and troubleshooting.
- Myth 1: Integration is a one-time cost. Reality: partner APIs change. Shopify releases a new API version every 3 months and supports each for at least 12 months, so every flow needs updating yearly.
- Myth 2: Real-time sync is always better. Reality: daily batches suit reporting and reconciliation; real time costs about 1.5–2×.
- Myth 3: If there is an API, it can be connected. Reality: mismatched codes and tax types are the hard part; field mapping often takes 30–40% of the hours.
- Myth 4: Middleware is always more expensive. Reality: about 10–15% more up front, but each new system adds only 1 connector.
Core Framework: The Integration Architecture Decision Tree
Bottom line: decide whether to integrate before deciding how; the number of data flows sets the architecture.
- Step 1, whether to integrate: monthly manual hours = records per month × minutes per record ÷ 60. Above 10 hours, or when errors cause overselling, integrate; otherwise use a CSV import template.
- Step 2, how real-time: real time for stock and order status, daily batches for reporting and accounting.
- Step 3, which architecture: up to 3 flows, point-to-point; 4+ systems and more than 6 flows, middleware; in between, depends on whether you add systems within 2 years.
| 3-year total cost (5 systems, 8 data flows) | Point-to-point | Middleware |
|---|---|---|
| Build | 8 flows × NT$57,500 = NT$460,000 | Middleware NT$220,000 + 5 connectors × NT$60,000 = NT$520,000 |
| Annual maintenance (3 years) | 20% × 3 = NT$276,000 | 12% × 3 = NT$187,000 |
| Troubleshooting (NT$1,500/hour) | 4 hours/month = NT$216,000 | 1 hour/month = NT$54,000 |
| 3-year total | NT$952,000 | NT$761,000 (about 20% lower) |
| Add a logistics system in year 3 | +3 flows = NT$1,132,000 | +1 connector = NT$821,000 (about 27% lower) |
Three Typical Scenarios Compared
Bottom line: the same tree gives different answers at different sizes.
- 8-person online shop: 2 systems, 2 data flows; official plugins or a CSV template, NT$0–30,000.
- 35-person food wholesaler: 5 systems, 8 data flows; middleware, real-time stock, batched accounting.
- 150-person manufacturer: already runs a large ERP; use the vendor's integration module first and outsource only the B2B ordering connector.
The Complete Hidden-Cost List
Bottom line: a quote shows only the build fee; the other half hides in these 5 items.
- Manual data moving: 600 records/month × 3 minutes = 30 hours. Even at Taiwan's 2026 minimum hourly wage of NT$196, that is about NT$70,000 a year.
- Field mapping and data cleanup: often quoted as a single "lump sum" line, yet it takes 30–40% of the hours.
- Keeping up with API versions: about 4–16 hours per flow per year.
- Vendor API module fees: some ERPs charge for an API license, about NT$20,000–60,000 a year.
- Silent outages: without alerts, breaks surface 3 days later; re-entry takes 1–2 person-days.
KPI Scorecard for a Vendor's Integration Capability
Bottom line: score 10 items from 1 to 5; under 30 usually means a rebuild within 3 years.
- Delivers a written data-flow list and field-mapping table
- Has automatic retry on failure
- Alerts within 15 minutes of a break
- Can trace every sync record by order number
- Contract states who maintains API version changes and at what cost
- Validates in a test (sandbox) environment first
- API keys use least privilege and are held by you
- Provides a manual re-sync tool
- Delivers an architecture diagram and connector documentation
- Agrees connector pricing for future systems in advance
ScriptWalker's Matching Options + When We Are Not a Fit
Bottom line: when there are too few flows, we will tell you not to build middleware.
ScriptWalker (a Taiwan-based Laravel/Flutter custom development studio) offers 4 models: project-based (building middleware, systems from NT$80,000), monthly retainer (monitoring and API version upkeep), advisory (inventory and architecture advice only) and full outsourcing. Not a fit when:
- You have only 2 systems and an official plugin already exists
- The other system has no API and its vendor will not open one
- The integration requires a certified consultant from a large ERP vendor
- You move fewer than 100 records a month
- You want us to modify the ERP vendor's core code as well
Transition Playbook: The First 90 Days of an Integration Project
Bottom line: settle master-data ownership first, then go live in batches.
- Month 1: inventory flows, set master data, pick the 2 most painful.
- Months 2–3: build middleware, run the first 2 flows alongside manual reconciliation for 2 weeks, then connect the rest.
- Day-90 review: failure rate below 0.5%, manual-hour reduction, alert-to-fix time.
Decision Checklist
Bottom line: tick 6 or more of 10 and middleware is worth evaluating.
- ☐ The company uses 4 or more systems that exchange data
- ☐ You need more than 6 data flows
- ☐ Manual data moving exceeds 10 hours a month
- ☐ You have oversold or mis-booked in the past year
- ☐ You may add new systems within 2 years
- ☐ The same product has different codes in different systems
- ☐ Nobody would know immediately if a sync broke
- ☐ Existing integrations were built piecemeal by different vendors
- ☐ There is no complete data-flow list
- ☐ You are willing to budget 12–20% of the build cost each year for maintenance
FAQ
How much does one integration cost?
About NT$30,000–60,000 one-way and NT$80,000–150,000 two-way, depending on field mapping and real-time needs.
Does every sync need to be real time?
No. Daily batches suit reporting and accounting; only stock and order status justify paying 1.5–2× for real time.
Can Zapier or n8n replace a middleware layer?
Yes, for up to 3 flows and a few hundred records a month; with field transformation and retries, middleware is more stable.
Is there an annual maintenance fee after integration?
Yes, typically 12–20% of the build cost, covering API version changes, expiring credentials and new fields.
Call to Action
Bottom line: draw your data flows and the answer becomes clear. Send us your system list and monthly record counts; a free 30-minute consultation will calculate the 3-year cost of both architectures and point out which flows need no integration at all.
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p