BigCommerce as a Channel

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

📋 Phase 1: Initial Channel Setup +
Access Channels Section
Log into your Flxpoint account and navigate to the Channels section.
Add New Channel
Click on + Add Channel to begin your BigCommerce integration.
Select BigCommerce
In the popup, choose BigCommerce as your channel and enter a channel name. Then click Continue.
Choose Authentication Method
Select your preferred authentication method and click Continue.
OAuth2 (Recommended): Choose this method for the easiest setup.
API Key (Advanced): Choose this method if OAuth2 is not suitable.
BigCommerce OAuth2 or API Key Selection
🔐 Phase 2: BigCommerce Authentication +
Authenticate OAuth2
For OAuth2: Enter your BigCommerce Store Hash in the provided field and click Continue.
Your Store Hash can be found in your BigCommerce admin panel URL (e.g., store-abc123 in https://store-abc123.mybigcommerce.com).
Authenticate API Key
For API Key: Obtain your Client ID, Access Token, and Store Hash:
Log into your BigCommerce admin panel.
Navigate to Settings > API Accounts.
Click Create API Account and select Create V2/V3 API Token.
Enter a name for the API account (e.g., "Flxpoint Integration").
Configure the API scopes with the necessary permissions (e.g., Products, Orders, Customers) and save.
Copy the Client ID, Access Token, and Store Hash from the generated credentials.
In Flxpoint, enter the Store Hash, Client ID, and Access Token in the respective fields and click Continue.
Complete OAuth2 Authentication
For OAuth2: You’ll be redirected to BigCommerce to install the Flxpoint app. Select Existing BigCommerce store and click Log in, or choose New to BigCommerce? to sign up.
Tip: Ensure you have your BigCommerce admin credentials ready for this step.
Authorize Flxpoint
For OAuth2: Log in with your BigCommerce admin credentials and grant the required permissions to Flxpoint to complete the installation.
For API Key: Skip this step as authorization is handled via the API credentials entered previously.
🔄 Phase 3: Configuration & Integration Setup +
Review Connection
Once authenticated, return to Flxpoint. Review the connection details and click Continue to proceed with the setup wizard.
Configure Integration Settings
Configure your integration settings:
Import Listings: Enable to import product listings from BigCommerce. Set the Master SKU field (e.g., BigCommerce Field: SKU) and enable Set New Listings to Paused if desired.
Publish Listings: Enable to create and publish listings to BigCommerce. Configure settings like Parent Images Direct Copy Behavior and Truncate Title to 250.
Sync Listings: Enable to sync pricing and quantity data with BigCommerce. Set the linking identifier (e.g., Flxpoint Listing: SKU to BigCommerce Listing: Variant - SKU).
Get Orders: Enable to import orders from BigCommerce. Select order statuses (e.g., Incomplete, Pending) and set the time range (e.g., 14 days).
Sync Orders: Enable to sync order and shipment data with BigCommerce.
Finalize Setup
Click Continue to finalize the setup. Your BigCommerce channel is now connected, and you can start running integrations manually or on a schedule.
Tip: Review the settings in the Integrations tab under your BigCommerce channel to ensure all desired operations are enabled.

 

Listing Operations

Flxpoint allows you to manage product listings on BigCommerce by syncing inventory, updating product details, and controlling pricing and availability. This ensures accurate and real-time updates across your BigCommerce store.

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.

Mapping templates control which BigCommerce product data is imported into your system.
Interface Overview
  • Screen labeled “Import Listings” at the top; name your template (e.g., “Import Listings 1”).
  • Buttons: Cancel, Save Mapping.
  • Columns: BigCommerce fields (left), system fields (right).
Mapping Options
  • Enable: Import the field (e.g., Name).
  • Disable: Ignore the field (e.g., Custom Field).
  • Required Fields: Name, SKU.
SKU Mapping Requirement
The SKU field must be mapped to avoid import errors.
  • Required Field: SKU ensures unique product identification.
  • Error Scenario: Unmapped SKU may cause:
    Invalid request: Missing required field 'sku' for product import
  • Fix: Go to Channels > BigCommerce > Templates > Import Listings > Field Mapping, map SKU, save, and re-run import.
Recommendation: Always map Name and SKU for successful imports.
Complete Field Mappings
Below are the fields you can enable for importing:
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 Enabled
Price List Price $19.99 Selling price Enabled
Inventory Level Quantity 100 Stock quantity Enabled
UPC UPC 123456789012 Universal Product Code Enabled
Weight Weight 2.5 Weight in kg Enabled
Width Width 12 Width in cm Enabled
Height Height 10 Height in cm Enabled
Depth Length 15 Length in cm Enabled
Images Product Images https://bigcommerce.com/toy.jpg Product images Enabled
Categories Category Path Toys > Educational Category hierarchy Enabled
Brand Brand Acme Product brand Enabled
Variant Fields
BigCommerce Field Maps To Example Purpose Status
Variant SKU Variant SKU TOY-BLUE-001 Variant identifier Enabled
Variant Price Variant List Price $21.99 Variant selling price Enabled
Variant Inventory Level Variant Quantity 50 Variant stock quantity Enabled
Variant UPC Variant UPC 123456789013 Variant UPC Enabled
Variant Image Variant Image https://bigcommerce.com/toy-blue.jpg Variant image Enabled
Practice Mapping
Try enabling/disabling BigCommerce - SKU:

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 08:37 PM -04, May 26, 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
The BigCommerce Import Listings integration automates catalog syncing, importing accurate product data, categories, and brands. Customize settings to streamline your workflow, ensuring your listings are ready for publishing. Happy importing!
 
 

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, or MPN.
  • 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).
  • 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) 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 fields to sync (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: Enable fields to sync (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates control which data is synced to BigCommerce.
Interface Overview
  • Screen labeled “Sync Listings” at the top; name your template (e.g., “Sync Listings 1”).
  • Buttons: Cancel, Save Mapping.
  • Columns: System fields (left), BigCommerce product/variant fields (right).
Mapping Options
  • Enable: Sync the field (e.g., Quantity).
  • Disable: Ignore the field (e.g., Custom Aggregate Field).
  • Required Fields: Inventory Level, Price.
Inventory Level Mapping Requirement
The Inventory Level field must be mapped to avoid sync errors.
  • Required Field: Inventory Level ensures accurate stock updates.
  • Error Scenario: Unmapped Inventory Level may cause:
    Invalid request: Missing required field 'inventory_level' for variant update
  • Fix: Go to Channels > BigCommerce > Templates > Sync Listings > Field Mapping, map Inventory Level, save, and re-run sync.
Recommendation: Always map Inventory Level and Price for reliable syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
System Field Maps To Example Purpose Status
Availability Description Availability Description In Stock Describes availability status Enabled
Estimated Cost Cost Price $10.50 Variant cost price Enabled
Estimated Dropship Fee Dropship Fee $2.00 Dropship fee Enabled
Estimated Shipping Cost Shipping Cost $5.00 Shipping cost Enabled
Quantity Inventory Level 100 Stock quantity Required
List Price Price $19.99 Selling price Required
MAP Map Price $15.99 Minimum advertised price Enabled
MSRP Retail Price $24.99 Manufacturer’s suggested price Enabled
List Price Sale Price $17.99 Discounted price Enabled
Practice Mapping
Try enabling/disabling Listing Variant - Quantity:

Be aware of these limitations:
  • Identifier Accuracy: Incorrect SKU, UPC, or MPN 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, or MPN 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 for enabled fields (e.g., Quantity, Price).
  • 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 08:33 PM -04, May 26, 2025, this integration is operational.
  • Inventory Level: Must be mapped to avoid sync errors.
  • Linking: Requires accurate SKU, UPC, or MPN.
  • Hiding/Delisting: Configurable to control visibility.
  • Stock Adjustments: Optional for refunds/cancellations.
Pro Tip: Regularly verify identifier accuracy to ensure successful linking.

Conclusion
The BigCommerce Sync & Link Listings integration keeps your 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:
    • Set title truncation, product name override, and image behavior.
    • Enable overwrite support if needed.
    • Configure scheduling.
  • 4 Create Mapping Template: Enable fields to publish (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates control which data is published to BigCommerce.
Interface Overview
  • Screen labeled “Publish Listings” at the top; name your template (e.g., “Publish Listings 1”).
  • Buttons: Cancel, Save Mapping.
  • Columns: System fields (left), BigCommerce product fields (right).
Mapping Options
  • Enable: Publish the field (e.g., Title).
  • Disable: Ignore the field (e.g., Custom Field).
  • Required Fields: Name, Weight, Type, Price.
Name Mapping Requirement
The Name field must be mapped to avoid publishing errors.
  • Required Field: Name ensures product creation.
  • Error Scenario: Unmapped Name may cause:
    Invalid request: Missing required field 'name' for product creation
  • Fix: Go to Channels > BigCommerce > Templates > Publish Listings > Field Mapping, map Name, save, and re-run sync.
Recommendation: Always map Name, Weight, Type, and Price for successful publishing.
Complete Field Mappings
Below are the fields you can enable for publishing, organized by category:
Listing Parent Fields
System Field Maps To Example Purpose Status
Attribute Metafields or Custom Fields Color: Blue Product attributes Enabled
Brand Brand Acme Product brand Enabled
Category 1 Category (Level 1) Toys Primary category Enabled
Category 2 Category (Level 2) Educational Secondary category Enabled
Category 3 Category (Level 3) Building Sets Tertiary category Enabled
Custom Field Custom Fields Material: Plastic Custom product data Enabled
Description Description

Fun toy set

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

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.
  • 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 08:05 PM -04, June 01, 2025, this integration is operational.
  • Required Fields: Name, weight, type, and price must be mapped.
  • Variants: Up to 250 supported per product.
  • Images: Limited to 8 MB; configurable via image behavior settings.
  • Overwriting: Supported to refresh product data.
  • SKUs: When a BigCommerce product has no variant options, FLX treats it as a regular product and sends the parent SKU (e.g., SSR) missing on the parent SKU—but present on the child—BigCommerce receives the un-prefixed value and shows it on the storefront. Apply the same prefix to both parent and child SKUs (use PMW bulk edit or SKU-prefix rule), delist the affected items, then run Publish Listings again to push the correct SKUs.
Pro Tip: Regularly check mapping templates to ensure all required fields are enabled.

Conclusion
The BigCommerce Publish Listings integration simplifies creating and updating product listings, with support for categories, brands, variants, and images. Customize settings and mappings to align with your catalog needs, ensuring an accurate and customer-ready store. Happy listing!
 
 


 

Order Operations

Flxpoint imports orders from BigCommerce into your system, automating order processing, tracking updates, and inventory adjustments. This streamlines fulfillment and ensures efficient handling of BigCommerce transactions.

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: Enable 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: Enable fields to import (e.g., billing address, State Code, line items).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates define which 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: Cancel, Save Mapping.
  • 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
  • Enable: Import the field (e.g., Quantity).
  • Disable: Ignore the field (e.g., Street Address 2).
  • Required Fields: Order - Date Created, Line Item - SKU, Quantity.
Quantity Mapping Requirement
The Line Item - Quantity field must be mapped to avoid import errors like NullPointerException (NPE).
  • Required Field: Quantity ensures order accuracy.
  • Error Scenario: 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 Line Item - Quantity, save, and re-run import.
Recommendation: Always map Quantity, SKU, and Date Created for stable imports.
Complete Field Mappings
Below are the fields you can enable for importing, organized by category:
Billing Address Fields
BigCommerce Field Maps To Example Purpose Status
City Billing Address - City San Francisco Specifies billing city Enabled
Company Billing Address - Company TechCorp Inc. Identifies billing company Enabled
Country Billing Address - Country United States Specifies billing country Enabled
Country Iso 2 Billing Address - Country Iso 2 US Provides country code Enabled
Email Billing Address - Email customer@example.com Contact email for billing Enabled
First Name Billing Address - First Name John Identifies buyer Enabled
Last Name Billing Address - Last Name Doe Identifies buyer Enabled
Phone Billing Address - Phone 555-123-4567 Contact phone for billing Enabled
State Billing Address - State California Specifies billing state Enabled
State Code Billing Address - State Code CA Two-letter state abbreviation Enabled
Street Address 1 Billing Address - Street Address 1 123 Main St Primary billing address Enabled
Street Address 2 Billing Address - Street Address 2 Apt 4B Secondary billing address Enabled
Zip Billing Address - Zip 94105 Specifies billing ZIP code Enabled
Shipping Address Fields
BigCommerce Field Maps To Example Purpose Status
City Shipping Address - City Los Angeles Specifies shipping city Enabled
Company Shipping Address - Company TechCorp Inc. Identifies shipping company Enabled
Country Shipping Address - Country United States Specifies shipping country Enabled
Country Iso 2 Shipping Address - Country Iso 2 US Provides country code Enabled
Email Shipping Address - Email customer@example.com Contact email for shipping Enabled
First Name Shipping Address - First Name Jane Identifies recipient Enabled
Last Name Shipping Address - Last Name Smith Identifies recipient Enabled
Phone Shipping Address - Phone 555-987-6543 Contact phone for shipping Enabled
Shipping Method Shipping Address - Shipping Method Standard Shipping Specifies shipping method Enabled
State Shipping Address - State California Specifies shipping state Enabled
State Code Shipping Address - State Code CA Two-letter state abbreviation Enabled
Street Address 1 Shipping Address - Street Address 1 456 Oak St Primary shipping address Enabled
Street Address 2 Shipping Address - Street Address 2 Suite 200 Secondary shipping address Enabled
Zip Shipping Address - Zip 90001 Specifies shipping ZIP code Enabled
Line Item Fields
BigCommerce Field Maps To Example Purpose Status
Base Cost Price Line Item - Base Cost Price $10.00 Base cost excluding tax Enabled
Base Price Line Item - Base Price $20.00 Base price excluding tax Enabled
Base Total Line Item - Base Total $40.00 Base total cost excluding tax Enabled
Base Wrapping Cost Line Item - Base Wrapping Cost $2.00 Base gift wrapping cost Enabled
Bin Picking Number Line Item - Bin Picking Number BIN-123 Identifies bin location Enabled
Brand Line Item - Brand Acme Specifies item brand Enabled
Cost Price Ex Tax Line Item - Cost Price Ex Tax $10.00 Cost price excluding tax Enabled
Cost Price Inc Tax Line Item - Cost Price Inc Tax $10.80 Cost price including tax Enabled
Cost Price Tax Line Item - Cost Price Tax $0.80 Tax on cost price Enabled
Fixed Shipping Cost Line Item - Fixed Shipping Cost $5.00 Fixed shipping cost Enabled
Fulfillment Source Line Item - Fulfillment Source Warehouse A Specifies fulfillment source Enabled
Id Line Item - Id 1 Unique line item ID Enabled
Name Line Item - Name Blue Widget Item name Enabled
Price Ex Tax Line Item - Price Ex Tax $20.00 Price excluding tax Enabled
Price Inc Tax Line Item - Price Inc Tax $21.60 Price including tax Enabled
Price Tax Line Item - Price Tax $1.60 Tax on price Enabled
Quantity Line Item - Quantity 2 Sets ordered units Required
Quantity Refunded Line Item - Quantity Refunded 1 Quantity refunded Enabled
Quantity Shipped Line Item - Quantity Shipped 1 Quantity shipped Enabled
Refund Amount Line Item - Refund Amount $20.00 Amount refunded Enabled
SKU Line Item - SKU PROD-001 Identifies product Required
Total Ex Tax Line Item - Total Ex Tax $40.00 Total cost excluding tax Enabled
Total Inc Tax Line Item - Total Inc Tax $43.20 Total cost including tax Enabled
Total Tax Line Item - Total Tax $3.20 Total tax amount Enabled
Type Line Item - Type physical Item type (e.g., physical, digital) Enabled
UPC Line Item - UPC 012345678905 Item UPC Enabled
Weight Line Item - Weight 1.5 Item weight (e.g., kg) Enabled
Wrapping Cost Ex Tax Line Item - Wrapping Cost Ex Tax $2.00 Wrapping cost excluding tax Enabled
Wrapping Cost Inc Tax Line Item - Wrapping Cost Inc Tax $2.16 Wrapping cost including tax Enabled
Wrapping Cost Tax Line Item - Wrapping Cost Tax $0.16 Tax on wrapping cost Enabled
Wrapping Message Line Item - Wrapping Message Happy Birthday! Gift wrapping message Enabled
Wrapping Name Line Item - Wrapping Name Festive Wrap Name of wrapping option Enabled
Order Fields
BigCommerce Field Maps To Example Purpose Status
Base Handling Cost Order - Base Handling Cost $3.00 Base handling cost excluding tax Enabled
Base Shipping Cost Order - Base Shipping Cost $5.00 Base shipping cost excluding tax Enabled
Base Wrapping Cost Order - Base Wrapping Cost $2.00 Base wrapping cost excluding tax Enabled
Coupon Discount Order - Coupon Discount $10.00 Total coupon discount Enabled
Currency Code Order - Currency Code USD Order currency Enabled
Currency Exchange Rate Order - Currency Exchange Rate 1.0 Currency exchange rate Enabled
Custom Status Order - Custom Status Custom Processing Custom order status Enabled
Customer Locale Order - Customer Locale en-US Customer language/region Enabled
Customer Message Order - Customer Message Please ship quickly! Customer notes Enabled
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 Enabled
Date Shipped Order - Date Shipped 2025-04-08T09:00:00Z Shipping date Enabled
Default Currency Code Order - Default Currency Code USD Store default currency Enabled
Discount Amount Order - Discount Amount $5.00 Total discount applied Enabled
Ebay Order Id Order - Ebay Order Id EBAY-12345 eBay order identifier Enabled
External Source Order - External Source eBay External order source Enabled
Geo IP Country Order - Geo IP Country United States Customer IP country Enabled
Geo IP Country Iso2 Order - Geo IP Country Iso2 US Customer IP country code Enabled
Gift Card Amount Order - Gift Card Amount $25.00 Gift card payment amount Enabled
Gift Certificate Amount Order - Gift Certificate Amount $10.00 Gift certificate payment Enabled
Handling Cost Ex Tax Order - Handling Cost Ex Tax $3.00 Handling cost excluding tax Enabled
Handling Cost Including Tax Order - Handling Cost Inc Tax $3.24 Handling cost including tax Enabled
Handling Cost Tax Order - Handling Cost Tax $0.24 Tax on handling cost Enabled
Items Total Order - Items Total 3 Total number of items Enabled
Order ID Order - Order ID 12345 Unique order identifier Enabled
Order Source Order - Order Source manual Order source (e.g., direct) Enabled
Payment Method Order - Payment Method Credit Card Payment method used Enabled
Payment Status Order - Payment Status paid Payment status Enabled
Refunded Amount Order - Refunded Amount $20.00 Total refunded amount Enabled
Shipping Address Count Order - Shipping Address Count 1 Number of shipping addresses Enabled
Shipping Cost Ex Tax Order - Shipping Cost Ex Tax $5.00 Shipping cost excluding tax Enabled
Shipping Cost Including Tax Order - Shipping Cost Inc Tax $5.40 Shipping cost including tax Enabled
Shipping Cost Tax Order - Shipping Cost Tax $0.40 Tax on shipping cost Enabled
Staff Notes Order - Staff Notes Expedited shipping requested Staff notes on order Enabled
Status Order - Status Awaiting Payment Order status Enabled
Store Credit Amount Order - Store Credit Amount $15.00 Store credit payment Enabled
Store Default Currency Code Order - Store Default Currency Code USD Store default currency Enabled
Store Default To Transactional Exchange Rate Order - Exchange Rate 1.0 Default to transactional rate Enabled
Subtotal Ex Tax Order - Subtotal Ex Tax $90.00 Subtotal excluding tax Enabled
Subtotal Including Tax Order - Subtotal Inc Tax $97.20 Subtotal including tax Enabled
Subtotal Tax Order - Subtotal Tax $7.20 Tax on subtotal Enabled
Total Ex Tax Order - Total Ex Tax $95.00 Total excluding tax Enabled
Total Inc Tax Order - Total Inc Tax $102.60 Total including tax Enabled
Total Tax Order - Total Tax $7.60 Total tax amount Enabled
Wrapping Cost Ex Tax Order - Wrapping Cost Ex Tax $2.00 Wrapping cost excluding tax Enabled
Wrapping Cost Inc Tax Order - Wrapping Cost Inc Tax $2.16 Wrapping cost including tax Enabled
Wrapping Cost Tax Order - Wrapping Cost Tax $0.16 Tax on wrapping cost Enabled
Practice Mapping
Try enabling/disabling Line Item - Quantity:

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.
    • 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 enabled in the mapping template.
  • 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 05:54 AM -04, May 27, 2025, this integration is operational.
  • Quantity: Must be mapped to avoid NPE 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: Enable shipment fields to sync (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.
  • 6 Verify Shipping Provider: In BigCommerce admin, go to Shipping Settings and confirm providers (e.g., “U.P.S.”).

Mapping templates control which shipment data is synced to BigCommerce.
Interface Overview
  • Screen labeled “Sync Orders” at the top; name your template (e.g., “Sync Orders 1”).
  • Buttons: Cancel, Save Mapping.
  • Columns: System fields (left), BigCommerce shipment fields (right).
Mapping Options
  • Enable: Sync the field (e.g., Tracking Number).
  • Disable: Ignore the field (e.g., Note).
  • Required Fields: Shipment - Tracking Number.
Tracking Number Mapping Requirement
The Shipment - Tracking Number field must be mapped to avoid sync errors.
  • Required Field: Tracking Number ensures accurate shipment updates.
  • Error Scenario: Unmapped Tracking Number may cause:
    Invalid request: Missing required field 'tracking_number' for shipment creation
  • Fix: Go to Channels > BigCommerce > Templates > Sync Orders > Field Mapping, map Tracking Number, save, and re-run sync.
Recommendation: Always map Tracking Number and Shipping Method for reliable shipment syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
System Field Maps To Example Purpose Status
Comments Shipment - Note Shipped via priority mail Additional shipment notes Enabled
Date Created Shipment - Shipped At 2025-05-26T10:00:00Z Shipment creation date Enabled
Merchant Shipping Cost Shipment - Shipping Cost $5.00 Merchant shipping cost Enabled
Shipping Method Shipment - Method Standard Shipping Shipping method used Enabled
Shipping Provider Shipment - Carrier U.P.S. Shipping carrier Enabled
Tracking Link Shipment - Tracking URL https://track.ups.com/123456 Tracking URL Enabled
Tracking Number Shipment - Tracking Number 1Z999AA10123456784 Tracks shipment Required
Tracking Carrier Shipment - Carrier UPS Carrier for tracking Enabled
Note: For accepted carrier values, refer to the Accepted Carrier Values CSV.
Practice Mapping
Try enabling/disabling Shipment - Tracking Number:

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: Disable “Shipping Provider” in the mapping template to send as null 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 for enabled fields (e.g., Tracking Number).
  • 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 08:22 PM -04, May 26, 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
The BigCommerce Sync Orders integration keeps your store updated with order and shipment data, supporting partial shipments and automatic customer notifications. Customize mappings and settings to align with your fulfillment workflow, ensuring accuracy and efficiency. Happy syncing!