WooCommerce as a Channel

WooCommerce is a leading eCommerce platform that allows businesses to sell products online and manage their sales channels efficiently. Integrating WooCommerce into Flxpoint as a channel allows you to automate order processing, inventory syncing, and product publishing between Flxpoint and WooCommerce. It helps streamline operations, ensuring that your product data and inventory levels are always up-to-date across your sales platforms.
 

 

How to Connect

📋 Phase 1: Initial Channel Setup +
Access Channels Section
Log into your Flxpoint account and navigate to the Channels section.
Create a New Channel
Click + Add Channel to start the integration process.
Tip: Have your Standard account credentials or API details ready to streamline setup.
Select WooCommerce and Name Channel
In the popup:
  • Choose WooCommerce as the channel type.
  • Enter a descriptive Channel Name (e.g., "Standard Store").
  • Click Save to continue.
A clear channel name helps identify this integration if you manage multiple channels.
Start the Integration Process
After creating the channel, you’ll see "No integrations created yet." Click Get Started to launch the setup wizard.
🔐 Phase 2: Authentication & Connection +
Important Note: The recommended method for connecting Standard to Flxpoint is via WooCommerce REST API key, which securely authorizes the connection without manual credential entry. Use API Key only if WooCommerce REST API key is unavailable (e.g., for custom integrations).
Select the Integration Type
In the Setup Integrations wizard, select WooCommerce REST API key for secure authorization, or choose API Key for manual credential entry.
Connect Your Account
For WooCommerce REST API key:
  • Enter your Store URL (e.g., https://your-store.com). Find this in your WooCommerce Admin under Settings > Domains or in your browser’s address bar.
  • Click Initiate WooCommerce REST API key Flow, select your store account, and Install the Flxpoint app in the WooCommerce dialog.
  • Review and Approve the requested permissions.
  • You’ll be redirected to Flxpoint upon completion.
For API Key (vendor flow when WooCommerce REST API key is unavailable):
  • Send your vendor the Vendor’s Guide to the WooCommerce App.
  • The vendor installs the Flxpoint App in their WooCommerce Admin and shares their Store URL and API Key with you.
  • Paste the vendor’s API Key as the Token and their Store URL.
Important: Use the platform’s native URL (e.g., https://your-store.com) (the full HTTPS URL of your WordPress site).
Authorize Access
For WooCommerce REST API key, no further credentials are needed after authorization. For API Key:
  • Enter a Connection Name (e.g., "Standard Connection #1").
  • Paste the API Access Token and Store URL.
  • Click Test Connection and then Continue if successful.
Troubleshooting: If the connection fails, verify credentials, permissions, and URL format. In WooCommerce Admin, go to Apps and Integrations, locate the Flxpoint app, and select Delete to reset, then restart from Phase 1.
Verify Connection
Review connection details in Flxpoint to ensure accuracy, then proceed.
Standard API Rate Limits: Standard enforces API rate limits to ensure platform stability. Details at Standard API Documentation:
  • REST API: 2 requests/sec, 40 requests/sec for premium plans.
  • REST API API: 50 points/sec.
  • WooCommerce REST API key: Exempt from rate limits; optimize with Flxpoint sync schedules.
Monitor usage in Flxpoint logs to adjust operations.
🔄 Phase 3: SKU Mapping & Configuration +
Set Up SKU Mapping
Configure Import Listings to align with your inventory:
  • Set new listings to Paused to review before publishing.
  • Map your internal Master SKU to Standard’s listing SKU.
Pro Tip: Use consistent SKU naming (e.g., "PROD-123" internally and "STD-PROD-123" on Standard) for easier inventory management.
Configure Integration Settings
Enable automated features:
  • Inventory & Pricing: Enable automatic synchronization of inventory levels and prices between Flxpoint and Standard.
  • Publish Listings: Standard uses REST API; map categories to global IDs from Standard’s Taxonomy. Adjust settings like "Truncate Title to 255" or "Enable variant images."
  • Order Sync: Select fulfillment and financial statuses (e.g., "Unfulfilled," "Authorized") for Get Orders.
  • Shipment Tracking: Configure tracking updates to notify Standard and customers when orders ship.
  • TikTok Shop (Optional): In WooCommerce Admin, install a TikTok Shop app, connect your store, and verify listings can be published via Flxpoint.
Note: TikTok Shop integration is optional and only needed if selling on that platform.
Complete Setup
Review settings and click Save. In Channels > Standard, run Import Listings, Get Orders, and manage syncs or schedules.
Next Steps: Run processes manually to verify sync accuracy before enabling automation.

 

 

Listing Operations

Import Listings

Supported | WooCommerce - Import Listings

Introduction to WooCommerce Import Listings
Welcome to the WooCommerce Import Listings integration guide! This integration lets you bring your WooCommerce product listings into Flxpoint, keeping your inventory in sync across both platforms. It ensures data consistency and helps you manage your listings efficiently. Let’s get started!
Purpose of This Integration
The WooCommerce Import Listings integration enables you to:
  • Pull your WooCommerce listings into Flxpoint, either creating new listings or linking them to existing ones using a Master SKU.
  • Pause new listings to link inventory before they sync back to WooCommerce, avoiding mismatches.
  • Ensure data consistency between WooCommerce and Flxpoint for accurate inventory management.
This ensures seamless inventory synchronization and streamlined listing management.
How the Integration Works
The integration follows these steps:
  • 1 Connecting to WooCommerce: Establish a connection using API credentials or WooCommerce REST API credentials to access your WooCommerce store.
  • 2 Fetching Listings Data: Flxpoint retrieves your product listings from WooCommerce.
  • 3 Matching Listings: Matches WooCommerce listings to Flxpoint listings using a Master SKU (e.g., WooCommerce Variant SKU).
  • 4 Importing Listings: Imports listings based on your settings (create only or create & overwrite), with an option to pause new listings.
  • 5 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your listings up-to-date across platforms.
Note: API failures pause the integration and trigger notifications.
Configuration Options
Customize the integration with these settings:
  • Enable Import Listings: Toggle this on to start importing WooCommerce listings.
  • How Listings Are Imported: Choose how Flxpoint handles WooCommerce listings:
    • Create Only: Imports WooCommerce listings and links them to existing Flxpoint listings by SKU. If there’s no SKU match, a new listing is created. On each run, only products and variants created after the last successful job run (plus a 2-hour buffer) are fetched — keeping runs fast and incremental.
    • Create & Overwrite Existing: Imports WooCommerce listings, links them by SKU, updates existing Flxpoint listings, and creates new listings if there’s no SKU match. On each run, only products and variants created or updated after the last successful job run (plus a 2-hour buffer) are fetched.
  • Master SKU: Select the WooCommerce field to use as the Master SKU for linking (e.g., WooCommerce Variant SKU or SKU).
  • Pause New Listings: Toggle this on to pause newly imported listings until inventory is linked.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Note: Pausing new listings helps avoid inventory mismatches by giving you time to link inventory.
Setup Instructions
Follow these steps:
  • 1 Add the Integration: Go to Channels > WooCommerce > Integrations, select “Import Listings.”
  • 2 Connect to WooCommerce: Use your WooCommerce Token and Store URL or set up a new connection via WooCommerce REST API credentials.
  • 3 Configure Settings:
    • Toggle on "Enable Import Listings."
    • Select how to import ("Create Only" or "Create & Overwrite Existing").
    • Choose the Master SKU field (e.g., WooCommerce Variant SKU).
    • Enable "Pause New Listings" if desired.
    • Configure scheduling (e.g., daily at 6 AM UTC).
  • 4 Run the Integration: Start with Run Sync or schedule automatic syncs.
Unpausing Listings
If you chose to pause new listings, you’ll need to unpause them to sync with WooCommerce:
  • 1 Go to Products in Flxpoint.
  • 2 Select the paused listings you want to unpause.
  • 3 Click ActionsChange Listing StatusUnpause Listings.
Once unpaused, your listings will sync properly with WooCommerce.
Pro Tip: Unpause listings only after linking inventory to ensure accurate syncing.
Data Imported
Here’s what data Flxpoint can import from WooCommerce:
  • Custom Fields: Supported. Parent and variant custom fields (post meta) come in as custom fields.
  • Variants/Options: Supported.
  • Quantity: Supported. Quantity is imported as a total for all locations.
  • Multiple Warehouses: Supported. Product data is saved for all locations.
  • Weight & Dimensions: Supported. Weight in oz, lb, kg, g; dimensions not available by default.
  • Images: Supported. Images are imported using store-hosted URLs, with multiple images supported.
  • List Pricing & Client Pricing: Not supported. You’ll need to set pricing manually in Flxpoint.
  • Categories: Not supported.
Limitations
Be aware of these limitations:
  • Pricing Not Imported: List and client pricing aren’t imported; set them manually in Flxpoint.
  • Categories Not Supported: Categories aren’t imported; manage them separately.
  • API Rate Limits: WooCommerce API rate limits may affect large import jobs; monitor usage to avoid interruptions.
Troubleshooting
Troubleshoot issues with these steps:
  • Connection Issues: Verify your WooCommerce Token and Store URL are correct.
  • Listings Not Linking: Ensure the Master SKU field (e.g., WooCommerce Variant SKU) matches between WooCommerce and Flxpoint.
  • Import Not Running: Check your sync schedule or run it manually with "Run Sync."
  • Other Errors: Review operation details for common errors and resolution steps.
  • Products Not Appearing After Import: If products or variants are missing after a run, confirm they were created or updated within the window since the last successful job run. Products in draft status or those not recently updated will not be fetched in Create Only or Create & Overwrite Existing modes. To re-fetch a broader historical window, contact support to adjust the last successful run timestamp.
Diagnostic Tip: Listings not linking often results from mismatched Master SKU fields.
Key Details You Need to Know
Key information:
  • Date: As of 09:29 PM -04, May 29, 2025, this integration is operational.
  • Incremental Fetching: For Create Only and Create & Overwrite Existing modes, each run fetches only records created or updated since the last successful run (with a 2-hour buffer). If products appear to be missing after a run, confirm they were active or updated within that window. Drafts or products not recently touched will not be re-fetched automatically.
  • Master SKU Requirement: Ensure the Master SKU field matches between WooCommerce and Flxpoint for proper linking.
  • API Limits: Monitor WooCommerce API rate limits to avoid sync interruptions.
Pro Tip: Use "Pause New Listings" to review and link inventory before syncing back to WooCommerce.
Conclusion
The WooCommerce Import Listings integration automates the syncing of your WooCommerce product listings into Flxpoint, ensuring accurate inventory management. Customize settings to fit your workflow, unpause listings as needed, and explore other WooCommerce integrations like Publish Listings or Sync Orders to enhance your operations. Happy syncing!
 
 

Sync & Link Listings

Introduction
Supported | WooCommerce - Sync & Link Listings

Introduction to WooCommerce Sync & Link Listings
Welcome to the WooCommerce Sync & Link Listings integration guide! This integration ensures that your pricing and quantity data stay consistent between Flxpoint and WooCommerce by synchronizing channel listings and linking them using a shared identifier. It ensures seamless inventory and pricing updates across platforms. Let’s get started!
Purpose of This Integration
The WooCommerce Sync & Link Listings integration enables you to:
  • Sync pricing and quantity data from Flxpoint to WooCommerce listings.
  • Link Flxpoint listings to WooCommerce listings using a chosen identifier (e.g., SKU or Barcode).
  • Specify a WooCommerce location for syncing inventory data.
This ensures consistent pricing and inventory data across your sales channels.
How the Integration Works
The integration follows these steps:
  • 1 Connecting to WooCommerce: Establish a connection using API credentials or WooCommerce REST API credentials to access your WooCommerce store.
  • 2 Identifying Listings: Flxpoint identifies matching listings between Flxpoint and WooCommerce using a linking identifier (e.g., SKU or Barcode).
  • 3 Mapping Data: Maps Flxpoint fields (e.g., List Price, Quantity) to WooCommerce fields using a mapping template.
  • 4 Syncing Data: Flxpoint updates your WooCommerce listings with pricing and quantity data for the specified location.
  • 5 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep pricing and inventory data up-to-date across platforms.
Note: API failures pause the integration and trigger notifications.
Configuration Options
Customize the integration with these settings:
  • Enable Sync Listings: Toggle this on to automatically synchronize pricing and quantity data with WooCommerce listings.
  • Linking Identifier: Choose the identifier to link Flxpoint and WooCommerce listings:
    • Flxpoint Listing: Options include SKU, ASIN, GTIN, MPN, or UPC.
    • WooCommerce Listing: Options include SKU or Barcode.
  • Location ID: Select the WooCommerce location to sync inventory data with (e.g., Shop Location). Learn more at WooCommerce Locations Documentation.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
  • Mapping Template: Define which Flxpoint fields sync to WooCommerce (e.g., List Price to WooCommerce Variant - Price).
  • Publications (if you also publish): To publish to multiple WooCommerce publications, enter a comma-separated list of Publication IDs in the Publish Listings configuration/template (e.g., 1234567890,9876543210 or full GIDs). No spaces; don’t mix formats.
Note: Ensure the linking identifier matches between Flxpoint and WooCommerce to avoid sync failures.
Setup Instructions
Follow these steps:
  • 1 Add the Integration: Go to Channels > WooCommerce > Integrations, select “Sync & Link Listings.”
  • 2 Connect to WooCommerce: Use your WooCommerce Token and Store URL or set up a new connection via WooCommerce REST API credentials.
  • 3 Configure Settings:
    • Toggle on "Enable Sync Listings."
    • Select the linking identifier (e.g., SKU for both Flxpoint and WooCommerce).
    • Choose the WooCommerce Location ID (e.g., Shop Location).
    • Configure scheduling (e.g., daily at 6 AM UTC).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping Template Details
Mapping templates control which Flxpoint data is synced to WooCommerce.
Interface Overview
  • Screen labeled “Sync & Link Listings” at the top; name your template (e.g., “WooCommerce Sync & Link Listings 1”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Flxpoint fields (left), WooCommerce fields (right).
Mapping Options
  • Enable: Send the field (e.g., Quantity).
  • Disable: Ignore the field (e.g., Estimated Cost).
  • Required Fields: Quantity is enabled by default for proper syncing.
Quantity Mapping Requirement
The Quantity field must be enabled to ensure proper inventory syncing.
  • Required Field: Quantity ensures accurate inventory levels in WooCommerce.
  • Error Scenario: Disabling Quantity may cause:
    Invalid request: Missing required field 'Quantity' for inventory sync
  • Fix: Go to Channels > WooCommerce > Templates > Sync & Link Listings > Field Mapping, enable Quantity, save, and re-run sync.
Recommendation: Always enable Quantity for reliable inventory syncing.
Complete Field Mappings
Variant Fields
Flxpoint Field Maps To Data Type Example Purpose Status
Estimated Cost WooCommerce Variant - Cost Number $20 Sets variant cost Disabled by Default
List Price WooCommerce Variant - Price Number $30 Sets selling price Disabled by Default
MSRP WooCommerce Variant - Compare At Price Number $50 Sets suggested retail price Disabled by Default
Quantity WooCommerce Variant - Quantity Number 50 Sets inventory quantity Enabled by Default
Practice Mapping
Try enabling/disabling Flxpoint - Quantity:
Data Synced
Here’s what data Flxpoint can sync to WooCommerce:
  • Cost: Supported (optional, can be disabled in mapping).
  • Price: Supported (optional, can be disabled in mapping).
  • Compare At Price (MSRP): Supported (optional, can be disabled in mapping).
  • Quantity: Supported (enabled by default).
Limitations
Be aware of these limitations:
  • Linking Identifier Match: The linking identifier (e.g., SKU) must match between Flxpoint and WooCommerce to avoid sync failures.
  • Location ID Validity: The Location ID must correspond to a valid WooCommerce location for accurate syncing.
  • Field Syncing: Only fields enabled in the mapping template will be synced to WooCommerce.
  • API Rate Limits: WooCommerce API rate limits may affect large sync jobs; monitor usage to avoid interruptions.
Troubleshooting
Troubleshoot issues with these steps:
  • Connection Issues: Verify your WooCommerce Token and Store URL are correct.
  • Listings Not Linking: Ensure the linking identifier (e.g., SKU) matches between Flxpoint and WooCommerce.
  • Sync Not Running: Check your sync schedule or run it manually with "Run Sync."
  • Data Not Syncing: Confirm that the fields are enabled in the mapping template.
  • Hide When Out of Stock — WooCommerce specifics: Queue the parent product when hiding/unhiding so variants follow; otherwise WooCommerce may error:
    Parent must be hidden before variant
  • Product Does Not Exist Error: If you see:
    REST API Request Failed: Product variant does not exist
    the product may have been deleted in WooCommerce but is still linked in Flxpoint. Unlink, then re-link.
  • Title or Variant Mismatch: Align titles and variant structure between systems.
Diagnostic Tip: Sync failures often result from mismatched identifiers or disabled fields.
Key Details You Need to Know
Key information:
  • Date: As of 09:31 PM -04, May 29, 2025, this integration is operational.
  • Required Fields: Quantity must be enabled in the mapping template.
  • API Limits: Monitor WooCommerce API rate limits to avoid sync interruptions.
  • Multiple Publications: Configure comma-separated Publication IDs in the Publish Listings integration when you need to target multiple publications.
Pro Tip: Ensure linking identifiers match and enable Quantity for reliable syncing.
Conclusion
The WooCommerce Sync & Link Listings integration automates pricing and inventory updates, ensuring consistency between Flxpoint and WooCommerce. Monitor sync logs via "View Logs" to ensure smooth operation, and explore other WooCommerce integrations like Publish Listings or Get Orders to further streamline your workflow. Happy syncing!
 
 

Publish Listings

Introduction
Supported | WooCommerce - Publish Listings

Introduction to WooCommerce Publish Listings
Welcome to the WooCommerce Publish Listings integration guide! This integration allows you to create and publish product listings from Flxpoint to your WooCommerce store, ensuring seamless inventory management. It ensures your product data is accurately reflected on WooCommerce, supporting features like variant positioning and product categories. Let's get started!
Setup Instructions
Follow these steps:
  • 1 Add the Integration: Go to Channels > WooCommerce > Integrations, select "Publish Listings."
  • 2 Connect to WooCommerce: Use your WooCommerce Token and Store URL or set up a new connection via WooCommerce REST API credentials.
  • 3 Configure Settings:
    • Toggle on "Enable Publish Listings."
    • Select the WooCommerce Location ID.
    • Set Publication IDs (multiple if needed).
    • Choose title handling ("Fail Product" or "Truncate Title to 255").
    • Configure advanced settings (Namespace, Underscore in Meta Fields, Image Duplication Logic, Smart Collections).
    • Configure scheduling (e.g., daily at 6 AM UTC).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Configuration Options
Customize the integration with these settings:
  • Enable Publish Listings: Toggle this on to start publishing listings to WooCommerce.
  • Location ID: Select the WooCommerce location to publish listings to (e.g., Shop Location). Learn more at WooCommerce Locations Documentation.
  • Should Additional Variant Images Be Added?: Enable this to upload variant images for products with a parent image.
  • Truncate Title to 255: Choose how to handle titles exceeding 255 characters:
    • Fail Product: Fails the listing if the title is too long.
    • Truncate Title to 255: Trims the title to 255 characters.
  • Namespace: Optionally set a namespace for custom field (post meta) fields.
  • Use Underscore in Meta Fields Name: Use underscores as separators in meta field names.
  • Advanced Image Duplication Logic: Prevent duplicate image uploads using cached checksums.
  • Auto-Create Smart Collection on "Product Type": Automatically create WooCommerce Smart Collections for mapped product types.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
  • Publication IDs (multiple): Publish to one or more WooCommerce publications using a comma-separated list. Use numeric IDs or full GIDs consistently and avoid spaces.
    Numeric: 1234567890,9876543210
    GID: gid://shopify/Publication/1234567890,gid://shopify/Publication/9876543210
    Invalid: 1234567890, 9876543210 (spaces) | 1234567890; (semicolon)
Tip: Set Publication IDs first, then create products or use hide → unhide to apply to existing ones.
Publication behavior: Publication targeting is applied when you create a new product or when you unhide a previously hidden product. For existing live products that need updated publications, perform a hide → unhide.
Note: API failures pause the integration and trigger notifications.
Mapping Template Details
Mapping templates control which Flxpoint data is published to WooCommerce.
Interface Overview
  • Screen labeled "Publish Listings" at the top; name your template (e.g., "WooCommerce Publish Listings 1").
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Flxpoint fields (left), WooCommerce fields (right).
Mapping Options
  • Enable: Send the field (e.g., Title, SKU).
  • Disable: Ignore the field (e.g., Client Pricing).
  • Required Fields: Title and SKU are required for proper publishing.
Title and SKU Mapping Requirement
The Title and SKU fields must be enabled to ensure proper listing creation.
  • Required Fields: Title and SKU uniquely identify the product and variants.
  • Error Scenario: Missing Title or SKU may cause:
    Invalid request: Missing required fields 'Title' or 'SKU' for listing creation
  • Fix: Go to Channels > WooCommerce > Templates > Publish Listings > Field Mapping, enable Title and SKU, save, and re-run sync.
Recommendation: Always enable Title, SKU, and Images for reliable listing publishing.
Publication IDs Mapping
If your template includes a Publication IDs field, enter a comma-separated list with no spaces. Use either all numeric IDs or all GIDs (don’t mix).
Complete Field Mappings
Product Fields
Flxpoint Field Maps To Data Type Example Purpose Status
Brand WooCommerce Product - Vendor Text BrandX Sets product vendor Supported
Title WooCommerce Product - Title Text Blue T-Shirt Sets product title Required
Description WooCommerce Product - Body HTML Text Comfortable cotton t-shirt Sets product description Supported
Product Images WooCommerce Product - Product Images Text image_url.jpg Sets product images Supported
Category 1 WooCommerce Product - Product Type Text gid://shopify/Taxonomy/Category/ap-1 Sets product type Supported
All Attributes WooCommerce Product - Attributes to Custom Fields Text color: blue Sets custom fields (post meta) Supported
Variant Fields
Flxpoint Field Maps To Data Type Example Purpose Status
SKU WooCommerce Variant - SKU Text variant-sku-001 Identifies the variant Required
List Price WooCommerce Variant - Price Number $30 Sets selling price Supported
Quantity WooCommerce Variant - Quantity Number 50 Sets inventory quantity Supported
Image WooCommerce Variant - Image Text variant_image_url.jpg Sets variant image Supported
Options (e.g., Color, Size) WooCommerce Variant - Options Text Color: Blue, Size: Medium Sets variant options Supported
Variant Images
  • Publishing Variant Images: Enable "Should Additional Variant Images Be Added?" in the configuration to upload variant-specific images. Follow WooCommerce size limits (up to 4472x4472 px, 20 MB).
  • Variant Positioning: Positions are applied on new product creation; updates won’t reorder existing variants.
  • Updating an already attached variant image: If an image is already attached, the integration replaces it automatically when re-publishing.
Category Mapping
Map your internal categories to WooCommerce's Taxonomy using global IDs:
  • Use the WooCommerce Product Taxonomy.
  • Example: Mapping "Live Animals" to gid://shopify/Taxonomy/Category/ap-1.
  • Create mapping sets or rules to automate category translation.
Understanding Custom Fields and Attributes
When publishing products with attributes to WooCommerce, it's important to understand how custom fields (post meta) work:
  • Unstructured Custom Fields: Flxpoint may create unstructured custom fields (post meta) when attributes are published if definitions don’t already exist.
  • "Undefined" Display: WooCommerce may display these as "undefined" in admin until you add definitions in Settings > Custom Data.
  • Custom Custom Field Mapping: Advanced mapping with specific namespaces and types is available via mapping templates (ensure definitions exist in WooCommerce).
Important: The custom fields (post meta) are created successfully; they appear as "undefined" only because they lack structured definitions. Add definitions in WooCommerce for labeled display/use on the storefront.
Workarounds for Custom Fields Management:
  • Use a WooCommerce App: Export/import custom fields (post meta) with a catalog tool after definitions are created in WooCommerce.
  • Manual Creation: Manually create custom field (post meta) definitions in WooCommerce Admin before publishing.
Advanced users: Create definitions first for a smoother admin/storefront experience.
Data Published
Here's what data Flxpoint can publish to WooCommerce:
  • Custom Fields: Parent and variant custom fields (post meta) (single-line text).
  • Attributes/Tags: Attributes can be uploaded as custom fields (post meta).
  • Variants/Options: Up to 100 variants per product, with up to three options.
  • Generic Pricing: Cost, list price, and MSRP as regular values; MAP as custom field (post meta).
  • Client Pricing: Not supported.
  • Quantity: Supported.
  • Multiple Warehouses: Not supported.
  • Weight & Dimensions: Weight in oz, lb, kg, g; dimensions as custom fields (post meta).
  • Images: Uses fixed hosted URLs; up to 4472x4472 px, 20 MB.
  • Categories: Single category; other levels as tags.
  • Offerings vs. Creation: New product creation is supported.
  • Option Limitations: Up to three options per product.
  • HTML Description: Supported.
  • Publishing Limits: Typical 1,000 products/day on non-Plus accounts.
Troubleshooting
  • Title too long: Enable “Truncate Title to 255”.
  • Variant option limit: Max 3 options, 100 variants.
  • Custom Field errors: Check Namespace/Key/Value; add definitions in WooCommerce if needed.
  • Image issues: Respect size/file limits; use duplicate protection when needed.
  • Invalid Publication ID: Use commas only, no spaces; keep IDs all numeric or all GIDs.
  • Change didn’t apply to existing products: Use hide → unhide to re-publish to the updated publications.
  • Product/Variant does not exist: If removed in WooCommerce, unlink/re-link before re-publishing.
Limitations
  • Options: Max 3 per product.
  • Variants: Max 100 per product.
  • Images: Up to 4472×4472 px; 20 MB.
  • Daily publishing: Typical limit of ~1000 products/day for non-Plus accounts.
  • Publication timing: Multi-publication targeting is applied on create/unhide events (not each routine sync).
 
 

 

 

Mapping Source Attributes to WooCommerce

Mapping Source Attributes to WooCommerce explains how product attributes pulled from any Flxpoint source — color, size, material, brand, and other variant-level fields — are published into your WooCommerce store, and which settings control whether each attribute becomes a global WooCommerce taxonomy attribute or a per-product custom attribute.

How Source Attributes Reach Flxpoint

When you connect a source integration (for example, S&S Activewear, Essendant, or any other supplier), Flxpoint imports each product's attributes alongside its inventory and pricing. Common attributes include:

  • Brand, Manufacturer Part Number (MPN)
  • Color, Size, Material, Gender, Style
  • Condition, Weight, and other supplier-specific fields
Tip: Attribute availability varies by source. Open a representative SKU in Catalog → Products and check the Attributes tab to verify which fields are populated for your supplier feed before configuring mapping.
Mapping Attributes Through Flxpoint
  • Source attributes are imported automatically with the source's Get Inventory operation.
  • Use a Mapping Template on the source to choose which attributes carry forward to your master products and variants. Set the mapping to Direct Copy for any attribute you want to publish unchanged.
  • Confirm the attribute exists in the source data before mapping — empty source values produce empty WooCommerce attributes.
Settings That Control Attribute Behavior

The two settings below live on your WooCommerce as a Channel integration in Flxpoint and decide whether each attribute becomes a global WooCommerce taxonomy attribute or a per-product custom attribute.

Setting Effect
Enable this to send all Flxpoint Attributes as WooCommerce Custom Attributes When ON: every Flxpoint attribute (except the always-global ones below) is created as a custom attribute on each WooCommerce product. Use this when you want attributes attached at the product level without expanding WooCommerce's global attribute taxonomy.
When OFF: attributes that match an existing WooCommerce global taxonomy term are linked to that global attribute; new attributes are created as custom.
Global Flxpoint Attribute Names (pipe-separated list) Lets you force selected Flxpoint attributes to publish as global WooCommerce attributes even when the "send all as custom" flag is ON. Enter the attribute names separated by |. Example: Color|Size|Brand.
Always global, regardless of the flag. Three attribute concepts are always created as global WooCommerce attributes because they are required for variations and filtering to work correctly: Brand, MPN, and the product option names used to define variations (for example, Color and Size on a multi-variant t-shirt).
Choosing Which Attributes Should Be Global
  • Use global for attributes that drive WooCommerce variations, navigation filters, or shop search facets (commonly Color, Size, Brand).
  • Use custom for attributes you only need on the individual product page (e.g., Material composition, Country of Origin, Care Instructions).
  • Match the attribute name to your existing WooCommerce taxonomy where possible. If your store already uses pa_color, name the Flxpoint attribute Color so the integration links to it rather than creating a duplicate.
Avoiding Duplicates and Overwrites
  • Don't map the same source field to two different WooCommerce attribute names — this creates duplicate attributes on each product.
  • If you change an attribute name after products have been published, WooCommerce keeps the old attribute alongside the new one until you remove it manually.
  • Scope each new attribute mapping to a small test product first, confirm the result in WooCommerce, and then promote it to the rest of your catalog.
What to Do When an Attribute Isn't in the Source
Not all suppliers expose every attribute. If your source feed doesn't include a value you need (for example, a parent color family or a style group), Flxpoint cannot publish it because the data isn't there to map. Options:
  • Ask your supplier whether they can include the field in their feed.
  • Use a Mapping Set in Flxpoint to derive the value from another field on the product.
  • Use a third-party WooCommerce plugin to add the attribute at the storefront layer — this is outside the Flxpoint integration but is sometimes the fastest path for attributes that aren't supplier-provided.
Best Practices Checklist
  • Decide on your shortlist of global attributes before publishing — typically Color, Size, and Brand for variation-heavy stores.
  • Verify each attribute is populated in the source feed before mapping it.
  • Avoid duplicate mappings of the same source field to multiple WooCommerce attributes.
  • Run a single-product publish test, review the result in WooCommerce, then expand to the full catalog.
  • Document which attributes are global vs custom in your store so future team members don't reintroduce inconsistencies.

 

Order Operations

Get Orders

Introduction
This integration imports orders from WooCommerce into Flxpoint for centralized order management. It ensures you can track and process WooCommerce orders efficiently within Flxpoint, supporting filters for fulfillment and financial statuses.
Follow these steps:
  • 1 Add the Integration: Go to Channels > WooCommerce > Integrations, select “Get Orders.”
  • 2 Connect to WooCommerce: Use your WooCommerce Token and Store URL or set up a new connection via WooCommerce REST API credentials.
  • 3 Configure Settings:
    • Toggle on "Enable Get Orders."
    • Select the Location ID and other filters (fulfillment status, financial status, etc.).
    • Configure retention period for personal information.
    • Add a tag to WooCommerce orders after import (optional).
    • Set the time frame for updated orders (e.g., last 14 days).
    • Configure scheduling (e.g., daily at 6 AM UTC).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Configuration Options
Customize the integration with these settings:
  • Enable Get Orders: Toggle this on to import WooCommerce orders.
  • Location ID: Select the WooCommerce location to import orders from. Orders with a different location are skipped unless you enable “Import Orders with No Location ID.”
  • Import Orders with No Location ID: Enable this to import orders lacking a location; disabled by default (skips such orders).
  • Get Orders with Fulfillment Status: Choose statuses to import: Unfulfilled, Partially Fulfilled, Fulfilled. Note that “Scheduled” and “On Hold” are not supported.
  • Get Orders with Financial Status: Choose statuses to import: Any, Authorized, Pending, Paid, Partially Paid, Partially Refunded, Voided, Unpaid.
  • Personal Identifying Information Retention: Choose retention period: Indefinitely, or 30/60/90 days after shipment.
  • Upload Tag to WooCommerce Order After Importing: Add a tag to WooCommerce orders after import (e.g., “Received by Flxpoint”).
  • Get Orders Updated in the Last X Days: Set the time frame for importing updated orders (e.g., last 14 days).
Advanced Options
  • Import Order Risk Rating
    When enabled, Flxpoint will import risk ratings from WooCommerce for each order, if risk assessment is enabled in WooCommerce or provided via a third-party app in WooCommerce.
    How it Works
    When enabled, orders will import with a risk rating tag:
     High, Medium, Low, Pending, or None

    Order import can be delayed up to 30 minutes for an order if fraud risk evaluation has not yet completed
    If a risk rating is not assigned after 30 minutes, the next Get Orders job will import the order with a risk rating of Pending or None.

    PENDING → WooCommerce had not added a risk rating at the time Flxpoint imported the order.

    NONE → WooCommerce did not run fraud analysis for this order.

    In Order Automation settings, you can build rules using these tags to automatically hold orders.
    Example Rule:
    When Order → Tag → Contains → High or Medium
     → Place Order On Hold
    This allows you to review potential high-risk orders before routing or fulfillment to your suppliers.
  • Read Location From Fulfillment Order (disabled by default). When enabled, Flxpoint will:
    • Fetch each order’s Fulfillment Orders via a separate API call.
    • If exactly one Fulfillment Order exists, use its assigned_location_id as the order’s location.
    • If zero or more than one Fulfillment Orders exist, the order is skipped and a warning is logged.
    • Compare that location ID with your configured Location filter before import.
Setting Spotlight — Why some orders don’t import:
If Read Location From Fulfillment Order is enabled and WooCommerce returns multiple Fulfillment Orders for a single order, Flxpoint will skip importing that order.

Fix: Go to Channels → WooCommerce → Integrations → Get Orders → Advanced Options and disable “Read Location From Fulfillment Order”, then re-run the sync.
Example: Orders 2209 and 2202 were skipped because multiple Fulfillment Orders were returned for each. Disabling the setting allowed these orders to import.
Note: Ensure your fulfillment and financial status filters match your order management needs to avoid missing orders.
Mapping templates control which WooCommerce order data is imported into Flxpoint.
Interface Overview
  • Screen labeled “Get Orders” at the top; name your template (e.g., “WooCommerce Get Orders 1”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: WooCommerce fields (left), Flxpoint fields (right).
Mapping Options
  • Enable: Import the field (e.g., Order ID).
  • Disable: Ignore the field (e.g., Custom Attributes).
  • Required Fields: Order ID and Line Items are required for proper order import.
Order ID and Line Items Mapping Requirement
The Order ID and Line Items fields must be enabled to ensure proper order importing.
  • Required Fields: Order ID and Line Items uniquely identify the order and its products.
  • Error Scenario: Missing Order ID or Line Items may cause:
    Invalid request: Missing required fields 'Order ID' or 'Line Items' for order import
  • Fix: Go to Channels > WooCommerce > Templates > Get Orders > Field Mapping, enable Order ID and Line Items, save, and re-run sync.
Recommendation: Always enable Order ID, Line Items, and billing/shipping addresses for accurate order importing.
Complete Field Mappings
Order Fields
WooCommerce Field Maps To Data Type Example Purpose Status
WooCommerce Order - ID Flxpoint Order ID Number 123456789 Identifies the order Required
WooCommerce Order - Financial Status Flxpoint Financial Status Text Paid Sets payment status Supported
WooCommerce Order - Fulfillment Status Flxpoint Fulfillment Status Text Unfulfilled Sets fulfillment status Supported
WooCommerce Order - Tags Flxpoint Order Tags Text Received by Flxpoint Sets order tags Supported
Line Item Fields
WooCommerce Field Maps To Data Type Example Purpose Status
WooCommerce Line Item - SKU Flxpoint Line Item SKU Text item-sku-001 Identifies the product Required
WooCommerce Line Item - Fulfillable Quantity Flxpoint Line Item Quantity Number 2 Sets quantity to fulfill Supported
WooCommerce Line Item - Price Flxpoint Line Item Price Number $30 Sets item price Supported
Address Fields
WooCommerce Field Maps To Data Type Example Purpose Status
WooCommerce Billing Address - Address 1 Flxpoint Billing Address - Address 1 Text 123 Main St Sets billing address Supported
WooCommerce Shipping Address - Address 1 Flxpoint Shipping Address - Address 1 Text 456 Oak St Sets shipping address Supported
Limitations
Be aware of these limitations:
  • Fulfillment Status Support: “Scheduled” and “On Hold” statuses are not supported; only Unfulfilled, Partially Fulfilled, and Fulfilled are importable.
  • Location ID Filtering: Orders with a different Location ID are skipped unless “Import Orders with No Location ID” is enabled.
  • Fulfillable Quantity Requirement: Orders must have a fulfillable quantity greater than 0 to be linked to Flxpoint listings.
  • Setting Interaction: If Read Location From Fulfillment Order is enabled and WooCommerce returns multiple Fulfillment Orders for a single order, that order will be skipped by design.
  • API Rate Limits: WooCommerce API rate limits may affect large import jobs; monitor usage to avoid interruptions.
Troubleshooting
Troubleshoot issues with these steps:
  • Orders Not Importing: Verify fulfillment/financial status filters and Location ID filter.
  • Location ID Issues: Ensure the Location ID matches or enable “Import Orders with No Location ID.”
  • Missing Data: Confirm required fields (Order ID, Line Items) are enabled in the mapping template.
  • Sync Not Running: Check your sync schedule or run it manually with "Run Sync" and view logs for details.
Orders show in WooCommerce/Postman but not in Flxpoint?
If you see multiple Fulfillment Orders in WooCommerce for a single order (common with split fulfillment) and Read Location From Fulfillment Order is enabled, Flxpoint will skip that order.

Resolution: Disable Read Location From Fulfillment Order and re-run the sync.
Path: Channels → WooCommerce → Integrations → Get Orders → Advanced Options.
Diagnostic Tip: Missing orders often result from mismatched Location IDs, restrictive status filters, or the Fulfillment Order setting described above.
 
 

Sync Orders

Supported | WooCommerce - Sync Orders

Introduction to WooCommerce Sync Orders
Welcome to the WooCommerce Sync Orders integration guide! This integration ensures that order data, such as fulfillment and shipment details, stays consistent between Flxpoint and WooCommerce. It helps you keep WooCommerce updated with tracking information and order statuses, supporting partial shipments and multiple locations. Let’s get started!
Purpose of This Integration
The WooCommerce Sync Orders integration enables you to:
  • Sync fulfillment data, including tracking information, from Flxpoint to WooCommerce.
  • Handle orders with multiple Location IDs, ensuring all items are synced correctly.
  • Support partial shipments, marking orders as Partially Shipped until fully completed.
This ensures consistent order data across your sales channels.
How the Integration Works
The integration follows these steps:
  • 1 Connecting to WooCommerce: Establish a connection using API credentials or WooCommerce REST API credentials to access your WooCommerce store.
  • 2 Identifying Orders: Flxpoint identifies orders in Flxpoint that need to be synced to WooCommerce based on their status and Location ID.
  • 3 Mapping Data: Maps Flxpoint fields (e.g., Tracking Number, Carrier) to WooCommerce fields using a mapping template.
  • 4 Syncing Fulfillment Data: Flxpoint sends fulfillment details to WooCommerce for the specified location.
  • 5 Handling Partial Shipments: Marks orders as Partially Shipped until fully completed, supporting multiple Location IDs.
  • 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep WooCommerce updated with the latest fulfillment information.
Note: API failures pause the integration and trigger notifications.
Configuration Options
Customize the integration with these settings:
  • Enable Sync Orders: Toggle this on to automatically synchronize order data with WooCommerce.
  • Location ID: Select the WooCommerce location to sync order data with (e.g., Shop Location). Learn more at WooCommerce Locations Documentation.
  • Sync "Closed" Order Status Back to WooCommerce: Enable this to sync and archive only future orders from WooCommerce for orders with partial or no fulfillment data.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
Note: Ensure the Location ID matches a valid WooCommerce location to avoid sync failures.
Setup Instructions
Follow these steps:
  • 1 Add the Integration: Go to Channels > WooCommerce > Integrations, select “Sync Orders.”
  • 2 Connect to WooCommerce: Use your WooCommerce Token and Store URL or set up a new connection via WooCommerce REST API credentials.
  • 3 Configure Settings:
    • Toggle on "Enable Sync Orders."
    • Select the WooCommerce Location ID (e.g., Shop Location).
    • Enable "Sync 'Closed' Order Status Back to WooCommerce" if desired.
    • Configure scheduling (e.g., daily at 6 AM UTC).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping Template Details
Mapping templates control which Flxpoint fulfillment data is synced to WooCommerce.
Interface Overview
  • Screen labeled “Sync Orders” at the top; name your template (e.g., “WooCommerce Sync Orders 1”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Flxpoint fields (left), WooCommerce fields (right).
Mapping Options
  • Enable: Sync the field (e.g., Tracking Number).
  • Disable: Ignore the field (e.g., Notify Customer).
  • Required Fields: Tracking Number is required for proper fulfillment syncing.
Tracking Number Mapping Requirement
The Tracking Number field must be enabled to ensure proper fulfillment syncing.
  • Required Field: Tracking Number uniquely identifies the shipment in WooCommerce.
  • Error Scenario: Missing Tracking Number may cause:
    Invalid request: Missing required field 'Tracking Number' for fulfillment sync
  • Fix: Go to Channels > WooCommerce > Templates > Sync Orders > Field Mapping, enable Tracking Number, save, and re-run sync.
Recommendation: Always enable Tracking Number, Tracking URL, and Carrier for reliable fulfillment syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Fulfillment Fields
Flxpoint Field Maps To Data Type Example Purpose Status
Carrier WooCommerce Fulfillment - Tracking Company Text UPS Sets the carrier Supported
Notify Customer WooCommerce Fulfillment - Notify Customer Boolean False Notifies the customer Supported (Default: False)
Tracking Number WooCommerce Fulfillment - Tracking Number Text 1Z9999W999999999 Sets the tracking number Required
Tracking URL WooCommerce Fulfillment - Tracking URL Text https://ups.com/track Sets the tracking URL Supported
Practice Mapping
Try enabling/disabling Flxpoint - Tracking Number:
Data Synced
Here’s what data Flxpoint can sync to WooCommerce:
  • Platform Notifications: Supported. Notify Customer can be set as True or False per mapping.
  • Partial Weekly Shipments: Supported.
  • Partial Order Item Shipments: Supported. Partial shipments are marked as Partially Shipped; fully shipped orders are marked as Shipped.
  • Post-Shipment Status Updates: Supported.
  • Manual Order Item Fulfillments: Not supported.
Limitations
Be aware of these limitations:
  • Multiple Location IDs: For orders with multiple Location IDs, shipments are synced only when available for all items; failed shipments are retried in the next sync job.
  • Location ID Validity: The Location ID must correspond to a valid WooCommerce location for accurate syncing.
  • Field Syncing: Only fields enabled in the mapping template will be synced to WooCommerce.
  • Manual Fulfillments: Manual order item fulfillments are not supported.
  • API Rate Limits: WooCommerce API rate limits may affect large sync jobs; monitor usage to avoid interruptions.
Troubleshooting
Troubleshoot issues with these steps:
  • Connection Issues: Verify your WooCommerce Token and Store URL are correct.
  • Sync Fails for Multiple Locations: Ensure all items in the order are available for shipment at the specified Location ID.
  • Data Not Syncing: Confirm that required fields (e.g., Tracking Number) are enabled in the mapping template.
  • Sync Not Running: Check your sync schedule or run it manually with "Run Sync."
Diagnostic Tip: Sync failures often result from mismatched Location IDs or disabled fields in the mapping template.
Key Details You Need to Know
Key information:
  • Date: As of 09:37 PM -04, May 29, 2025, this integration is operational.
  • Required Fields: Tracking Number must be enabled in the mapping template.
  • API Limits: Monitor WooCommerce API rate limits to avoid sync interruptions.
Pro Tip: Enable "Sync 'Closed' Order Status Back to WooCommerce" to manage partial or unfulfilled orders more effectively.
Conclusion
The WooCommerce Sync Orders integration keeps your order data consistent by syncing fulfillment details between Flxpoint and WooCommerce. Monitor sync logs via "View Logs" to ensure smooth operation, and explore other WooCommerce integrations like Get Orders or Publish Listings to further streamline your workflow. Happy syncing!
 
 

 

 

 

 

 

Troubleshooting

Troubleshooting

Common WooCommerce issues — click any item to expand.

Still stuck? Reach out to Flxpoint Support with the job run ID, affected SKU(s), and a screenshot of the error.