BigCommerce Connector FAQs
These frequently asked questions cover the most common setup, sync, and troubleshooting topics for the Odoo BigCommerce Connector. For a full feature list and sync matrix, see BigCommerce Connector Features.
Getting Started
Go to , click New, pick BigCommerce, paste your Store Hash and Access Token, then run Test Connection followed by Confirm. Confirming imports your order statuses every time. The first time you confirm, it also imports your categories, brands, sales channels, locations, and tax classes.
Details: Create a BigCommerce instance in Odoo.
The Store Hash is the alphanumeric identifier in your BigCommerce admin URL. When you log in to the BigCommerce control panel, look at the URL, it has the form https://store-<store_hash>.mybigcommerce.com. The connector uses the Store Hash to build the API base URL (https://api.bigcommerce.com/stores/<store_hash>) and the Shop URL, the BigCommerce control panel address used for the links back to orders and products.
Step-by-step: Generate BigCommerce Credentials.
Create a Store API Account in BigCommerce and set every OAuth scope to modify. Missing scopes will surface as permission errors during sync, visible in . Step-by-step instructions live in Generate BigCommerce Credentials.
Details: Generate BigCommerce Credentials.
Test Connection only verifies that the credentials reach BigCommerce, while Confirm additionally imports order statuses, and on the first confirmation sales channels, locations, tax classes, categories, and brands. If Confirm fails:
Check the API account has scopes for Products, Channels, and Information & Settings in addition to read scopes.
Open to see the exact endpoint and error message returned.
If the error mentions inventory locations, your store may not yet have an inventory location configured in BigCommerce, create at least one location and retry.
Products & Listings
Yes. Add the products to listings first. Then, from the operations wizard, choose Export Listings, select the sales channels to publish to, and run it. Every listing of the instance that is not yet exported is created in BigCommerce with images, pricing, inventory, categories, and brand, and then published to the selected sales channels.
Details: Export Products From Odoo.
Use the Update Listings operation to push your latest product changes (name, description, weight, SKU, inventory tracking, attributes) to BigCommerce. You can run it manually on selected listings whenever you make updates, Odoo doesn’t push every keystroke automatically, so you stay in control of when changes go live.
Yes. The connector imports BigCommerce product variants as Odoo product variants and creates the required product attributes and values automatically. Existing Odoo attributes must use the Instantly variant creation mode, otherwise the import of that product fails and the reason is logged. Each variant retains its own SKU, price, weight, and inventory levels. On export, Odoo product variants are pushed to BigCommerce as product options + variants. Note that BigCommerce requires at most one image per variant, so the connector links the first matching image to each variant.
Both are imported automatically the first time you click Confirm on an instance. You can also import them manually: go to , click Operations on the instance, choose Import, then Import Categories or Import Brands. A category or brand that a listing uses is also imported when it is missing during listing import. Imported categories are recreated in Odoo with the parent-child hierarchy preserved, and imported brands are stored as marketplace-specific records that get assigned to listings during product import.
Details: Import Brands From BigCommerce, Import Categories From BigCommerce.
Each BigCommerce instance has its own Pricelist field. The Export Prices operation reads prices from that pricelist and pushes them to the matching BigCommerce listings. To switch pricelists, open , edit the instance, and change the Pricelist under the Products tab. Prices are exported in the pricelist’s currency.
On the Orders tab of the instance, three fallback product fields are available in developer mode: Gift Certificate Product, Custom Product and Custom Storable Product. When a BigCommerce order contains a gift certificate or a custom (non-catalog) item, the connector imports the order line using the matching fallback product instead of failing. A catalog product that has no matching SKU in Odoo still fails the import and is written to the log.
The most common causes:
The product was not modified inside the Date Range you selected.
The product matches an existing Odoo listing but Update Existing Listing? is not enabled.
No Odoo product matches the SKU and Create Odoo Products? is not enabled.
Inventory import only updates storable products that are not tracked by lot or serial number.
Skipped lines are logged at .
It depends on whether you are exporting a brand-new listing or updating one that already exists in BigCommerce:
New listings: Go to , click the Operations button on the instance record, choose Export Listings, select one or more entries in the Sales Channels field, and run the operation. The listing is created in BigCommerce and then published to the selected channels.
Already-exported listings: Open the listing from and click the Manage Sales Channels button. In the wizard, select the desired sales channels and click either Publish or Unpublish.
Publish adds the selected sales channels to the product while preserving all existing channel assignments.
Unpublish removes the product only from the selected sales channels without affecting any remaining assigned channels.
Sales Channels themselves are imported when you confirm the instance for the first time. See Manage Sales Channels.
Orders
Order taxes are created from the tax lines BigCommerce reports on each order, according to the Tax System set on the Orders tab of the instance. Tax-inclusive or tax-exclusive pricing is read per order. BigCommerce tax classes are used on listings, see BigCommerce Tax Classes.
Each BigCommerce instance has a list on its Workflow tab where every payment gateway × payment status combination (Authorized, Captured, Paid, Pending, Refunded, Partially Refunded, Held for Review, Declined, Void, etc.) maps to its own workflow. The workflow decides what runs: confirm the Sale Order, create the Invoice, validate the Invoice, register the Payment. Unknown gateways are created on first sight, but the order is not imported until you add a line for that gateway (use Configure Workflow on the log line) and retry the failed line. See BigCommerce Financial Workflow Configuration.
Orders are imported by the Import Order scheduled action (15 minutes by default). It is created inactive, so activate it on the Automatic Jobs tab of the instance and adjust the interval to match your traffic. To import right away, use the operations wizard with a Marketplace Order ID (the orders are imported at once), or with a Date Range (the orders are added to a queue job).
A single BigCommerce order with multiple shipping addresses is automatically split into multiple Delivery Orders in Odoo, one Delivery Order per shipping address. Each Delivery Order is fulfilled, validated, and pushed back to BigCommerce independently with its own carrier and tracking number. The Sale Order itself stays as one record, but the fulfillment side becomes one delivery per destination. This is enabled automatically and requires no extra configuration.
Cancel the Sale Order in Odoo first. Then click Cancel In BigCommerce on the cancelled order. In the window, enter a Cancel Reason (kept in the Odoo chatter) and, for paid orders, optionally switch on Refund Payments to also push a full refund. Then click Cancel Order. The connector sets the order status to Cancelled in BigCommerce, and if the refund option was on, pushes the refund and creates a credit note in Odoo.
Details: Cancel Order In BigCommerce From Odoo.
The Update in Marketplace button is on the Delivery Order, not the Sale Order. It appears once the outgoing delivery is validated (Done), is linked to a BigCommerce order and has not been sent yet. Clicking it pushes the carrier code and the tracking number to BigCommerce as a shipment. The same push can run on a schedule via the Export Order Status/Tracking Information scheduled action, which is inactive until you activate it.
Orders can be brought in manually from the operations wizard or on schedule via the Import Order automatic job (inactive by default). The Order Status filter on the Orders tab of the instance decides which BigCommerce statuses are eligible for import. If it is empty, orders of every status are imported. You can also pass a comma-separated list of Marketplace Order ID values to import specific orders only. The filter is not applied to those orders.
Details: Import BigCommerce Orders In Odoo.
The Mark As Paid In BigCommerce button only appears when all of these are true:
The instance has Mark Order as Paid? enabled.
The Sale Order is fully invoiced and all customer invoices are paid in Odoo.
The order’s BigCommerce payment status is not already Captured, Paid, Refunded, or Partially Refunded.
The BigCommerce order status is Incomplete, Pending or Awaiting Payment.
The Sale Order is linked to a BigCommerce order (has a BigCommerce ID).
Create a credit note against the original customer invoice in Odoo, reduce or remove the lines you do not refund, and post it. Then click Refund In BigCommerce, enter a Refund Description and click Refund. The connector sends the product lines and quantities of the credit note, and BigCommerce calculates the refund total. Full refunds work the same way, the credit note simply covers all lines.
Details: Refund Orders From Odoo To BigCommerce.
Customers & Multi-Store
When a BigCommerce order is imported, the connector looks up the customer by email + name + address. If a matching contact already exists in Odoo, it is reused; otherwise a new contact is created automatically. An Invoice contact is created from the billing address, and a Delivery contact is created for each shipping address, as child contacts under the main customer record.
Yes. Enable Create Company Contact? on the Customer tab of the instance. When enabled, the connector creates a parent Company contact when the billing or a shipping address has a company name, and attaches the individual customer plus their billing/shipping addresses as children of that company. This keeps B2B order records organized by company in Odoo’s contacts list.
Inventory & Pricing
Yes. Per-instance scheduled actions exist for inventory export (every 30 minutes by default), inventory import (daily by default), and price export (daily by default). They are created inactive, so activate them on the Automatic Jobs tab of the instance. You can adjust the intervals or run any sync manually from the operations wizard.
Yes. Each listing has Export Qty Type and Export Qty Value fields on its Inventory tab:
Fix: push a fixed quantity instead of your on-hand stock. The pushed quantity never goes above your on-hand stock (e.g. 5 pushes at most 5 units).
Percentage: push only a percentage of on-hand (e.g. 90 % so you keep a 10 % buffer).
Useful for keeping safety stock so you don’t oversell when sync timing is tight.
Each BigCommerce location is mirrored as a Location record in Odoo. Only locations with Enable Import/Export Stock? turned on participate in stock sync. On import, the BigCommerce quantity is written as the counted quantity of the matched products at the stock location mapped to each enabled location. On export, the quantity of the stock location mapped to each enabled BigCommerce location is pushed to that location, in batches.
Details: Configure BigCommerce Locations.
Troubleshooting
At . Each log has its operation type, and each log line holds the message (which contains the BigCommerce ID) and its status. When a workflow is missing, the log line also has a Configure Workflow button that opens the matching financial workflow form pre-filled with the payment gateway and payment status combination missing from your configuration.
Dependencies
The module depends on Base Marketplace. No additional packages or libraries are required beyond a standard Odoo install.