Contract-tested connectors · one-way
BigCommerce → Odoo
TackQuote can run order and product Flows from BigCommerce to Odoo when both systems are connected. Each record type has its own page so a Customer path is not described as if it were an Order path.
BigCommerce Order → Odoo
A order record on BigCommerce is normalized by TackQuote and written to Odoo when the Flow is active and both connections pass server validation.
- 1
A order record is read from BigCommerce (read, webhook).
- 2
BigCommerce can emit a webhook for this record type, which TackQuote can use as a Flow trigger when that webhook is already forwarded into Flows.
- 3
TackQuote calls the Odoo Order writer and requires a destination id or an explicit verified result before marking the run successful.
Frequently asked questions
Which BigCommerce → Odoo records can TackQuote actually move?
Only the record types listed on this page: order and product. Product Flows are omitted until an event-specific product writer exists.
What does the evidence tier on this page mean?
Both connectors declare the operations the Flow engine calls, and both are covered by connector contract tests. That is a statement about the two connectors, tested separately. This pair has never been recorded running end to end, and this is not a production-support commitment.
Does “Start with this Flow” create a live Flow?
No. The button opens the Flow builder with this source, destination, and record type selected. A Flow is stored only after both connections exist and the API accepts the combination.
Open the BigCommerce → Odoo builder
This selects the pair in the builder. It does not create a Flow until both connections exist and the server accepts the combination.