BigCommerce Connector

Connector status: In progress Being built. Not verified yet.

Illustration · sample data

Sync example

Review one record

Source

BigCommerce

Connector status: In progress

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

Tajo’s BigCommerce connector is in progress. The code exists, but it has not yet passed a run against a live BigCommerce store.

What the code does

  • Reads customers, newsletter subscribers, customer addresses, orders and catalog products, and uses the modification date to read only what changed.
  • Updates a customer’s email, name, phone and company.

Not available today

  • Real-time updates through BigCommerce webhooks
  • Abandoned-cart recovery
  • Multiple storefronts
  • Inventory and back-in-stock tracking

Open-Source Implementation Map

This section is derived from official or public repository material discovered for the BigCommerce connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.

Repository Snapshot

RepositoryCommitLanguages / formatsFiles
bigcommerce/api-specsdcf4840YAML (166), JSON (61), Markdown (6), YAML (4), gitignore (2), github/codeowners (1)244

Integration Shape

graph LR
Source["BigCommerce API / repository"] --> Auth["Auth and scopes"]
Source --> Objects["Objects, events, and schemas"]
Auth --> Tajo["Tajo connector runtime"]
Objects --> Tajo
Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"]
Tajo --> Ops["Backfill, cursor, retries, logs"]

What To Reuse

  • BigCommerce API Specifications
  • As of December 27, 2023, you can find all the public BigCommerce DevDocs at https://github.com/bigcommerce/docs!
  • This repository is archived and read only. The final commit has been tagged.
  • If you maintain API clients, the new bigcommerce/docs repo is now your source for the most up-to-date API specifications.
  • This consolidation lets the BigCommerce DX team offer a more streamlined developer experience. issues, discussions, and pull requests at bigcommerce/docs!

Tajo Revamp Checklist

  • Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
  • Map primary resources into explicit Tajo sync objects with stable external IDs.
  • Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
  • Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
  • Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
  • Keep examples small and runnable against sandbox or test-mode accounts.

Sources

Request early access

Enter your first name and business email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: bigcommerce.md

Loading Markdown…