Welcome to the ScanSource Integration Guide! This document will help you seamlessly connect Flxpoint with ScanSource for efficient inventory and order management. Let’s dive in and get started!
How to Connect
ScanSource Integration Setup Guide
📋 Phase 1: Creating Your ScanSource Source
+
Create Source in Flxpoint
Log into your Flxpoint account, navigate to the Sources tab, and click + Add Source to begin.
Set Up Source Details
Enter "ScanSource Supplier" as the source name, select the source type (e.g., Vendor Warehouse), and optionally assign a vendor for better reporting. Click Save & Next to continue.
Tip: Assigning a vendor improves your reporting capabilities and helps with product organization.
Choose Integration Type
After creating your source, you'll see the Integrations section. If no integrations are set up yet, click Start Creating Integrations. You can set up any of these integrations based on your needs:
- Get Inventory (Primary): Retrieves primary inventory data from ScanSource via FTP.
- Get Inventory (Secondary): Sets up an additional inventory feed from ScanSource via FTP.
- Send Orders: Sends orders to ScanSource for fulfillment via API.
- Get Shipments: Pulls shipment information from ScanSource via API.
Note: You can activate any combination of these integrations based on your business needs.
🔐 Phase 2: Setting Up Connection
+
Obtain Your Connection Credentials
To connect to ScanSource, you’ll need FTP credentials for inventory operations and API credentials for order processing. Follow these steps to obtain them:
- Log into your ScanSource account or contact ScanSource support at ScanSource Support to request FTP and API credentials.
- For FTP (used for Get Inventory Primary/Secondary): Retrieve your FTP User, FTP Password, FTP Host, and FTP Port.
- For API (used for Send Orders and Get Shipments): Obtain your API Key and Environment settings.
Important: Keep your credentials secure and do not share them publicly, as they provide access to your ScanSource account data.
Configure Connection Details for FTP
In the New Connection form, enter the FTP details required to connect to ScanSource for inventory retrieval:
- Connection Name: "ScanSource FTP Connection" (or any descriptive name).
- FTP User: Your ScanSource username.
- FTP Password: Your ScanSource password.
- FTP Port: Typically 21 (default FTP port).
- FTP Host: The ScanSource FTP server address.
- FTP Protocol: Select "FTP" from the dropdown.
- File Transfer Mode: Choose "Binary file type" (recommended for inventory files).
- Maintain Constant Connection: Toggle ON for reliability.
Tip: If the connection test fails, double-check your credentials and ensure your ScanSource account is configured for FTP access. Refer to the first carousel image for setup details.
🛒 Phase 3: Setting Up Order Processing
+
Configure Order Processing Integrations
For Send Orders and Get Shipments integrations, create a new connection using API credentials:
- Send Orders: Enable to send orders to ScanSource for fulfillment via API. Map order fields (e.g., Customer Name, Shipping Address) to ensure accurate order transmission.
- Get Shipments: Enable to retrieve shipment updates from ScanSource via API. Map shipment fields (e.g., Tracking Number, Shipment Date) to Flxpoint fields.
Configure Connection Details for API
In the New Connection form, enter the API details for order processing:
- Connection Name: "ScanSource API Connection" (or any descriptive name).
- API Key: Your ScanSource API key.
- Environment: Select "Production" (or "Sandbox" for testing if available).
Tip: Refer to the second carousel image for API setup details.
Automated Order Settings
Configure how orders will be processed:
- Toggle Automatically Send Orders ON to have Flxpoint automatically send orders to ScanSource.
- Set any additional order rules or conditions as needed (e.g., minimum order quantity, specific product categories).
✅ Phase 4: Mapping and Activation
+
Create Field Mapping
After setting up your connections, map ScanSource fields to Flxpoint fields for Get Inventory (Primary) and Get Inventory (Secondary):
- Choose an existing mapping template or create a new one.
- Map essential fields like SKU, Price, Quantity, and Description.
- Set up any transformations needed (e.g., price markups, quantity adjustments).
Tip: For inventory feeds, make sure to map both product details and inventory quantity fields.
Configure SKU Mapping
In the Master SKU section, set up your preferred SKU mapping (Inventory SKU → Master SKU). Consider adding a SKU prefix (e.g., "SCAN-") to identify ScanSource inventory in your system.
Activate and Verify
Complete the setup by clicking Save and Complete. Your ScanSource integration is now active and will run based on your settings.
Next Steps: The initial inventory sync may take some time to complete. You can monitor the progress in the Integrations section of your Flxpoint dashboard under Fulfillment Sources.
×
![]()
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates
Get Inventory (Primary)
Supported | ScanSource - Get Inventory [Primary]
Introduction to ScanSource Get Inventory [Primary]
Welcome to the ScanSource (SS) Get Inventory [Primary] integration guide! This integration retrieves inventory data from ScanSource into Flxpoint, syncing product details, pricing, quantities, and more from full file feeds. It ensures accurate inventory tracking and management within Flxpoint’s Global Inventory Pool (GIP). Let’s get started!
The ScanSource Get Inventory [Primary] integration enables you to:
- Fetch inventory data, including product details, pricing, and quantities, from ScanSource full file feeds.
- Sync inventory data with Flxpoint’s Global Inventory Pool (GIP) for centralized management.
- Support detailed product metadata, such as weights, dimensions, and categories, for accurate inventory records.
The integration follows these steps:
- 1 Connecting to ScanSource: Establish a connection using API credentials to access ScanSource file feeds.
- 2 Fetching Inventory Data: Downloads full file feeds (e.g., `master.txt` for list price, enhanced file for MSRP) from ScanSource.
- 3 Extracting Inventory Details: Extracts product details (e.g., SKU, Quantity, List Price) from the file feeds.
- 4 Mapping Data: Maps ScanSource fields (e.g., Distributor Part Number, Quantity Available) to Flxpoint inventory fields using a mapping template.
- 5 Syncing Data: Imports the mapped data into Flxpoint, updating inventory records in the Global Inventory Pool (GIP).
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your inventory data up-to-date in Flxpoint.
Note: File download failures pause the integration and trigger notifications.
Customize the integration with these settings:
- Connection: Provide ScanSource API credentials to access file feeds (required).
- File Selection: Specify the full file feeds to process (e.g., `master.txt` for list price, enhanced file for MSRP).
- Mapping Template: Define how ScanSource fields map to Flxpoint inventory fields (see Mapping Template Details).
- Sync Frequency: Run manually or schedule syncs (e.g., daily at 6 AM UTC).
Note: Ensure your API credentials are valid to avoid connection issues during file retrieval.
Follow these steps:
- 1 Add the Integration: Go to Channels > ScanSource > Integrations, select “Get Inventory [Primary].”
- 2 Connect to ScanSource: Enter your ScanSource API credentials to establish a connection.
-
3 Configure Settings:
- Specify the full file feeds to process (e.g., `master.txt`, enhanced file).
- Configure sync frequency (e.g., daily at 6 AM UTC).
- 4 Create Mapping Template: Configure field mappings for inventory data (see Mapping Template Details).
- 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping templates control which ScanSource inventory data is imported into Flxpoint.
Interface Overview
- Screen labeled “Get Inventory [Primary]” at the top; name your template (e.g., “ScanSource Inventory Primary 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: ScanSource fields (left), Flxpoint fields (right).
Mapping Options
- Don't Map: Ignore the field (e.g., Authorization Codes).
- Set To Empty: Clear the field in Flxpoint.
- Direct Copy: Copy the field as-is (e.g., for All Images).
- Field: Map a ScanSource field to a Flxpoint field (e.g., ScanSource Product - Manufacturer to Flxpoint Brand).
- Value: Set a static value (e.g., Weight Unit to “lb”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., only sync if Item Status is Active).
- Required Fields: Distributor Part Number (for SKU), Quantity Available.
Distributor Part Number Mapping Requirement
The Distributor Part Number field must be mapped to ensure proper inventory identification in Flxpoint.
- Required Field: Distributor Part Number uniquely identifies inventory items.
-
Error Scenario: Unmapped Distributor Part Number may cause:
Invalid request: Missing required field 'Distributor Part Number' for inventory sync
- Fix: Go to Channels > ScanSource > Templates > Get Inventory [Primary] > Field Mapping, map Distributor Part Number to Flxpoint SKU, save, and re-run sync.
Recommendation: Always map Distributor Part Number, Quantity Available, and Description for reliable inventory syncing.
Complete Field Mappings
Below are the fields you can map from ScanSource to Flxpoint:
Inventory Parent Fields
| ScanSource Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| ScanSource Product - Web Description | Flxpoint Description | Text | High-quality wireless mouse | Sets product description | Supported |
| ScanSource Inventory - Description | Flxpoint Title | Text | Wireless Mouse | Sets product title | Supported |
| ScanSource Inventory - Distributor Part Number | Flxpoint Parent SKU | Text | SS-MOUSE-001 | Sets parent SKU identifier | Required |
| ScanSource Product - Manufacturer | Flxpoint Brand | Text | Logitech | Sets product brand | Supported |
| ScanSource Product - Product Hierarchy 1 | Flxpoint Category 1 | Text | Electronics | Sets primary category | Supported |
| ScanSource Product - Product Hierarchy 2 | Flxpoint Category 2 | Text | Peripherals | Sets secondary category | Supported |
| ScanSource Product - Product Hierarchy 3 | Flxpoint Category 3 | Text | Mice | Sets tertiary category | Supported |
| ScanSource Product - Item Image URL | Flxpoint All Images | Text | https://example.com/image.jpg | Sets product images | Direct Copy Supported |
| ScanSource Product - Spec Sheet URL | Flxpoint Custom Field | Text | https://example.com/specs.pdf | Sets specification sheet URL | Supported |
| ScanSource Product - Country Of Origin | Flxpoint Custom Field | Text | USA | Sets country of origin | Supported |
| ScanSource Inventory - UNSPSC Code | Flxpoint Custom Field | Text | 43211708 | Sets UNSPSC code | Supported |
Inventory Variant Fields
| ScanSource Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| ScanSource Inventory - Distributor Part Number | Flxpoint SKU | Text | SS-MOUSE-001 | Identifies the variant | Required |
| ScanSource Inventory - Distributor Part Number | Flxpoint Master SKU | Text | SS-MOUSE-001 | Sets master SKU identifier | Supported |
| ScanSource Product - Quantity Available | Flxpoint Quantity | Number | 100 | Sets inventory quantity | Supported |
| ScanSource Inventory - List Price | Flxpoint Source List Price | Number | $50 | Sets selling price | Supported |
| ScanSource Product - MSRP | Flxpoint MSRP | Number | $75 | Sets manufacturer’s suggested retail price | Supported |
| ScanSource Product - Contract Price | Flxpoint Cost | Number | $40 | Sets product cost | Supported |
| ScanSource Product - EAN UPC | Flxpoint UPC | Text | 012345678905 | Sets universal product code | Supported |
| ScanSource Product - EAN UPC | Flxpoint GTIN | Text | 012345678905 | Sets global trade item number | Supported |
| ScanSource Product - Manufacturer Item Number | Flxpoint MPN | Text | MPN123 | Sets manufacturer part number | Supported |
| ScanSource Product - Gross Weight | Flxpoint Weight | Number | 0.5 | Sets variant weight | Supported |
| ScanSource Product - Gross Weight UOM | Flxpoint Weight Unit | Text | lb | Sets unit of weight | Supported |
| ScanSource Product - Packaged Height | Flxpoint Height | Number | 5 | Sets height | Supported |
| ScanSource Product - Packaged Length | Flxpoint Length | Number | 10 | Sets length | Supported |
| ScanSource Product - Packaged Width | Flxpoint Width | Number | 8 | Sets width | Supported |
| ScanSource Product - Packaged Height UOM | Flxpoint Dimension Unit | Text | in | Sets dimension unit | Supported |
Practice Mapping
Try mapping ScanSource Inventory - Distributor Part Number:
Here’s what data Flxpoint can retrieve from ScanSource:
- Custom Fields: Supported. Metadata fields (e.g., UNSPSC Code, Country Of Origin) can be mapped individually, but there’s no “direct copy” option for custom fields.
- Variations/Options: Not supported.
- Generic Pricing: Supported. List price from `master.txt`, MSRP from enhanced file.
- Client Pricing: Uncertain. Files require client credentials, so unique pricing may be available but is not confirmed.
- Quantity: Supported.
- Multiple Warehouses: Not supported.
- Weights & Dimensions: Supported. Includes weight, height, length, width, and units.
- Images: Supported. Item Image URL can be mapped.
- Categories: Supported. Product Hierarchy fields can be mapped to Flxpoint categories.
- Feed Type: Full file feed only; no delta feed support.
- Archive Support: Supported via full file archiving.
Be aware of these limitations:
- Full Feed Only: Only full file feeds are supported; delta feeds are not available.
- Multiple Warehouses Not Supported: Inventory data is not associated with multiple warehouses.
- Variations/Options Not Supported: Product variations or options cannot be imported.
- Required Fields: Distributor Part Number and Quantity Available must be mapped.
- File Access: Requires valid API credentials to access ScanSource file feeds; connectivity issues may pause the integration.
Troubleshoot issues with these steps:
- Inventory Not Syncing: Verify your ScanSource API credentials are correct and the file feeds are accessible.
- Missing Data: Ensure Distributor Part Number and Quantity Available are mapped in the template.
- File Download Errors: Check for connectivity issues or incorrect file paths; ensure the specified files (e.g., `master.txt`) exist.
-
Incomplete Data: If products are missing, ensure all required fields are populated and mapped:
Warning: Product skipped due to missing Distributor Part Number
Diagnostic Tip: Missing inventory data often results from unmapped required fields or file access issues.
Key information:
- Date: As of 07:44 AM -04, May 30, 2025, this integration is operational.
- Required Fields: Distributor Part Number and Quantity Available must be mapped.
- File Access: Ensure API credentials are valid to avoid sync interruptions.
Pro Tip: Map all required fields and test file access to ensure smooth inventory syncing.
Conclusion
The ScanSource Get Inventory [Primary] integration automates inventory retrieval, ensuring your Flxpoint Global Inventory Pool reflects accurate ScanSource product data. Customize mappings and schedules to fit your workflow, streamlining inventory management. Happy syncing!
Get Inventory (Secondary)
Supported | ScanSource - Get Inventory [Secondary]
Introduction to ScanSource Get Inventory [Secondary]
Welcome to the ScanSource (SS) Get Inventory [Secondary] integration guide! This integration retrieves secondary inventory data, focusing on variant-level details like quantity and pricing, from ScanSource into Flxpoint. It complements the primary inventory integration by syncing variant-specific data into Flxpoint’s Global Inventory Pool (GIP). Let’s get started!
The ScanSource Get Inventory [Secondary] integration enables you to:
- Fetch variant-level inventory data, such as quantity and pricing, from ScanSource full file feeds.
- Sync this data with Flxpoint’s Global Inventory Pool (GIP) for centralized management.
- Ensure accurate variant details to support inventory tracking across your sales channels.
The integration follows these steps:
- 1 Connecting to ScanSource: Establish a connection using API credentials to access ScanSource file feeds.
- 2 Fetching Inventory Data: Downloads full file feeds from ScanSource, focusing on variant-level details.
- 3 Extracting Variant Details: Extracts variant data (e.g., SKU, Quantity, List Price) from the file feeds.
- 4 Mapping Data: Maps ScanSource variant fields (e.g., Distributor Part Number, Quantity Available) to Flxpoint inventory fields using a mapping template.
- 5 Syncing Data: Imports the mapped data into Flxpoint, updating variant records in the Global Inventory Pool (GIP).
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your variant inventory data up-to-date in Flxpoint.
Note: File download failures pause the integration and trigger notifications.
Customize the integration with these settings:
- Connection: Provide ScanSource API credentials to access file feeds (required).
- File Selection: Specify the full file feeds to process for variant data.
- Mapping Template: Define how ScanSource variant fields map to Flxpoint inventory fields (see Mapping Template Details).
- Sync Frequency: Run manually or schedule syncs (e.g., daily at 6 AM UTC).
Note: Ensure your API credentials are valid to avoid connection issues during file retrieval.
Follow these steps:
- 1 Add the Integration: Go to Channels > ScanSource > Integrations, select “Get Inventory [Secondary].”
- 2 Connect to ScanSource: Enter your ScanSource API credentials to establish a connection.
-
3 Configure Settings:
- Specify the full file feeds to process for variant data.
- Configure sync frequency (e.g., daily at 6 AM UTC).
- 4 Create Mapping Template: Configure field mappings for variant data (see Mapping Template Details).
- 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping templates control which ScanSource variant inventory data is imported into Flxpoint.
Interface Overview
- Screen labeled “Get Inventory [Secondary]” at the top; name your template (e.g., “ScanSource Inventory Secondary 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: ScanSource fields (left), Flxpoint fields (right).
Mapping Options
- Don't Map: Ignore the field (e.g., Authorization Codes).
- Set To Empty: Clear the field in Flxpoint.
- Field: Map a ScanSource field to a Flxpoint field (e.g., ScanSource Inventory - Distributor Part Number to Flxpoint SKU).
- Value: Set a static value (e.g., Weight Unit to “lb”).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., only sync if Active is T).
- Required Fields: Distributor Part Number (for SKU), Quantity Available.
Distributor Part Number Mapping Requirement
The Distributor Part Number field must be mapped to ensure proper variant identification in Flxpoint.
- Required Field: Distributor Part Number uniquely identifies inventory variants.
-
Error Scenario: Unmapped Distributor Part Number may cause:
Invalid request: Missing required field 'Distributor Part Number' for inventory sync
- Fix: Go to Channels > ScanSource > Templates > Get Inventory [Secondary] > Field Mapping, map Distributor Part Number to Flxpoint SKU, save, and re-run sync.
Recommendation: Always map Distributor Part Number and Quantity Available for reliable variant syncing.
Complete Field Mappings
Below are the fields you can map from ScanSource to Flxpoint:
Inventory Variant Fields
| ScanSource Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| ScanSource Inventory - Distributor Part Number | Flxpoint SKU | Text | SS-MOUSE-001 | Identifies the variant | Required |
| ScanSource Inventory - Available Qty | Flxpoint Quantity | Number | 100 | Sets inventory quantity | Supported |
| ScanSource Inventory - List Price | Flxpoint Source List Price | Number | $50 | Sets selling price | Supported |
| ScanSource Inventory - Upc Code | Flxpoint UPC | Text | 012345678905 | Sets universal product code | Supported |
| ScanSource Inventory - Upc Code | Flxpoint GTIN | Text | 012345678905 | Sets global trade item number | Supported |
| ScanSource Inventory - Weight | Flxpoint Weight | Number | 0.5 | Sets variant weight | Supported |
| ScanSource Inventory - Uom | Flxpoint Weight Unit | Text | lb | Sets unit of weight | Supported |
| ScanSource Inventory - Height | Flxpoint Height | Number | 5 | Sets height | Supported |
| ScanSource Inventory - Length | Flxpoint Length | Number | 10 | Sets length | Supported |
| ScanSource Inventory - Width | Flxpoint Width | Number | 8 | Sets width | Supported |
Practice Mapping
Try mapping ScanSource Inventory - Distributor Part Number:
Here’s what data Flxpoint can retrieve from ScanSource:
- Custom Fields (Variants Only): Not supported.
- Generic Pricing: Supported (e.g., List Price).
- Client Pricing: Uncertain; files require client credentials, so unique pricing may be available but is not confirmed.
- Quantity: Supported.
- Multiple Warehouses: Not supported.
- Weights & Dimensions: Supported (includes Weight, Height, Length, Width, and units).
- Feed Type: Full file feed only; no delta feed support.
- Archive Support: Supported via full feed.
Be aware of these limitations:
- Full Feed Only: Only full file feeds are supported; delta feeds are not available.
- Multiple Warehouses Not Supported: Variant data is not associated with multiple warehouses.
- Custom Fields Not Supported: Variant-level custom fields cannot be imported.
- Required Fields: Distributor Part Number and Quantity Available must be mapped.
- File Access: Requires valid API credentials to access ScanSource file feeds; connectivity issues may pause the integration.
Troubleshoot issues with these steps:
- Variants Not Syncing: Verify your ScanSource API credentials are correct and the file feeds are accessible.
- Missing Quantities or Pricing: Ensure Distributor Part Number and Quantity Available are mapped in the mapping template.
- File Download Errors: Check for connectivity issues or incorrect file paths; ensure the specified files exist.
-
Incomplete Data: If variants are missing, ensure all required fields are populated and mapped:
Warning: Variant skipped due to missing Distributor Part Number
Diagnostic Tip: Missing variant data often results from unmapped required fields or file access issues.
Key information:
- Date: As of 08:00 AM -04, May 30, 2025, this integration is operational.
- Required Fields: Distributor Part Number and Quantity Available must be mapped.
- File Access: Ensure API credentials are valid to avoid sync interruptions.
Pro Tip: Map all required fields and test file access to ensure smooth variant syncing.
Conclusion
The ScanSource Get Inventory [Secondary] integration enhances inventory management by syncing variant-level data like quantity and pricing into Flxpoint’s Global Inventory Pool. With detailed field mappings and scheduled syncs, it ensures accurate variant tracking across your sales channels. Happy syncing!
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.
Send Fulfillment Requests
Supported | ScanSource - Send Fulfillment Requests
Introduction to ScanSource Send Fulfillment Requests
Welcome to the ScanSource (SS) Send Fulfillment Requests integration guide! This integration sends fulfillment requests from Flxpoint to ScanSource, ensuring accurate order processing with shipping details and item SKUs. It streamlines order fulfillment by automating the submission process, including an automated shipping selection via API. Let’s get started!
The ScanSource Send Fulfillment Requests integration enables you to:
- Send fulfillment requests from Flxpoint to ScanSource for order processing.
- Include shipping details and item SKUs without requiring customer or internal item ID associations.
- Automate shipping selection using a Ship Quote API call, with the option to hard-code service level codes.
The integration follows these steps:
- 1 Connecting to ScanSource: Establish a connection using ScanSource API credentials.
- 2 Preparing Order Data: Collects fulfillment request data, including Fulfillment Request Number, shipping details, and item SKUs from Flxpoint.
- 3 Mapping Data: Maps Flxpoint fields (e.g., Fulfillment Request Number, SKU) to ScanSource order fields using a mapping template.
- 4 Determining Shipping: Automatically retrieves a service level code via a Ship Quote API call, unless a code is hard-coded or rules are applied.
- 5 Submitting Fulfillment Request: Sends the fulfillment request to ScanSource via an API call, marking the order as processed.
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to ensure timely order fulfillment with ScanSource.
Note: API failures pause the integration and trigger notifications.
Customize the integration with these settings:
- Connection: Provide ScanSource API credentials to establish a connection (required).
- Service Level Code: Optionally hard-code a service level code or apply rules to bypass the Ship Quote API call; if not set, the API call retrieves it automatically.
- Mapping Template: Define how Flxpoint fields map to ScanSource order fields (see Mapping Template Details).
- Sync Frequency: Run manually or schedule syncs (e.g., daily at 6 AM UTC).
Note: Ensure your API credentials are valid to avoid connection issues during submission.
Follow these steps:
- 1 Add the Integration: Go to Channels > ScanSource > Integrations, select “Send Fulfillment Requests.”
- 2 Connect to ScanSource: Enter your ScanSource API credentials to establish a connection.
-
3 Configure Settings:
- Optionally hard-code a service level code or apply rules for shipping selection.
- Configure sync frequency (e.g., daily at 6 AM UTC).
- 4 Create Mapping Template: Configure field mappings for orders (see Mapping Template Details).
- 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping templates control how Flxpoint order data is sent to ScanSource for fulfillment.
Interface Overview
- Screen labeled “Send Fulfillment Requests” at the top; name your template (e.g., “ScanSource Send FRs 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Flxpoint fields (left), ScanSource fields (right).
Mapping Options
- Don't Map: Ignore the field (e.g., Note).
- Set To Empty: Clear the field in ScanSource.
- Field: Map a Flxpoint field to a ScanSource field (e.g., Fulfillment Request Number to PO Number).
- Value: Set a static value (e.g., Shipping Method Code to a specific code).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., map Quantity only if greater than 0).
- Required Fields: Fulfillment Request Number, SKU, Quantity.
Fulfillment Request Number Mapping Requirement
The Fulfillment Request Number field must be mapped to ensure proper order submission and later reference in Get Shipments.
- Required Field: Fulfillment Request Number uniquely identifies the order in ScanSource.
-
Error Scenario: Unmapped Fulfillment Request Number may cause:
Invalid request: Missing required field 'Fulfillment Request Number' for order submission
- Fix: Go to Channels > ScanSource > Templates > Send Fulfillment Requests > Field Mapping, map Fulfillment Request Number to ScanSource PO Number, save, and re-run sync.
Recommendation: Always map Fulfillment Request Number, SKU, and Quantity for reliable order submission.
Complete Field Mappings
Below are the fields you can map from Flxpoint to ScanSource:
Order Fields
| Flxpoint Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| Fulfillment Request - Fulfillment Request Number | ScanSource PO Number | Text | FR-12345 | Identifies the order | Required |
| Fulfillment Request - Note | ScanSource Memo | Text | Urgent delivery | Adds order notes | Supported |
| Shipping Address - Email | ScanSource Entered By Email Address | Text | customer@example.com | Sets contact email | Supported |
| Source Shipping Method - Shipping Code | ScanSource Shipping Method Code | Text | STD | Sets shipping method | Supported |
Order Address Fields
| Flxpoint Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| Shipping Address - Full Name | ScanSource Name | Text | John Doe | Sets recipient name | Supported |
| Shipping Address - Address Line 1 | ScanSource Street 1 | Text | 123 Main St | Sets primary address line | Supported |
| Shipping Address - Address Line 2 | ScanSource Street 2 | Text | Apt 4B | Sets secondary address line | Supported |
| Shipping Address - City | ScanSource City | Text | New York | Sets city | Supported |
| Shipping Address - State | ScanSource State | Text | NY | Sets state | Supported |
| Shipping Address - Country | ScanSource Country | Text | USA | Sets country | Supported |
| Shipping Address - Postal Code | ScanSource Postal Code | Text | 10001 | Sets postal code | Supported |
Order Item Fields
| Flxpoint Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| Fulfillment Request Item - SKU | ScanSource Part Number | Text | SS-MOUSE-001 | Identifies the product | Required |
| Fulfillment Request Item - Quantity | ScanSource Quantity | Number | 2 | Sets the quantity to fulfill | Required |
| Fulfillment Request Item - Cost | ScanSource Price | Number | $50 | Sets item price | Supported |
| Fulfillment Request Item - PO Line Item # | ScanSource PO Line Number | Number | 1 | Identifies the line item | Supported |
Practice Mapping
Try mapping Fulfillment Request - Fulfillment Request Number:
Here’s what data Flxpoint sends to ScanSource:
- Fulfillment Request Number: Required for submission and later reference in Get Shipments.
- Customer Association: Not required; only shipping details are sent.
- FR Item Association: Sends SKU directly; no internal item ID needed.
- Auto Acknowledgements: Not applicable; orders are marked as processed upon submission.
- Shipping Selection: Automated via Ship Quote API call; can be hard-coded or overridden with rules.
- Custom Fields: Not supported.
- Attachments: Not supported.
Be aware of these limitations:
- Service Level Code Required: Order submission requires a service level code for shipping; this is automated via a Ship Quote API call if not provided.
- Required Fields: Fulfillment Request Number, SKU, and Quantity must be mapped.
- No Custom Fields or Attachments: Custom fields and attachments are not supported.
Troubleshoot issues with these steps:
- Order Not Submitting: Verify your ScanSource API credentials and ensure connectivity.
- Missing Required Fields: Ensure Fulfillment Request Number, SKU, and Quantity are mapped in the template.
-
Shipping Errors: If a service level code is missing and the Ship Quote API call fails, hard-code a code or check API connectivity:
Error: Missing service level code for order submission
- Incomplete Submission: Verify all required fields are populated and mapped correctly.
Diagnostic Tip: Failed submissions often result from unmapped required fields or API connectivity issues.
Key information:
- Date: As of 07:58 AM -04, May 30, 2025, this integration is operational.
- Required Fields: Fulfillment Request Number, SKU, and Quantity must be mapped.
- API Connectivity: Ensure API credentials are valid to avoid submission interruptions.
Pro Tip: Map all required fields and test API connectivity to ensure smooth order submission.
Conclusion
The ScanSource Send Fulfillment Requests integration automates order fulfillment by sending requests from Flxpoint to ScanSource, ensuring accurate processing with shipping details and SKUs. With automated shipping selection and detailed field mappings, it streamlines your order management process. Happy fulfilling!
Get Shipments
Supported | ScanSource - Get Shipments
Introduction to ScanSource Get Shipments
Welcome to the ScanSource (SS) Get Shipments integration guide! This integration retrieves shipment data from ScanSource into Flxpoint, syncing tracking information like tracking numbers and carrier details for fulfilled orders. It ensures accurate shipment tracking within Flxpoint, assuming full shipments as item details are not provided. Let’s get started!
The ScanSource Get Shipments integration enables you to:
- Retrieve shipment data from ScanSource to update Flxpoint with fulfilled order details.
- Sync tracking information, including carrier, tracking number, and status.
- Ensure accurate shipment tracking by importing full shipment records into Flxpoint.
The integration follows these steps:
- 1 Connecting to ScanSource: Establish a connection using ScanSource API credentials.
- 2 Fetching Shipment Data: Queries ScanSource for shipment records associated with previously submitted fulfillment requests.
- 3 Extracting Shipment Details: Extracts tracking information (e.g., Tracking Number, Carrier Code) from the response.
- 4 Mapping Data: Maps ScanSource shipment fields to Flxpoint fields using a mapping template.
- 5 Syncing Data: Imports the mapped shipment data into Flxpoint, updating order records.
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep your shipment data up-to-date in Flxpoint.
Note: API failures pause the integration and trigger notifications.
Customize the integration with these settings:
- Connection: Provide ScanSource API credentials to establish a connection (required).
- Mapping Template: Define how ScanSource shipment fields map to Flxpoint fields (see Mapping Template Details).
- Sync Frequency: Run manually or schedule syncs (e.g., daily at 6 AM UTC).
Note: Ensure your API credentials are valid to avoid connection issues during data retrieval.
Follow these steps:
- 1 Add the Integration: Go to Channels > ScanSource > Integrations, select “Get Shipments.”
- 2 Connect to ScanSource: Enter your ScanSource API credentials to establish a connection.
-
3 Configure Settings:
- Configure sync frequency (e.g., daily at 6 AM UTC).
- 4 Create Mapping Template: Configure field mappings for shipments (see Mapping Template Details).
- 5 Run the Integration: Start with Run Sync or schedule automatic syncs.
Mapping templates control how ScanSource shipment data is imported into Flxpoint.
Interface Overview
- Screen labeled “Get Shipments” at the top; name your template (e.g., “ScanSource Get Shipments 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: ScanSource fields (left), Flxpoint fields (right).
Mapping Options
- Don't Map: Ignore the field (e.g., Delivery Signature Name).
- Set To Empty: Clear the field in Flxpoint.
- Field: Map a ScanSource field to a Flxpoint field (e.g., ScanSource Shipment - Tracking Number to Flxpoint Tracking Number).
- Value: Set a static value (e.g., Method to a specific value).
- Mapping Set: Apply a predefined mapping set for complex mappings.
- Rules: Add custom rules to transform or filter data (e.g., prepend a value to Delivery Signature Name).
- Required Fields: Tracking Number, Fulfillment Request Number.
Tracking Number Mapping Requirement
The Tracking Number field must be mapped to ensure proper shipment tracking in Flxpoint.
- Required Field: Tracking Number uniquely identifies the shipment.
-
Error Scenario: Missing Tracking Number may cause:
Invalid request: Missing required field 'Tracking Number' for shipment import
- Fix: Go to Channels > ScanSource > Templates > Get Shipments > Field Mapping, map Tracking Number to Flxpoint Tracking Number, save, and re-run sync.
Recommendation: Always map Tracking Number and Fulfillment Request Number for accurate shipment tracking.
Complete Field Mappings
Below are the fields you can map from ScanSource to Flxpoint:
Shipment Fields
| ScanSource Field | Maps To | Data Type | Example | Purpose | Status |
|---|---|---|---|---|---|
| ScanSource Shipment - Tracking Number | Flxpoint Tracking Number | Text | 1Z9999W999999999 | Sets the tracking number | Required |
| ScanSource Shipment - Carrier Code | Flxpoint Carrier | Text | UPS | Sets the carrier | Supported |
| ScanSource Shipment - Service Info | Flxpoint Method | Text | Ground | Sets the shipping method | Supported |
| ScanSource Shipment - Fulfillment Request Number | Flxpoint Fulfillment Request Number | Text | FR-12345 | Links to the original fulfillment request | Required |
| ScanSource Shipment - Delivery Signature Name | Flxpoint Note | Text | Jane Doe | Adds a delivery note | Supported |
Practice Mapping
Try mapping ScanSource Shipment - Tracking Number:
Here’s what data Flxpoint can retrieve from ScanSource:
- Carrier & Methods: Provided by ScanSource (e.g., Carrier Code, Service Info).
- Shipment Item Association: Not supported; assumes full shipment as no items are returned.
- Partial Shipments: Not supported; assumes full shipment as no items are returned.
- Invoice Information: Not supported.
- Custom Fields: Not supported.
Be aware of these limitations:
- No Partial Shipment Support: Assumes full shipments as item details are not provided.
- Required Fields: Tracking Number and Fulfillment Request Number must be mapped.
- No Custom Fields or Invoice Info: Custom fields and invoice information are not supported.
Troubleshoot issues with these steps:
- Shipments Not Importing: Verify your ScanSource API credentials and ensure connectivity.
- Missing Data: Ensure Tracking Number and Fulfillment Request Number are mapped in the mapping template.
- API Errors: Check for ScanSource API connectivity issues; reduce sync frequency if needed.
-
Incomplete Data: If shipment details are missing, ensure all required fields are populated and mapped:
Warning: Shipment import failed due to missing Tracking Number
Diagnostic Tip: Missing shipment data often results from unmapped required fields or API connectivity issues.
Key information:
- Date: As of 08:08 AM -04, May 30, 2025, this integration is operational.
- Required Fields: Tracking Number and Fulfillment Request Number must be mapped.
- API Connectivity: Ensure API credentials are valid to avoid sync interruptions.
Pro Tip: Map all required fields and verify API connectivity to ensure accurate shipment retrieval.
Conclusion
The ScanSource Get Shipments integration automates the retrieval of shipment data from ScanSource to Flxpoint, ensuring accurate tracking of fulfilled orders. With detailed field mappings and scheduled syncs, it enhances your order fulfillment process, despite assuming full shipments. Happy tracking!