Does Ceven need Shopify Plus, or do I install on basic Shopify?

Any Shopify tier, Basic, Shopify, Advanced, or Plus, supports the Ceven integration. The Admin API surface Ceven uses is identical across tiers. The only Plus-only feature is the multi-store organization view; on lower tiers, you connect each store separately. There's no add-on app fee from Shopify for installing Ceven, and the integration uses the standard public-app OAuth flow rather than custom-app credentials, so you don't need a Shopify Partners account or any developer setup.

Can Ceven manage multiple Shopify stores from one workspace?

Yes. Each Shopify store connects independently, when you click Connect on the Shopify card a second time, Ceven prompts for the second store's domain and runs a fresh OAuth flow. Both connections live side by side in your workspace and workflows can reference either by store name. The cleanest pattern is one Ceven workspace per business with all your stores connected, so the agent can answer cross-store questions like 'which products are out of stock on either site this morning'. For brands running more than 5 stores, talk to support about the multi-store dashboard.

How does Ceven handle Shopify Functions and other installed apps?

Ceven reads the state apps write, discount codes minted by a loyalty app, custom fields written by a subscription app, fulfillment statuses set by a 3PL app, but Ceven doesn't directly call other apps' endpoints. If a workflow needs an action that's only available through another app's API, connect that app to Ceven separately (most major ones have their own toolkit). Shopify Functions you've custom-deployed run server-side and Ceven sees their results in the order/checkout data, not their source code.

What's the latency on Shopify webhook events?

Shopify's webhook delivery is usually under 2 seconds from the in-store event to Ceven's intake, and Ceven processes most events into the agent workflow within an additional 1-3 seconds. There's no guaranteed SLA, Shopify themselves only commit to 'eventual', and during their peak load windows (BFCM, big drops) latency can stretch to 30+ seconds. Workflows that absolutely need real-time should poll instead of relying on webhooks, but for the 99% of ops use cases, order routing, inventory alerts, fraud review, webhooks are the right primitive.

Does Ceven respect Shopify's API rate limits per-workspace or per-store?

Per-store. Shopify rate limits are scoped to each store's API client, so connecting multiple Ceven workspaces to the same store will compete for the same rate-limit budget. Within a single workspace, Ceven's token-bucket scheduler ensures no single workflow exhausts the limit before others get a fair share. If you see 'Shopify throttled' errors during a heavy migration or bulk update, batch the workflow with explicit pagination, Ceven will not auto-batch a single prompt that asks for unbounded volume.

Can Ceven access historical orders, or only those after I connect?

Both. After connect, Ceven backfills the last 60 days of orders, customers, and inventory snapshots into the workflow context so your first prompts work against real data. Webhook subscriptions for future events fire immediately on connect. If you need a longer backfill for a one-time analysis, run a paginated list-orders workflow with the date range you need, Shopify's pagination handles up to 250 records per page and Ceven walks the cursor for you. For very large stores (1M+ orders), expect a multi-minute backfill and a progress indicator in the integration's status page.

Shopify

Brings live order, customer, and inventory data into the agent layer so support replies with full context, ops catches low stock early, and finance reconciles payouts without copying CSVs.

Get started for free

Try Shopify in Ceven

Ask Ceven anything

Standard

What Ceven does with Shopify

Order intake → Slack + help desk routing with full customer context
Inventory-level alerts cross-checked against active campaigns
Refund drafting with fulfillment + shipment history pre-attached
Vendor price-change → product price update with margin check
Payout reconciliation against bank deposits in QBO or NetSuite
Returns + RMA workflows wired to the warehouse system

Why use Ceven?

One connection, every action
Connect Shopify once and Ceven's agents can run all of its tools. No setup per task and no scripts to maintain.
No glue code, no RPA
Describe the outcome in plain English. Ceven picks the right Shopify calls, fills the params, and handles the result.
Works on your existing stack
Shopify sits next to the rest of your tools, so work flows across all of them in one chat instead of five tabs.
Managed auth, you just build
Ceven handles OAuth, tokens, scopes, and refresh. Your team never copies an API key or babysits a token.

Supported tools

Every action Ceven's agents can run on Shopify, with when to use it. Items tagged "event" are webhooks Ceven listens for; the rest the agent calls on demand.

read

List orders

Pull recent orders with filter by status, channel, or fulfillment state. Drives daily ops standups and the support agent's 'recent activity' lookups.

read

Get order

Fetch one order with line items, shipping address, customer history, and current fulfillment + refund state. Always the first call in a support-side workflow.

write

Update order

Edit an order's notes, tags, or custom attributes. Used to mark orders as 'fraud review', 'VIP', or 'replacement shipment' from agent-driven flags.

write

Refund order

Issue a full or partial refund against an order's line items, optionally restocking inventory. Common path: customer complaint resolution after the support agent gathered evidence.

read

List products

Pull products with variant, inventory, and pricing data. Used by the merchandising agent to find SKUs matching a vendor price-change email or to spot-check site-wide pricing.

write

Update product

Change a product's price, inventory commitment, or descriptive copy. Most-used write action, vendor cost changes, promo activation, copy updates from marketing.

write

Create product

Add a new product with variants and inventory levels, typically wired into a PIM or vendor-onboarding flow.

write

Update inventory level

Adjust on-hand quantity at a specific location. Used by warehouse-cycle-count workflows and the manual-fix flow when a vendor ships short.

List customers

Search customers by email, total spend, last order date, or tag. Drives VIP tagging, win-back batches, and the 'why did this customer email us' lookup.

read

Get customer

Pull one customer's order history, lifetime value, addresses on file, and tags. Always loaded into the support agent's context before drafting any reply.

write

Create fulfillment

Mark line items as fulfilled with a tracking number and carrier. Wires the warehouse-management system's shipping confirmation into Shopify so the customer gets the shipped email.

read

List discounts

Pull active and scheduled discount codes with usage limits and current redemption counts. Used to spot-check promo health mid-campaign.

write

Create discount code

Mint a single-use or limited-redemption discount, typically in service of a goodwill credit or a support resolution.

read

List abandoned checkouts

Pull checkouts that didn't complete in the last 24-72 hours with the customer's email and cart. Feeds the recovery-email workflow.

event

Webhook: orders/create

Fires on every new order. Routes into the ops Slack channel for >$1,000 orders and into the fraud-review queue when address and IP geo disagree.

event

Webhook: inventory_levels/update

Fires when stock crosses a threshold. Triggers a campaign-pause workflow if the SKU has an active ad and inventory drops below the 7-day burn rate.

16 actions · scroll to see them all

Workflows that pair Shopify with your other tools

Shopify × ShipStation

How: Warehouse manager sees ShipStation tracking numbers auto-write back to Shopify the moment a label prints, killing the 6 PM 'is this shipped yet' email.

Shopify × QuickBooks Online

How: Bookkeeper for an 8-figure brand pulls Shopify payouts into QBO with per-order splits, taxes, shipping, refunds, and platform fees on separate lines.

Shopify × Klaviyo

How: Marketing ops auto-tags Shopify customers as 'VIP' after the second $500+ order and Klaviyo's win-back flow picks them up the next morning.

Shopify × Slack

How: Ops manager gets a Slack DM on every order over $1,000 with the customer's prior order count, shipping address, and fraud-score.

Connecting Shopify

1
Open Integrations in your Ceven dashboard
From the chat surface, click Settings → Integrations. Find Shopify in the Industry Systems category.
2
Click Connect on the Shopify card
Ceven asks for your myshopify store domain (the *.myshopify.com URL, even if you have a custom domain). Enter it and click Continue.
3
Approve Ceven in your Shopify admin
Shopify opens its admin consent screen. The scopes Ceven requests are read+write on orders, products, customers, inventory, fulfillment, discounts, and read-only on payouts. Click Install app.
4
Return to Ceven
Shopify redirects back to Ceven. The Shopify card on Integrations flips to 'Connected', showing the store name and the current API version pinned.
5
Run a sample prompt
Open /app and try a Shopify prompt, for example, 'pull the 5 most recent orders'. If you see live data, you're done.

Open the Integrations dashboard ›

Limitations and gotchas

Shopify behavior worth knowing before you write a workflow against it.

Shopify's REST and GraphQL APIs have different rate limits

Shopify Admin's REST endpoint uses a leaky-bucket limit (40 req/burst, 2/sec sustained), while GraphQL Admin uses a cost-based limit (1000 cost points/sec, where a complex query can cost 50-200). Ceven prefers GraphQL for read-heavy flows (product lists, customer search) because it batches better, and REST for write-heavy flows (order updates, refunds) because the cost accounting is simpler. If a workflow hits 'Throttled', the agent falls back to GraphQL with cursor pagination, but a one-shot prompt that asks for 'every product' on a 50k-SKU store will be slow regardless, paginate explicitly.

Inventory levels are per-location, and 'on hand' is not 'available'

Each product variant has inventory per location (warehouse, store, drop-shipper), and Shopify tracks both on_hand and available (on_hand minus committed-to-orders). Agents that adjust inventory should always update on_hand, available is computed. The common bug: workflow pulls available to make a stock decision, but the customer-facing storefront also pulls available, so a sudden adjustment can backfire mid-checkout. Use on_hand as the source of truth in any cross-location ops flow.

Never worry about agent reliability

Ceven runs Shopify like a careful operator, not a black box. Every run is visible, gated where it counts, and built to stop rather than guess.

Every action is logged

See exactly what the agent did in Shopify, when, and why. The trail is built for sign off, not guesswork.

It pauses, it never guesses

If Shopify is unreachable or a step is unclear, the agent stops and asks instead of plowing ahead and making a mess.

Approvals where they matter

Gate any write behind a human OK. Nothing irreversible happens in Shopify without someone saying yes first.

Least privilege by default

Ceven asks Shopify for read scopes first and only the writes a workflow needs. Revoke the whole grant any time.

Frequently asked questions

Does Ceven need Shopify Plus, or do I install on basic Shopify?: Any Shopify tier, Basic, Shopify, Advanced, or Plus, supports the Ceven integration. The Admin API surface Ceven uses is identical across tiers. The only Plus-only feature is the multi-store organization view; on lower tiers, you connect each store separately. There's no add-on app fee from Shopify for installing Ceven, and the integration uses the standard public-app OAuth flow rather than custom-app credentials, so you don't need a Shopify Partners account or any developer setup.
Can Ceven manage multiple Shopify stores from one workspace?: Yes. Each Shopify store connects independently, when you click Connect on the Shopify card a second time, Ceven prompts for the second store's domain and runs a fresh OAuth flow. Both connections live side by side in your workspace and workflows can reference either by store name. The cleanest pattern is one Ceven workspace per business with all your stores connected, so the agent can answer cross-store questions like 'which products are out of stock on either site this morning'. For brands running more than 5 stores, talk to support about the multi-store dashboard.
How does Ceven handle Shopify Functions and other installed apps?: Ceven reads the state apps write, discount codes minted by a loyalty app, custom fields written by a subscription app, fulfillment statuses set by a 3PL app, but Ceven doesn't directly call other apps' endpoints. If a workflow needs an action that's only available through another app's API, connect that app to Ceven separately (most major ones have their own toolkit). Shopify Functions you've custom-deployed run server-side and Ceven sees their results in the order/checkout data, not their source code.
What's the latency on Shopify webhook events?: Shopify's webhook delivery is usually under 2 seconds from the in-store event to Ceven's intake, and Ceven processes most events into the agent workflow within an additional 1-3 seconds. There's no guaranteed SLA, Shopify themselves only commit to 'eventual', and during their peak load windows (BFCM, big drops) latency can stretch to 30+ seconds. Workflows that absolutely need real-time should poll instead of relying on webhooks, but for the 99% of ops use cases, order routing, inventory alerts, fraud review, webhooks are the right primitive.
Does Ceven respect Shopify's API rate limits per-workspace or per-store?: Per-store. Shopify rate limits are scoped to each store's API client, so connecting multiple Ceven workspaces to the same store will compete for the same rate-limit budget. Within a single workspace, Ceven's token-bucket scheduler ensures no single workflow exhausts the limit before others get a fair share. If you see 'Shopify throttled' errors during a heavy migration or bulk update, batch the workflow with explicit pagination, Ceven will not auto-batch a single prompt that asks for unbounded volume.
Can Ceven access historical orders, or only those after I connect?: Both. After connect, Ceven backfills the last 60 days of orders, customers, and inventory snapshots into the workflow context so your first prompts work against real data. Webhook subscriptions for future events fire immediately on connect. If you need a longer backfill for a one-time analysis, run a paginated list-orders workflow with the date range you need, Shopify's pagination handles up to 250 records per page and Ceven walks the cursor for you. For very large stores (1M+ orders), expect a multi-minute backfill and a progress indicator in the integration's status page.

When Shopify is not the right fit

Shopify is the wrong primary system for B2B operators who run net-60 invoicing, custom-contract pricing, or quote-to-order flows with multiple approvers, Shopify Plus's B2B tools work but it's catching up rather than leading, and a NetSuite or Sage Intacct setup usually wins for those shapes. For pure DTC, marketplace, and most omnichannel retail, Shopify is the default.

More Industry Systems integrations

Alternatives to Shopify

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

bigcommercewoocommercemagento

Setting up Shopify? Email support@ceven.io with your tenant ID, or security@ceven.io for security questions.

Try Ceven on your stack

Start for free