Create a BigCommerce instance in Odoo

To create your BigCommerce instance in Odoo, navigate to Marketplaces ‣ Configuration ‣ Instance and click on New.

  1. Choose a meaningful name for your Instance (for example TeqStars BigCommerce) and set Marketplace to BigCommerce.

  2. On the Credentials tab, fill in the required BigCommerce API credentials (Store Hash and Access Token). Follow the Generate BigCommerce Credentials guide to create a Store API Account with the right OAuth scopes and connect your BigCommerce store to Odoo.

Let’s begin with the instance configuration process for the BigCommerce Odoo Connector. By following the configurations below you’ll be able to set up and customize the integration according to your business needs. The remaining sections describe each configuration group on the instance form, and the final Confirming the Instance section walks you through testing and confirming the connection.

Last Processed On

Last Processed On
  • Last Processed On shows the date and time when a specific import or export last ran.

  • Each date is updated when the matching operation runs, whether you start it from Operations or a scheduled job runs it. The tab appears after the instance is confirmed.

Configurations

Configurations

Under the Configuration tab, you can define the core operational settings for your BigCommerce instance:

  • Warehouse: Select the Odoo warehouse related to this instance. This warehouse will be utilized for stock operations and order processing for this marketplace.

  • Country: Select the country related to the instance (e.g., United States).

  • Company: Choose the company related to this instance.

  • Language: Select the language related to the instance (e.g., English (US)).

  • Log Level: Choose which type of log level you would like to have. You can choose between All, Success, or Error (default Error). The system will create logs for each marketplace operation. To view the logs, navigate to Marketplaces ‣ Queues ‣ Logs.

  • Weight Unit: Mirrors the BigCommerce store’s weight measurement (LBS, KGS, Ounces, Grams, or Tonnes). The connector reads it from your BigCommerce store settings when you confirm the instance, and the field is locked afterwards. Odoo product weights are converted to this unit when you export or update listings, and BigCommerce weights are converted from it on import.

  • Queue Batch Limit: Default to 100 records. We aren’t suggesting to change this.

Note

To modify the Queue Batch Limit, activate the developer mode and navigate to Marketplaces ‣ Configuration ‣ Instance and click on the Configuration tab.

Product Configurations

Product Configurations
  • Pricelist

    Pricelist refers to a pricing configuration that determines the prices of products during the product sync operation between BigCommerce and Odoo. When prices are imported or exported during synchronization, this pricelist is used to set the appropriate prices. When the BigCommerce order currency matches the pricelist currency, this pricelist is used on the order. When it differs, the connector uses a pricelist named BigCommerce: <instance name> in the order currency, and creates it if it does not exist.

  • Export Odoo Product’s Sale Price?

    When exporting Odoo products, the standard behavior is to export the prices based on the pricelist configured on the instance. However, if you want to export the product’s sale price directly, bypassing the pricelist, you can enable this option to customize the export behavior.

  • Create Odoo Products?

    Enabling Create Odoo Products? allows the BigCommerce Odoo Connector to automatically create new products in your Odoo catalog when no matching product is found by SKU during listing import. Every product from your BigCommerce store is then represented in your Odoo catalog.

    Tip

    If you already have existing products in your Odoo ERP system, it is not recommended to enable Create Odoo Products? on the instance.

  • Update Category in Odoo Products?

    When the connector creates a new Odoo product during listing import and the BigCommerce product has exactly one category, the product gets the matching Odoo product category. Existing Odoo products are not changed.

  • Sync Listing Images?

    Images associated with products being imported from BigCommerce to Odoo will be synchronized and attached to the corresponding listing during the import operation. By syncing the listing images, the images are properly available and associated with the matching listings within the Odoo system.

Note

BigCommerce listings are matched to Odoo products by SKU. SKU is the standard matching key for BigCommerce, applied automatically by the connector, no extra configuration is required on the instance form.

Stock Configurations

Stock Configurations
  • Stock Based On (default Quantity On Hand)

    When exporting inventory from Odoo to BigCommerce, you can choose Free To Use Quantity, Quantity On Hand, or Forecasted Quantity based on your requirements. The selected quantity is what is exported to BigCommerce.

    Tip

    • Forecasted Quantity: Quantity on Hand - Outgoing + Incoming

    • Free To Use Quantity: Quantity on Hand - Reserved Quantity

  • Validate Inventory Adjustment?

    When disabled (default), the inventory import writes the BigCommerce quantity as a counted quantity that you apply yourself from Inventory ‣ Operations ‣ Adjustments ‣ Physical Inventory. When enabled, the quantity is applied right after the import.

Note

To be included in Import Inventory, the matched Odoo product must track inventory and be tracked by quantity only. Products tracked by lot or serial number are skipped because BigCommerce returns aggregate quantities per location, with no lot or serial breakdown that Odoo could use to allocate the imported stock safely.

For per-location configuration (warehouse, stock location, enable toggle), see Configure BigCommerce Locations.

Orders Configurations

Orders Configurations
  • Order Status

    A multi-select list of BigCommerce order statuses that are eligible for import. The connector loads the BigCommerce statuses into Odoo when you confirm the instance. If you select statuses, only orders whose BigCommerce status is in the selected list are picked up by Import Orders. If you leave the field empty, orders of every status are imported. Add Refunded and Partially Refunded if you want credit notes created from BigCommerce refunds.

  • Mark Order as Paid?

    When enabled, registering a payment on a fully invoiced BigCommerce order (or clicking Mark As Paid In BigCommerce on the sale order) moves the order in BigCommerce to Awaiting Fulfillment, so it can be fulfilled. This is useful for offline payments, bank transfers, cash on delivery, or any payment not captured by a BigCommerce payment gateway. See Mark As Paid Orders From Odoo To BigCommerce for the full flow and visibility rules.

  • Use Marketplace’s Order Sequence?

    This feature allows you to name orders in Odoo based on the BigCommerce order number rather than using the default Odoo sequence. This ensures that the order names in Odoo correspond directly to the order numbers generated by the BigCommerce platform, providing consistency and easier cross-referencing between Odoo and BigCommerce.

  • Order Prefix

    This feature allows you to specify a prefix that will be added to the names of imported orders. When importing orders from your BigCommerce store to your Odoo ERP system, the connector will set the order name with the given prefix. This helps to easily identify and distinguish the imported orders in your Odoo system. The field is shown and used only when Use Marketplace’s Order Sequence? is enabled.

  • Sales Team

    By configuring this feature, you can ensure that all imported orders from BigCommerce are automatically assigned to the specified default Sales Team in Odoo.

  • Salesperson

    Select a salesperson who will be responsible for processing the orders received from your BigCommerce store. It is important to ensure that the assigned user has sufficient access rights in Odoo.

  • Tax System

    The tax system on the BigCommerce Instance offers three options for handling taxes when importing orders from BigCommerce:

    1. Odoo’s Default Tax Behaviour (Taxes will be taken from Odoo Product):

      With this option selected, Odoo will use the tax information defined on the Odoo products and related fiscal rules. When importing orders from BigCommerce, the connector ignores BigCommerce tax lines and applies the taxes configured on the corresponding Odoo products. This keeps tax calculation fully aligned with your Odoo tax configuration.

    2. Follow Marketplace Tax (no fiscal position mappings):

      With this option, the connector follows the tax amounts coming from BigCommerce. For each tax on the BigCommerce order, Odoo looks for a matching tax; if it does not exist, a new tax can be created and linked to the configured Tax Account fields. The resulting Odoo taxes are applied directly on the order and shipping lines without applying any fiscal position mappings.

    3. Follow Marketplace Tax and applies fiscal position mappings:

      This option also starts from the taxes provided by BigCommerce, creating or reusing matching Odoo taxes as needed. After determining the Odoo taxes based on BigCommerce tax lines, the connector applies the fiscal position of the order to remap those taxes before posting them on the order lines. This lets you respect BigCommerce tax amounts while still using Odoo fiscal position rules for accounting and reporting.

  • Tax Account (shown and required only when Tax System is not Odoo’s Default Tax Behaviour)

    Specifies the account associated with a tax when it is created in Odoo from a BigCommerce tax line. This account is used to record tax-related transactions and ensures accurate tracking and reporting of tax amounts within your Odoo ERP system. By setting the Tax Account, you make sure that taxes coming from BigCommerce are properly accounted for and integrated into your financial management processes.

  • Tax Account on Credit Notes (shown and required only when Tax System is not Odoo’s Default Tax Behaviour)

    Specifies the account associated with a tax when a credit note is created in Odoo from a BigCommerce refund. This account is used to record tax-related transactions on credit notes and ensures accurate tracking and reporting of refund tax amounts within your Odoo ERP system.

  • Tax Rounding

    The number of decimals used when Odoo searches for or creates a tax from a BigCommerce tax rate (default 2). Set 0 for no rounding. The field is shown only when Tax System is not Odoo’s Default Tax Behaviour.

  • Custom Product (Only visible in developer mode)

    This feature allows the import of BigCommerce orders that contain custom (non-catalog) items into Odoo. These custom items, typically consumable products, are imported as separate products on the order in Odoo using the configured product.

  • Custom Storable Product (Only visible in developer mode)

    BigCommerce orders that contain custom fulfillable (storable) items are imported using this product for those lines when no matching Odoo product is found.

  • Gift Certificate Product (Only visible in developer mode)

    Allows the import of BigCommerce gift certificate amounts using a specific service-type product. When a BigCommerce order includes a gift certificate, the amount is imported into Odoo as a negative line using this product.

  • Delivery Product (Only visible in developer mode)

    Defines the specific product in Odoo that represents the charges associated with the delivery of orders from your BigCommerce store. While creating a new delivery method, you can associate the Delivery Product with that particular method so the associated product is used to calculate and represent the delivery charges for orders using that delivery method.

  • Create Single Invoice? (Only visible in developer mode)

    Determines whether a single invoice should be created once all items in an order are available for invoicing. When enabled (default), the invoice is generated only after all products are ready. When disabled, invoices can be created separately for each product as it becomes ready.

Customer Configurations

Customer Configurations
  • Receivable Account

    This allows you to specify the default account for receivables when creating customers from BigCommerce orders. By setting this field to Account Receivable instead of the default account, you ensure that receivable transactions, such as invoices and payments, associated with the customer are correctly accounted for in the Odoo ERP system.

  • Create Company Contact?

    When a contact is being created during order import, the connector checks if the BigCommerce billing address or a shipping address contains a company name. If found, it generates a separate Company contact and links the individual contact to it as a child contact, ensuring that the company’s information is properly recorded and linked to the contact in Odoo. This feature is recommended for B2B stores where the same company places orders from multiple individuals.

Financial Workflow Configuration

Financial Workflow Configuration
  • Workflow is a configuration setting used in the BigCommerce Odoo Connector that enables the automatic processing of orders from BigCommerce. This workflow automates various actions, including confirming orders, creating invoices, validating invoices, and registering payments.

  • By setting up the Marketplace Workflow, you can speed up the order processing cycle and save time by eliminating manual interventions. The workflow ensures that orders from BigCommerce are processed and managed within your Odoo system.

  • Payment Terms

    Payment Terms are set on the customer of the imported order, and the order takes them from the customer. They specify when and how the customer is expected to make the payment for their purchase.

  • Marketplace Workflow

    • It enables the automatic processing of orders from BigCommerce. This workflow automates various steps, including confirming orders, creating invoices, validating invoices, and registering payments.

    • To learn more about the details and configuration options of the Marketplace Workflow, please refer to the following link: Configure Marketplace Order Workflow.

  • Payment Gateways & Payment Status

    • The order workflow is defined for the combination of the Payment Gateway used for the transaction and the Payment Status of the order on BigCommerce.

    • Odoo picks the workflow line that matches the payment gateway and the payment status of the order (or Any). The Payment Terms and the Marketplace Workflow of that line are then applied.

For payment gateways, log lines for missing workflows and credit notes, see BigCommerce Financial Workflow Configuration.

Note

The Payment Gateway and Payment Status values are read from each BigCommerce order during import. If a gateway sent by BigCommerce is not yet listed in Marketplaces ‣ BigCommerce ‣ Configuration ‣ Payment Gateways, the connector creates it automatically the first time it is encountered, so you only need to fill in the workflow line for the new gateway.

Automatic Jobs Configurations

Automatic Jobs Configurations
  • Automatic Jobs Configurations allow for the automation of various tasks related to exporting and importing data between BigCommerce and Odoo. Each job is created inactive, so turn on Active for the jobs you want and set Interval Number and Interval Unit. Each row has a Run Manually button. Here’s an explanation of each Automatic Job.

  • Import Order

    • When this job is active, the connector imports new orders from BigCommerce to Odoo.

    • The orders placed by customers on your BigCommerce store are transferred to Odoo for further processing and fulfillment.

    • Order configuration and Workflow configuration will be used while importing and processing orders.

  • Export Order Status/Tracking Information

    • When this job is active, it exports the order status and tracking information from Odoo to BigCommerce.

    • Order updates, such as shipment status and tracking numbers, are sent for validated Delivery Orders.

  • Import Product’s Inventory

    • When this job is active, the connector imports the inventory levels of products from BigCommerce to Odoo.

    • The quantities are written for each matched product at the stock location mapped to each enabled BigCommerce location.

    • Validate Inventory Adjustment? configuration will be used while importing product’s inventory.

  • Export Product’s Inventory

    • When this job is active, it exports the inventory levels of products from Odoo to BigCommerce.

    • Only the listing items whose stock changed since the last export are sent.

    • Stock Based On configuration will be used while exporting stock.

  • Export Product’s Price

    • When this job is active, it exports the changed product prices from Odoo to BigCommerce.

    • Prices that changed in the instance pricelist since the last export are sent. Prices of 0 are not sent.

    • Pricelist will be used while exporting price to BigCommerce.

Note

It’s important not to schedule all your jobs to run at the same time interval because it can consume a significant amount of your system resources. Instead, it’s recommended to leave a gap between them. This helps ensure that your system resources are not over-used and can handle the workload more efficiently.

Notification & Alerts

Notification & Alerts
  • Activity Configuration

    When a queue job line process fails, the system creates an activity based on the specified configuration. By configuring Activity, Due Date In, and Responsible, the system can automatically generate an activity for the responsible person whenever a queue line fails. This helps ensure that appropriate follow-up actions are taken to address and resolve any issues or errors encountered during the queue processing.

  • Smart Notification Configuration

    Add a line for each user with Notify to, Type (All, Error or Success), Sticky, Order Import and Product Import. The user receives an in-app pop-up with the number of orders or products that were imported successfully or failed. Sticky keeps the pop-up on screen until it is closed.

Confirming the Instance

  • Click Test Connection first to verify the Store Hash and Access Token are valid. On success, Odoo shows a rainbow animation with the message Successfully Connected.

  • Once the form is filled in and the connection has been tested, click Confirm. The connector:

    • Imports the store currency and configures the pricelist accordingly.

    • Reads the store’s weight unit.

    • Imports the BigCommerce Order Statuses.

    • On the first confirmation only, imports Sales Channels, Locations, Tax Classes, Categories and Brands. These imports run while you wait for Confirm to finish.

    • Sets the instance state to Confirmed.

    Instance Confirmation