Skip to content
Storage ⇄ CRM

Box to Shopify integration — real-time, two-way sync

Keep Box and Shopify in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Box and Shopify

Keep the paperwork with the relationship: Shopify and Box share every customer's records and files in real time, in both directions.

Shopify holds the customer relationship as structured records; Box holds the files that belong to those relationships, from contracts and proposals to signed agreements and statements of work. The two are linked in practice and disconnected in software: someone downloads a document, renames it, and uploads it to the right folder, or exports records out to storage for retention. Done by hand, files drift away from the records they belong to and copies fall out of date.

Stacksync keeps ProductMedias, ProductVariants, Orders, Customers in Shopify aligned with Collaborations, Users, Groups, Tasks in Box, in real time. A new account or deal can open its own folder in Box; a document filed in Box can surface as a link and metadata on the matching record in Shopify; and records from Shopify can be written into Box as files or objects for backup, archival, and compliance. You choose which side owns what, and Stacksync keeps the two consistent as either one changes.

Common use cases

  • 01 Write inventory levels from a WMS or ERP into Shopify locations to keep availability accurate.
  • 02 Mirror the product catalog from a PIM or database into Shopify products, variants, and metafields.
  • 03 Stream enterprise Events (admin events) into a warehouse for audit, DLP, and access-review reporting.
  • 04 Two-way sync of Files and Folders between Box and an operational database so applications track document status without calling the Box API directly.

Common sync patterns

One place for a customer's files

Attachments that accumulate against a record in Shopify collect in that customer's folder in Box, so the full document history lives in one place and is reachable by anyone who needs it.

A folder per account or deal

When an account or deal is created in Shopify, a matching folder or container opens in Box, named and organized the same way, so files have a home the moment they are needed.

Documents linked back to the record

A contract, proposal, or signed agreement filed in Box surfaces as a link on the matching record in Shopify, so the customer's paperwork sits with the relationship instead of a shared drive.

What you can sync between Box and Shopify

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Box objects Shopify objects How this pairing syncs
Files Core content object with versions, name, size, and metadata; synced two-way so files and their attributes move between Box and a database or another store. ProductVariants Synced with incremental and full sync per the Stacksync docs. Files is specific to Box and ProductVariants to Shopify — each maps to any object or custom field on the other side.
Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. Folders is specific to Box and Orders to Shopify — each maps to any object or custom field on the other side.
Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. Metadata is specific to Box and Customers to Shopify — each maps to any object or custom field on the other side.
Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. Collaborations is specific to Box and Abandoned Checkouts to Shopify — each maps to any object or custom field on the other side.
Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Products Catalog entries; often mastered in a PIM or ERP and written into Shopify. Users is specific to Box and Products to Shopify — each maps to any object or custom field on the other side.
Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. ProductMedias Synced with incremental and full sync per the Stacksync docs. Groups is specific to Box and ProductMedias to Shopify — each maps to any object or custom field on the other side.

How changes propagate between Box and Shopify

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Box Shopify Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

DeliveryEach detected change is written to Shopify through its API, with automatic retries and rate-limit backoff.

Shopify Box Sub-second propagation

DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.

DeliveryEach detected change is written to Box through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Box ⇄ Shopify

Connect Box and Shopify for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Box–Shopify connection.

Real-time

Two-way sync

Changes in Box or Shopify instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Box or Shopify data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Box or Shopify record.

Observability

Monitoring

Track your Box ⇄ Shopify sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Box and Shopify.

How the Box and Shopify connectors work

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.

Shopify

Integration surface
GraphQL Admin API (primary) and REST Admin API (legacy)
Authentication
OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

How to connect Box to Shopify — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Box and Shopify with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Box connected
    Shopify connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Box and Shopify objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Box ⇄ Shopify
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Box Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Box and Shopify integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 523 integrations available for Box and Shopify.

Popular · 6 of 523
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.