Integrating Shopify with GP: Which Approach Is Right for Your Team?
You’re going to work through these questions one way or another. Here’s the short version — from our experience of 20+ years of GP integrations.
What are my actual options for connecting Shopify to GP?
Three approaches come up in every evaluation.
- Managed Integration — i95Dev Connect
- Right for: B2B pricing complexity, Dexterity customizations in the instance, a lean IT team that didn’t sign up to own middleware, and a BC migration somewhere in the next few years.
- We configure it. We own both update surfaces — GP version changes and Shopify’s quarterly API cycle. When either side changes, we handle it. Not your team.
- Honest trade-off: configuration changes go through us, not directly into your code.
- Custom Development
- Right for: requirements so non-standard that nothing on the market handles them. For most GP+Shopify operations, that’s not the situation.
- Your team or agency builds the middleware from scratch. Nobody knows your GP instance better than the people who’ve been running it.
- Honest trade-off: every GP upgrade and Shopify API change becomes your team’s unscheduled work, indefinitely. When the developer who built it leaves, you inherit undocumented logic nobody wants to touch.
- iPaaS — Celigo, Boomi, APPSeCONNECT
- Right for: organizations with dedicated integration engineers who want direct, long-term configuration control.
- Platform infrastructure with pre-built GP templates. You or a partner configures and owns the GP-specific mapping logic.
- Honest trade-off: the platform is stable. Your configuration isn’t. Reconfigure when GP changes. Reconfigure when Shopify changes.
Does it matter that my ERP is specifically GP — or is the comparison the same for any ERP?
Yes — significantly. Every ERP has specific constraints that change which integration approach holds up: its data model, its customization layer, and how it handles change over time. GP’s version of this starts with pricing — the way GP structures customer-specific rates and tiers doesn’t map natively to how Shopify displays prices, and that’s before you get to the customization layer and the two independent update cycles both sides push. The right approach for GP accounts for all three. The next questions cover each one.
Which approaches account for GP customizations before go-live — and which find out after?
Most GP instances running for five or more years have been modified — custom fields, custom document types, modifications that touch the same areas the integration needs to read.
| Approach | When you find out about customization conflicts |
|---|---|
| Managed — i95Dev Connect | Before the integration is built — scoped and designed around upfront |
| Custom build | During build — delays and change orders |
| iPaaS | During implementation or after go-live — on your real order data |
Generic connectors map to standard GP. Against your actual instance, they hit things in unexpected places. The failure rarely shows up at go-live. It surfaces weeks later as orders that won’t reconcile or quantities slightly off but not obviously wrong.
The question that separates approaches: when do you find out if your specific customizations are a problem — before the integration is built, or after it’s live?
Which approaches absorb both update cycles — and which leave them with your team?
Shopify updates quarterly. GP updates annually. Two independent change events, on two different schedules, neither of which you control.
| Approach | Shopify API updates | GP version updates |
|---|---|---|
| Managed — i95Dev Connect | i95Dev handles it | i95Dev handles it |
| Custom build | Your team | Your team |
| iPaaS | Your team | Your team |
If your IT team is already stretched, owning one update cycle is manageable. Owning two indefinitely is the situation that creates the Friday where orders stop flowing and nobody’s sure which side of the integration broke first.
One more thing worth factoring in: GP’s support timeline
- GP mainstream support ends December 31, 2029
- If a Business Central migration is anywhere in your horizon, the right investment is one that carries forward to BC — not one that needs to be rebuilt when you get there
- i95Dev Connect supports both GP and BC on Shopify — you solve this once, not twice
If I go with each approach, what does my team actually end up owning?
Managed Integration — i95Dev Connect
- i95Dev owns both update surfaces
- Your team monitors the error queue
- Your team doesn’t debug middleware
Custom Build
- Two unscheduled maintenance events per year minimum — one for Shopify API changes, one for GP version updates
- Each requires someone who understands both your Shopify integration and your GP setup
- Your ops team finds out when orders stop flowing, not that maintenance was due
iPaaS
- The platform is stable. Your configuration isn’t.
- Reconfigure when GP changes. Reconfigure when Shopify changes.
- The vendor’s job ends at the platform. Your team’s job begins where the template does — and doesn’t end.
That shift doesn’t show up in a feature comparison. It shows up the first time a Shopify update lands and either someone on your team is working a weekend, or they’re not.
How long does this actually take to go live?
| Approach | Typical timeline | What to know |
|---|---|---|
| Managed — i95Dev Connect | Weeks | Significant Dexterity customizations add a scoping phase upfront — which prevents surprises that add months on the other side |
| iPaaS | 3–6 months | Customizations the template wasn’t built for surface during implementation, not before |
| Custom development | 6–18 months | Scope expands, timelines double |
The number worth tracking isn’t time-to-go-live. It’s time-to-stable: when the integration runs without someone actively managing it.
What should I be asking vendors that will actually reveal the difference?
These questions work for any vendor — including us. A vendor with genuine GP depth answers all five specifically. A vendor without it describes their product instead.
- “Walk me through how you map GP pricing to Shopify for a B2B customer.”
- Not “do you support customer pricing” — ask them to walk through it
- Which tables do they read from? How does the right price reach the right customer account in Shopify?
- If they describe the field mapping specifically, they know GP pricing
- If they offer a demo instead, they’re syncing the default price and calling it customer pricing
- “What’s your process when our GP instance has customizations?”
- The answer should include a step that happens before the integration is built — a scoping step, not an implementation surprise
- If the answer is “we handle it during implementation,” ask what happens to your go-live timeline when they find something unexpected mid-build
- “Which Shopify API version does your connector run on right now?”
- A vendor tracking Shopify’s update calendar answers without checking
- If they have to look it up, the Shopify-side maintenance is unmanaged
- “When something breaks after an update, who fixes it — specifically?”
- Not the SLA — the actual person
- Someone with your setup in front of them, or a general support queue that starts fresh each time?
- The specificity of the answer is the signal
- “If we eventually move from GP to Business Central, what happens to the integration?”
- A vendor who can only answer this for GP means two integration projects instead of one
- What you want to hear: their BC connector exists, they’ve migrated GP+Shopify integrations to BC+Shopify before, and your configuration carries forward — not rebuilt from scratch
- i95Dev Connect supports both. Ask us directly.
Given all of this — what’s the right call for my specific setup?
It depends on specifics no comparison guide can answer for you: your GP version, how your B2B pricing is structured, how extensively your instance has been customized, your team’s bandwidth, and where a BC migration sits in your timeline.
Four questions about your GP version, Dexterity customizations, B2B pricing, and migration timeline. We come back to you with a specific recommendation, not a generic one.
Talk to someone about your GP setup ? 30 minutes. Specific to your configuration.