# Shopify OMS, PIM and ESP integrations, with an owner for every connection.

> For operations and engineering leads, we connect Shopify to order management, product information, email, reviews, loyalty and subscription platforms. Each integration has a named owner, a written data map and failure handling, so a failed sync is caught and retried. Work starts with a three-week Architecture Review of every system Shopify talks to.

Custom apps and integrations · OMS, PIM and ESP integrations

- **Starts with:** A three-week Architecture Review
- **Typical build:** Phased by system, each priced before it starts
- **You own:** The connectors, the data map and the runbooks

## When does an integration need more than a connector?
- Stock, prices or product data disagree between Shopify and the system behind it.
- Orders reach the order management system late, duplicated or not at all.
- Product content is edited in a PIM, then again by hand in Shopify.
- Email flows miss events because customer and order data arrive incomplete.
- Each connector belongs to a different vendor, and nobody owns the whole flow.

## How does an integration project run?
1. **Map the systems** — Every system and flow, and the source of truth for each field.
2. **Choose connector or custom** — Use a supported connector where it fits; build where it falls short.
3. **Design for failure** — Retries, duplicate protection, alerts and a reconciliation job for every flow.
4. **Build and rehearse** — Typed services and webhooks, tested against copies of real data before launch.
5. **Hand over the runbook** — Monitoring, alerts and a runbook naming who fixes what when something fails.

## Every connection mapped, monitored and owned
- A system map with the source of truth per field
- A connector-or-custom decision for each integration
- Integration code in your repository, with tests
- Retries, duplicate protection and reconciliation jobs
- Monitoring and alerts routed to a named owner
- A runbook for each integration your team can follow

## What usually goes wrong
- **Letting systems fight over the same field** — Name a source of truth for every field.
- **Trusting webhooks to arrive every time** — Webhooks can be missed; reconcile on a schedule too.
- **Syncing without duplicate protection** — Retries create duplicates unless every write is safe to repeat.
- **Leaving failures for customers to report** — Alerts should reach a named owner, not a shared inbox.

## Questions
### Should we use an off-the-shelf connector or build a custom integration?

Use the connector if it handles your data and failure cases. Many do. Build custom when the connector cannot model your rules, hides failures, or forces manual fixes. Often the answer is a connector plus a small service you own for the parts it misses.

### Who owns each integration after launch?

You do, with a name against each connection. The runbook says who is alerted, who fixes what and which vendor to call. Your team can run it, or the Care tier of our Engineering Partnership can take on upkeep, API versions and fixes.

### How are integration failures caught and fixed?

Every flow retries on failure, ignores duplicates, and alerts a named owner when retries run out. A scheduled reconciliation job compares Shopify with the other system and flags drift, because webhooks alone can be missed. Logs show what failed, when and why.

### Which systems do you integrate with Shopify?

Order management, product information, email, reviews, loyalty and subscription platforms, connected through their APIs and Shopify’s Admin API and webhooks. If a platform has a usable API, we can integrate it; the Architecture Review checks how well. ERP integration has its own page.

### Where does integration code run?

In a small service you own, hosted in your accounts, for example on Cloudflare Workers. It listens to Shopify webhooks and calls the other system’s API. Where Shopify Flow or a native connector can do the job, we use that instead and write less code.

[Book an Architecture Review](https://www.studioantipodes.com/start-a-project)