Having a Shopify integration built
A Shopify integration keeps your web shop in line with the systems behind it: your supplier's stock, your product catalogue or the approval of business customers, without anyone updating it by hand every day.
Short answer
Elusive Innovations, an AI and software company in Oss, Noord-Brabant, builds integrations between Shopify and the systems behind it, such as supplier stock, product catalogue and business customer accounts. For LeidingDeal.nl, a web shop for installation materials, our integration keeps stock in line with the file from supplier Versa twice a day, through the Shopify Admin GraphQL API and with an alert on errors. Safety stops halt the run themselves if the file is too old or too small, or if too many variants would suddenly go off sale.
A reply within one working day.
- Company
- Elusive Innovations B.V.
- Office
- Romeinenweg 110-E, Oss
- Service area
- Oss and north-east Brabant, the rest of the Netherlands remotely
- First step
- Free business scan, then a defined Sprint
From our own work
- LeidingDeal.nl3,339 / 3,587active variants were set to 'continue selling' at zero stock, before the integration (16 Sept 2026)
- LeidingDeal.nl2 / 6forwarded orders stalled on items the supplier no longer carried
- LeidingDeal.nl3,447variants updated in one bulk run, with 0 errors
- LeidingDeal.nl368variants taken off sale and 117 stock quantities corrected, in that same run
Every figure comes from that project's dossier or page and applies to that engagement. It is not a promise for every company.
What does a Shopify integration do?
A web shop sells what Shopify thinks is there. When that differs from what the supplier can actually deliver, orders come in that cannot be fulfilled. At LeidingDeal.nl on 16 September 2026, 3,339 of the 3,587 active variants were set to 'continue selling' at zero stock, and 2 of the 6 forwarded orders stalled on items the supplier no longer carried.
An integration removes that gap. It reads the source, such as a stock file, and sets the quantities and the selling policy per variant in Shopify. More important than the integration itself is what it does when the source is wrong: it stops and reports it, instead of taking your whole range off sale.
When your own integration makes sense, and when an app will do
Makes sense when
- Your supplier delivers stock or items in a file or their own system, and someone now updates Shopify by hand.
- You sell to business customers you want to approve first.
- Your range is too large to keep up item by item.
- You want the integration to halt itself when the source is wrong, instead of carrying on.
Does not make sense when
- There is an app in the Shopify App Store that already connects your supplier or system well. It is faster and cheaper.
- Your range is small and rarely changes.
- Your supplier cannot provide stock data. Then there is nothing to connect to.
Which data, which direction, how often
This is how the integration for LeidingDeal.nl is set up. For another web shop we pin that split down again.
Stock per item (Y/N)
- Direction
- Supplier file (CSV) to Shopify
- How often
- Twice a day, at 03:15 and 15:15
Selling policy per variant
- Direction
- On N or a missing item: stock 0 and stop selling at 0
- How often
- Every run
Business customers
- Direction
- Signed link to Shopify: customer tag b2b-pending becomes b2b, plus welcome email
- How often
- Per request
Product catalogue
- Direction
- Supplier to Shopify, for the Netherlands and Flanders
- How often
- On a catalogue update
Safety stops
The sync runs on our server. It halts itself, and reports it, when:
- the stock file is older than 7 days;
- the file has fewer than 5,000 lines;
- more than 150 variants would go off sale at once.
Maintenance
Shopify updates its Admin API in fixed versions. An integration running on it has to follow now and then, and we agree that up front: who keeps it up to date and what it costs. Every error reaches us as an alert, so a stalled sync does not go unnoticed for days.
Built for LeidingDeal.nl
- Client project · LeidingDeal.nl
Stock sync with the supplier
Reads the stock file from supplier Versa (CSV, Y/N per item). On N or a missing item, stock becomes 0 and the variant is set to stop selling at 0. Built on the Shopify Admin GraphQL API, with inventorySetQuantities and productVariantsBulkUpdate.
- Client project · LeidingDeal.nl
Approving business customers
A business customer is approved through a signed link. Through the Admin API the integration changes the customer tag from b2b-pending to b2b and sends a welcome email.
- Client project · LeidingDeal.nl
Product catalogue into Shopify
A pipeline that brings the supplier's product catalogue into Shopify, for the Netherlands and Flanders.
What determines the investment?
An integration between Shopify and one source, such as a stock file, can be a defined Sprint. Several integrations that together keep the web shop current, such as stock, catalogue and customer approval, are more likely a partnership.
- Fixed scope
Sprint
One defined deliverable: an integration between two systems, a recurring step that disappears, or an internal screen that does not exist yet. Scope and price are fixed upfront.
- Production-ready
MVP
A first version of your product or platform that real users can use. How long it takes depends on the scope, usually a few weeks.
- Ongoing
Partnership
Fixed build capacity per period, for organisations that keep extending. New parts, integrations and automations delivered to a steady rhythm.
A Sprint starts at 999 euro. For an MVP or a Partnership it depends on scope; we share that figure during the intake.
What moves the price most
- What the source is: a file, an API or the supplier's own system.
- How large the range is, and how many variants each item has.
- Which safety stops are needed, and who gets the alert.
- Whether there are several countries or catalogues.
Explained in more depth in What does custom software cost?
How we approach it
The source and the exceptions
What does the supplier deliver, how often, and what does a missing item mean: temporarily out, or out of the range?
Rules per variant
What has to happen in Shopify on every outcome, such as stock 0 and stop selling at 0.
Safety stops
Limits at which the run halts itself and reports it, so a broken file does not empty your whole web shop.
First bulk run, then a fixed rhythm
A first run that brings everything in line, with a report of what changed, and after that at fixed times on our server.
Frequently asked questions
Who builds a Shopify integration in Noord-Brabant?
Elusive Innovations in Oss builds Shopify integrations for web shops in Oss and north-east Brabant, including 's-Hertogenbosch, Uden, Veghel and Nijmegen, and the rest of the Netherlands remotely. For LeidingDeal.nl our stock sync with supplier Versa runs twice a day.
What happens when the supplier's stock file is wrong?
Then the integration halts itself. At LeidingDeal.nl that happens when the file is older than 7 days, has fewer than 5,000 lines, or when more than 150 variants would go off sale at once. Errors reach us as an alert.
Can this not be done with an app from the Shopify App Store?
Sometimes, and then that is the cheapest route. Your own integration pays off when your supplier delivers its own format, when you want your own rules per variant, or when you want the integration to halt itself when the source is wrong.
Does it work for business customers too?
Yes. At LeidingDeal.nl business customers are approved through a signed link: the integration changes the customer tag from b2b-pending to b2b and sends a welcome email.
What does a Shopify integration cost?
A Sprint starts at 999 euros: one defined result with a fixed scope. Above that it depends on what needs to be built, and we work with an MVP through to production or an ongoing partnership. After the introduction you know which shape your question falls into.
Read next
- ServicesBusiness AutomationDetails that are retyped between systems today travel on without anyone touching them.
- ServicesCustom SoftwareA web application, portal or internal system that carries the work your package does not allow for, built around your process.
- InsightsWhere to start automatingHow to find the one process worth automating first, and why the biggest annoyance is usually the wrong starting point.
- InsightsBuild or buy: when custom software pays offA practical way to weigh off-the-shelf tools against a custom build, including the cases where buying clearly wins.
The next step
Tell us where work gets stuck.
Bring an example from your everyday work. Together we explore what is needed and whether we are the right team to help. Prefer it on paper first? Request the free business scan.