> Skip to main content
🅱️ BigCommerce

All your channel feeds from one BigCommerce connection

BigCommerce's native channel integrations are limited. Trajekt connects directly to the BigCommerce API to pull your complete product catalogue and generate feeds for Google Shopping, ChatGPT, Meta, TikTok, Awin, and every other channel you need.

✓ BigCommerce API native✓ Custom fields supported✓ Variant products handled✓ Multi-channel from one connection
Also see: BigCommerce Google Shopping setup guide — step-by-step walkthrough.
60K+
BigCommerce stores in the UK
50K
products per feed supported on Growth plan
REST API
BigCommerce V2/V3 API — no app install required
11
channels from one BigCommerce connection

BigCommerce Product Feed — what Trajekt does for you

🔌

API connection

Trajekt connects via BigCommerce's V3 Products API. Create an API account in BigCommerce admin with read-only product permissions and paste the credentials into Trajekt.

🎨

Variant handling

BigCommerce variant products with option combinations are correctly mapped — each variant appears as a separate feed row with shared item_group_id for Google and Meta grouping.

📦

Custom fields

BigCommerce product custom fields are available in Trajekt's rules engine — map brand, GTIN, material, and any other custom field to feed attributes.

💰

Sale price support

BigCommerce sale prices are pulled and mapped to sale_price in your feeds. Sale price effective dates are included for platforms that support scheduled promotions.

🖼️

Multiple images

All BigCommerce product images are pulled. Primary image maps to image_link; additional images map to additional_image_link for Google, Meta, and ChatGPT feeds.

🔄

Scheduled updates

Trajekt syncs with BigCommerce on your chosen schedule and regenerates feeds automatically.

BigCommerce Product Feed — frequently asked questions

Trajekt connects via the BigCommerce API. In BigCommerce admin, go to Settings > API Accounts > Create API Account. Set permissions for Products (read-only) and Inventory (read-only). Copy the Client ID, Client Secret, and Access Token into Trajekt.
Trajekt pulls: product names, descriptions, prices, sale prices, SKUs, GTINs/MPNs, images, variants with options, categories, brands, availability, and custom fields.
BigCommerce variants (option combinations) are correctly handled. Each variant appears as a separate feed row with its own price, SKU, and availability. All variants share the same item_group_id (parent product ID).
GTINs can be stored in BigCommerce's built-in UPC/EAN field or in a custom product field. Trajekt can pull GTINs from either location — just tell Trajekt which field contains your barcode data.
Yes. BigCommerce product custom fields are accessible via the V3 API and available in Trajekt's rules engine. Custom fields for brand, material, age group, gender, or any other product data can be mapped to feed attributes.
BigCommerce has a native Google Shopping integration but it has limitations — limited rule customisation, no AI enrichment, and restricted channel support. Trajekt provides more flexibility, supports more channels, and includes AI-powered feed rules.
Trajekt pulls BigCommerce category names and lets you map them to Google's product taxonomy (google_product_category) or use them directly as product_type values in your feeds.
Yes. Trajekt fetches BigCommerce products in paginated API requests and handles large catalogues. Growth plan: up to 25,000 products. Pro plan: up to 75,000. Agency plan: unlimited.
For headless BigCommerce implementations, Trajekt still connects to the standard BigCommerce API — the storefront implementation doesn't affect API access. Product data is pulled from the same V3 API regardless of your frontend.
From one BigCommerce connection, Trajekt can generate feeds for: Google Shopping, ChatGPT Shopping, Meta/Facebook, Instagram, TikTok Shop, Pinterest, Microsoft/Bing, Awin, and any custom XML or CSV format you need.
No. Trajekt only needs read-only API access to Products and Inventory. No write permissions, no admin UI access, and no installation of BigCommerce apps is required.

How BigCommerce data maps to feed attributes

Trajekt connects via the BigCommerce Catalog API and maps your BigCommerce data to the correct feed attributes for each channel.

BigCommerce field Feed attribute Notes
Product titletitleTrajekt rules restructure for Shopping (Brand + Name + Attributes)
DescriptiondescriptionHTML stripped automatically; AI enrichment available
Product URLlinkVariant-level URLs used where available
Main imageimage_linkFull-size URL (not thumbnail). Secondary images → additional_image_link
Price (inc. VAT)priceGBP format: 29.99 GBP. Variant prices used per row
Sale pricesale_priceActive compare-at price mapped when lower than regular price
Stock statusavailabilityin_stock / out_of_stock per variant, updated daily
Custom attributesgtin / brand / materialbrand, GTIN, UPC — BigCommerce has native fields for these which Trajekt maps automatically
Variant IDid / item_group_idBigCommerce variant IDs become feed row IDs, with the parent product ID as item_group_id
Category / typeproduct_type / google_product_categoryMapped to GPC numeric IDs via Trajekt category rules
Agency tip: BigCommerce's native Google Shopping integration is limited. Trajekt via the Catalog API accesses your full custom field set and generates feeds for all channels, not just Google

Common BigCommerce feed problems — and how Trajekt fixes them

Price mismatchesSale prices changing in BigCommerce but not reflected in your feed until the next crawl. Trajekt’s daily refresh (or twice-daily on Growth+) keeps prices current. A manual re-run can be triggered any time before a sale launches.
Missing GTINsBigCommerce doesn’t have a native barcode field in all versions. Trajekt maps your custom barcode/EAN attribute directly to the gtin feed field via a rule. Branded products get their GTINs; own-brand products get identifier_exists: no.
Thumbnail imagesSome BigCommerce configurations export thumbnail image URLs rather than full-size images. Trajekt maps to the full-size image URL via the API, ensuring images meet Google’s 800×800px recommended minimum.
Unoptimised titlesDefault BigCommerce product names are written for on-site browsing, not Shopping search matching. Trajekt rules restructure titles to the Shopping-optimal format (Brand + Product + Attributes) without changing anything in your BigCommerce store.
No custom labelsBigCommerce has no native custom label concept for Shopping. Trajekt sets custom_label_0–4 automatically via rules — by price range, category, stock level, or any field in your BigCommerce data.

Connect your BigCommerce store to every channel today

Trajekt connects to BigCommerce's API and generates feeds for Google, ChatGPT, Meta, TikTok — automatically updated on your schedule.