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¶
Yes. Fully compatible with Odoo Enterprise (On-premise and Odoo.SH) and Odoo Community. Not compatible with Odoo Online (SaaS) as it does not support third-party apps.
Any BigCommerce store that supports Store API Accounts — Standard, Plus, Pro, and Enterprise plans. The connector authenticates with the long-lived Access Token issued for that account.
Go to , click Create, pick BigCommerce, paste your Store Hash and Access Token, then run Test Connection followed by Confirm. Confirming auto-imports your categories, brands, sales channels, locations, order statuses, 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 storefront URL.
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, 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. From the operations wizard, choose Export Listings, pick the products and sales channels to publish to, and run it. The connector creates the listing in BigCommerce with images, pricing, inventory, categories, and brand — and publishes it to the selected sales channels in one call.
Details: Export Products From Odoo.
Use the Update Listing 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. 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 when you click Confirm on a new instance, and they can also be imported manually at any time from and . Imported categories are recreated in Odoo with parent-child hierarchy preserved, and imported brands are stored as marketplace-specific records that get assigned automatically to listings during product import.
Details: Import Brands From BigCommerce, Import Categories From BigCommerce.
Each BigCommerce instance has its own Pricelist field. The Export Price 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 General tab. Prices are exported in the pricelist’s currency.
On the instance, the Product Configuration tab has two fallback product fields: Gift Certificate Product and Custom Product. When a BigCommerce order contains a gift certificate or a custom (non-catalog) item, the connector imports the order line using the configured fallback product instead of failing. This lets the order import succeed even when the line item has no matching SKU in your Odoo catalog. Configure both fields before importing real orders.
The most common causes:
The product is in Draft status in BigCommerce — only active listings are imported by default.
The product matches an existing Odoo listing but Update Existing Listing? is not enabled.
The product has a tracking type incompatible with the operation (e.g. inventory import only updates products with Tracking = No Tracking).
Skipped lines are logged at Marketplace --> Queues --> Logs.
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 published to the selected channels in the same call.
Already-exported listings — Sales Channel management for existing BigCommerce listings is handled through the dedicated Manage Sales Channels action. Go to , click the Listing button on the instance record, select one or more listings, open the Actions menu, and choose Manage Sales Channels. From 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 automatically when you confirm the instance.
Orders¶
No. Odoo’s default delivery confirmation email is automatically suppressed for BigCommerce orders, because BigCommerce sends its own shipment notification when the order is marked shipped. Your customers receive exactly one shipment email — the one from BigCommerce.
The connector imports your BigCommerce tax classes and applies them automatically to orders and invoices. Tax-inclusive vs. tax-exclusive pricing is detected per-order from BigCommerce, so the invoice totals always match what the customer saw at checkout.
Each BigCommerce instance has a Financial Workflow matrix 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 automatically: confirm the Sale Order, validate the Delivery Order, create an Invoice, register Payment. Unknown gateways are auto-created on first sight so nothing blocks the order import; you just configure the new gateway’s workflow afterwards.
Orders are imported on a schedule via the built-in Import Orders automatic action (every 15 minutes by default). You can adjust the interval to match your traffic. For instant imports, run the operations wizard manually — by date range, single order ID, or comma-separated multiple IDs.
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.
When BigCommerce reports an order as partially fulfilled (some lines shipped, others not), the connector reads the per-line quantity_shipped value and creates a Delivery Order in Odoo with only the shipped quantities. Remaining unshipped quantities stay as a separate (Pending) Delivery Order. This avoids the all-or-nothing behavior where the entire order would otherwise be marked done in Odoo.
Open the Sale Order linked to the BigCommerce order and click Cancel in BigCommerce. A wizard opens where you can enter a Cancellation Reason and optionally tick Refund Payment to also push a refund alongside the cancellation. The connector calls the BigCommerce API to set the order status to Cancelled, and (if the refund toggle was on) records a credit note in Odoo for the refund amount.
Details: Cancel Order In BigCommerce From Odoo.
The button is on the Delivery Order, not the Sale Order. It appears once the delivery is validated (Done) and the order is linked to a BigCommerce order. Clicking it pushes the carrier code, tracking number, and the Shipped status back to BigCommerce in one call. The same action can also run automatically on a schedule via the Update Order Status scheduled action.
Orders can be brought in manually from the operations wizard or on schedule via the Import Order automatic job (inactive by default). The instance-level Order Status filter (defaulting to Awaiting Fulfillment) decides which BigCommerce statuses are eligible for import. You can also pass a comma-separated list of Marketplace Order ID values to import specific orders only.
Details: Import BigCommerce Orders In Odoo.
The 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, Refunded, or Partially Refunded.
The Sale Order is linked to a BigCommerce order (has a BigCommerce ID).
Create a partial credit note against the original customer invoice in Odoo, post it, then click Refund in BigCommerce and confirm. The connector pushes the refund to BigCommerce and stores the resulting refund ID on the credit note. Full refunds work the same way — the credit note simply covers the entire invoice amount.
Details: Refund Orders From Odoo To BigCommerce.
Customers & Multi-Store¶
The connector uses a default fallback customer for orders that have no customer attached on the BigCommerce side (rare guest checkouts). The order still imports successfully — you can re-assign it to a real contact later if the buyer creates an account.
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. Billing and Shipping addresses are stored as child contacts under the main customer record. A fallback contact is used when an order has no customer attached (rare guest checkouts).
Yes. Enable Create Company Contact? on the instance’s Order Configuration tab. When enabled, the connector creates a parent Company contact 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.
Yes. Create one Instance per BigCommerce store from . Each instance has its own Store Hash, Access Token, warehouse, pricelist, financial workflow, and scheduled actions. There is no hard limit on the number of instances.
Inventory & Pricing¶
Yes. Per-instance scheduled actions run inventory and price sync automatically — stock every 30 minutes, prices daily, by default. You can adjust the intervals or run any sync manually from the operations wizard.
Yes. When an imported BigCommerce order is in a different currency than your instance’s default pricelist, the connector automatically creates (or reuses) a matching pricelist in that currency and assigns it to the order. You don’t have to juggle pricelists manually for stores that sell in multiple currencies.
Yes. Each listing has an Export Qty Type setting:
Fix — subtract a fixed number from on-hand before pushing (e.g. always reserve 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, one Inventory Adjustment is created per enabled location. On export, Odoo combines on-hand quantities across all enabled stock locations linked to that BigCommerce location and pushes the total in batches.
Details: Configure BigCommerce Locations.
Troubleshooting¶
The connector automatically reads BigCommerce’s rate-limit response headers and waits the required time before retrying — no failed jobs, no manual restarts. Large catalogs and bulk operations sync reliably even during high-traffic periods on BigCommerce’s side. Pagination through large result sets is also handled automatically; you don’t have to worry about page sizes.
Failed records are flagged in the queue with detailed error logs while the rest of the queue keeps processing — one bad order never blocks the others. Click through to the source line, fix the issue, and retry.
Open , locate the job with failed lines, open the failed line, and click Retry. The connector re-fetches fresh data from BigCommerce for that record before retrying, so the job uses the latest BigCommerce state and not the originally cached data.
At . Each log line includes the operation, the BigCommerce ID, the error message, and (when relevant) a Configure Workflow shortcut 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.
Support¶
Yes. Every purchase includes a free 60 to 90 minute screen-share session with our team. We walk through credentials, configuration, first import, and go-live live with you — not a PDF, not a chatbot, real developer support.
We offer free support for the initial 60 days after the purchase date. Beginning from version 13, each app version will be sold separately as per Odoo Policy.