Shopify Connector

Illustration · sample data

Sync example

Review one record

Source

Shopify

Connector status: In progress

→

Destination

Your other tool

Connector status: Custom tool

Field mapping

Source field	Destination field	Sample value
record.id	source_id	record_1042
record.updated_at	updated_at	2026-10-18T08:00:00Z
record.value	value	sample_value

1. Draft
2. Review one record
3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

Tajo’s Shopify connector is in progress. The code exists, but it has not yet passed a run against a live Shopify store.

The Tajo app is not listed in the Shopify App Store, so there is no self-serve install today.

What the code does

• Reads customers, orders and products, with variants, images and inventory, through the Shopify Admin API.
• Searches customers with Shopify’s query syntax.
• Starts and checks bulk exports of customers, orders or products.
• Reads a variant’s inventory across locations and applies a stock adjustment at one location.
• Writes to a customer: adds or replaces tags and sets metafields.
• Receives Shopify webhooks for customers, orders and refunds, checks Shopify’s HMAC signature, and records them as events.

Not available today

• Abandoned-cart recovery and browse tracking. Code exists for checkout events and for a storefront pixel, but none of it has been verified on a store.
• Real-time customer sync to Brevo contacts

Open-Source Implementation Map

No official open-source repository was found in the current Tajo connector catalog for Shopify. Keep this page focused on the verified public API contract and vendor documentation until an official schema, SDK, MCP server, or public integration repository is available.

Tajo Revamp Checklist

• Verify authentication and scope requirements against the vendor documentation before each connector release.
• Document primary sync objects, external IDs, pagination strategy, and rate limits explicitly.
• Add smoke tests from public API examples rather than undocumented behavior.
• Capture webhook signature verification and replay protection when the vendor supports webhooks.
• Record gaps where no official public repository or schema exists so future maintainers know what still needs source-backed validation.