Kroll as a Source

Table of Contents

How To Connect Product Operations Order Operations

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

🧭 Phase 1: Launch the Source Wizard +

Open Sources and start the Wizard

Go to Sources (building icon) → + Add Source → Configure Single Source. This opens the Source Wizard.

Step 1 — Create Source

Enter a clear name (e.g., Kroll). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most Kroll setups, we recommend Vendor Warehouse. Use the other options only if they better match how you store and ship inventory.

Vendor Warehouse (Recommended): You send POs/FRs to Kroll so they ship directly to your customers.
Internal Warehouse: You stock items and ship from your own facility.
External Warehouse: A 3PL or external partner ships your owned inventory.
Product Data Source: Content-only source to enrich product details (no fulfillment).

For Kroll: select Vendor Warehouse. This enables sending Fulfillment Requests to Kroll and using their inventory for routing.

After selecting the Source Type, click Save & Next.

Step 2 — Vendor Set-Up

Choose Yes (Recommended) to Assign Vendor → Confirm. You'll enable Vendor reporting and optional portal.

Step 3 — Order Fulfillment

Decide if this source is eligible to fulfill orders:

Yes (Recommended): You can route orders here.
No: Routing/Shipping steps won't apply.

Click Confirm.

Step 4 — Order Fulfillment Settings

Use Defaults or No, Customize. You'll see:

Override: Auto Processing (Use Global / Auto Process / Do NOT Auto Process).
Commit Stock + Inventory Management Options.
Allow Backorders / Cancel Unacknowledged Items.

Click Save & Next.

Step 5 — Shipping Cost Estimations

Pick one:

Yes, Use Rate Shopping (Real-Time Estimates).
No, Set Up via Rules.

If using real-time, acknowledge you have valid dimensions, weight, and source address. Click Save & Next.

Step 6 — Order Routing Groups

Enable on all routing groups? Select Yes or No, Customize. Optionally mark Default Order Routing Group. Save & Next.

Reminder: Complete Step 1 — Shipping Methods and Step 2 — Source Location in Phase 2 below, then return (if needed) to finalize.

🚚 Phase 2: Shipping Methods & Source Location (Finish the Wizard) +

Goal

Finish the Source Wizard by confirming your Ship From location and reviewing shipping behavior for Kroll.

Step 1 — Shipping Methods

When the wizard opens the Shipping Methods step for this Source:

Skip if you do not need to configure shipping methods at this time.
Or Add Method to configure shipping methods if required for your setup.

Click Save & Next to continue.

Step 2 — Source Location (Ship From)

Enter the Ship From address:

Address, City, State/Code, Postal Code, Country/Code
Optional: Contact Name, Phone, Email

This address is used for routing logic, rate shopping (if enabled), and reporting.

Finish the Wizard

Review Steps 1–2, then click Save and Complete. The wizard is now finished.

Next: Proceed to Phase 3 to create your Kroll connections for inventory and order operations.

🔑 Phase 3: Create Your Kroll Connection +

Goal

Kroll supports two connection types—FTP (Basic Auth) for inventory operations and Kroll API for order operations. You will create one or both depending on which integrations you need. The FTP connection powers Get Inventory Primary and Get Inventory Secondary. The API connection powers Send Fulfillment Requests and Get Shipments.

Step 1 — Open Get Inventory [Primary] and start

Inside your Kroll source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations. In the connector gallery, choose Kroll. If you don't see it, use Not Listed? → Request a custom integration.

Step 2 — Choose your Connection Type

In New Kroll Connection, select one of:

FTP (Basic Auth) — for inventory file pickup over FTP. Used by Get Inventory Primary and Get Inventory Secondary.
Kroll API — for order operations via API. Used by Send Fulfillment Requests and Get Shipments.

Note: You may need both connection types if you plan to use both inventory and order operations. Create them one at a time.

Step 3a — If you choose FTP (Basic Auth)

Fill the form with the credentials provided by Kroll:

Connection Name (required) — a friendly label for this connection
FTP Username (required) — also used as your Account Number for API connections
FTP Password (required)

Click Test Connection → Save Connection.

Tip: The FTP Username doubles as your Account Number. Keep it handy—you'll need it again if you create a Kroll API connection.

Step 3b — If you choose Kroll API

Enter:

Connection Name (required) — a friendly label for this connection
Account Number (required) — same as your FTP Username
API Username (required)
API Password (required)

Then Test Connection and Save Connection.

Note: The Account Number here is the same value as the FTP Username from the FTP connection. If you already created an FTP connection, use that same value.

Step 4 — How Flxpoint uses these connections

Important: Unlike some integrations that use a single connection for everything, Kroll uses two separate connections for different operation types:

FTP (Basic Auth) connection → powers Get Inventory [Primary] and Get Inventory [Secondary]
Kroll API connection → powers Send Fulfillment Requests and Get Shipments

Tip: When configuring each operation later, make sure you select the correct connection type for that operation. Inventory operations need the FTP connection; order operations need the API connection.

Next Configure Product & Order Operations 🚀

Now that your Kroll connections are saved, go to the Operations section of this doc to set up the Kroll integrations you need (Inventory and Order operations). Each operation will let you select the appropriate Kroll Connection (FTP for inventory, API for orders).

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)

Introduction

Kroll is a trusted wholesale distributor specializing in tactical, outdoor, and law enforcement products. The Get Inventory (Primary) job imports Kroll product data and quantities into your Global Inventory Pool via FTP connection.

Use GIP to keep Kroll inventory current in Flxpoint: import the full product catalog with core details (titles, descriptions, categories, images, weight, dimensions), keep quantities and pricing up to date, and handle discontinued stock identification.

The sections below walk through each step of the setup and configuration process.

        Note: GIP is the import process. After each run, products/quantities live in
        the Global Inventory Pool and can be mapped to downstream channels.
      

Each run follows this workflow:

1Select Connection — Choose FTP (Basic Auth) when creating your connection.
2Fetch Data — Flxpoint reads files from Kroll's FTP server including:
- ProductData/KrollDealer_Inventory_Export2K-TXT — Stock levels.
- ProductData/Kroll_Stock_Disco_CSO.txt — Discontinued/deactivated stock info. Only SKUs with QTY_Available = 0 are treated as discontinued. SKUs with quantity > 0 continue to import as active.
- ProductData/Kroll_Complete_Catalog.txt — Full catalog.
- ProductImages/NCR/Large/NCR-3138D.png — Product images.
3Map Fields — Incoming data is matched to your Mapping Template.
4Save to Global Inventory Pool — The pool is updated; changes flow to channels after your next push.

Follow these steps in your Kroll source → Get Inventory (Primary):

Step 1: Connect an Integration

Choose Kroll and create an FTP (Basic Auth) connection.

Fields: Connection Name, FTP Username, FTP Password.
Tip: Use to validate your credentials.

Step 2: Configure Settings

File Path — Specify the path to the Kroll files on the FTP server.
Image Handling — Choose between FTP download or Source Image Grabber depending on your setup.

Step 3: Define a Mapping Template

Use the recommended fields from the Mapping Utilities section below, then adjust for your catalog.

Step 4: Save & Schedule

Run manually or enable a schedule (jobs run in UTC). The status page will show Connected, Configured, and Mapped with the template once complete.

Recommended Mapping (Kroll GIP)

Starter field mapping for Kroll (adjust per your template):

Flxpoint Field	Kroll Field	Example	Purpose	Status
SKU (T)	Inventory: SKU	KRL12345	Product identifier	Required
Title (T)	Inventory: Title	Blue Widget	Display title	Required
Description (T)	Inventory: Description	A durable blue widget	Short description	Optional
Long Description (T)	Inventory: Long Description	A high-quality...	Detailed description	Optional
Manufacturer (T)	Inventory: Manufacturer	Kroll Inc.	Manufacturer	Optional
MPN (T)	Inventory: MPN	WGT-12345	Manufacturer Part Number	Optional
UPC (T)	Inventory: UPC	012345678905	Barcode	Optional
Cost (N)	Inventory: Cost	15.00	Cost price	Optional
MSRP (N)	Inventory: MSRP	29.99	Retail price	Optional
Quantity (N)	Inventory: Quantity	100	Stock quantity	Optional
Weight (N)	Inventory: Weight	2.5	Product weight	Optional
Weight Unit (T)	Inventory: Weight Unit	pound	Unit of weight	Optional
Height (N)	Inventory: Height	10	Height	Optional
Length (N)	Inventory: Length	15	Length	Optional
Width (N)	Inventory: Width	12	Width	Optional
Image (T)	Inventory: Image	https://...	Product image URL	Optional
Primary Category (T)	Inventory: Primary Category	Widgets	Main category	Optional
Sub Category (T)	Inventory: Sub Category	Blue Widgets	Subcategory	Optional
Parent SKU (T)	Inventory: Parent SKU	KRL-PARENT	Parent SKU for variants	Optional
Country of Origin (T)	Inventory: Country of Origin	USA	Country of origin	Optional

Available Source Fields

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

Match It — Directly map a source field to a Flxpoint field.
Set It — Set a fixed/static value for a field.
Transform It (Mapping Set) — Apply a transformation or mapping set to the value.
Smart Rules — Use conditional logic to determine the mapped value.
Skip It (Don't Map) — Ignore the field entirely.
Skip It (Set to Empty) — Clear the field value on each sync.

        
        Summary: Map the core fields above and verify your FTP connection to ensure product data,
        pricing, and quantity import correctly.

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
FTP credentials are confirmed with Kroll.
Image handling setting is configured (FTP download or Source Image Grabber).

Troubleshooting

Data Not Importing: Verify Kroll FTP credentials and file paths. Ensure the connection passes Test Connection and that the file paths match the expected Kroll FTP directory structure.
Images Not Loading: Check image handling settings. Confirm whether you are using FTP download or Source Image Grabber and that the configuration matches your setup.
Fields Not Mapping: Ensure the desired fields are enabled in the Mapping Dashboard and that the mapping template is saved and selected.
Discontinued SKUs Behaving Unexpectedly: If a SKU still imports as active despite being in the discontinued (Kroll_Stock_Disco_CSO.txt) file, check the QTY_Available value. Only SKUs with QTY_Available = 0 are treated as discontinued; SKUs with QTY_Available > 0 continue to import as active.

Operation Details

Feature	Availability	What to Expect
Custom Fields	Supported	100 custom fields, 10 summary fields.
Variations / Options	Supported	Option Name/Value 1-10.
Quantity	Supported	From FTP files.
Weights & Dimensions	Supported	Weight, Height, Length, Width.
Images	Supported	Via FTP or Source Image Grabber.
Categories	Supported	Two-level (Primary + Sub).
Weight Unit Options	Supported	pound, ounce, gram, kilogram (full name) or lb, oz (abbreviated).

        
        Tip: Run a manual sync first to verify field mapping before enabling a recurring schedule.
      

Get Inventory (Secondary)

Introduction

The Kroll – Get Inventory (Secondary) integration retrieves secondary inventory data from Kroll's FTP server, focusing on variant-level fields like SKU, Cost, Dimensions, MAP, MSRP, Quantity, and Weight. This job uses the same FTP connection configured during primary inventory setup.

The sections below walk through each step of the setup and configuration process.

        Tip: This operation reuses the same FTP (Basic Auth) connection from Get Inventory (Primary).
        No separate connection is needed.
      

Use this job to:

Refresh variant-level cost, MSRP, and MAP for existing SKUs.
Update quantities and related inventory fields.
Sync dimensions and weight data for shipping calculations.

Each run follows this workflow:

1Connection — Uses the existing FTP (Basic Auth) connection to retrieve secondary inventory data from Kroll's FTP server.
2Parse & Map — The file includes variant-level fields such as SKU, Cost, Dimensions, MAP, MSRP, Quantity, and Weight. Mapping targets the fields listed in the Mapping Utilities section below.
3Write — Updates variant data in the Global Inventory Pool.

Example: SKU KRL12345 has cost 15.00, MSRP 29.99, MAP 25.00, and quantity 100 ⇒ Flxpoint updates the variant with all secondary fields.

Step 1: Select Existing Kroll FTP Connection

Choose Kroll and select the existing FTP (Basic Auth) connection configured during primary inventory setup.

Step 2: Configure Settings

File Paths — Configure the file paths for secondary inventory data on the Kroll FTP server.
Remote File Name Pattern — The filename pattern for the secondary data feed.
Inbound Remote File Folder — The source directory for the secondary feed.
File Action — Set to Read.

Step 3: Define a Mapping Template

Choose or create a mapping template named Kroll – Get Inventory [Secondary]. Use the recommended fields from the Mapping Utilities section below.

Step 4: Save & Schedule

Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped with your template.

Recommended Mapping (Secondary)

Map the variant-level fields below for secondary inventory updates. Field names are drawn from the Kroll Inventory Item schema.

Flxpoint Field	Kroll Field	Example	Purpose	Status
SKU (T)	Inventory Variant: SKU	`KRL12345`	Product variant identifier	Required
Cost (N)	Inventory Variant: Cost	`15.00`	Cost price	Optional
Dimension Unit (T)	Inventory Variant: Dimension Unit	`inch`	Dimension unit	Optional
GTIN (T)	Inventory Variant: GTIN	`012345678905`	Global Trade Item Number	Optional
Height (N)	Inventory Variant: Height	`10`	Height	Optional
Length (N)	Inventory Variant: Length	`15`	Length	Optional
MAP (N)	Inventory Variant: MAP	`25.00`	Min Advertised Price	Optional
MSRP (N)	Inventory Variant: MSRP	`29.99`	Retail price	Optional
Quantity (N)	Inventory Variant: Quantity	`100`	Stock quantity	Optional
Shipping Cost (N)	Inventory Variant: Shipping Cost	`5.00`	Shipping cost	Optional
Source List Price (N)	Inventory Variant: List Price	`30.00`	List price	Optional
UPC (T)	Inventory Variant: UPC	`012345678905`	Barcode	Optional
Weight (N)	Inventory Variant: Weight	`2.5`	Weight	Optional
Weight Unit (T)	Inventory Variant: Weight Unit	`pound`	Weight unit	Optional
Width (N)	Inventory Variant: Width	`12`	Width	Optional
Custom Aggregate Fields (5) (T)	Inventory Variant: Custom Aggregate	`Special Order: Yes`	Custom key/value pairs	Optional

Available Source Fields

The following fields are available from the Kroll Inventory schema:

Kroll Inventory: Cost (N), Height (N), Length (N), MAP (N), MSRP (N), Quantity (N), SKU (T), Weight (N), Width (N).
Additional: Dimension Unit (T), GTIN (T), Shipping Cost (N), Source List Price (N), UPC (T), Weight Unit (T), Custom Aggregate Fields (5) (T).

Mapping Options

Options include Field, Value, Mapping Set, Rules, Don't Map, Set to Empty.

        
        Summary: Secondary mapping focuses on variant-level fields including cost, quantity,
        dimensions, MAP, MSRP, and weight. Keep catalog-level fields (titles, images, descriptions) in the
        Primary job.
      

Quick Checks

Connection reuses the same FTP connection from Get Inventory (Primary) and shows Connected.
Mapping template is selected and saved.
File paths are configured correctly for secondary data.
Remote File Name Pattern and Inbound Folder are set correctly.

Troubleshooting

Data not importing? Verify FTP credentials and file paths are correct. Use Test Connection to confirm the connection is active.
Fields not mapping? Check the Mapping Dashboard to confirm all fields are mapped correctly in the template. Ensure the source field names match the Kroll schema.
Missing quantities? Confirm the secondary data file contains the expected quantity fields and that the file is present in the configured FTP directory.
Cost or MSRP not updating? Verify the mapping template includes the Cost and MSRP fields and that the source file contains non-empty values.

Operation Details

Feature	Availability	What to Expect
Variant-Level Fields	Supported	SKU, Cost, MAP, MSRP, Quantity, Weight, Dimensions.
Custom Aggregate Fields	Supported	Up to 5 custom key/value pairs per variant.
Connection	Shared	Reuses the same Kroll FTP connection from primary inventory setup.
Scheduling	Supported	Run on demand or via recurring schedule (UTC).
Catalog-Level Fields	Not Supported	Titles, images, and descriptions belong in the Primary job.

        
        Tip: Run Secondary on a more frequent schedule than Primary to keep cost, quantity,
        and pricing data fresh between full catalog syncs.

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

Introduction

The Kroll – Send Fulfillment Requests integration sends Flxpoint Fulfillment Requests (FRs) to Kroll as Purchase Order Requests via SOAP API. This uses the Kroll API connection (Account Number, API Username, API Password). The SOAP endpoint is https://api.krollcorp.com/EBusiness/Kroll.Dealer.EBusiness.svc/Docs?singleWsdl.

Configuration involves selecting the API connection, defining fulfillment and shipping settings, and creating a mapping template that maps Flxpoint FR fields to Kroll's purchase order format.

The sections below walk through each step of the setup and configuration process.

The Send Fulfillment Requests integration converts Flxpoint FRs into Kroll Purchase Order Requests via SOAP API. If no error is received during submission, the FR is marked as processed.

The setup is completed in four steps.

Step 1: Select Kroll API Connection

Select Kroll and choose your existing API connection. This connection requires your Kroll Account Number, API Username, and API Password.

Click Test Connection, then Save Connection once successful.

        
        Tip: Reuse the same Kroll API connection if one was already created for other operations.
      

Step 2: Configure Settings

FulfillmentMethod * — Choose one of:
- SHIP_PRODUCT_THAT_IS_AVAILABLE_NOW_AND_OTHER_PRODUCT_WHEN_AVAILABLE
- REJECT_ORDER_IF_ALL_PRODUCTS_ARE_NOT_AVAILABLE
Confirm To Email Address * — Required. The email address for order confirmations.
Confirm To Name * — Required. The name associated with the confirmation email.

Expand Advanced Settings if needed:

Hold for X hours — Temporarily hold FRs before sending (useful for manual review).
Only Send During Business Hours — Restrict sends to business hours only.

Click Save and Proceed.

        
        Important: Payment Method is required and must be set to either CreditCard
        or AccountTerms. ShipVia must use a valid shipping code (see Mapping Utilities below).

Step 3: Define a Mapping Template

Choose or create a mapping template named Kroll – Send FRs. Click Save and Complete.

Step 4: Save & Schedule

Run on demand or enable scheduling. Schedules run in UTC. The status page will show Connected, Configured, and Mapped.

The Mapping Template defines how Flxpoint fulfillment request data maps to Kroll's Purchase Order SOAP API schema. Header fields and line items map from your order to Kroll's required format.

Recommended Mapping (Key Fields)

Flxpoint Field	Kroll Field	Example	Purpose	Status
Bypass Address Validation (T)	Kroll Order	`Yes`	Skip address validation	Optional
Fulfillment Request Number (T)	External PO	`FR12345`	External PO Number	Optional
Address Line 1 (T)	Ship To Address1	`123 Main St`	Shipping address	Required
Address Line 2 (T)	Ship To Address2	`Apt 4B`	Address line 2	Optional
Address Line 3 (T)	Ship To Address3	`Suite 100`	Address line 3	Optional
City (T)	Ship To City	`Los Angeles`	City	Required
Country Code (T)	Ship To Country Code	`US`	Country	Required
Full Name (T)	Ship To Name	`John Doe`	Recipient name	Required
Postal Code (T)	Ship To Postal Code	`90210`	Zip code	Required
State (T)	Ship To State Province	`California`	State	Required
Phone (T)	Ship To Telephone	`555-123-4567`	Phone	Optional
Method (T)	Ship Via	`UPSGround`	Shipping method code	Required
Signature Required (T)	Signature Required	`Yes`	Signature required	Optional
Quantity (N)	Quantity Ordered	`5`	Order quantity	Required
SKU (T)	Sku	`KRL12345`	Product SKU	Required

Available Source Fields

The following field categories are available from Flxpoint:

Billing Address: Address Line 1, Address Line 2, City, Country Code, Full Name, Postal Code, State.
Fulfillment Request: Fulfillment Request Number, Payment Method, Confirm To Email, Confirm To Name.
FR Item: SKU, Quantity, Unit Price.
Shipping Address: Address Line 1, Address Line 2, Address Line 3, City, Country Code, Full Name, Phone, Postal Code, State.
Source Shipping Method: Ship Via, Signature Required, Bypass Address Validation.

Valid ShipVia Codes

The Ship Via field must use one of the following valid codes:

FedExPriorityOvernightCustomerPickUpFedExExpressSaver FedExStandardOvernightFedExGroundFedExTwoDay UPSNextDayAirUPSSecondDayAirUPSGround UPSThreeDaySelectUPSNextDayAirSaverUPSNextDayAirEarlyAM UPSSecondDayAirAMUSPSParcelPostUSPSFirstClass LessThanLoadFreightExpressMailFedExSmartPost BestRateFlatRate

Let's Break It Down: Map shipping address fields, SKU, and quantity as required fields. Use a valid ShipVia code for the shipping method. Payment Method must be either CreditCard or AccountTerms.

        
        Summary: Map the key fields above for accurate FR submission to Kroll.
        Ship To fields, SKU, Quantity, and ShipVia are the most critical fields to verify.

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
FulfillmentMethod is configured (ship available or reject if incomplete).
Confirm To Email Address and Confirm To Name are filled in.
ShipVia uses a valid shipping code from the list above.
Payment Method is set to CreditCard or AccountTerms.

Troubleshooting

Request not sending? Verify API credentials (Account Number, API Username, API Password) and confirm the connection passes Test Connection.
Fields not mapping? Check the Mapping Dashboard to confirm all required fields are mapped correctly. Ensure Ship To address fields, SKU, and Quantity are present.
API rejection? Confirm ShipVia uses a valid code from the list. Verify Payment Method is set to CreditCard or AccountTerms. Check that all required Ship To fields are populated.
Missing confirmation details? Ensure Confirm To Email Address and Confirm To Name are configured in the integration settings.
Address validation errors? If the shipping address is causing failures, consider mapping Bypass Address Validation to Yes to skip validation.

Operation Workflow

FR is submitted to Kroll via SOAP API using the configured connection.
The request is sent as a Purchase Order Request to the Kroll endpoint.
If no error is received during submission, the FR is marked as processed.

Operation Details

Feature	Availability	What to Expect
Fulfillment Request Number	Supported	FR number is mappable and sent as External PO.
Ship To Address	Supported	Full address including Address Lines 1-3, City, State, Postal Code, Country.
Shipping Method (ShipVia)	Supported	Must use valid ShipVia codes (FedEx, UPS, USPS, etc.).
FR Item Association	Supported	Line items include SKU and Quantity in the request payload.
Signature Required	Supported	Can be mapped per order.
Auto Acknowledgements	Not Supported	No acknowledgement is received on submission.
Custom Fields	Not Supported	FR focuses on standard header + item fields.
Attachments	Not Supported	Additional files are not transmitted with the FR.

        
        Tip: Test with a single order first to verify ShipVia, Ship To Address,
        and API connectivity before enabling automation.

Get Shipments

Introduction

The Kroll – Get Shipments integration retrieves shipment data from Kroll via API, including carrier, tracking numbers, and shipment items. This operation uses the same Kroll API connection configured for other operations.

The sections below walk through each step of the setup and configuration process.

        Note: This operation retrieves shipment confirmations from Kroll via API and updates
        your orders with carrier, tracking, and item-level shipped quantities.
      

Use this job to:

Retrieve shipment data including carrier, shipping method, and tracking numbers from Kroll.
Update orders with ship date and shipping cost.
Associate shipped items by SKU and support partial shipments.

Each run follows this workflow:

1Connect — Uses the Kroll API connection (Account Number, API Username, API Password) to query shipment data.
2Parse — Carrier, method, tracking number, ship date, and line items (SKU & shipped qty) are parsed into your mapping template.
3Save — Shipment data posts back to the order; partial shipments are supported.

Example: Kroll returns a shipment with Carrier=UPS, Method=Ground, Tracking=1Z999…, ShipDate=2025-05-15, and line with SKU=KRL12345, ShippedQty=5 → order gets updated accordingly.

Step 1: Select Kroll API Connection

Choose Kroll and select your existing API connection.

Step 2: Create a Mapping Template

Choose or create a mapping template named Kroll – Get Shipments. Use the recommended fields from the Mapping Utilities section below.

Step 3: Save & Schedule

Run manually or schedule (UTC).

Mapping Template (Recommended Fields)

Use these source fields from Kroll – Get Shipments and Get Shipment Items to populate your shipment object.

Flxpoint Field	Kroll Field	Example	Purpose	Status
Shipped Via (T)	Shipment: Carrier	`UPS`	Carrier	Required
Order Confirmation Number (T)	Shipment: FR Number	`FR12345`	Link to FR	Required
Shipped Via (T)	Shipment: Method	`Ground`	Shipping method	Optional
Note (T)	Shipment: Note	`Shipped via UPS`	Note	Optional
Shipment Date (D)	Shipment: Shipped At	`2025-05-15T20:59:00Z`	Ship date	Required
Freight Amount (N)	Shipment: Shipping Cost	`10.00`	Shipping cost	Optional
Tracking Numbers (T)	Shipment: Tracking Number	`1Z999...`	Tracking	Required
Tracking URL (T)	Shipment: Tracking URL	`https://ups.com/...`	Tracking URL	Optional
Quantity Shipped (N)	Shipment Item: Quantity	`5`	Qty shipped	Required
Sku (T)	Shipment Item: Sku	`KRL12345`	Product SKU	Required
All Custom Fields (T)	Shipment Item: Custom Fields	`Special Handling: Yes`	Custom fields	Optional

Available Source Fields

The following fields are available from the Kroll Shipment schema:

Kroll Shipment: Discount Amount, Freight Amount, Order Confirmation Number, Order Status, Product Amount, Shipment Date, Shipment Identifier, Shipped Via, Total Amount, Tracking Numbers.
Kroll Shipment Item: Amount, Quantity Shipped, Sku, Unit Amount.

Operation Workflow

Shipment data is fetched via the Kroll API connection configured in settings.
Data is returned as structured API responses containing shipment headers and line items.
Partial shipments are supported — multiple API responses can incrementally complete fulfillment.

        
        Summary: Map carrier, tracking, ship date, FR number, and line-level SKU/quantity
        to get full shipment visibility in Flxpoint.

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
FR Number is mapped to associate shipments with the correct fulfillment requests.
Tracking Number and Carrier fields are mapped.

Troubleshooting

Data not importing? Verify API credentials (Account Number, API Username, API Password) and confirm the connection passes Test Connection. Check that shipments exist for the target FRs.
Fields not mapping? Check the Mapping Dashboard to confirm all fields are mapped correctly. Ensure the source field names match the Kroll shipment schema.
Missing tracking numbers? Some shipments may not include tracking data. Check if the shipment has been fully processed on the Kroll side.
Item lines not attaching? Ensure the Kroll response includes SKU and that your template maps it to the shipment line item.

Operation Details

Feature	Availability	What to Expect
Carrier & Methods	Supported	Carrier and method are available in the API response.
Shipment Item Association	Supported	Item association is by SKU.
Partial Shipments	Supported	Multiple responses can incrementally complete fulfillment.
Tracking Numbers	Supported	Tracking number and tracking URL are available.
Shipping Cost	Supported	Freight amount is available per shipment.
Custom Fields	Supported	Custom fields available at the shipment item level.
Invoice Information	Not Supported	Invoice/financials are not part of this operation. Use Get Invoices instead.

        
        Tip: Schedule this job to run frequently to keep shipment status and tracking
        information up to date in Flxpoint.

Get Invoices

Introduction

The Kroll – Get Purchase Order Invoices integration retrieves invoice data from Kroll via API for financial tracking and order reconciliation. This operation uses the same Kroll API connection configured for other operations.

The sections below walk through each step of the setup and configuration process.

        What it does: Fetches invoice data from Kroll via API and saves invoice headers,
        line items, and costs into Flxpoint for the related Fulfillment Requests (FRs).
      

Use this job to:

Capture official invoice totals (product costs, shipping, tax, fees) for accounting.
Associate invoice lines to FR items using the supplier SKU.
Support downstream reporting and margin analysis across orders.

Each run follows this workflow:

1Connect — Uses the Kroll API connection (Account Number, API Username, API Password) to query invoice data.
2Fetch Data — Job retrieves invoice records from Kroll via the API endpoint.
3Map — Invoice header and item fields are mapped via your Mapping Template (see recommendations below).
4Save — Flxpoint creates/updates PO Invoices linked to your FRs.

Example: If an invoice shows Item Cost = $50.00, Shipping = $10.00, Tax = $7.50, and references SKU KRL12345, the job will save an invoice with the associated costs and link the line item to SKU KRL12345.

Step 1: Select Kroll API Connection

Choose Kroll and select your existing API connection.

Step 2: Create a Mapping Template

Choose or create a mapping template named Kroll – Get Purchase Order Invoices. Use the recommended fields from the Mapping Utilities section below.

Step 3: Save & Schedule

Run on demand or enable a schedule (UTC).

Mapping Template (Recommended Fields)

Suggested starting point for Kroll invoice header and line items:

Flxpoint Field	Kroll Field	Example	Purpose	Status
Fee Cost (N)	Source Invoice: Fee Cost	`5.00`	Fee cost	Optional
Order Confirmation Number (T)	Source Invoice: FR Number	`FR12345`	Link to FR	Required
Shipment Date (D)	Source Invoice: Invoice Date	`2025-05-15T20:59:00Z`	Invoice date	Required
Invoice Number (T)	Source Invoice: Invoice Number	`INV12345`	Invoice number	Required
Order Status (T)	Source Invoice: Invoice Status	`Unpaid`	Status (Unpaid/Paid)	Required
Other Cost (N)	Source Invoice: Other Cost	`3.00`	Additional costs	Optional
Freight Amount (N)	Source Invoice: Shipping Cost	`10.00`	Shipping cost	Optional
Tax Cost (N)	Source Invoice: Tax Cost	`7.50`	Tax cost	Optional
Amount (N)	Source Invoice Item: Cost	`50.00`	Item total cost	Required
Invoice Item Type (T)	Source Invoice Item: Type	`Product`	Item type	Required
Unit Amount (N)	Source Invoice Item: Per Unit Cost	`10.00`	Per unit cost	Optional
Quantity Shipped (N)	Source Invoice Item: Quantity	`5`	Qty invoiced	Required
Sku (T)	Source Invoice Item: SKU	`KRL12345`	Product SKU	Required
Title (T)	Source Invoice Item: Title	`Blue Widget`	Item title	Optional
All Custom Fields (T)	Source Invoice Item: Custom Fields	`Special Order: Yes`	Custom fields	Optional

Available Source Fields

The following fields are available from the Kroll Invoice schema:

Kroll Shipment: Discount Amount, Freight Amount, Order Confirmation Number, Order Status, Product Amount, Shipment Date, Shipment Identifier, Total Amount.
Kroll Shipment Item: Amount, Quantity Shipped, Sku, Unit Amount.

Tip: Header-level Shipping/Tax/Other costs are added as separate invoice items. Map all cost fields to get complete financial visibility for reconciliation.

        
        Summary: Map the invoice header fields (number, date, status, costs) and line-level
        SKU/quantity/amount to get complete invoice data in Flxpoint.

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
FR Number is mapped to associate invoices with the correct fulfillment requests.
Invoice Number and Invoice Date fields are mapped.

Troubleshooting

Data not importing? Verify API credentials (Account Number, API Username, API Password) and confirm the connection passes Test Connection. Check that invoices exist for the target FRs.
Fields not mapping? Check the Mapping Dashboard to confirm all fields are mapped correctly. Ensure the source field names match the Kroll invoice schema.
Invoices not linking to FRs? Ensure the FR Number (Order Confirmation Number) is mapped and that the FR exists in Flxpoint. Verify the SKU in the invoice matches the SKU used on the FR line.
Missing costs? Map Freight Amount, Tax Cost, and Other Cost fields at the header level. Verify values are present in the Kroll API response.

Operation Details

Feature	Availability	What to Expect
Invoice Format	Supported	Data retrieved via Kroll API.
Line Item Costs	Supported	Amount and Per Unit Cost available at line level.
Item Association	Supported	SKU is provided for linking to FR items.
Invoice Status	Supported	Unpaid or Paid status available.
Header-Level Costs	Supported	Fee Cost, Other Cost, Shipping Cost, and Tax Cost available.
Custom Fields	Supported	Custom fields available at the invoice item level.

        
        Tip: Schedule this job to run regularly to keep invoice data current for
        financial reconciliation and margin analysis.

Troubleshooting

Common issues and solutions for Kroll integration. Expand each item to learn more.

Inventory not syncing or FTP connection failing

Discontinued SKUs behaving unexpectedly

Secondary variant data not updating

Order submission failing via Kroll API

Shipments or tracking not importing

Invoices missing or data mismatch

Still need help? If you're experiencing issues not covered here, contact Kroll or your Flxpoint account manager.

Contact Support

Flxpoint Knowledge

Kroll as a Source

How To Connect

Choose the right Source Type

Product Operations

Get Inventory (Primary)

Get Inventory (Secondary)

Order Operations

Send Fulfillment Requests

Get Shipments

Get Invoices

Troubleshooting

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

Flxpoint Knowledge

How To Connect

Choose the right Source Type

Product Operations

Get Inventory (Primary)

Get Inventory (Secondary)

Order Operations

Send Fulfillment Requests

Get Shipments

Get Invoices

Troubleshooting

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

Related Articles