BigCommerce as a Channel

Table of Contents

How To Connect Listing Operations Order Operations

BigCommerce is a fully supported sales channel in Flxpoint, enabling direct integration with your store to manage product listings, inventory updates, order syncing, and fulfillment operations. This integration helps ensure accurate data flow and efficient operations between your BigCommerce store and Flxpoint.

How To Connect

Important Note: Ensure your BigCommerce store is fully set up before connecting.

The recommended connection method is BigCommerce API App (OAuth2). Use the API Bearer Token method only if OAuth2 is not suitable for your setup.

Verify that your BigCommerce store has the necessary API access enabled in the store settings.

If using the Bearer Token method, double-check your API credentials (Client ID, Client Secret, and Access Token) to avoid connection issues.

Many steps in this setup process can be skipped and configured later from the channel settings if needed.

📋 Phase 1: Initial Channel Setup +

Access Sales Channels

Create a New Channel

Click Create Channel (or Add Channel) and select BigCommerce from the channel list.

Tip: Having your BigCommerce account credentials ready will make this process smoother.

Configure Integration Type

In the Configure Integration Type screen, choose the processes you want to enable:

Sync Listings

Publish Listings

Get Orders

Sync Orders

Enter a Channel Name (e.g., "BigCommerce"), then click Save & Next.

🔐 Phase 2: Channel Connection & Authentication +

Set Up BigCommerce Connection

On the Connect Channel screen, set up a new BigCommerce connection:

Select your preferred connection type. We recommend BigCommerce API App (OAuth2) for most users.

For OAuth2: Enter your Store Hash and click Initiate OAuth2 Flow to log in to your BigCommerce account and grant access to Flxpoint.

For Bearer Token (if OAuth2 is not suitable): Enter your Store Hash, Client ID, and Access Token from BigCommerce.

Click Save Connection and optionally Test Connection to verify the setup.

Important: Ensure your BigCommerce API credentials are correct to avoid connection issues.

Confirm Integrations

In the Confirm Integrations screen, verify your selected processes (e.g., Sync Listings, Publish Listings, Get Orders, Sync Orders) and the BigCommerce connection. Check the box to acknowledge the information is correct, then click Save & Next.

🔄 Phase 3: Configuration & Feature Setup +

Set Pricing & Quantity Rules

In the Pricing & Quantity screen, create rules to set pricing and/or quantity for your listings:

Click Add Rule to create a new pricing or quantity rule if needed.

If no rules are needed, you can skip this step by clicking Skip and configure it later from the channel settings.

Click Save & Next to proceed.

Link Listings Settings

In the Link Listings: Settings screen, manage how to connect your listings in Flxpoint to those already listed on BigCommerce:

Choose whether to use default settings: Yes, Use Default or No, Customize.

Under Link After Building Listings, decide if Flxpoint should automatically attempt to link listings to existing ones on the channel after building (default is No).

You can skip this step by clicking Skip and configure it later from the channel settings.

Click Save & Next to proceed.

Sync Listings Settings

In the Sync Listings: Settings screen, configure the price, quantity, and/or status of listings on your BigCommerce channel:

Set the Linking Priority (e.g., Listing Variant SKU) to determine how Flxpoint matches listings (options include GTIN, MPN, SKU, UPC, etc.).

Select a Mapping Template (e.g., "Sync Listings 1") or create a new one if needed.

You can skip this step by clicking Skip and configure it later from the channel settings.

Click Save & Next to proceed.

Get Orders Settings

In the Get Orders: Settings screen, configure how to import orders and customer invoices from your BigCommerce channel:

Under Import FFL Details from BigCommerce via Automatic FFL App, choose Yes or No.

Select the Order Status to import (e.g., Incomplete, Pending, Awaiting Payment, Awaiting Pickup, Awaiting Shipment, Awaiting Fulfillment, Partially Refunded).

In Advanced Settings, set the Personal Identifying Information Retention (e.g., Indefinitely) and specify how far back to fetch orders with Get Orders Created Within the Last X Days (e.g., 14 days).

Select a Mapping Template (e.g., "Get Orders 4") or create a new one if needed.

You can skip this step by clicking Skip and configure it later from the channel settings.

Click Save & Next to proceed.

Automate Integrations

In the Automate Integrations screen, schedule how often integrations should run:

For Sync Listings, choose Yes to schedule automatic syncing of price, quantity, and/or status changes to existing listings.

For Publish Listings, choose Yes to schedule automatic publishing of new listings or overwriting existing ones.

For Get Orders, choose Yes to schedule automatic importing of orders into Flxpoint.

For Sync Orders, choose Yes to schedule automatic syncing of tracking updates to orders on your channel.

You can skip this step by clicking Skip and configure it later from the channel settings.

Click Save & Next to proceed.

✅ Phase 4: Finalize and Manage Channel +

Complete Additional Settings

Complete the remaining setup steps as needed:

In Publish Settings, configure settings for publishing listings if selected in Step 3.

In Order Fulfillment, set up order settings and shipping mappings.

In Advanced Workflows, configure custom automation for listing statuses or order handling.

In Listing Status, set up rules for managing listing statuses.

In Invoicing, configure invoice adjustments if needed.

These steps can be skipped by clicking Skip and configured later from the channel settings.

Click Save & Next to proceed through each step.

Manage Your BigCommerce Channel

Your BigCommerce channel is now set up! You can revisit it in Sales Channels to:

Start Import Listings to create and update listings and products in Flxpoint.

Start Get Orders to import new orders and send back acknowledgments.

Configure additional settings like Send Accounting Shipments, Publish Listings, Sync Orders, and Sync Listings as needed.

Adjust any skipped steps (e.g., Pricing & Quantity, Link Settings, Sync Settings, Automate Integrations) from the channel settings.

Next Steps: Monitor the initial sync progress in the Sales Channels section. You can adjust settings or enable additional operations as needed to optimize your BigCommerce integration.

Listing Operations

Import Listings

Supported | BigCommerce - Import Listings

Introduction to BigCommerce Import Listings Integration

Welcome to the BigCommerce Import Listings integration guide! This integration imports your product catalog from your BigCommerce store into your system, syncing titles, images, categories, and brands. It simplifies inventory management, keeping listings accurate and ready for publishing. Let’s get started!

The BigCommerce Import Listings integration enables you to:

Import product details, including titles, descriptions, variants, and images.
Replicate category structures up to 3 levels deep.
Map brands to products for organized catalog management.

This ensures your system reflects the latest BigCommerce product data.

The integration follows these steps:

1 Fetching Brands and Categories: GET calls to v3/catalog/brands and v3/catalog/categories retrieve brand and category data.
2 Fetching Products: GET call to v3/catalog/products?include=variants,images retrieves the product catalog.
3 Mapping Brands and Categories: Use product IDs to map brands and categories to products.
4 Syncing Data: Import data into your system, creating or updating listings.
5 Execution: Run manually with Run Sync or schedule (e.g., daily).

Pro Tip: Schedule daily imports to keep your catalog current.

Note: API failures pause the integration and trigger notifications.

Customize the integration with these settings:

Set New Listings to Paused: Pause new listings to verify data before syncing.
Master SKU Setup: Select a BigCommerce field (e.g., SKU) as the Master SKU identifier.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Product Import Scope: Create and update products/listings directly.

Note: Pausing new listings helps manage price and quantity accuracy.

Follow these steps:

1 Add the Integration: Go to Channels > BigCommerce > Integrations, select “Import Listings.”
2 Connect to BigCommerce: Provide Store Hash, initiate OAuth2 authentication, and install the Flxpoint app.
3 Configure Settings:
- Enable pausing new listings if needed.
- Select Master SKU field.
- Configure scheduling.
4 Run the Integration: Start with Run Sync or schedule.

This integration focuses on importing product listings and does not directly handle shipping mappings, which are typically managed in order-related integrations (e.g., Sync Orders). However:

Weights & Dimensions: Import weights (in kilograms) and dimensions (in centimeters) to support shipping calculations in your system.
Coordination: Ensure product data aligns with shipping configurations in other integrations for accurate fulfillment.

Note: Verify weight and dimension mappings to ensure compatibility with shipping settings.

This integration focuses on importing product listings and does not directly handle Federal Firearms License (FFL) details, as FFL compliance is typically managed during order processing (e.g., via the Get Orders integration). For FFL-related products:

Product Attributes: Import custom fields or attributes (e.g., “FFL Required”) to flag FFL items in your system.
Coordination: Ensure FFL-related product data is compatible with order processing integrations.

             Pro Tip: Coordinate with order-related integrations to manage FFL compliance effectively.
          

The integration supports:

Category Depth: Imports categories up to 3 levels via v3/catalog/categories.
Images: Retrieves images hosted on BigCommerce URLs.
Variants: Imports variant data (e.g., SKUs, prices) with include=variants.
Weights & Dimensions: Imports in kilograms and centimeters.
API Operations: Uses GET requests to catalog endpoints.
Scheduling: Manual or automated runs (e.g., daily).

A mapping template defines how data from BigCommerce orders is imported into your system.

Interface Overview

Screen labeled “Import Listings” at the top; name your template (e.g., “Import Listings 1”).
Buttons: Delete, Duplicate, Save.
Sections include mappings for:
- Product Fields: Fields like Name, SKU, Description.
- Variant Fields: Fields like Variant SKU, Variant Price.

Mapping Options

You can choose from the following options for each field:

Don’t Map: Ignore the field entirely.
Set To Empty: Clear any existing data in that field in your system.
Field: Map a field from BigCommerce (e.g., BigCommerce Product’s “Name”) to a field in your system.
Value: Set a constant value for all products.
Mapping Set: Apply a predefined transformation or mapping table.
Rules: Use conditional logic to modify fields based on specific criteria (more advanced).

               Recommendation: Ensure required fields like Name and SKU are mapped using the Field option to avoid import errors.
            

Complete Field Mappings

Below are the fields you can map from BigCommerce to your system:

Product Fields

BigCommerce Field	Maps To	Example	Purpose	Status
Name	Product Title	Luxury Toy Set	Product name	Required
SKU	Master SKU	TOY-001	Unique identifier	Required
Description	Product Description	Fun educational toy	Product description	Optional
Price	List Price	$19.99	Selling price	Optional
Inventory Level	Quantity	100	Stock quantity	Optional
UPC	UPC	123456789012	Universal Product Code	Optional
Weight	Weight	2.5	Weight in kg	Optional
Width	Width	12	Width in cm	Optional
Height	Height	10	Height in cm	Optional
Depth	Length	15	Length in cm	Optional
Images	Product Images	https://bigcommerce.com/toy.jpg	Product images	Optional
Categories	Category Path	Toys > Educational	Category hierarchy	Optional
Brand	Brand	Acme	Product brand	Optional

Variant Fields

BigCommerce Field	Maps To	Example	Purpose	Status
Variant SKU	Variant SKU	TOY-BLUE-001	Variant identifier	Optional
Variant Price	Variant List Price	$21.99	Variant selling price	Optional
Variant Inventory Level	Variant Quantity	50	Variant stock quantity	Optional
Variant UPC	Variant UPC	123456789013	Variant UPC	Optional
Variant Image	Variant Image	https://bigcommerce.com/toy-blue.jpg	Variant image	Optional

Practice Mapping

Here’s a quick example—if you map the “Name” field:

Be aware of these limitations:

Category Depth: Limited to 3 levels of category hierarchy.
API Rate Limits: Exceeding limits pauses the integration.
Image Hosting: Images are hosted on BigCommerce URLs.
Weights & Dimensions: Available only in kilograms and centimeters.

Troubleshoot issues with these steps:

Connection Issues: Verify Store Hash and Flxpoint app installation.
API Errors: Ensure v3/catalog/products, v3/catalog/brands, and v3/catalog/categories are accessible.
Rate Limits: Confirm you haven’t hit BigCommerce’s API limits.
Data Missing: Check API response for missing fields or incorrect parameters.
Contact Support: Reach out to Flxpoint or BigCommerce with error details.

Diagnostic Tip: API rate limit errors often cause import pauses.

Key information:

Date: As of 06:23 AM -04, May 27, 2025, this integration is operational.
SKU Mapping: Required to avoid import errors.
Categories: Supports up to 3 levels of depth.
Units: Weights in kilograms, dimensions in centimeters.
Images: Hosted on BigCommerce URLs.

Pro Tip: Use the pause new listings option to verify data before syncing.

Conclusion

With the BigCommerce Import Listings integration set up, your system will seamlessly pull in product data, including categories, brands, and images, keeping your catalog up to date. This automation lets you focus on growing your business while ensuring your listings are accurate and ready to go!

Sync & Link Listings

Supported | BigCommerce - Sync & Link Listings

Introduction to BigCommerce Sync & Link Listings Integration

Welcome to the BigCommerce Sync & Link Listings integration guide! This integration keeps your BigCommerce store’s product listings updated with the latest price, quantity, and status (PQS) data. It links listings using identifiers like SKU or UPC, and allows hiding or delisting products to control visibility. Let’s get started!

The BigCommerce Sync & Link Listings integration enables you to:

Update price, quantity, and status (PQS) for products and variants.
Link listings to BigCommerce products using identifiers like SKU, UPC, MPN, or GTIN.
Manage visibility by hiding or delisting products on the storefront.

This ensures your store reflects accurate and current listing data.

The integration follows these steps:

1 Linking Listings: Match listings to BigCommerce products using prioritized identifiers (e.g., SKU, UPC, MPN, GTIN).
2 Updating PQS: Send PQS updates via PUT to v3/catalog/products/{productId}/variants/{variantId} for price, inventory, and visibility.
3 Hiding Products: Configure hiding options (e.g., hide, keep accessible, redirect) for out-of-stock products.
4 Delisting Products: Delete linked products from BigCommerce, requiring republishing to restore.
5 Mapping Data: Map fields (e.g., Quantity to Inventory Level) for syncing.
6 Execution: Run manually with Run Sync or schedule (e.g., daily).

Pro Tip: Prioritize SKU for linking to ensure accurate product matching.

Note: API failures pause the integration and trigger notifications.

Customize the integration with these settings:

Linking Priority: Set identifier order (e.g., SKU, UPC, MPN, GTIN) for matching.
Hiding Behavior: Hide out-of-stock products, keep page accessible, redirect to category, or do nothing.
Automatic Stock Adjustment: Enable/disable stock adjustments for refunds/cancellations.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Mapping Template: Define which fields sync to BigCommerce (e.g., Quantity, Price).

Note: Configure hiding behavior to manage out-of-stock visibility.

Follow these steps:

1 Add the Integration: Go to Channels > BigCommerce > Integrations, select “Sync Listings.”
2 Connect to BigCommerce: Use an existing OAuth2 connection or set up a new one with Store Hash and Flxpoint app.
3 Configure Settings:
- Set linking priority (e.g., SKU first).
- Define hiding behavior for out-of-stock products.
- Enable stock adjustments if needed.
- Configure scheduling.
4 Create Mapping Template: Map fields to sync with BigCommerce (see Mapping Template Details).
5 Run the Integration: Start with Run Sync or schedule.

This integration focuses on syncing product listings (price, quantity, status) and does not directly handle shipping mappings, which are typically managed in order-related integrations (e.g., Sync Orders). However:

Estimated Shipping Cost: Map fields like “Estimated Shipping Cost” to BigCommerce to support shipping calculations in your store.
Coordination: Ensure product data aligns with shipping configurations in other integrations for accurate fulfillment.

Note: Verify shipping-related field mappings to ensure compatibility with BigCommerce settings.

This integration focuses on syncing and linking product listings and does not directly handle Federal Firearms License (FFL) details, as FFL compliance is typically managed during order processing (e.g., via the Get Orders integration). For FFL-related products:

Product Visibility: Use hiding or delisting options to control FFL product availability.
Coordination: Ensure FFL-related product data is compatible with order processing integrations.

             Pro Tip: Coordinate with order-related integrations to manage FFL compliance effectively.
          

The integration supports:

PQS Updates: Updates price, quantity, and status via v3/catalog/products/{productId}/variants/{variantId}.
Linking Identifiers: Supports SKU, UPC, MPN, GTIN for product matching.
Visibility Management: Hiding options (hide, accessible, redirect, do nothing) and delisting.
Stock Adjustments: Optional for refunds/cancellations.
Mapping Flexibility: Supports custom field mappings (e.g., Quantity to Inventory Level).
API Operations: Uses PUT requests for updates.
Scheduling: Manual or automated runs (e.g., daily).

Mapping templates define how data from your system is synced to BigCommerce.

Interface Overview

Screen labeled “Sync Listings” at the top; name your template (e.g., “Sync Listings 1”).
Buttons: Delete, Duplicate, Save.
Sections for mappings:
- From Value: Fields from your system (e.g., Listing Variant fields like Quantity, List Price).
- To BigCommerce Sync Product/Variant Field: Fields in BigCommerce (e.g., Inventory Level, Price).

Mapping Options

You can choose from the following options for each field:

Don’t Map: Ignore the field entirely.
Set To Empty: Clear any existing data in that field.
Field: Map a field from your system (e.g., Listing Variant’s “Quantity”) to a BigCommerce field.
Value: Set a constant value for all products.
Mapping Set: Apply a predefined transformation or mapping table.
Rules: Use conditional logic to modify fields based on specific criteria (more advanced).

               Recommendation: Always map required fields like Inventory Level and Price using the Field option to avoid sync errors.
            

Complete Field Mappings

Below are the fields you can map from your system to BigCommerce:

System Field	Maps To	Example	Purpose	Status
Custom Aggregate Field	Custom Field	Special Offer	Aggregated custom data	Optional
Estimated Cost	Cost Price	$10.50	Variant cost price	Optional
Estimated Dropship Fee	Dropship Fee	$2.00	Dropship fee	Optional
Estimated Shipping Cost	Shipping Cost	$5.00	Shipping cost	Optional
Quantity	Inventory Level	100	Stock quantity	Required
List Price	Price	$19.99	Selling price	Required
MAP	Map Price	$15.99	Minimum advertised price	Optional
MSRP	Retail Price	$24.99	Manufacturer’s suggested price	Optional
List Price	Sale Price	$17.99	Discounted price	Optional
Availability Description	Availability Description	In Stock	Availability status	Optional

Practice Mapping

Try mapping the “Listing Variant - Quantity” field:

Be aware of these limitations:

Identifier Accuracy: Incorrect SKU, UPC, MPN, or GTIN may cause linking failures.
Hiding Options: Limited to hide, keep accessible, redirect, or do nothing.
Delisting: Deleted products require republishing to restore.
API Rate Limits: Exceeding limits pauses the integration.

Troubleshoot issues with these steps:

Connection Issues: Verify Store Hash and Flxpoint app installation.
Linking Failures: Ensure SKU, UPC, MPN, or GTIN are correct and prioritized properly.
Sync Errors: Confirm v3/catalog/products/{productId}/variants/{variantId} is accessible and IDs are valid.
Missing Updates: Check mapping template to ensure required fields like Inventory Level and Price are mapped using the Field option.
Rate Limits: Verify you haven’t hit BigCommerce’s API limits.
Contact Support: Reach out to Flxpoint or BigCommerce with error details.

Diagnostic Tip: Linking errors often stem from mismatched identifiers.

Key information:

Date: As of 06:49 AM -04, May 27, 2025, this integration is operational.
Inventory Level: Must be mapped to avoid sync errors.
Linking: Requires accurate SKU, UPC, MPN, or GTIN.
Hiding/Delisting: Configurable to control visibility.
Stock Adjustments: Optional for refunds/cancellations.

Pro Tip: Regularly verify identifier accuracy to ensure successful linking.

Conclusion

With the BigCommerce Sync & Link Listings integration configured, your system will keep your BigCommerce store updated with accurate price, quantity, and status data, with flexible linking, hiding, and delisting options. Customize mappings and settings to maintain a seamless storefront. Happy syncing!

Publish Listings

Supported | BigCommerce - Publish Listings

Introduction to BigCommerce Publish Listings Integration

Welcome to the BigCommerce Publish Listings integration guide! This integration enables you to create and update product listings on your BigCommerce store, managing categories, brands, variants, and more. With options to truncate titles, overwrite listings, and handle images, it streamlines your catalog management. Let’s get started!

The BigCommerce Publish Listings integration enables you to:

Create new products or update existing ones on BigCommerce.
Manage categories and brands, creating them if they don’t exist.
Support variants, custom fields, attributes, and images for comprehensive listings.

This ensures your store’s catalog is accurate and ready for customers.

The integration follows these steps:

1 Fetching Categories and Brands: GET requests to v3/catalog/categories/tree and v3/catalog/brands retrieve category and brand structures.
2 Creating Categories and Brands: POST requests to v3/catalog/categories or v3/catalog/brands create missing categories/brands.
3 Creating Products: POST to v3/catalog/products creates products with required fields (name, weight, type, price).
4 Adding Variants: POST to v3/catalog/products/{bigCommerceProductId}/variants creates up to 250 variants.
5 Mapping Data: Map fields (e.g., Title to Name) to publish to BigCommerce.
6 Execution: Run manually with Run Sync or schedule.

             Pro Tip: Ensure required fields (name, weight, type, price) are mapped to avoid publishing errors.
          

Note: Missing required fields will cause product creation to fail.

Customize the integration with these settings:

Attribute Fields > 250 Characters: Truncate to 250 characters, skip custom fields, or fail product (default: Fail Product).
Override Product Name: Overwrite with Flxpoint name (Yes) or keep BigCommerce name (No).
Parent Images Direct Copy Behavior: Use all parent/variant images, parent and first variant image, only parent images, or only first parent image.
Truncate Title To 250: Truncate titles to 250 characters or fail product (default: Fail Product).
Overwrite Support: Enable to refresh complete product data.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).

Note: Adjust truncation settings to handle long titles or attributes.

Follow these steps:

1 Add the Integration: Go to Channels > BigCommerce > Integrations, select “Publish Listings.”
2 Connect to BigCommerce: Use an existing OAuth2 connection or set up a new one with Store Hash and Flxpoint app.
3 Configure Settings:
- Adjust title truncation, product name override, and image behavior.
- Enable overwrite support if needed.
- Configure scheduling.
4 Create Mapping Template: Map fields to publish to BigCommerce (see Mapping Template Details).
5 Run the Integration: Start with Run Sync or schedule.

This integration focuses on publishing product listings and does not directly handle shipping mappings, which are typically managed in order-related integrations (e.g., Sync Orders). However:

Weights & Dimensions: Map weights (in kilograms) and dimensions (in centimeters) to BigCommerce fields to support shipping calculations in your store.
Coordination: Ensure product data aligns with shipping configurations in other integrations for accurate fulfillment.

Note: Verify weight and dimension mappings to ensure compatibility with BigCommerce shipping settings.

This integration focuses on publishing product listings and does not directly handle Federal Firearms License (FFL) details, as FFL compliance is typically managed during order processing (e.g., via the Get Orders integration). For FFL-related products:

Product Attributes: Use custom fields or attributes (e.g., “FFL Required”) in the mapping template to flag FFL items.
Coordination: Ensure FFL-related product data is compatible with order processing integrations.

             Pro Tip: Coordinate with order-related integrations to manage FFL compliance effectively.
          

The integration supports:

Variants: Up to 250 variants per product via v3/catalog/products/{bigCommerceProductId}/variants.
Categories: Up to 3 levels of depth, managed via v3/catalog/categories.
Images: Multiple images (≤8 MB) with configurable “Parent Images Direct Copy Behavior.”
Custom Fields/Attributes: Mapped as parent fields or metafields.
Pricing & Currency: Supports cost, MSRP, list price, and client-specific pricing with currency conversion.
Inventory: Quantity updates from multiple warehouses.
Overwrites: Refreshes complete product data if enabled.
API Operations: Uses GET and POST requests to catalog endpoints.
Scheduling: Manual or automated runs (e.g., daily).

Mapping templates define how data from your system is published to BigCommerce.

Interface Overview

Screen labeled “Publish Listings” at the top; name your template (e.g., “Publish Listings 1”).
Buttons: Delete, Duplicate, Save.
Sections for mappings:
- From Value: Fields from your system (e.g., Listing Parent fields like Title, Parent SKU; Listing Variant fields like UPC, MSRP).
- To BigCommerce Product Field: Fields in BigCommerce (e.g., Name, UPC, Retail Price).

Mapping Options

You can choose from the following options for each field:

Don’t Map: Ignore the field entirely.
Set To Empty: Clear any existing data in that field on BigCommerce.
Field: Map a field from your system (e.g., Listing Parent’s “Title”) to a BigCommerce field.
Value: Set a constant value for all products.
Mapping Set: Apply a predefined transformation or mapping table.
Rules: Use conditional logic to modify fields based on specific criteria (more advanced).

               Recommendation: Always map required fields like Name, Weight, Type, and Price using the Field option to avoid publishing errors.
            

Complete Field Mappings

Below are the fields you can map from your system to BigCommerce, organized by category:

Listing Parent Fields

System Field	Maps To	Example	Purpose	Status
Attribute	Metafields or Custom Fields	Color: Blue	Product attributes	Optional
Brand	Brand	Acme	Product brand	Optional
Category 1	Category (Level 1)	Toys	Primary category	Optional
Category 2	Category (Level 2)	Educational	Secondary category	Optional
Category 3	Category (Level 3)	Building Sets	Tertiary category	Optional
Custom Field	Custom Fields	Material: Plastic	Custom product data	Optional
Description	Description	Fun toy set	Product description (HTML)	Optional
Image	Images	https://example.com/toy.jpg	Product images (≤8MB)	Optional
Parent SKU	SKU	TOY-001	Parent product SKU	Optional
Title	Name	Luxury Toy Set	Product name	Required

Listing Variant Fields

System Field	Maps To	Example	Purpose	Status
ASIN	ASIN	B01ABC123	Amazon Standard ID	Optional
Custom Aggregate Field	Custom Fields	Bundle: Yes	Aggregated custom data	Optional
Custom Field	Custom Fields	Size: Small	Variant custom data	Optional
Description	Variant Description	Small blue toy	Variant description	Optional
Dimensional Weight	Dimensional Weight	0.5	Shipping weight	Optional
Estimated Cost	Cost Price	$10.00	Variant cost	Optional
Estimated Dropship Fee	Dropship Fee	$2.00	Dropship fee	Optional
Estimated Shipping Cost	Shipping Cost	$5.00	Shipping cost	Optional
GTIN	GTIN	0123456789012	Global Trade Item Number	Optional
Height	Height	10	Height in cm	Optional
Image	Variant Image	https://example.com/toy-blue.jpg	Variant image (≤8MB)	Optional
Length	Length	15	Length in cm	Optional
List Price	Sale Price	$19.99	Discounted price	Optional
MAP	Minimum Advertised Price	$18.99	Minimum advertised price	Optional
MPN	MPN	TOY-MPN123	Manufacturer Part Number	Optional
MSRP	Retail Price	$24.99	Manufacturer’s suggested price	Optional
Master SKU	Master SKU	TOY-MASTER-001	Master SKU for variants	Optional
Option	Variant Option	Color: Blue	Variant option (≤250)	Optional
Quantity	Inventory Level	100	Stock quantity	Optional
SKU	Variant SKU	TOY-BLUE-001	Variant SKU	Optional
Title	Variant Name	Blue Luxury Toy	Variant name	Optional
UPC	UPC	123456789012	Universal Product Code	Optional
Weight	Weight	2.5	Weight in kg	Required
Width	Width	12	Width in cm	Optional

Additional Fields

System Field	Maps To	Example	Purpose	Status
Type	Type	physical	Product type (physical/digital)	Required
Price	Price	$19.99	Product price	Required

Practice Mapping

Try mapping the “Listing Parent - Title” field:

Be aware of these limitations:

Required Fields: Name, weight, type, and price are mandatory.
Title/Attribute Limits: Limited to 250 characters (configurable via truncation settings).
Variant Limit: Up to 250 variants per product.
Image Size: Maximum 8 MB per image.
Category Depth: Up to 3 levels supported.

Troubleshoot issues with these steps:

Connection Issues: Verify Store Hash and Flxpoint app installation.
Missing Required Fields: Ensure name, weight, type, and price are mapped using the Field option.
Title/Attribute Errors: Adjust “Truncate Title To 250” or “Attribute Fields > 250 Characters” settings.
Image Failures: Confirm images are under 8 MB.
Variant Errors: Ensure variant count is ≤250.
API Issues: Verify access to v3/catalog/products and v3/catalog/categories, and check API rate limits.
Contact Support: Reach out to Flxpoint or BigCommerce with error details.

Diagnostic Tip: Missing required fields often cause publishing failures.

Key information:

Date: As of 06:44 AM -04, May 27, 2025, this integration is operational.
Name: Must be mapped to avoid publishing errors.
Variants: Up to 250 supported per product.
Images: Limited to 8 MB; configurable via image behavior settings.
Categories: Supports up to 3 levels of depth.

             Pro Tip: Regularly check mapping templates to ensure all required fields are mapped correctly.
          

Conclusion

With the BigCommerce Publish Listings integration set up, you can efficiently create and update product listings on your BigCommerce store. From managing categories and brands to handling variants, images, and custom fields, this integration ensures your store’s catalog is accurate and ready for customers—all with the flexibility to customize how your data is published!

Order Operations

Get Orders

Supported | BigCommerce - Get Orders

Introduction to BigCommerce Get Orders Integration

Welcome to the BigCommerce Get Orders integration guide! This integration imports orders from your BigCommerce store into your system, centralizing order data for efficient management and fulfillment. With support for multi-status imports, FFL details, digital items, gift certificates, and customizable mappings, including the new State Code field, you’ll streamline your workflow. Let’s get started!

The BigCommerce Get Orders integration connects your system to your BigCommerce store to:

Retrieve orders based on status, including support for multiple statuses (e.g., Incomplete, Pending).
Fetch associated products, shipping/billing addresses (including State Code), and FFL details (if enabled).
Handle special cases like refunded items, gift certificates, and digital items.
Map order data to your system’s fields for seamless integration.

This ensures your system stays updated with order data, enhancing sales, fulfillment, and customer management efficiency.

The integration follows a structured process:

1 Fetching Orders: A GET request to v2/orders retrieves orders in batches of 50, using status_id to filter by status.
2 Fetching Products: A GET request to v2/orders/{orderId}/products retrieves product details (e.g., SKU, quantity, price).
3 Fetching Shipping Addresses: A GET request to v2/orders/{orderId}/shipping_addresses retrieves addresses, including State Code, supporting multiple addresses per line item if enabled.
4 Importing FFL Details: If enabled, FFL details are retrieved from Order Comments via the Automatic FFL app.
5 Mapping Data: A mapping template maps data (e.g., SKU “PROD-001”, State Code “CA”) to your system’s fields.
6 Execution: Run manually via Run Sync or schedule (e.g., daily/weekly).

Pro Tip: Use multi-status imports to capture orders across different stages.

Note: Payment information is ignored for filtering; orders are imported based on status.

Customize the integration with these settings:

Enable Get Orders: Toggle to import orders.
Import FFL Details: Enable to retrieve FFL details from Order Comments via Automatic FFL app.
Order Status: Select one or more statuses (e.g., Incomplete, Pending, Awaiting Payment).
Time Frame: Fetch orders created within a period (default: 14 days).
PII Retention: Set retention period (e.g., Indefinitely, 30/60/90 days post-shipment).
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Currency Conversion: Add rules in the mapping template to convert totals (e.g., to USD).
Custom Fields: Map fields like customer notes or staff notes in the mapping template.

Note: A 7-day time frame speeds up imports for recent orders.

Follow these steps to set up the integration:

1 Add the Integration: Go to Channels > BigCommerce > Integrations, select “Get Orders.”
2 Connect to BigCommerce: Use an existing OAuth2 connection or set up a new one with Store Hash and Flxpoint app.
3 Configure Settings:
- Enable FFL details import if needed.
- Select order statuses to import.
- Set PII retention period.
- Specify time range for fetching orders.
- Enable scheduling if desired.
4 Create Mapping Template: Define how fields from BigCommerce are imported into your system (see Mapping Template Details).
5 Run the Integration: Start with Run Sync or schedule.

Map BigCommerce’s “Shipping Method” field to Flxpoint shipping policies:

“Standard Shipping” to Flxpoint “Standard” policy.
“Express Shipping” to Flxpoint “Express” policy.

This ensures accurate alignment of shipping methods for fulfillment.

Note: Verify mappings in Flxpoint’s shipping management section to match BigCommerce methods.

For orders requiring Federal Firearms License (FFL) compliance:

FFL Details Import: Enable “Import FFL Details” to retrieve FFL information from Order Comments via the Automatic FFL app.
Compliance Checks: Configure rules in source settings (e.g., flag items like “Firearms”) to ensure compliance.
Manual Review: Orders with FFL details may require manual verification in Flxpoint.

This ensures compliance with firearm regulations during order processing.

Pro Tip: Regularly check Order Comments for accurate FFL data.

The integration supports:

Order & Payment Statuses: Imported based on status (e.g., Awaiting Payment); payment data ignored for filtering.
Order Acknowledgment: Handled manually in Flxpoint post-import.
Order Receipt/Invoice & Currency: Configured by store location; supports currency conversion rules (e.g., to USD).
Shipping Selection: Mapped in Flxpoint’s shipping management section.
Custom Fields: Supported (e.g., customer notes, staff notes).
PII Restrictions: Configurable retention periods (e.g., 30/60/90 days).
Digital Items/Donations: Supported with type “digital” or generated SKUs for gift certificates.
Weight & Dimensions: Retrieved in store units (e.g., kg, cm).
Batch Processing: Imports 50 orders per batch.

Mapping templates define how BigCommerce order data is imported into your system.

Interface Overview

Screen labeled “Get Orders” at the top; name your template (e.g., “Get Orders 1”).
Buttons: Delete, Duplicate, Save.
Sections for mappings:
- Billing Address: Street Address 1, City, State, State Code, etc.
- Shipping Address: Shipping Method, Country, State, State Code, etc.
- Line Items: SKU, Quantity, Price Ex Tax, etc.
- Order Details: Order ID, Date Created, Total Inc Tax, etc.

Mapping Options

You can choose from the following options for each field:

Don’t Map: Ignore the field entirely.
Set To Empty: Clear any existing data in that field in your system.
Field: Map a field from BigCommerce (e.g., BigCommerce Billing Address’s “Street Address 1”) to a field in your system.
Value: Set a constant value for all orders.
Mapping Set: Apply a predefined transformation or mapping table.
Rules: Use conditional logic to modify fields based on specific criteria (more advanced).

               Recommendation: Always map required fields like Date Created, SKU, and Quantity using the Field option to avoid import errors.
            

Complete Field Mappings

Below are the fields you can map from BigCommerce to your system, organized by category:

Billing Address Fields

BigCommerce Field	Maps To	Example	Purpose	Status
City	Billing Address - City	San Francisco	Specifies billing city	Optional
Company	Billing Address - Company	TechCorp Inc.	Identifies billing company	Optional
Country	Billing Address - Country	United States	Specifies billing country	Optional
Country Iso 2	Billing Address - Country Iso 2	US	Provides country code	Optional
Email	Billing Address - Email	customer@example.com	Contact email for billing	Optional
First Name	Billing Address - First Name	John	Identifies buyer	Optional
Last Name	Billing Address - Last Name	Doe	Identifies buyer	Optional
Phone	Billing Address - Phone	555-123-4567	Contact phone for billing	Optional
State	Billing Address - State	California	Specifies billing state	Optional
State Code	Billing Address - State Code	CA	Two-letter state abbreviation	Optional
Street Address 1	Billing Address - Street Address 1	123 Main St	Primary billing address	Optional
Street Address 2	Billing Address - Street Address 2	Apt 4B	Secondary billing address	Optional
Zip	Billing Address - Zip	94105	Specifies billing ZIP code	Optional

Shipping Address Fields

BigCommerce Field	Maps To	Example	Purpose	Status
City	Shipping Address - City	Los Angeles	Specifies shipping city	Optional
Company	Shipping Address - Company	TechCorp Inc.	Identifies shipping company	Optional
Country	Shipping Address - Country	United States	Specifies shipping country	Optional
Country Iso 2	Shipping Address - Country Iso 2	US	Provides country code	Optional
Email	Shipping Address - Email	customer@example.com	Contact email for shipping	Optional
First Name	Shipping Address - First Name	Jane	Identifies recipient	Optional
Last Name	Shipping Address - Last Name	Smith	Identifies recipient	Optional
Phone	Shipping Address - Phone	555-987-6543	Contact phone for shipping	Optional
Shipping Method	Shipping Address - Shipping Method	Standard Shipping	Specifies shipping method	Optional
State	Shipping Address - State	California	Specifies shipping state	Optional
State Code	Shipping Address - State Code	CA	Two-letter state abbreviation	Optional
Street Address 1	Shipping Address - Street Address 1	456 Oak St	Primary shipping address	Optional
Street Address 2	Shipping Address - Street Address 2	Suite 200	Secondary shipping address	Optional
Zip	Shipping Address - Zip	90001	Specifies shipping ZIP code	Optional

Line Item Fields

BigCommerce Field	Maps To	Example	Purpose	Status
Base Cost Price	Line Item - Base Cost Price	$10.00	Base cost excluding tax	Optional
Base Price	Line Item - Base Price	$20.00	Base price excluding tax	Optional
Base Total	Line Item - Base Total	$40.00	Base total cost excluding tax	Optional
Base Wrapping Cost	Line Item - Base Wrapping Cost	$2.00	Base gift wrapping cost	Optional
Bin Picking Number	Line Item - Bin Picking Number	BIN-123	Identifies bin location	Optional
Brand	Line Item - Brand	Acme	Specifies item brand	Optional
Cost Price Ex Tax	Line Item - Cost Price Ex Tax	$10.00	Cost price excluding tax	Optional
Cost Price Inc Tax	Line Item - Cost Price Inc Tax	$10.80	Cost price including tax	Optional
Cost Price Tax	Line Item - Cost Price Tax	$0.80	Tax on cost price	Optional
Fixed Shipping Cost	Line Item - Fixed Shipping Cost	$5.00	Fixed shipping cost	Optional
Fulfillment Source	Line Item - Fulfillment Source	Warehouse A	Specifies fulfillment source	Optional
Id	Line Item - Id	1	Unique line item ID	Optional
Name	Line Item - Name	Blue Widget	Item name	Optional
Price Ex Tax	Line Item - Price Ex Tax	$20.00	Price excluding tax	Optional
Price Inc Tax	Line Item - Price Inc Tax	$21.60	Price including tax	Optional
Price Tax	Line Item - Price Tax	$1.60	Tax on price	Optional
Quantity	Line Item - Quantity	2	Sets ordered units	Required
Quantity Refunded	Line Item - Quantity Refunded	1	Quantity refunded	Optional
Quantity Shipped	Line Item - Quantity Shipped	1	Quantity shipped	Optional
Refund Amount	Line Item - Refund Amount	$20.00	Amount refunded	Optional
SKU	Line Item - SKU	PROD-001	Identifies product	Required
Total Ex Tax	Line Item - Total Ex Tax	$40.00	Total cost excluding tax	Optional
Total Inc Tax	Line Item - Total Inc Tax	$43.20	Total cost including tax	Optional
Total Tax	Line Item - Total Tax	$3.20	Total tax amount	Optional
Type	Line Item - Type	physical	Item type (e.g., physical, digital)	Optional
UPC	Line Item - UPC	012345678905	Item UPC	Optional
Weight	Line Item - Weight	1.5	Item weight (e.g., kg)	Optional
Wrapping Cost Ex Tax	Line Item - Wrapping Cost Ex Tax	$2.00	Wrapping cost excluding tax	Optional
Wrapping Cost Inc Tax	Line Item - Wrapping Cost Inc Tax	$2.16	Wrapping cost including tax	Optional
Wrapping Cost Tax	Line Item - Wrapping Cost Tax	$0.16	Tax on wrapping cost	Optional
Wrapping Message	Line Item - Wrapping Message	Happy Birthday!	Gift wrapping message	Optional
Wrapping Name	Line Item - Wrapping Name	Festive Wrap	Name of wrapping option	Optional

Order Fields

BigCommerce Field	Maps To	Example	Purpose	Status
Base Handling Cost	Order - Base Handling Cost	$3.00	Base handling cost excluding tax	Optional
Base Shipping Cost	Order - Base Shipping Cost	$5.00	Base shipping cost excluding tax	Optional
Base Wrapping Cost	Order - Base Wrapping Cost	$2.00	Base wrapping cost excluding tax	Optional
Coupon Discount	Order - Coupon Discount	$10.00	Total coupon discount	Optional
Currency Code	Order - Currency Code	USD	Order currency	Optional
Currency Exchange Rate	Order - Currency Exchange Rate	1.0	Currency exchange rate	Optional
Custom Status	Order - Custom Status	Custom Processing	Custom order status	Optional
Customer Locale	Order - Customer Locale	en-US	Customer language/region	Optional
Customer Message	Order - Customer Message	Please ship quickly!	Customer notes	Optional
Date Created	Order - Date Created	2025-04-07T10:00:00Z	Order creation date	Required
Date Modified	Order - Date Modified	2025-04-07T12:00:00Z	Last modification date	Optional
Date Shipped	Order - Date Shipped	2025-04-08T09:00:00Z	Shipping date	Optional
Default Currency Code	Order - Default Currency Code	USD	Store default currency	Optional
Discount Amount	Order - Discount Amount	$5.00	Total discount applied	Optional
Ebay Order Id	Order - Ebay Order Id	EBAY-12345	eBay order identifier	Optional
External Source	Order - External Source	eBay	External order source	Optional
Geo IP Country	Order - Geo IP Country	United States	Customer IP country	Optional
Geo IP Country Iso2	Order - Geo IP Country Iso2	US	Customer IP country code	Optional
Gift Card Amount	Order - Gift Card Amount	$25.00	Gift card payment amount	Optional
Gift Certificate Amount	Order - Gift Certificate Amount	$10.00	Gift certificate payment	Optional
Handling Cost Ex Tax	Order - Handling Cost Ex Tax	$3.00	Handling cost excluding tax	Optional
Handling Cost Including Tax	Order - Handling Cost Inc Tax	$3.24	Handling cost including tax	Optional
Handling Cost Tax	Order - Handling Cost Tax	$0.24	Tax on handling cost	Optional
Items Total	Order - Items Total	3	Total number of items	Optional
Order ID	Order - Order ID	12345	Unique order identifier	Optional
Order Source	Order - Order Source	manual	Order source (e.g., direct)	Optional
Payment Method	Order - Payment Method	Credit Card	Payment method used	Optional
Payment Status	Order - Payment Status	paid	Payment status	Optional
Refunded Amount	Order - Refunded Amount	$20.00	Total refunded amount	Optional
Shipping Address Count	Order - Shipping Address Count	1	Number of shipping addresses	Optional
Shipping Cost Ex Tax	Order - Shipping Cost Ex Tax	$5.00	Shipping cost excluding tax	Optional
Shipping Cost Including Tax	Order - Shipping Cost Inc Tax	$5.40	Shipping cost including tax	Optional
Shipping Cost Tax	Order - Shipping Cost Tax	$0.40	Tax on shipping cost	Optional
Staff Notes	Order - Staff Notes	Expedited shipping requested	Staff notes on order	Optional
Status	Order - Status	Awaiting Payment	Order status	Optional
Store Credit Amount	Order - Store Credit Amount	$15.00	Store credit payment	Optional
Store Default Currency Code	Order - Store Default Currency Code	USD	Store default currency	Optional
Store Default To Transactional Exchange Rate	Order - Exchange Rate	1.0	Default to transactional rate	Optional
Subtotal Ex Tax	Order - Subtotal Ex Tax	$90.00	Subtotal excluding tax	Optional
Subtotal Including Tax	Order - Subtotal Inc Tax	$97.20	Subtotal including tax	Optional
Subtotal Tax	Order - Subtotal Tax	$7.20	Tax on subtotal	Optional
Total Ex Tax	Order - Total Ex Tax	$95.00	Total excluding tax	Optional
Total Inc Tax	Order - Total Inc Tax	$102.60	Total including tax	Optional
Total Tax	Order - Total Tax	$7.60	Total tax amount	Optional
Wrapping Cost Ex Tax	Order - Wrapping Cost Ex Tax	$2.00	Wrapping cost excluding tax	Optional
Wrapping Cost Inc Tax	Order - Wrapping Cost Inc Tax	$2.16	Wrapping cost including tax	Optional
Wrapping Cost Tax	Order - Wrapping Cost Tax	$0.16	Tax on wrapping cost	Optional

Practice Mapping

Try mapping the “Line Item - Quantity” field:

Be aware of these limitations:

Missing SKUs: Orders without SKUs will not be saved in Flxpoint.
Multiple Shipping Addresses: If enabled, each line item may have a unique shipping address.
Digital Items: Imported as line items with type “digital.”
Gift Certificates: Use generated SKUs if none provided:
- With product name: name + "-" + order item ID.
- With same names: type + "-" + order item ID.
Order Acknowledgement: Must be handled manually in Flxpoint.
Weights & Dimensions: Retrieved in store units (e.g., kilograms, centimeters); ensure mapping alignment.

If issues arise, try these steps:

Verify Connection: Ensure BigCommerce connection (Store Hash, Flxpoint app) is active with valid OAuth2 credentials.
Check API Access: Confirm access to v2/orders, v2/orders/{orderId}/products, v2/orders/{orderId}/shipping_addresses. Check API rate limits.
SKU Issues: If an order fails due to missing SKU, verify line item in BigCommerce. For gift certificates:
- If type is “giftcertificate” and no SKU:
  - With name: name + "-" + order item ID.
  - With same names: type + "-" + order item ID.
Refunded Items: Ensure line item quantity and quantity refunded fields are mapped to calculate effective quantity.
FFL Details: If not importing, confirm “Import FFL details” is enabled and details exist in Order Comments.
Multiple Shipping Addresses: If enabled but missing, ensure “BigCommerce Shipping Address” fields are mapped per line item.
Quantity Not Importing:
- Ensure Line Item - Quantity is mapped using the Field option.
- Unmapped Quantity may cause:
  Cannot invoke "java.lang.Integer.intValue()" because the return value of "BigCommerceProductDto.getQuantity()" is null
- Fix: Go to Channels > BigCommerce > Templates > Get Orders > Field Mapping, map Quantity, save, and re-run.
State Code Not Importing: Ensure Billing Address - State Code and Shipping Address - State Code are mapped using the Field option.
Sync Not Running: Check schedule or run manually.
Review Logs: Check “View Logs” for errors.
Contact Support: Reach out to Flxpoint or BigCommerce with error details.

Diagnostic Tip: Check API rate limits if orders import inconsistently.

Key information:

Date: As of 06:26 AM -04, May 27, 2025, this integration is operational.
Quantity: Must be mapped to avoid import errors.
FFL Details: Imported from Order Comments if enabled.
Multi-Status Support: Import orders across multiple statuses.
Digital Items/Gift Certificates: Supported with generated SKUs.
PII Retention: Configurable to comply with privacy requirements.
Currency: Set by store location; conversion rules can be added.
Order Acknowledgement: Available in Flxpoint post-import.
🆕 State Code Mapping: Map State Code for Billing and Shipping Addresses to capture two-letter state abbreviations (e.g., CA, NY) if available in BigCommerce data.

             Pro Tip: Regularly check import logs to ensure all data, especially Quantity, SKU, and State Code, is correct.
          

Conclusion

The BigCommerce Get Orders integration centralizes your orders in Flxpoint, with flexible filters, FFL support, and mapping, including the new State Code field, for efficient fulfillment. Customize settings and mappings to align with your workflows, making order management more accurate and seamless!

Sync Orders

Supported | BigCommerce - Sync Orders

Introduction to BigCommerce Sync Orders Integration

Welcome to the BigCommerce Sync Orders integration guide! This integration synchronizes order data and shipment updates between your system and BigCommerce store, ensuring accurate order statuses and customer notifications. Using the BigCommerce v2 API, it streamlines fulfillment by updating tracking numbers, shipping providers, and order statuses. Let’s get started!

The BigCommerce Sync Orders integration enables you to:

Sync order data and update shipment details, such as tracking numbers and shipping providers.
Use the BigCommerce v2 API to create shipments via POST requests to v2/orders/{order_id}/shipments.
Automatically update order statuses (e.g., "Partially Shipped" or "Shipped") based on shipment progress.
Ensure BigCommerce notifies customers of shipment updates if store notifications are enabled.

This streamlines order fulfillment and keeps your store in sync with shipment data.

The integration follows these steps:

1 Connecting to BigCommerce: Establish a connection using OAuth2 authentication to access your store.
2 Syncing Orders: Synchronize orders between your system and BigCommerce for up-to-date data.
3 Updating Shipments: Send shipment details (e.g., tracking number) via POST to v2/orders/{order_id}/shipments.
4 Partial Shipments: Update status to "Partially Shipped" for partial shipments; set to "Shipped" when complete.
5 Customer Notifications: BigCommerce sends shipment emails if notifications are enabled.
6 Mapping Data: Map shipment fields (e.g., Tracking Number) to BigCommerce fields.

             Pro Tip: Ensure shipping providers match those in your BigCommerce store to avoid sync errors.
          

Note: The integration does not interact with the "Notify Customer" flag.

Customize the integration with these settings:

Shipping Provider Handling: Send as null if the provider isn’t enabled in BigCommerce to avoid errors.
Partial Shipment Updates: Enable to mark orders as "Partially Shipped" until fully shipped.
Mapping Template: Define which shipment fields sync to BigCommerce.
Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).

Note: Verify shipping providers in BigCommerce settings for seamless syncing.

Follow these steps:

1 Add the Integration: Go to Channels > BigCommerce > Integrations, select “Sync Orders.”
2 Connect to BigCommerce: Use an existing OAuth2 connection or set up a new one with Store Hash and Flxpoint app.
3 Configure Settings:
- Set shipping provider handling (e.g., send as null if unavailable).
- Enable partial shipment updates.
- Configure scheduling.
4 Create Mapping Template: Map fields to sync with BigCommerce (see Mapping Template Details).
5 Run the Integration: Start with Run Sync or schedule.

Map BigCommerce’s “Shipping Method” field to Flxpoint shipping policies:

“Standard Shipping” to Flxpoint “Standard” policy.
“Express Shipping” to Flxpoint “Express” policy.

This ensures accurate alignment of shipping methods for shipment updates.

Note: Verify mappings in Flxpoint’s shipping management section to match BigCommerce methods.

This integration focuses on syncing order and shipment data and does not directly handle Federal Firearms License (FFL) details, as FFL information is typically managed during order import (e.g., via the Get Orders integration). For FFL-compliant orders:

FFL Details: Ensure FFL data is included in order comments during order import for reference in shipment updates.
Compliance Checks: Configure rules in source settings (e.g., flag items like “Firearms”) to ensure compliance during fulfillment.

             Pro Tip: Coordinate with the Get Orders integration to ensure FFL details are available for syncing.
          

The integration supports:

Partial Shipments: Updates statuses to “Partially Shipped” or “Shipped” based on progress.
Customer Notifications: Handled by BigCommerce if store notifications are enabled.
Shipping Providers: Must match BigCommerce settings or be sent as null.
API Operations: Uses POST requests to v2/orders/{order_id}/shipments.
Mapping Flexibility: Supports custom field mappings (e.g., Tracking Number, Shipping Method).
Scheduling: Manual or automated runs (e.g., daily).

Mapping templates define how shipment data from your system is synced to BigCommerce.

Interface Overview

Screen labeled “Sync Orders” at the top; name your template (e.g., “Sync Orders 1”).
Buttons: Delete, Duplicate, Save.
Sections for mappings:
- From Value: Fields from your system (e.g., Shipment fields like Tracking Number, Shipping Method).
- To BigCommerce Shipment Field: Fields in BigCommerce (e.g., Tracking Number, Shipping Method).

Mapping Options

You can choose from the following options for each field:

Don’t Map: Ignore the field entirely.
Set To Empty: Clear any existing data in that field.
Field: Map a field from your system (e.g., Shipment’s “Tracking Number”) to a BigCommerce field.
Value: Set a constant value for all shipments.
Mapping Set: Apply a predefined transformation or mapping table.
Rules: Use conditional logic to modify fields based on specific criteria (more advanced).

               Recommendation: Always map the Tracking Number field using the Field option to avoid sync errors.
            

Complete Field Mappings

Below are the fields you can map from your system to BigCommerce:

System Field	Maps To	Example	Purpose	Status
Comments	Shipment - Note	Shipped via priority mail	Additional shipment notes	Optional
Date Created	Shipment - Shipped At	2025-05-26T10:00:00Z	Shipment creation date	Optional
Merchant Shipping Cost	Shipment - Shipping Cost	$5.00	Merchant shipping cost	Optional
Shipping Method	Shipment - Method	Standard Shipping	Shipping method used	Optional
Shipping Provider	Shipment - Carrier	U.P.S.	Shipping carrier	Optional
Tracking Link	Shipment - Tracking URL	https://track.ups.com/123456	Tracking URL	Optional
Tracking Number	Shipment - Tracking Number	1Z999AA10123456784	Tracks shipment	Required
Tracking Carrier	Shipment - Carrier	UPS	Carrier for tracking	Optional

Note: For accepted carrier values, refer to the Accepted Carrier Values CSV.

Shipping Provider Configuration

If a valid shipping provider exists in your BigCommerce store, configure it directly in the store’s settings. If no valid provider is detected, use the Set To Empty option to clear the Shipping Provider field and avoid errors.

Configure a valid shipping provider in BigCommerce settings.

Use “Set To Empty” to clear the Shipping Provider field if no valid carrier is detected.

Practice Mapping

Try mapping the “Tracking Number” field:

Be aware of these limitations:

Shipping Provider Mismatch: Providers must match those enabled in BigCommerce, or send as null.
Manual Order Item Updates: May not trigger customer notifications unless configured in BigCommerce.
Notify Customer Flag: Not directly managed by the integration; relies on BigCommerce settings.
Partial Shipments: Requires careful tracking to update statuses correctly.

Troubleshoot issues with these steps:

Invalid Shipping Provider: Use “Set To Empty” for the Shipping Provider field in the mapping template if not enabled in BigCommerce.
Orders Not Syncing: Verify OAuth2 authentication and Store Hash.
API Errors: Ensure v2/orders/{order_id}/shipments is accessible and order ID is correct.
Missing Shipment Data: Check mapping template to ensure required fields like Tracking Number are mapped using the Field option.
Rate Limits: Confirm you haven’t hit BigCommerce’s API limits.
Sync Not Running: Check schedule or run manually.
Contact Support: Reach out to Flxpoint or BigCommerce with error details.

Diagnostic Tip: Invalid provider errors often stem from unmapped or mismatched shipping providers.

Key information:

Date: As of 06:37 AM -04, May 27, 2025, this integration is operational.
Tracking Number: Must be mapped to avoid sync errors.
Partial Shipments: Supported with status updates to “Partially Shipped” or “Shipped.”
Customer Notifications: Handled by BigCommerce if enabled.
Shipping Provider: Must match BigCommerce settings or be sent as null.

             Pro Tip: Regularly verify shipping provider settings in BigCommerce to ensure smooth syncing.
          

Conclusion

With the BigCommerce Sync Orders integration configured, your system will keep your BigCommerce store updated with the latest order and shipment data. You’ll be able to manage partial shipments, update tracking information, and ensure customers are notified automatically—all while maintaining accurate order statuses with minimal manual effort!

Flxpoint Knowledge

How To Connect

Listing Operations

Import Listings

Sync & Link Listings

Publish Listings

Order Operations

Get Orders

Sync Orders

Related Articles