Connect Shopify to the systems you already run.
Fyntri builds Shopify integrations for UK merchants when an App Store connector is wrong for the data shape, or when stock, orders and fulfilment have to stay honest across systems. Work is Custom with a written estimate. We agree the outcome, quote the named scope, then you approve before work starts.
- Written estimate first
- Fail loudly, not silently
- You own the code where we build it
App, middleware, or leave it alone?
We recommend the cheaper option that works. Custom is not the default flex.
App Store first
Use an App Store app when
- Official connector covers itYour fields and volume fit what the app already supports.
- Simple sync is enoughOne-way or basic two-way sync without hard reconciliation.
- You accept their billingPer-order fees and their support model are fine for you.
Custom · written estimate
Build Custom when
- Bespoke data shapeCustom line properties, multi-location stock, or ERP fields no connector maps.
- Bi-directional with reconciliationOrders, stock or money can drift and need a written truth rule.
- No trustworthy connectorNothing maintained that fits, or the risk is too high.
- You need ownershipCode in your GitHub or Partner account, not locked to a vendor app.
Systems we scope against.
No “we integrate with everything” claim. If it has a documented API or a stable file drop, we can scope it.
| System type | Typical flows | Notes |
|---|---|---|
| ERP / back office | Orders out, stock and SKUs in | NetSuite, Brightpearl-class, and bespoke APIs |
| 3PL / WMS | Fulfilment, tracking, inventory | Webhooks and Admin API, with exception handling |
| Accounting | Orders and refunds to ledgers | Prefer App Store first (Xero/QBO-class) |
| CRM / email | Customers and events | Prefer App Store first (Klaviyo-class) |
| Supplier / catalogue | Products, price, stock | See the supplier feeds page |
| Custom / legacy | Flat file, SFTP, niche API | Scoped after reviewing your systems |
How Custom work is sold.
We agree what you need, put the price and scope in writing, and start after you approve.
-
01
Agree the outcome
We write what “done” means for the named scope before any work is booked.
-
02
Written estimate
A written quote for that scope.
-
03
Approve and book
You approve the estimate. The work happens inside that written scope.
-
04
Change orders in writing
Anything new gets a written change order before work starts.
What “done” has to include.
Integrations fail quietly unless these are in the scope.
- Idempotent jobsDuplicate webhooks must not double orders or stock moves.
- Retries and alertingBreaks should surface without us telling you first.
- Reconciliation where it mattersA report when stock or money can drift between systems.
- API version awarenessUses an agreed Shopify API version, with maintenance requirements explained at handover.
What you provide.
Access and a rough field map beat a vague wish list. The estimate is only as good as this.
- Shopify accessA collaborator or staff account on the store.
- Target system pathAPI docs, sandbox, or a credentials path we can use safely.
- Field map draftWhat must match on both sides, even if rough.
- Volume and peakNormal load and Black Friday-class expectations.
- Ops ownershipWho gets alerted and acts when something fails after handover.
Shopify integrations, answered.
Cost, ERP and 3PL fit, middleware vs custom, performance, ownership and Standard exclusions.
How much does a Shopify integration cost?
Integrations are Custom with a written estimate after we know the systems and flows. A short discovery is common before larger builds.
Can you integrate Shopify with our ERP or 3PL?
Usually yes if it has a documented API or a stable file export. We confirm feasibility in discovery before you approve the quote.
Should we build a custom app or use middleware?
Middleware is often faster to stand up and easier to change. A custom app gives tighter control and can avoid per-order fees. We size both against volume and tell you which pays back sooner.
Will a custom integration slow the storefront?
It should not. Shopper-facing work gets a performance budget. Back-office sync runs server-side.
What happens if the sync breaks?
Error handling and alerting are part of the build. You should be able to see a failure without waiting for a customer complaint.
Who owns what you build?
You do. Where we write code, it lives in your repo or your Partner app install unless the written scope says otherwise.
Is this included in the £5,000 Standard setup?
No. ERP, warehouse and 3PL integrations sit outside Standard. They are Custom with a written estimate.
Do you only work with Shopify Plus?
No. Plus, Markets and B2B patterns are Custom when needed. Standard store plans can still need solid integrations.
Let’s make
your next move
a good one.
A new store. A fresh start.
A Shopify problem worth solving.