Can the BigCommerce adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your BigCommerce tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
Will this break our existing reports?
No. The adapter writes through a versioned schema layer with full lineage. Existing reports, BI extracts and Excel pivot-tables keep working unchanged while new fields and new objects are added behind the scenes for the BigCommerce surface.
Is this a packaged BigCommerce connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.
How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The BigCommerce adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for San Antonio, Texas. After go-live, the BigCommerce adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
How long does the BigCommerce integration take to ship?
Our standard window is thirty days from signed scope to live BigCommerce adapter in production, plus a one-week monitored stabilization phase. For San Antonio, Texas, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.