Catalogues grow faster than the ability to search them. A BigCommerce store with thousands of SKUs, several channels and years of orders holds the answer to most merchandising questions — but the admin search matches product titles, and the answer is usually in a description, a custom field, or the note an agent left on an order. The BigCommerce connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Search the catalogue by description, not by SKU
Ask for "the outdoor range with the two-year warranty" and get the products, including the ones whose titles say nothing about either.
Ask why a product line underperforms
Order notes, return reasons and customer messages carry the cause. Matched by meaning, five differently worded complaints about the same fault come back as one group.
Answer a customer question from their own history
Orders, notes and past contacts for one customer, answered together instead of assembled by hand across tabs.
What is read, and what is never listed
What crosses, and what stays in BigCommerce
Read
products, categories, custom fields, order details and customer records you enable.
Written back
nonenothing. No products edited, no orders changed, no emails sent.
Stored
a searchable copy of that text, plus a link back to the record in the control panel.
Never read
payment card data, and object types you left disabled.
What you will be granting
Read-only API access scoped to the resources you tick — the catalogue alone is a valid choice — revocable from the store's control panel.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Create a read-only API account in the BigCommerce control panel and paste it into Knowledge.
- 02
Choose which resources to include: catalogue, orders, customers.
- 03
Decide whether customer names and emails should be excluded from answers.
- 04
Set the refresh interval.
Limits, honestly
- One-way and read-only. BigCommerce remains the system of record.
- Answers reflect the last refresh, not the order placed a minute ago.
- Payment data is never read.
- Theme files, apps and the analytics suite are out of scope for now.
- Multi-storefront setups connect one store at a time.