Connect your shop with read-only REST API keys, browse your catalog to find the SKUs that need images, and bring them into the studio by product URL or CSV.
Create a REST API key under WooCommerce → Settings → Advanced → REST API, then enter your shop URL, consumer key and secret. Read permission is enough.
GridShot loads your WooCommerce categories and products so you can see which SKUs are missing on-model shots. Products enter the studio through their product URL or as a CSV batch — several photos of one item become perspectives of a single product.
Each run produces a grid of 16–25 variations in about 5–15 minutes. You deliver only the shots you actually want as final images.
The connection reads from the WooCommerce REST API (/wp-json/wc/v3). These product fields arrive in GridShot:
| Field | WooCommerce source | What it is used for |
|---|---|---|
| Product name | name | Becomes the product name in GridShot. |
| Description | description | Kept as product context you can review and edit. |
| SKU | sku | Stays attached so outputs map back to your catalog. |
| Category | categories | The first category is used for grouping and filtering. |
| Product images | images | The full gallery is pulled; the first image serves as the primary reference. |
| Product link | permalink | Kept as the source URL back to the product in your shop. |
GridShot renders garment length and fit from curated values: brand truth instead of an AI guess. Well-maintained WooCommerce attributes like “Length: midi” or “Fit: oversized” are exactly the right source for those values, because you already wrote them for your customers.
To be precise about what the integration does today: those attributes are not carried over automatically. The connection reads name, description, SKU, category and images while you browse. Curated length and fit are set inside GridShot per product — and once set, they take priority over what the AI infers from the photos.
GridShot does not write to WooCommerce. The API key you create only needs read permission, so the connection can never change product data, prices or stock.
This is a deliberate trade-off: one manual upload step in exchange for an integration that cannot touch your live catalog.
No subscription and no tiers. You pay for the images you publish:
So a product for which you publish four images costs roughly $4 plus the compute for the runs behind them — and the $10 starting credit covers your first SKUs before you top up at all.
See full pricingAll three paths feed the same generation pipeline. They differ only in how products get in.
The Shopify integration connects via OAuth rather than API keys. From product selection onward the workflow is identical.
Shopify integrationThe CSV workflow takes a spreadsheet of product URLs and pushes them through as one batch job — the faster path for hundreds of SKUs at once, and the fallback for shop systems without a direct connection.
CSV workflowRead is enough. Create the key under WooCommerce → Settings → Advanced → REST API with read permission; GridShot only fetches categories, products and their images.
No. The connection reads name, description, SKU, category and images while you browse. Length and fit are set as curated values inside GridShot, where they take priority over what the AI infers from the photos. Your WooCommerce attributes are the right source to copy them from, because they are your brand truth rather than a guess.
You browse the products the REST API returns and bring the ones you need into the studio by product URL or CSV. Colours that exist as separate products in WooCommerce are picked individually; where colours are variations of a single product, you work from that product’s gallery images and organise the variants inside GridShot.
No. The connection is read-only and there is no write-back path. Finished images are downloaded from GridShot and added to your product gallery by you.
Start with one category and a handful of products so you can judge the output on your own garments. The $10 starting credit covers those first images. For large batches, the CSV workflow is usually the faster route.