Kroll is a trusted wholesale distributor specializing in tactical, outdoor, and law enforcement products. When integrated as a source in Flxpoint, it allows you to efficiently import product catalogs, synchronize inventory, and automate order fulfillment via FTP or API connections. With Kroll, you gain access to up-to-date inventory data and seamless order processing for their extensive product range.
How To Connect
Step 1: Log into your Flxpoint account and go to the Sources tab.
Step 2: Click + Add Source to create a new source for your vendor.
Step 3: Enter the source name as "Kroll", select the source type (e.g., Vendor Warehouse), and choose whether to assign a vendor (recommended for better reporting). Click Save & Next.
Step 4: Navigate to the desired integration (e.g., Get Inventory, Send Fulfillment Requests, Get Shipments, or Get Inventory [Secondary]) under Integrations. If no integrations are set up, click Start Creating Integrations. You can activate any of these four integrations or others as needed.
Step 5: Select your vendor’s integration (e.g., Kroll) from the list to open the connection setup screen.
Step 6: Fill out the New Kroll Connection form with the appropriate credentials based on the integration:
For Get Inventory [Primary/Secondary]: Use FTP credentials.
Connection Name – e.g., "Kroll FTP Connection" (required).
FTP Username – Your Kroll FTP username, also used as the Account Number for other integrations (required).
FTP Password – Your Kroll FTP password (required).
For Send Fulfillment Requests or Get Shipments: Use API credentials.
Connection Name – e.g., "Kroll API Connection" (required).
Account Number – Same as your FTP Username (required).
API Username – Your Kroll API username (required).
API Password – Your Kroll API password (required).
Step 7: Click Test Connection to verify your credentials, then click Save Connection.
Step 8: Choose or create a Mapping Template. Map Kroll fields (e.g., SKU, Quantity) to Flxpoint fields, then click Save and Complete.
Step 9: Your Kroll integration is now active. The selected process (e.g., Get Inventory, Send Fulfillment Requests) will run based on your settings.
×
![]()
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 | Kroll - Get Inventory [Primary]
Introduction to Kroll - Get Inventory [Primary] Integration
The Kroll - Get Inventory [Primary] tool connects to your Kroll FTP account and pulls in all the essential files to manage your inventory and product details seamlessly. This guide helps you set up the integration to retrieve and map Kroll’s inventory data into your Flxpoint system. Let’s dive in!
The Kroll - Get Inventory [Primary] integration connects your Flxpoint system to Kroll to:
- Retrieve essential inventory and product data files from Kroll’s FTP server, such as stock levels, discontinued stock info, full product catalog, and high-quality images.
- Map Kroll’s data fields to your inventory system for seamless integration and management.
- Ensure accurate and up-to-date inventory details by pulling in comprehensive product information.
The integration follows a structured process to retrieve and map inventory data from Kroll:
- Secure FTP Connection: Establishes a secure FTP connection using your Kroll account details (username, password, etc.).
-
File Retrieval: Pulls in essential files from specified paths, including:
- ProductData/KrollDealer_Inventory_Export2K-TXT: Contains stock levels for selected warehouses (e.g., Kroll’s main distribution centers).
- ProductData/Kroll_Stock_Disco_CSO.txt: Provides discontinued stock info to keep your inventory up to date.
- ProductData/Kroll_Complete_Catalog.txt: A full catalog of products with details like SKU, title, and categories.
- ProductImages/NCR/Large/NCR-3138D.png: High-quality product images for your listings, directly linked for easy integration.
- Data Mapping: Uses the Mapping Dashboard ("Kroll - Get Inventory [Primary]") to map Kroll’s data fields to your inventory system.
- Image Handling: Supports downloading images via FTP or using a separate process like Source Image Grabber for efficiency.
Note: Ensure your Kroll FTP account credentials are correctly configured to avoid retrieval failures.
Customize the integration to fit your needs:
- File Path: Specify the exact path to your files (e.g., /drive/assets_cloudfront_s3_us_east_1_amazonaws.com/integration_files/kroll/kroll_ftp_image_feed.csv).
- Image Handling: Choose to download images via FTP or use a separate process like Source Image Grabber for efficiency.
Follow these steps to set up the Kroll - Get Inventory [Primary] integration:
- 1 Configure FTP Connection: Provide your Kroll FTP account details (username, password, etc.) to establish a secure connection.
- 2 Specify File Paths: Set the exact paths to your Kroll files (e.g., /drive/assets_cloudfront_s3_us_east_1_amazonaws.com/integration_files/kroll/kroll_ftp_image_feed.csv).
- 3 Configure Image Handling: Decide whether to download images via FTP or use a separate process like Source Image Grabber.
- 4 Create a Mapping Template: Use the Mapping Dashboard ("Kroll - Get Inventory [Primary]") to define how Kroll’s data fields map to your inventory system (details below).
- The mapping screen is labeled “Kroll - Get Inventory [Primary]” in the Mapping Dashboard.
- Buttons available: Save to save your mappings, Duplicate to copy setups, and Delete to remove unwanted mappings.
-
Features include:
- Dropdowns: Searchable dropdowns to quickly find and map fields.
- Columns: Left (Kroll fields), Right (your inventory fields).
This section provides key details about the Kroll - Get Inventory [Primary] integration to help you understand the process:
- Kroll Integration: Connects to your Kroll FTP account to retrieve inventory and product data files, including stock levels, discontinued stock info, full product catalog, and images.
- Extra Features: Supports 100 custom fields for unique details, 10 summary fields for totals (e.g., stock across locations), and searchable dropdowns for efficient mapping.
- Weight Unit Options: Choose between full names ("pound," "ounce," "gram," "kilogram") or abbreviated versions ("lb," "oz"); full name takes priority if both are set.
Tip: Use the Mapping Dashboard’s smart rules and transformation tools to customize data mapping, ensuring Kroll’s data aligns perfectly with your inventory system.
Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text or "N" for numbers, as in the dashboard):
Kroll - Get Inventory [Primary] Mappings
| Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU (T) | Inventory: SKU | KRL12345 | Identifies the product in your inventory system | Required |
| Title (T) | Inventory: Title | Blue Widget | Sets the product’s display title | Required |
| Description (T) | Inventory: Description | A durable blue widget | Provides a short description of the product | Optional |
| Long Description (T) | Inventory: Long Description | A high-quality blue widget made from durable materials, perfect for everyday use. | Provides a detailed description of the product | Optional |
| Manufacturer (T) | Inventory: Manufacturer | Kroll Inc. | Specifies the product’s manufacturer | Optional |
| MPN (T) | Inventory: MPN | WGT-12345 | Sets the Manufacturer Part Number for identification | Optional |
| UPC (T) | Inventory: UPC | 012345678905 | Sets the Universal Product Code for barcoding | Optional |
| Cost (N) | Inventory: Cost | 15.00 | Records the product’s cost price | Optional |
| MSRP (N) | Inventory: MSRP | 29.99 | Sets the Manufacturer’s Suggested Retail Price | Optional |
| Quantity (N) | Inventory: Quantity | 100 | Records the stock quantity available | Optional |
| Weight (N) | Inventory: Weight | 2.5 | Records the product weight (requires a weight unit) | Optional |
| Weight Unit (T) | Inventory: Weight Unit | pound | Specifies the unit of weight (options: pound, ounce, gram, kilogram; full name takes priority if both full and abbreviated are set) | Optional |
| Weight Unit (Abbreviated) (T) | Inventory: Weight Unit | lb | Specifies the abbreviated unit of weight (options: lb, oz; used if full name is not set) | Optional |
| Height (N) | Inventory: Height | 10 | Records the height of the product for shipping and storage | Optional |
| Length (N) | Inventory: Length | 15 | Records the length of the product for shipping and storage | Optional |
| Width (N) | Inventory: Width | 12 | Records the width of the product for shipping and storage | Optional |
| Image (T) | Inventory: Image | https://example.com/NCR-3138D.png | Sets the URL or path to the product image | Optional |
| Primary Category (T) | Inventory: Primary Category | Widgets | Assigns the product to the main category | Optional |
| Sub Category (T) | Inventory: Sub Category | Blue Widgets | Assigns the product to a subcategory | Optional |
| Parent SKU (T) | Inventory: Parent SKU | KRL-PARENT | Links the product to a parent SKU for variants | Optional |
| Country of Origin (T) | Inventory: Country of Origin | USA | Records where the product is made | Optional |
| Hazardous (T) | Inventory: Hazardous | Yes | Indicates if the product has hazardous properties | Optional |
| Restricted (T) | Inventory: Restricted | Shipping Limited | Records any restrictions on the product (e.g., shipping limits) | Optional |
| Option Name 1-10 (T) | Inventory: Option Name 1-10 | Color | Names of product options (e.g., "Color," "Size") | Optional |
| Option Value 1-10 (T) | Inventory: Option Value 1-10 | Blue | Values for product options (e.g., "Blue," "Large") | Optional |
Available Source Fields
Kroll provides fields under categories like:
- Product Data: Cost (N), Country of Origin (T), Description (T), Hazardous (T), Height (N), Length (N), Width (N), Image (T), Long Description (T), Manufacturer (T), MPN (T), MSRP (N), Option Name 1-10 (T), Option Value 1-10 (T), Parent SKU (T), Primary Category (T), Quantity (N), Restricted (T), SKU (T), Sub Category (T), Title (T), UPC (T), Weight (N), Weight Unit (T), Weight Unit (Abbreviated) (T).
Mapping Options
You can choose from the following options for each field:
- Match It: Link a Kroll field (e.g., UPC) to your inventory field.
- Set It: Choose a fixed value (e.g., "pound" for all weights).
- Transform It (Mapping Set): Use preset tools to adjust data (e.g., combine categories).
- Smart Rules: Add "if-then" logic (e.g., only map items with stock).
- Skip It (Don’t Map): Ignore the field entirely.
- Skip It (Set to Empty): Clear the field in your inventory system, removing existing data.
If the integration encounters an issue, try these steps:
- Data Not Importing: Verify your Kroll FTP account credentials and ensure the file paths are correct (e.g., /drive/assets_cloudfront_s3_us_east_1_amazonaws.com/integration_files/kroll/kroll_ftp_image_feed.csv).
- Images Not Loading: Check your image handling settings—ensure you’ve chosen either FTP download or Source Image Grabber, and confirm the image paths are valid.
- Fields Not Mapping: Ensure the desired fields are enabled in the Mapping Dashboard and that smart rules or transformations are correctly configured.
Conclusion
With the Kroll - Get Inventory [Primary] integration, you can seamlessly retrieve and map Kroll’s inventory and product data into your Flxpoint system. Flexible configuration options, a robust Mapping Dashboard, and support for custom fields ensure your inventory management is accurate and efficient.
Get Inventory (Secondary)
Supported | Kroll - Get Inventory [Secondary]
Introduction to Kroll - Get Inventory [Secondary] Integration
The Kroll - Get Inventory [Secondary] tool connects to your Kroll FTP account to retrieve secondary inventory data, focusing on key fields like SKU, Cost, Dimensions, MAP, MSRP, and Quantity. This guide helps you set up the integration to map Kroll’s data into your Flxpoint system seamlessly. Let’s dive in!
The Kroll - Get Inventory [Secondary] integration connects your Flxpoint system to Kroll to:
- Retrieve secondary inventory data from Kroll’s FTP server, focusing on fields like SKU, Cost, Dimensions, MAP, MSRP, and Quantity.
- Map Kroll’s data fields to your inventory system for seamless integration and management.
- Ensure accurate and up-to-date inventory details by pulling in essential product information.
The integration follows a structured process to retrieve and map secondary inventory data from Kroll (inferred based on similarity to Kroll - Get Inventory [Primary]):
- Secure FTP Connection: Establishes a secure FTP connection using your Kroll account details (username, password, etc.).
- File Retrieval: Pulls in secondary inventory data files from specified paths, focusing on fields like SKU, Cost, Dimensions (Height, Length, Width), MAP, MSRP, Quantity, and Weight.
- Data Mapping: Uses the Mapping Dashboard ("Kroll - Get Inventory [Secondary]") to map Kroll’s data fields to your inventory system.
Note: Ensure your Kroll FTP account credentials are correctly configured to avoid retrieval failures.
Customize the integration to fit your needs (inferred based on similarity to Kroll - Get Inventory [Primary]):
- File Path: Specify the exact path to your Kroll secondary inventory files.
Follow these steps to set up the Kroll - Get Inventory [Secondary] integration (inferred based on context):
- 1 Configure FTP Connection: Provide your Kroll FTP account details (username, password, etc.) to establish a secure connection.
- 2 Specify File Paths: Set the exact paths to your Kroll secondary inventory files.
- 3 Create a Mapping Template: Use the Mapping Dashboard ("Kroll - Get Inventory [Secondary]") to define how Kroll’s data fields map to your inventory system (details below).
- The mapping screen is labeled “Kroll - Get Inventory [Secondary]” in the Mapping Dashboard.
- Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
-
Sections include:
- From Value: Kroll fields (e.g., Kroll Inventory: SKU, Cost).
- To Inventory Variant Field: Your inventory fields (e.g., SKU, Cost).
- Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.
This section provides key details about the Kroll - Get Inventory [Secondary] integration to help you understand the process:
- Kroll Integration: Connects to your Kroll FTP account to retrieve secondary inventory data, focusing on fields like SKU, Cost, Dimensions, MAP, MSRP, and Quantity.
Tip: Ensure your file paths are correctly specified to retrieve the secondary inventory data successfully.
Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text or "N" for numbers, as in the dashboard):
Kroll - Get Inventory [Secondary] Mappings
| Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| SKU (T) | Inventory Variant: SKU | KRL12345 | Identifies the product variant in your inventory system | Required |
| Cost (N) | Inventory Variant: Cost | 15.00 | Records the product variant’s cost price | Optional |
| Dimension Unit (T) | Inventory Variant: Dimension Unit | inch | Specifies the unit for dimensions (e.g., inch, cm) | Optional |
| GTIN (T) | Inventory Variant: GTIN | 012345678905 | Sets the Global Trade Item Number for the product variant | Optional |
| Height (N) | Inventory Variant: Height | 10 | Records the height of the product variant for shipping and storage | Optional |
| Length (N) | Inventory Variant: Length | 15 | Records the length of the product variant for shipping and storage | Optional |
| MAP (N) | Inventory Variant: MAP | 25.00 | Sets the Minimum Advertised Price for the product variant | Optional |
| MSRP (N) | Inventory Variant: MSRP | 29.99 | Sets the Manufacturer’s Suggested Retail Price for the product variant | Optional |
| Quantity (N) | Inventory Variant: Quantity | 100 | Records the stock quantity available for the product variant | Optional |
| Shipping Cost (N) | Inventory Variant: Shipping Cost | 5.00 | Records the shipping cost for the product variant | Optional |
| Source List Price (N) | Inventory Variant: List Price | 30.00 | Records the source list price for the product variant | Optional |
| UPC (T) | Inventory Variant: UPC | 012345678905 | Sets the Universal Product Code for the product variant | Optional |
| Weight (N) | Inventory Variant: Weight | 2.5 | Records the product variant’s weight (requires a weight unit) | Optional |
| Weight Unit (T) | Inventory Variant: Weight Unit | pound | Specifies the unit of weight (options: pound, ounce, gram, kilogram) | Optional |
| Width (N) | Inventory Variant: Width | 12 | Records the width of the product variant for shipping and storage | Optional |
| Custom Aggregate Fields (5) (T) | Inventory Variant: Custom Aggregate Fields | Special Order: Yes | Records custom key/value pairs for the product variant | Optional |
Available Source Fields
Kroll provides fields under categories like:
- Kroll Inventory: Cost (N), Height (N), Length (N), MAP (N), MSRP (N), Quantity (N), SKU (T), Weight (N), Width (N).
- Additional Fields: Dimension Unit (T), GTIN (T), Shipping Cost (N), Source List Price (N), UPC (T), Weight Unit (T), Custom Aggregate Fields (5) (T).
Mapping Options
You can choose from the following options for each field:
- Field: Link a Kroll field (e.g., SKU) to your inventory field.
- Value: Choose a fixed value for the field.
- Mapping Set: Use preset tools to adjust data (e.g., combine fields).
- Rules: Add "if-then" logic (e.g., only map items with stock).
- Don’t Map: Ignore the field entirely.
- Set to Empty: Clear the field in your inventory system, removing existing data.
If the integration encounters an issue, try these steps:
- Data Not Importing: Verify your Kroll FTP account credentials and ensure the file paths for secondary inventory data are correct.
- Fields Not Mapping: Ensure the desired fields are enabled in the Mapping Dashboard and that rules or mapping sets are correctly configured.
Conclusion
With the Kroll - Get Inventory [Secondary] integration, you can efficiently retrieve and map Kroll’s secondary inventory data into your Flxpoint system. Flexible mapping options and a user-friendly Mapping Dashboard ensure your inventory management is accurate and tailored to your needs.
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 | Kroll - Send FRs
Introduction to Kroll - Send FRs Integration
The Kroll - Send FRs integration allows you to send Flxpoint Fulfillment Requests (FRs) to Kroll as Purchase Order Requests via SOAP API. This guide helps you set up the integration to map and send FR data to Kroll, ensuring seamless order fulfillment. Let’s get started!
The Kroll - Send FRs integration connects your Flxpoint system to Kroll to:
- Send Flxpoint Fulfillment Requests (FRs) to Kroll as Purchase Order Requests via SOAP API.
- Map FR data fields to Kroll’s order fields for accurate fulfillment processing.
- Ensure seamless order fulfillment by integrating with Kroll’s system.
The integration follows a structured process to send Fulfillment Requests to Kroll:
- Data Retrieval: Takes a Flxpoint Fulfillment Request (FR) containing details like shipping address, billing address, and fulfillment items.
- Data Mapping: Maps the FR data to a Kroll Purchase Order Request using the Mapping Dashboard ("Kroll - Send FRs").
- Purchase Order Mapping: Maps the Flxpoint Purchase Order ID (FR ID) as the "Purchase Order Number" and the Flxpoint Purchase Order # (FR #) as the "External PO Number" (can be overridden in the mapping template).
-
SOAP API Submission: Sends the Purchase Order Request to Kroll via the SOAP API endpoint
https://api.krollcorp.com/EBusiness/Kroll.Dealer.EBusiness.svc/Docs?singleWsdlusing theIEBusinessService. - Response Handling: Records the response retrieved from the API for tracking and verification.
Note: Ensure your Kroll API credentials are correctly configured to avoid submission failures.
Customize the integration to fit your needs:
-
FulfillmentMethod: Choose the fulfillment flow:
- SHIP_PRODUCT_THAT_IS_AVAILABLE_NOW_AND_OTHER_PRODUCT_WHEN_AVAILABLE: Ships available products now and others later (kill or fill flow).
- REJECT_ORDER_IF_ALL_PRODUCTS_ARE_NOT_AVAILABLE: Rejects the order if all products are not available.
- Confirm To Email Address: Set the dealer email address for confirmation (required).
- Confirm To Name: Set the dealer name for confirmation (required).
Follow these steps to set up the Kroll - Send FRs integration:
-
1 Configure API Connection: Provide your Kroll API credentials to connect to the SOAP API endpoint
https://api.krollcorp.com/EBusiness/Kroll.Dealer.EBusiness.svc/Docs?singleWsdl. - 2 Set FulfillmentMethod: Choose the fulfillment flow (e.g., SHIP_PRODUCT_THAT_IS_AVAILABLE_NOW_AND_OTHER_PRODUCT_WHEN_AVAILABLE or REJECT_ORDER_IF_ALL_PRODUCTS_ARE_NOT_AVAILABLE).
- 3 Configure Confirmation Details: Set the required "Confirm To Email Address" and "Confirm To Name" fields with the dealer’s email and name.
- 4 Create a Mapping Template: Use the Mapping Dashboard ("Kroll - Send FRs") to define how Flxpoint FR fields map to Kroll order fields (details below).
- 5 Send Fulfillment Requests: Trigger the integration to send FRs to Kroll, either manually or on a schedule, and monitor the API response.
- The mapping screen is labeled “Kroll - Send FRs” in the Mapping Dashboard.
- Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
-
Sections include:
- From Value: Flxpoint fields (e.g., Billing Address: Address Line 1, Fulfillment Request Item: SKU).
- To Kroll Order Field: Kroll fields (e.g., Ship To Address1, Quantity Ordered).
- Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.
This section provides key details about the Kroll - Send FRs integration to help you understand the process:
- Current Date and Time: As of 08:56 PM -04 on Thursday, May 15, 2025, this integration is fully operational for sending Fulfillment Requests to Kroll.
-
Kroll Integration: Sends Flxpoint FRs to Kroll via SOAP API using the endpoint
https://api.krollcorp.com/EBusiness/Kroll.Dealer.EBusiness.svc/Docs?singleWsdl. - Payment Method Requirement: You must map a Payment Method (CreditCard or AccountTerms). For CreditCard, additional data mapping is required.
- ShipVia Codes: Supports specific shipping codes, including FedExPriorityOvernight, CustomerPickUp, FedExExpressSaver, FedExStandardOvernight, FedExGround, FedExTwoDay, UPSNextDayAir, UPSSecondDayAir, UPSGround, UPSThreeDaySelect, UPSNextDayAirSaver, UPSNextDayAirEarlyAM, UPSSecondDayAirAM, USPSParcelPost, USPSFirstClass, LessThanLoadFreight, ExpressMail, FedExSmartPost, BestRate, FlatRate.
Tip: Ensure the Payment Method and ShipVia fields are correctly mapped to avoid rejection by Kroll’s API.
Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, "D" for dates, as in the dashboard):
Kroll - Send FRs Mappings
| Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Bypass Address Validation (T) | Kroll Order: Bypass Address Validation | Yes | Indicates whether to bypass address validation | Optional |
| Fulfillment Request Number (T) | Kroll Order: External PO | FR12345 | Maps the Flxpoint FR # as the External PO Number (can be overridden) | Optional |
| Address Line 1 (T) | Kroll Order: Ship To Address1 | 123 Main St | Records the first line of the shipping address | Required |
| Address Line 2 (T) | Kroll Order: Ship To Address2 | Apt 4B | Records the second line of the shipping address | Optional |
| Address Line 3 (T) | Kroll Order: Ship To Address3 | Suite 100 | Records the third line of the shipping address | Optional |
| City (T) | Kroll Order: Ship To City | Los Angeles | Records the city of the shipping address | Required |
| Country Code (T) | Kroll Order: Ship To Country Code | US | Records the country code of the shipping address | Required |
| Full Name (T) | Kroll Order: Ship To Name | John Doe | Records the name of the shipping recipient | Required |
| Postal Code (T) | Kroll Order: Ship To Postal Code | 90210 | Records the postal code of the shipping address | Required |
| State (T) | Kroll Order: Ship To State Province | California | Records the state or province of the shipping address | Required |
| Phone (T) | Kroll Order: Ship To Telephone Number | 555-123-4567 | Records the telephone number for the shipping contact | Optional |
| Method (T) | Kroll Order: Ship Via | UPSGround | Specifies the shipping method (must use specific codes like FedExGround, UPSNextDayAir) | Required |
| Signature Required (T) | Kroll Order: Signature Required | Yes | Indicates whether a signature is required for delivery | Optional |
| Quantity (N) | Kroll Order Item: Quantity Ordered | 5 | Records the quantity ordered for the item | Required |
| SKU (T) | Kroll Order Item: Sku | KRL12345 | Identifies the product item in the order | Required |
Available Source Fields
Flxpoint provides fields under categories like:
- Billing Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
- Fulfillment Request: Estimated Dropship Fee (N), Estimated Shipping Cost (N), Fulfillment Request Number (T), Generated At (D), Note (T), Sent At (D), Total Cost (N), Total Weight (lbs) (N).
- Fulfillment Request Item: Bin Location (T), Cost (N), MPN (T), PO Line Item # (N), Quantity (N), SKU (T), Subtotal (N), Title (T), UPC (T).
- Shipping Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
- Source Shipping Method: Carrier (T), Description (T), Method (T), Shipping Code (T).
Mapping Options
You can choose from the following options for each field:
- Field: Link a Flxpoint field (e.g., SKU) to a Kroll order field.
- Value: Choose a fixed value for the field.
- Mapping Set: Use preset tools to adjust data (e.g., combine fields).
- Rules: Add "if-then" logic (e.g., only map if quantity > 0).
- Don’t Map: Ignore the field entirely.
- Set to Empty: Clear the field in the Kroll order, removing existing data.
If the integration encounters an issue, try these steps:
-
Request Not Sending: Verify your Kroll API credentials and ensure the SOAP API endpoint
https://api.krollcorp.com/EBusiness/Kroll.Dealer.EBusiness.svc/Docs?singleWsdlis accessible. - Fields Not Mapping: Ensure required fields like Payment Method, ShipVia, Ship To Address1, and Quantity Ordered are mapped correctly in the Mapping Dashboard.
- API Rejection: Check that the ShipVia code matches one of the allowed values (e.g., FedExGround, UPSNextDayAir) and that the Payment Method (CreditCard or AccountTerms) is properly set.
- Missing Confirmation Details: Confirm that "Confirm To Email Address" and "Confirm To Name" are set in the configuration settings.
Conclusion
With the Kroll - Send FRs integration, you can efficiently send Flxpoint Fulfillment Requests to Kroll as Purchase Order Requests, ensuring accurate order fulfillment. Flexible configuration options and a robust Mapping Dashboard streamline the process, integrating seamlessly with Kroll’s system.
Get Shipments
Supported | Kroll - Get Shipments
Introduction to Kroll - Get Shipments Integration
The Kroll - Get Shipments integration retrieves shipment data from Kroll and maps it into your Flxpoint system, ensuring accurate tracking and fulfillment updates. This guide helps you set up the integration to import shipment details seamlessly. Let’s get started!
The Kroll - Get Shipments integration connects your Flxpoint system to Kroll to:
- Retrieve shipment data from Kroll, including carrier, tracking numbers, and shipment items.
- Map Kroll shipment data to Flxpoint shipment fields for accurate tracking and fulfillment updates.
- Ensure seamless integration of shipment details into your Flxpoint system.
The integration follows a structured process to retrieve and map shipment data from Kroll (inferred based on similarity to other Kroll integrations):
- API Connection: Connects to Kroll’s system, likely via SOAP API, to retrieve shipment data.
- Data Retrieval: Pulls shipment details, including carrier, tracking numbers, shipment dates, and shipment items, from Kroll.
- Data Mapping: Uses the Mapping Dashboard ("Kroll - Get Shipments") to map Kroll shipment data to Flxpoint shipment fields.
Note: Ensure your Kroll API credentials are correctly configured to avoid retrieval failures.
Customize the integration to fit your needs (inferred based on context):
- API Credentials: Provide your Kroll API credentials to establish a connection.
Follow these steps to set up the Kroll - Get Shipments integration (inferred based on context):
- 1 Configure API Connection: Provide your Kroll API credentials to connect to Kroll’s system.
- 2 Create a Mapping Template: Use the Mapping Dashboard ("Kroll - Get Shipments") to define how Kroll shipment fields map to Flxpoint shipment fields (details below).
- 3 Retrieve Shipments: Trigger the integration to retrieve shipment data from Kroll, either manually or on a schedule.
- The mapping screen is labeled “Kroll - Get Shipments” in the Mapping Dashboard.
- Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
-
Sections include:
- From Value: Kroll fields (e.g., Kroll Shipment: Shipped Via, Kroll Shipment Item: Sku).
- To Shipment Field: Flxpoint shipment fields (e.g., Carrier, Sku).
- Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.
This section provides key details about the Kroll - Get Shipments integration to help you understand the process:
- Current Date and Time: As of 08:59 PM -04 on Thursday, May 15, 2025, this integration is fully operational for retrieving shipment data from Kroll.
- Kroll Integration: Retrieves shipment data from Kroll, likely via SOAP API, focusing on fields like carrier, tracking numbers, and shipment items.
Tip: Ensure all required fields (e.g., Carrier, Sku) are mapped to avoid incomplete shipment data in Flxpoint.
Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, "D" for dates, as in the dashboard):
Kroll - Get Shipments Mappings
| Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Shipped Via (T) | Shipment: Carrier | UPS | Identifies the shipping carrier for the shipment | Required |
| Order Confirmation Number (T) | Shipment: Fulfillment Request Number | FR12345 | Associates the shipment with the Flxpoint Fulfillment Request | Required |
| Shipped Via (T) | Shipment: Method | Ground | Specifies the shipping method used for the shipment | Optional |
| Note (T) | Shipment: Note | Shipped via UPS on 2025-05-15 | Adds a note to the shipment record | Optional |
| Shipment Date (D) | Shipment: Shipped At | 2025-05-15T20:59:00Z | Records the date and time the shipment was sent | Required |
| Freight Amount (N) | Shipment: Shipping Cost | 10.00 | Records the shipping cost for the shipment | Optional |
| Tracking Numbers (T) | Shipment: Tracking Number | 1Z9999W99999999999 | Records the tracking number for the shipment | Required |
| Tracking URL (T) | Shipment: Tracking URL | https://ups.com/track?tracknum=1Z9999W99999999999 | Provides the URL for tracking the shipment (inferred mapping) | Optional |
| Quantity Shipped (N) | Shipment Item: Quantity | 5 | Records the quantity shipped for the item | Required |
| Sku (T) | Shipment Item: Sku | KRL12345 | Identifies the product item in the shipment | Required |
| All Custom Fields (T) | Shipment Item: Custom Fields | Special Handling: Yes | Records custom key/value pairs for the shipment item | Optional |
Available Source Fields
Kroll provides fields under categories like:
- Kroll Shipment: Discount Amount (N), Freight Amount (N), Order Confirmation Number (T), Order Status (T), Product Amount (N), Shipment Date (D), Shipment Identifier (T), Shipped Via (T), Total Amount (N), Tracking Numbers (T).
- Kroll Shipment Item: Amount (N), Quantity Shipped (N), Sku (T), Unit Amount (N).
Mapping Options
You can choose from the following options for each field:
- Field: Link a Kroll field (e.g., Sku) to a Flxpoint shipment field.
- Value: Choose a fixed value for the field.
- Mapping Set: Use preset tools to adjust data (e.g., combine fields).
- Rules: Add "if-then" logic (e.g., only map if quantity > 0).
- Direct Copy: Directly copy the field value (for shipment items).
- Don’t Map: Ignore the field entirely.
- Set to Empty: Clear the field in the Flxpoint shipment, removing existing data.
If the integration encounters an issue, try these steps:
- Data Not Importing: Verify your Kroll API credentials and ensure the API connection is active.
- Fields Not Mapping: Ensure required fields like Carrier, Fulfillment Request Number, Tracking Number, and Sku are mapped correctly in the Mapping Dashboard.
Conclusion
With the Kroll - Get Shipments integration, you can efficiently retrieve and map shipment data from Kroll into your Flxpoint system. Flexible mapping options and a user-friendly Mapping Dashboard ensure your shipment tracking and fulfillment updates are accurate and seamless.
Get Invoices
Supported | Kroll - Get Purchase Order Invoices
Introduction to Kroll - Get Purchase Order Invoices Integration
The Kroll - Get Purchase Order Invoices integration retrieves purchase order invoice data from Kroll and maps it into your Flxpoint system, ensuring accurate financial tracking and order reconciliation. This guide helps you set up the integration to import invoice details seamlessly. Let’s get started!
The Kroll - Get Purchase Order Invoices integration connects your Flxpoint system to Kroll to:
- Retrieve purchase order invoice data from Kroll, including invoice details and items.
- Map Kroll invoice data to Flxpoint source invoice fields for accurate financial tracking.
- Ensure seamless integration of invoice details into your Flxpoint system for order reconciliation.
The integration follows a structured process to retrieve and map invoice data from Kroll (inferred based on similarity to other Kroll integrations):
- API Connection: Connects to Kroll’s system, likely via SOAP API, to retrieve purchase order invoice data.
- Data Retrieval: Pulls invoice details, including Fulfillment Request Number, Invoice Date, costs, and invoice items, from Kroll.
- Data Mapping: Uses the Mapping Dashboard ("Kroll - Get Purchase Order Invoices") to map Kroll invoice data to Flxpoint source invoice fields.
Note: Ensure your Kroll API credentials are correctly configured to avoid retrieval failures.
Customize the integration to fit your needs (inferred based on context):
- API Credentials: Provide your Kroll API credentials to establish a connection.
Follow these steps to set up the Kroll - Get Purchase Order Invoices integration (inferred based on context):
- 1 Configure API Connection: Provide your Kroll API credentials to connect to Kroll’s system.
- 2 Create a Mapping Template: Use the Mapping Dashboard ("Kroll - Get Purchase Order Invoices") to define how Kroll invoice fields map to Flxpoint source invoice fields (details below).
- 3 Retrieve Invoices: Trigger the integration to retrieve invoice data from Kroll, either manually or on a schedule.
- The mapping screen is labeled “Kroll - Get Purchase Order Invoices” in the Mapping Dashboard.
- Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
-
Sections include:
- From Value: Kroll fields (e.g., Kroll Shipment: Order Confirmation Number, Kroll Shipment Item: Sku).
- To Source Invoice Field: Flxpoint source invoice fields (e.g., Fulfillment Request Number, SKU).
- Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.
This section provides key details about the Kroll - Get Purchase Order Invoices integration to help you understand the process:
- Current Date and Time: As of 09:03 PM -04 on Thursday, May 15, 2025, this integration is fully operational for retrieving purchase order invoice data from Kroll.
- Kroll Integration: Retrieves purchase order invoice data from Kroll, likely via SOAP API, focusing on fields like Fulfillment Request Number, Invoice Date, and invoice items.
Tip: Ensure all required fields (e.g., Fulfillment Request Number, SKU) are mapped to avoid incomplete invoice data in Flxpoint.
Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, "D" for dates, as in the dashboard):
Kroll - Get Purchase Order Invoices Mappings
| Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Fee Cost (N) | Source Invoice: Fee Cost | 5.00 | Records the fee cost associated with the invoice | Optional |
| Order Confirmation Number (T) | Source Invoice: Fulfillment Request Number | FR12345 | Associates the invoice with the Flxpoint Fulfillment Request | Required |
| Shipment Date (D) | Source Invoice: Invoice Date | 2025-05-15T21:03:00Z | Records the date the invoice was issued | Required |
| Invoice Number (T) | Source Invoice: Invoice Number | INV12345 | Records the invoice number (inferred mapping) | Required |
| Order Status (T) | Source Invoice: Invoice Status | Unpaid | Records the status of the invoice (options: Unpaid, Paid) | Required |
| Other Cost (N) | Source Invoice: Other Cost | 3.00 | Records any additional costs associated with the invoice | Optional |
| Freight Amount (N) | Source Invoice: Shipping Cost | 10.00 | Records the shipping cost for the invoice | Optional |
| Tax Cost (N) | Source Invoice: Tax Cost | 7.50 | Records the tax cost associated with the invoice | Optional |
| Amount (N) | Source Invoice Item: Cost | 50.00 | Records the total cost for the invoice item | Required |
| Invoice Item Type (T) | Source Invoice Item: Invoice Item Type | Product | Specifies the type of invoice item (options: Product, Shipping, Fee, Tax, Other) | Required |
| Unit Amount (N) | Source Invoice Item: Per Unit Cost | 10.00 | Records the cost per unit for the invoice item | Optional |
| Quantity Shipped (N) | Source Invoice Item: Quantity | 5 | Records the quantity invoiced for the item | Required |
| Sku (T) | Source Invoice Item: SKU | KRL12345 | Identifies the product item on the invoice | Required |
| Title (T) | Source Invoice Item: Title | Blue Widget | Records the title of the invoiced item | Optional |
| All Custom Fields (T) | Source Invoice Item: Custom Fields | Special Order: Yes | Records custom key/value pairs for the invoice item | Optional |
Available Source Fields
Kroll provides fields under categories like:
- Kroll Shipment: Discount Amount (N), Freight Amount (N), Order Confirmation Number (T), Order Status (T), Product Amount (N), Shipment Date (D), Shipment Identifier (T), Total Amount (N).
- Kroll Shipment Item: Amount (N), Quantity Shipped (N), Sku (T), Unit Amount (N).
Mapping Options
You can choose from the following options for each field:
- Field: Link a Kroll field (e.g., Sku) to a Flxpoint source invoice field.
- Value: Choose a fixed value for the field.
- Mapping Set: Use preset tools to adjust data (e.g., combine fields).
- Rules: Add "if-then" logic (e.g., only map if quantity > 0).
- Direct Copy: Directly copy the field value (for invoice items).
- Don’t Map: Ignore the field entirely.
- Set to Empty: Clear the field in the Flxpoint source invoice, removing existing data.
If the integration encounters an issue, try these steps:
- Data Not Importing: Verify your Kroll API credentials and ensure the API connection is active.
- Fields Not Mapping: Ensure required fields like Fulfillment Request Number, Invoice Date, SKU, and Quantity are mapped correctly in the Mapping Dashboard.
Conclusion
With the Kroll - Get Purchase Order Invoices integration, you can efficiently retrieve and map invoice data from Kroll into your Flxpoint system. Flexible mapping options and a user-friendly Mapping Dashboard ensure your financial tracking and order reconciliation are accurate and seamless.