Using Raspberry with BigCommerce
Raspberry AI connects directly to your BigCommerce storefront so approved imagery reaches your product pages the moment it is ready. Search your catalog from inside Raspberry, select a product, and attach generated images as product images — one at a time or an entire batch in a single submit.
E-commerce Platform Hosted storefront and product catalog platform
BigCommerce is a hosted e-commerce platform brands use to run their online storefront — product catalog, variants, inventory, media, and checkout. If your organization runs on BigCommerce, the integration lets you push newly generated imagery from Raspberry AI directly onto the right product without leaving Raspberry.
Think of it as a one-way bridge from Raspberry into your storefront. Instead of exporting a design, opening the BigCommerce control panel, finding the product, and uploading images one at a time, you pick the product from inside Raspberry and one click attaches the image as a product image.
Export from Raspberry directly onto a BigCommerce product's image list. No download, no control-panel navigation, no re-upload — the image is attached where shoppers will see it.
Select multiple images anywhere multi-select is supported and every one uploads in a single submit. Batch Apply and Batch Recolor in the Editor carry their full output through automatically, so a whole colorway run reaches the product in one action.
The export modal opens on a live product picker that streams your catalog and filters by title as you type, so finding the right product takes seconds even in a large catalog.
The Export To menu appears in the Create Module, the Library, on Board nodes, and throughout the Editor — including the generation footer, layer menu, Batch Apply, and Batch Recolor.
Images are sent at full quality.
BigCommerce returns per-file results, so the confirmation tells you exactly how many images landed and how many did not — no guessing after a large upload.
An admin connects the store once and every member of the organization can export to it. There is no per-user setup and no credentials for individual designers to manage.
Team
How they use the integration
Design
Push approved product imagery onto live products without a handoff step
E-commerce
Keep product pages current with the latest visuals as soon as they are generated
Merchandising
Refresh seasonal and promotional imagery across the catalog in bulk
Cross-functional
Work from one connection so creative output reaches the storefront without a queue





















.png)
.png)
.png)




























.png)
.png)
.png)

























BigCommerce is a premium integration gated by Raspberry's connector-token system. Enabling it costs 1 connector token from your organization's quota.
BigCommerce uses OAuth 2.0 via the Single-Click App flow. Raspberry starts the flow from its own settings modal — you enter your store hash, sign in on BigCommerce, and approve the scopes.
Go to Organization Settings → Integrations.
Find BigCommerce and click Enable.
Enter your store hash. Anything Raspberry can normalize to a bare hash works: abc123xyz, stores/abc123xyz, or with a trailing slash. Find it in your BigCommerce control panel URL — the {hash} in store-{hash}.mybigcommerce.com — or under Settings → API accounts
A BigCommerce login window opens — sign in as the store owner or an admin account
Approve the scopes Raspberry requests: Products (modify) and Store information (read)
A BigCommerce login window opens — sign in as the store owner or an admin account
Note: Connecting is an admin action, and the admin needs BigCommerce's Manage apps permission. Once an admin connects the organization's store, all members of the org can export to it.
One store per organization. Every export goes through the store the admin installed the app on. If you run multiple storefronts — for example US and EU — you will need to choose which one this Raspberry org is bound to. Multi-store support is not currently available.
To disconnect, return to Organization Settings and click Disconnect. This removes Raspberry's stored token. To also uninstall the app on BigCommerce's side, go to your BigCommerce control panel → Apps → My Apps → Raspberry → Uninstall.
If you try to export before connecting, the Export To menu opens the connect modal first and then automatically re-opens the export modal with your image loaded, so you do not lose the click.
You can export from anywhere the Export To menu appears:
From the Create Module — right-click any generated image → Export To → BigCommerce
From the Library — select one or more images → Export → BigCommerce (multi-select triggers a bulk export)
From the Board — right-click any image node → Export To → BigCommerce
From the Editor — use the generation footer, layer menu, Batch Apply, or Batch Recolor Export To menu → BigCommerce (batch flows carry all generated images through as a bulk export)
The Export to BigCommerce modal opens directly on a product picker. There is no destination toggle, because product images are the only target.
The picker streams the first page of your products
Type into the search box to filter by title — wildcard match on both sides
Scroll or load more to paginate
Select the product you want and click Export
Every image in the selection is uploaded and attached as product images on that product
A confirmation tells you how many landed
Filenames are auto-derived. There is no filename field on the export modal — the name in BigCommerce comes from the source image. BigCommerce is forgiving of duplicate filenames on product images, so repeated exports of the same asset generally succeed.
All images in a bulk export land on the same product. If you need images split across multiple products, run separate exports.
Result
What you see
All images uploaded
"N images exported to BigCommerce."
Some uploaded, some failed
Warning: "Exported N of M images to BigCommerce (K failed)."
None uploaded
Error: "Failed to export to BigCommerce."
Partial success is most common with very large batches — BigCommerce rate-limits per store, so some files can be throttled mid-upload. The warning tells you exactly how many landed; wait a minute and re-export the ones that did not.
Store (store-{hash}.mybigcommerce.com)
├── Products
│ ├── Product A
│ │ └── Images ← Export target: images land here
│ └── Product B
└── Categories
Products are the primary catalog unit and each has its own image list. Store files, digital downloads, and category images are not export targets today — only per-product images.
BigCommerce OAuth tokens do not expire by default. They stay valid until the app is uninstalled or the store owner revokes access. You should not need to reconnect unless an admin uninstalls the Raspberry app from BigCommerce, the store's plan is downgraded or cancelled, or you explicitly click Disconnect. If you see "BigCommerce authorization expired" or a 401 error, reconnect from Organization Settings.
BigCommerce enforces per-store API rate limits on a request-bucket model — roughly 20,000 requests per hour per store on Standard plans, higher on Pro and Enterprise. Single-image exports sit well within these limits. Very large bulk exports can reach the ceiling, which shows up as a partial-success warning rather than a hard failure.
Problem
What to try
Connect button is disabled or hidden
Your org may be over its connector-token quota, or the integration is gated for your account. Contact your Raspberry representative.
Store-hash step rejects your input
Use the raw hash (abc123xyz) or stores/abc123xyz. Do not paste the full store-abc123xyz.mybigcommerce.com — trim to just the hash.
OAuth popup opens then closes with an error
The signed-in user may not have permission to install apps. Sign in as the store owner, or a user with Manage apps permission, and retry.
"Integration not found" inside the export modal
Disconnect and reconnect BigCommerce from Organization Settings.
Product picker is empty
Your catalog may be empty or all products archived. Confirm in the BigCommerce control panel.
Search does not find a product you know exists
Search matches title only, with wildcard prefix and suffix. Try a shorter substring.
Bulk export returns a partial-success warning
Some images were throttled during the batch. Wait a minute and re-export only the ones that did not land.
"Rate limit exceeded"
BigCommerce's request bucket is drained. Wait a minute and retry; break large batches into smaller ones if it recurs.
Export succeeds but images are not on the product
Refresh the product page in BigCommerce — new images can take a few seconds to appear. Confirm you exported to the product you selected.
I want to export to store files, categories, or digital downloads
Not supported today. Only per-product images are wired up.
I want to pull products from BigCommerce into Raspberry
Not supported. The product list inside the export modal chooses where to send an image; it never copies products into Raspberry.
Can I connect two BigCommerce stores?
Not today — one store per Raspberry org. Contact your Raspberry representative if you need multi-store.
.
BigCommerce
Best for
Brands running their storefront on BigCommerce that want generated imagery to land directly on the right product
How you connect
Enter your store hash → OAuth Single-Click App popup → approve scopes
Who can enable
Org admins with BigCommerce Manage apps permission
Cost
1 connector token from your org's quota
Per-user setup
None — the org shares a single connection
Import supported
No — export only
Export supported
Yes — to a product's images, from Create, Library, Board, and Editor
Destinations
Product images only
Product picker on export
Yes — searchable and paginated
Bulk export
Yes — multi-image selection uploads in one submit, with per-file success reporting
Filename customization
No — auto-derived from source
File types
PNG, JPG, WebP, GIF
Token expiry
Tokens do not expire — persistent until app uninstall or disconnect
API
REST Management API
Rate limits
~20,000 requests/hour per store on Standard plans; higher on Pro and Enterprise
Multi-store
Not supported — one store per Raspberry org
Yes. The integration connects to your existing BigCommerce store. If you do not have an active BigCommerce plan, contact their sales team directly.
Yes. Once an admin connects the organization's store, all members of the org can export to it. There is no per-user setup.
Not currently. One store per Raspberry organization. If you run separate US and EU storefronts, you will need to choose which one this org is bound to.
No. BigCommerce is export only. The product list inside the export modal is a destination picker, not an importer — it never copies products into Raspberry.
Yes. Bulk export is supported anywhere multi-select is available, and every image in the selection uploads in one submit. They all attach to the same product.
Not today. The filename is derived from the source image automatically.
No. Only the images you explicitly export are sent. Nothing is shared in the background.
Yes. Credentials are encrypted at rest and are never exposed in the interface after initial setup.
Yes. Go to Organization Settings → Integrations, find BigCommerce, and click Disconnect. Your stored token is deleted immediately. To also uninstall the app on BigCommerce's side, do that from the BigCommerce control panel.