Flxpoint Knowledge

Contact us

Kinsey's as a Source

Table of Contents

Overview How to connect Product Operations Order Operations

Kinsey's is a wholesale distributor of archery, hunting, and outdoor sporting goods — bows, crossbows, arrows, firearms, optics, and related gear from top brands. As a source in Flxpoint, Kinsey's provides reliable catalog imports, pricing and inventory sync, fulfillment-request submission, shipment tracking, invoice retrieval (including line-by-line breakdowns of product, fee, shipping, and tax), and product image retrieval.
 

 

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., Kinsey's as Source). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most Kinsey's 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 Kinsey's 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 Kinsey's: select Vendor Warehouse. This enables sending Fulfillment Requests to Kinsey's 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 Kinsey's. For most Kinsey's accounts, you do not create a Source Shipping Method here—Kinsey's will choose the carrier and service on their side when they receive the Fulfillment Request.

Step 1 — Shipping Methods (Skip for Kinsey's)
When the wizard opens the Shipping Methods step for this Source:
  • For typical Kinsey's setups, do not click "Add Method" and do not configure a Shipping Method on this screen.
  • Leave the list of methods empty and continue to the next step in the wizard.
Why? Kinsey's automatically selects the shipping method based on your account preferences, order details, and carrier availability. Sending a method from Flxpoint is not required and may conflict with how Kinsey's is configured to ship your orders.

Only create a Source Shipping Method if:
  • Your Kinsey's representative has explicitly confirmed that your account is configured to receive a shipping method via the API, and you plan to map it in your Send Fulfillment Request template; or
  • You are using Rate Shopping with a provider that requires a Source Shipping Method for routing.
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 gather the Kinsey's credentials you'll use for all Kinsey's integrations.
🔐 Phase 3: Create Your Kinsey's Connection +
Goal

To connect Kinsey's in Flxpoint, you'll gather the credentials required to create an Kinsey's Connection. Kinsey's supports two connection types—FTP (Basic Auth) and Kinsey's API Token. This connection is created once and powers all Kinsey's operations.

Step 1 — Open Get Inventory [Primary] and start
Inside your Kinsey's source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations. In the connector gallery, choose Kinseys. If you don't see it, use Not Listed? → Request a custom integration.
Step 2 — Choose your Connection Type
In New Kinseys Connection, select one of:
  • FTP (Basic Auth) — for file pickup over FTP.
  • Kinseys API Token — direct API auth (Group Code + User ID + Password).
Step 3a — If you choose FTP (Basic Auth)
Fill the form exactly as provided by Kinsey's:
  • Connection Name
  • FTP Protocol: FTP
  • FTP Host
  • FTP Port
  • FTP User
  • FTP Password
  • File Transfer Mode: Binary file type
Expand Advanced Settings if needed:
  • Maintain constant connection: Optional
  • Use unbuffered private data channel: Only for resolving specific FTPS errors
Click Test Connection → Save Connection.
Step 3b — If you choose Kinseys API Token
Enter:
  • Connection Name
  • Group Code
  • User ID
  • Password
Then Test Connection and Save Connection.
Note: These fields match the "New Kinseys Connection" modal exactly.
Step 4 — How Flxpoint uses this connection
One connection, all operations: This single Kinsey's Connection is reused by all Kinsey's integrations you'll configure later, including: Inventory [Primary], Inventory [Secondary], Fulfillment Requests, and Shipments. You don't need separate credentials for each operation.
Next Configure Product & Order Operations 🚀
Now that your Kinsey's Connection is saved, go to the Operations section of this doc to set up the Kinsey's integrations you need (Inventory and Order operations). Each operation will let you select the Kinsey's Connection you just created.

 


Product & Order Operations

Now that you’ve finished the wizard, you’ll see Kinseys has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your Kinseys stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to Kinseys and pulling back shipment/tracking data. All four use the same Kinseys connection and credentials you just set up so you can simply choose the operations that match your workflow.

 

Product Operations

Get Inventory Primary imports your Kinseys catalog including metadata such as attributes, images, titles and description. We recommend running this once daily to import any new items. Get Inventory Secondary is a faster, more efficient operation to import more frequent pricing and quantity updates. We recommend running this hourly.     

Get Inventory (Primary)

Introduction

In Flxpoint, Get Inventory (Primary) (GIP) is the job that imports Kinseys product data and quantities into your Global Inventory Pool. This job supports two connection methods (FTP or API token) and lets you aggregate quantities across selected warehouses.

Use GIP to keep Kinseys inventory current in Flxpoint: import the full Kinseys catalog with core details (brand, titles/descriptions, categories, images, weight), keep quantities current by optionally summing across selected warehouses, and bring in dealer pricing when available to you (client-specific pricing).

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.
KNS Pricing & Missing Cost Note: KNS often provides two different feeds:
  • Quantity feed (hardcoded): ftp.sprich.com → user onhand, pass onhand, file sprfull.ezoh (typically quantity-only).
  • Pricing feed (customer-specific): Credentials/file provided by KNS per customer. File names vary (e.g., JPR.x12_832_0724.csv) and contain your dealer pricing.
If you connect only to the quantity feed, costs will appear empty. Obtain your pricing FTP (or use the API) to import cost/MSRP.

Each run follows this workflow:

  • 1Select Connection — Choose FTP (Basic Auth) or Kinseys API Token when creating your connection.
  • 2Fetch Data —
    FTP: Flxpoint reads the latest CSV from your provider's FTP folder (you supply folder + filename pattern). API: Flxpoint requests product, quantity, and price from Kinseys's API using your Group Code / User ID / Password.
    When API is used, price/qty is read from the API; otherwise, the FTP feed is used, per your configuration.
  • 3Map Fields — Incoming columns are matched to your Mapping Template.
  • 4Save to Global Inventory Pool — The pool is updated; changes flow to channels after your next push.
Example: If you select Dallas and Phoenix warehouses and they report 4 and 7 units, the available quantity shown in Flxpoint will be 11.

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

Step 1: Connect an Integration

Choose Kinseys and create a connection.

Connection Type
  • FTP (Basic Auth)
    Fields: Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password.
    Advanced: File Transfer Mode (Binary), Maintain Constant Connection (optional), Use Unbuffered Private Data Channel (for FTPS 534 policy only).
    Tip: Use Test ConnectionValidates credentials and folder visibility before you save. after entering your credentials.
  • Kinseys API Token
    Fields: Connection Name, Group Code, User ID, Password.
    Use Case: Preferred when you need dealer pricing and direct price/qty from the API.
Step 2: Configure Settings
  • Remote File Name Pattern (FTP only) — e.g., *.csv or an exact filename.
  • Inbound Remote File Folder (FTP only) — e.g., /incoming/products.
  • File Action — set to Read for GIP.
  • Warehouse — choose All or select specific locations. What does this do? Available Quantity will be the sum from the selected Warehouses. 
    ALL ATLANTA BALTIMORE BIRMINGHAM BOSTON CHARLOTTE CHICAGO COLUMBUS DALLAS DENVER EDMONTON GRAND RAPIDS HOUSTON INDIANAPOLIS KANSAS CITY LOS ANGELES MIAMI NEW YORK PHOENIX PITTSBURGH SALT LAKE CITY SAN ANTONIO SEATTLE ST. LOUIS VANCOUVER
  • Archive/Un-Archive Inventory — Enable to archive items missing from the feed and auto-restore them if they reappear.
    Recommendation: Don't enable Archive on both Primary and Secondary for the same source.
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 (e.g., "Kinseys Get Source Products 1") once complete.


Recommended Mapping (Get Inventory Primary)

Kinsey's API uses two endpoints: the Products API (/v2/Products) for catalog data such as name, description, images, brand, and barcode; and the Inventory API (/v2/Inventory) for real-time stock levels, cost, MAP, and MSRP. Map each Flxpoint field to the correct source field per the table below.

Flxpoint Field Kinsey's Source Field Status Notes
SKU (T) Inventory: SKU Required Primary product identifier
Title (T) Product: Name Required Product display name
Description (T) Product: Description Optional Short or long description
UPC (T) Product: Barcode Optional ⚠️ Map to Product: Barcode (Products API), NOT Inventory: UPC. UPC values live in the Products API barcode field — the Inventory API does not carry UPC.
Cost (N) Inventory: Cost Optional Unit cost from inventory feed
Quantity (N) Inventory: Quantity Optional Real-time stock from Inventory API
MSRP (N) Inventory: MSRP Optional Retail price
MAP (N) Inventory: MAP Optional Minimum advertised price
Weight (N) Product: Weight Optional Shipping weight
Image (T) Product: Image URL Optional Primary product image
Brand (T) Product: Brand Optional Manufacturer/brand name
⚠️ Important — UPC source field: UPC values for Kinsey's products are stored in the Products API as the Barcode field. They are not present in the Inventory API response.

To import UPC values correctly, map:

  • Flxpoint field: UPC (T)
  • Source field: Product: Barcode

If UPC is mapped to an Inventory API field instead, any product not present in the Inventory API (~9K items in a typical Kinsey's catalog) will import with a blank UPC.

Catalog vs Inventory coverage: Kinsey's Products API has approximately 29K items; the Inventory API returns ~20K variants. Products not present in the Inventory API will still be saved to Flxpoint, but will be missing quantity, cost, MAP, and MSRP — these fields come exclusively from the Inventory API.
Recommended Mapping (Starter)

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

Flxpoint Field Kinseys Field Notes
SKU Sku / Catalog Sku Unique product identifier.
Title Description 1 (fallback: Description 2/3) Human-readable product name.
Brand Brand Name / Manufacturer Name Normalize as needed.
Quantity Quantity Aggregated when multiple warehouses are selected.
Client Price Dealer Price Dealer-specific pricing when available.
MSRP Retail Price or column AF per pricing file Map from pricing file when available.
Cost column CI per pricing file "Promo Level 1 Dealer Cost."
Category 1 Department Name Top-level category.
Category 2 Class Name / Subclass Name Second-level category.
Weight Weight Pounds.
UPC Upc Barcode (if present).
Attributes Product Specifications, Marketing Text, etc. Bring as custom attributes.
Images (Image URL fields if provided) Single primary image supported.
Also available to map: Department/Class/Subclass Numbers, UNSPSC, No Return, UPS Shippable, Country of Origin, and more.
Pricing Feed Details (SPR)
Feeds You May Receive from SPR
  • Quantity (On-hand) FTP — ftp.sprich.com | user onhand | pass onhand | file sprfull.ezoh.
    Typically contains quantities only.
  • Pricing FTP (Customer-Specific) — Credentials + file name are provided per customer by KNS (name varies).
    Sample: JPR.x12_832_0724.csv | Specs: "Price File Header List & Descriptions.xlsx".
Required for costs: Connect your pricing FTP (or use KNS API). If you only connect to onhand, cost/MSRP will import as empty.
Column Mapping (Pricing File)
Flxpoint Target KNS Column Description
Wholesale Cost CI — "Promo Level 1 Dealer Cost" Dealer/contract cost used as item cost.
MSRP AF — "Current Retail Price" Retail/MSRP reference.
When to use API: If KNS confirms your FTP pricing file is unavailable or delayed, request API credentials (Group Code, User ID, Password) and switch the connection to API to fetch price & quantity directly.
Operation Workflow & Notes
  • Rich content (long descriptions/specs) can be sourced from Etilize FTP when provided. Use your assigned FTP host/folder and file pattern.
  • Multiple warehouses are supported in configuration (sum of selected warehouses shows as Available Quantity).
  • API vs FTP: When the API connection is used, price/qty is read from the Kinseys API; otherwise FTP is used for price/qty.
Summary: Map the core fields above and verify your pricing source (FTP file or API) to ensure cost, MSRP, and quantity import correctly.

UPC missing on imported items

If UPC values are blank on some or all imported Kinsey's items, check your Get Inventory (Primary) mapping template:

  1. Open Get Inventory (Primary) → Mapping Template.
  2. Find the UPC (T) field row.
  3. Confirm it is mapped to Product: Barcode (not to any Inventory API field).
  4. Save the template and re-run Get Inventory (Primary). UPC values should populate on the next run for all products where Kinsey's provides a barcode in their Products API.
Note: Not all Kinsey's products include a barcode value in their Products API. Items that lack a barcode on Kinsey's side will continue to import with a blank UPC — this is expected and not a mapping error.
Items missing quantity, cost, or MSRP

Kinsey's Products API (~29K items) and Inventory API (~20K variants) do not have full overlap. Products not present in the Inventory API will still be saved to Flxpoint, but quantity, cost, MAP, and MSRP will be blank. This is expected behavior — those fields are sourced exclusively from the Inventory API. Contact Kinsey's if you believe a specific SKU should be present in their inventory feed.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Warehouse selection matches your fulfillment needs (All or specific locations).
  • Archive is enabled in one integration only (Primary or Secondary, not both).
  • If using FTP: Remote File Name Pattern and Inbound Folder are set correctly.
  • If using API: Group Code, User ID, and Password are confirmed with Kinsey's.
Troubleshooting
  • Costs are empty:
    • Confirm you have a pricing FTP from KNS (customer-specific credentials) or use the API. The onhand FTP (ftp.sprich.com / onhand/onhand) is typically quantity-only.
    • Verify you're pulling the correct pricing file (name varies; example JPR.x12_832_0724.csv) and mapping CI to Cost, AF to MSRP per "Price File Header List & Descriptions.xlsx".
    • If KNS confirms the FTP file no longer carries pricing, request API credentials (Group Code, User ID, Password) and switch the connection to API.
  • FTP auth / connection errors: Re-check host, port, username/password, and try Test Connection. For FTPS 534 policy failures, toggle "Use Unbuffered Private Data Channel."
  • API credential errors: Confirm Group Code, User ID, and Password. Ensure your account has access to price/qty endpoints.
  • No quantities or mismatches: Verify selected Warehouse options and that the source file/API returns non-zero Quantity.
  • Items missing after a run: If Archive is enabled, SKUs absent from the feed will be archived (qty set to zero) until they reappear.
Customer Action (when costs missing): Contact SP Richard to request the correct pricing FTP credentials/file or API credentials for pricing access.
Operation Details
Feature Availability What to Expect
Custom Fields Supported Extra product attributes saved as variant custom fields.
Variations / Options Not Supported Simple products only.
Generic Pricing (& Currency) Not Supported Use client/dealer price when applicable.
Client Pricing (& Currency) Supported Dealer price per account.
Quantity Supported From API/FTP; sums across selected warehouses.
Multiple Warehouses Supported Select in configuration to aggregate.
Weights & Dimensions (& Units) Supported Weight only, in pounds.
Images Supported Single image per product (additional via custom fields if provided).
Categories Supported Two-level structure for mapping.
Delta vs Full Feed Full Feed This is a full product feed.
Archive Support Supported Archive missing SKUs; auto-restore when they return.
Tip: Run a manual sync first to verify field mapping and pricing data before enabling a recurring schedule.
 
 

Get Inventory (Secondary)

Introduction

Get Inventory (Secondary) is the incremental update job for Kinseys. It typically pulls a compact file containing cost, MSRP, and quantity by warehouse, and updates your Global Inventory Pool accordingly. This job is designed as a delta feed (cost/qty only), complementing the Primary catalog import.

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

Tip: Use Secondary for higher-frequency price/qty refreshes. Keep rich catalog fields (titles, images, long descriptions) in the Primary job.

Use this job to:

  • Refresh dealer cost and MSRP for existing SKUs.
  • Update quantities and aggregate across the warehouses you select.
  • Optionally create variants during the run (advanced setting).

Each run follows this workflow:

  • 1Connection — Uses an FTP (Basic Auth) connection to retrieve the inventory feed (e.g., sprfull.ezoh) and, if configured, a separate price file (CSV). The price file headings specify which columns hold cost/MSRP.
  • 2Parse & Map — The file includes warehouse codes and quantities for each SKU. Mapping then targets only the fields listed in "Recommended Mapping (Secondary)." Fields like Item Number, Current Quantity, and MSRP come from your Kinseys Inventory Item schema.
  • 3Write — Updates cost/qty in the Global Inventory Pool.
Example: SKU ABC-123 has cost 12.10, MSRP 19.99. Phoenix shows 4, Dallas shows 6 ⇒ Flxpoint quantity becomes 10 when both warehouses are selected.
Step 1: Connect an Integration

Choose Kinseys and use FTP (Basic Auth) credentials.

Step 2: Configure Settings
  • Remote File Name Pattern — e.g., sprfull*.ezoh or your provider's exact filename.
  • Inbound Remote File Folder — the source directory for the feed.
  • File Action — set to Read.
  • Archive/Un-Archive Inventory — Archiving removes SKUs not present in this delta. Recommendation: if archiving is already enabled in the Primary job, leave it off here to avoid conflicts.
  • Warehouse — Select All or specific locations (available quantity is the sum of selected warehouses; the UI tooltip confirms this).
  • Advanced > Allow Create Variant — toggle Yes to allow variant creation during Secondary runs.
Step 3: Define a Mapping Template

Use the "Secondary" mapping 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 (e.g., "Get Inventory 2").


Recommended Mapping (Secondary)

Map only the fields you need for delta updates. Field names below are drawn from your Kinseys Inventory Item schema & templates.

Flxpoint Field Kinseys Field Notes
SKU Item Number Primary identifier used to match existing products.
Quantity Current Quantity Per-warehouse quantities; Flxpoint aggregates based on selections.
Dealer Cost Price file column CI "Promo Level 1 Dealer Cost" From the separate price CSV.
MSRP Price file column AF "Current Retail Price" From the separate price CSV.
Warehouse Code Warehouse Code Used to attribute quantity by location.
Warehouse Codes (Examples)

The inventory feed encodes quantity per warehouse. Common codes include:

001: Atlanta, GA002: Charlotte, NC003: Miami, FL 004: Tampa, FL005: Dallas, TX006: Memphis, TN 007: Kansas City, MO008: Houston, TX009: Columbus, OH 010: Paul, MN011: Denver, CO012: Richmond, VA 013: Oklahoma City, OK014: Street, Fort, OR015: San Antonio, TX 016: Birmingham, AL017: New Orleans, LA018: St. Louis, MO 019: Baltimore, MD020: Orlando, FL022: Greensboro, NC 023: Philadelphia, PA024: Indianapolis, IN026: Nashville, TN 027: Jacksonville, FL028: Seattle, WA029: Syracuse, NY 030: Sacramento, CA031: Los Angeles, CA033: Salt Lake City, UT 034: Boston, MA035: Chicago, IL036: Phoenix, AZ 037: New York, NY038: Pittsburgh, PA039: Grand Rapids, MI
Summary: Secondary mapping focuses on cost, quantity, and warehouse code only. Keep catalog-level fields (titles, images, descriptions) in the Primary job.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Warehouse selection matches your fulfillment needs.
  • Archive is off if already enabled in Primary.
  • Remote File Name Pattern and Inbound Folder are set correctly.
Troubleshooting
  • FTP connection fails: Verify host/port and credentials; try Test Connection. For FTPS 534 policy issues, use the unbuffered private data channel setting.
  • Missing or zero quantities: Confirm the file contains the warehouse codes you selected and that Current Quantity is non-zero.
  • Price not updating: Ensure the price CSV column mapping uses CI (Dealer Cost) and AF (Current Retail Price).
  • Unexpected archives: If Archive is enabled and a SKU is absent from the delta, it will be archived with qty=0 until it reappears.
Operation Details
Feature Availability What to Expect
Custom Fields (Variants Only) Not Supported Secondary focuses on price/qty only.
Generic Pricing (& Currency) Not Supported Use dealer pricing.
Client Pricing (& Currency) Supported Mapped to dealerPrice, available in USD.
Quantity Supported From feed; aggregated across chosen warehouses.
Multiple Warehouses Supported Select locations in config; quantity sums across selections.
Weights & Dimensions (& Units) Not Supported Not provided in the delta file.
Delta Feed vs Full Feed Supported (Delta) Only cost and quantity are saved.
Archive Support Supported Toggle in configuration.
Tip: Run Secondary on a more frequent schedule than Primary to keep cost and quantity data fresh between full catalog syncs.
 
 
Optional but recommended

Keep your catalog up to date automatically

After configuring Get Inventory Primary and Get Inventory Secondary, you can schedule both jobs so items, inventory, and pricing update for you.

  • Schedule Primary to import new and updated items.
  • Schedule Secondary after Primary to refresh stock and pricing.
  • Adjust the cadence anytime if your supplier changes their update frequency.
How to schedule Get Inventory operations in Flxpoint
Click the animation to view it larger.

 

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 Kinsey's – Send Fulfillment Requests integration automates sending purchase orders (POs) to Kinsey's for fulfillment. Flxpoint converts fulfillment request details — such as shipping addresses, item quantities, and distribution center codes — into Kinsey's' required XML format and uploads the file to your configured FTP outbound folder.

This integration uses an FTP (Basic Auth) connection configured during inventory setup. Configuration involves selecting the connection, defining settings (outbound folder, Ship To Account), and creating a mapping template that includes the mandatory ShipNode.ShipNode field.

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

The Send Fulfillment Requests integration converts Flxpoint fulfillment requests into Kinsey's purchase orders in XML format. The XML is uploaded via FTP to Kinsey's' inbound folder. If no error is received during upload, the FR is marked as processed.

The setup is completed in four steps.

Step 1: Connect an Integration

Select Kinseys and choose your existing FTP (Basic Auth) connection. This is the same connection used for inventory operations. If you need a new connection, enter:

  • Connection Name
    Internal reference name (e.g., Kinsey's FTP).
  • FTP Protocol
    FTP.
  • FTP Host
    Provided by Kinsey's.
  • FTP Port
    Provided by Kinsey's.
  • FTP User
    Your FTP username.
  • FTP Password
    Your FTP password.
  • File Transfer Mode
    Binary file type.

Click Test Connection, then Save Connection once successful.

Tip: You do not need a separate connection. Reuse the same Kinsey's FTP connection created during inventory setup.
Step 2: Configure Settings
  • Outbound Remote File Folder * — required. The path on the Kinsey's FTP where XML FRs should be written.
  • Ship To Account Number * — Your Kinsey's ship-to account identifier used on the FR.
    • If a Ship To Account is mapped in the template, that mapped value is used.
    • If it is not mapped, the value configured here is used.
    • If no Ship To Account value is available from either source, the Send Fulfillment Request job will fail.

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.

Step 3: Define a Mapping Template

Choose an existing template (e.g., Send Purchase Orders 2) or create a new one. Click Save and Complete.

Required: Your mapping template must include ShipNode.ShipNode as a two-digit DC value (e.g., "01", "31"). This field is mandatory even when using Source Complete "C". Do not prefix with "DC ".
Template tip: If the DC is constant, set a constant value like "01". If it varies by product or region, add a transform/rule that always outputs two digits.
Step 4: Save & Complete

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 Kinsey's' External Order XML schema. Header fields and line items map from your order to Kinsey's' required format.

Kinsey's Requirement — ShipNode (DC)
  • Mandatory field: XML must include ShipNode.ShipNode.
  • Format: exactly two digits, with leading zero if needed (e.g., "01", "31"). Do not send "DC 01".
  • Source Complete "C": even though Kinsey's sources the order (DC not chosen from this value), the field is still required and must be valid.
Example (valid): <ShipNode><ShipNode>01</ShipNode></ShipNode>
Example (invalid): <ShipNode><ShipNode>DC 01</ShipNode></ShipNode>
Recommended Mapping (Key Fields)
Business Value Kinsey's FR Field Notes
FR / PO Number CustomerPONo Mappable in template; used as the Fulfillment Request Number.
Distribution Center (DC) ShipNode.ShipNode Mandatory. Exactly two digits (e.g., "01", "31"). Required even with Source Complete "C".
Ship-To Account ShipToAccount Configured in job settings. Can also be mapped in template (mapping takes precedence over settings).
Shipping Method ParcelZone / Carrier fields Can pass supplier shipping method; selection UI not supported.
Items Line Items (SKU) SKU is sent with each FR line.
Ship To Account Source SUPPORTED (Mapping + Settings) If Ship To Account is mapped in the template, that value is used. If not mapped, the value from integration settings is used. If no value exists in either place, the Send Fulfillment Request job fails.
Ship To Account (Optional Mapping)
  • You can also map Ship To Account in this template when you need different ship-to accounts per rule (for example, per warehouse, brand, or channel).
  • When present in the mapping, this value takes precedence over the Ship To Account configured in the job settings.
  • If neither the mapping nor the job settings provides a Ship To Account, the Send Fulfillment Request job will fail.
Tip: If your DC varies by product or region, set ShipNode.ShipNode via a mapping rule or transformation that yields a two-digit string. Avoid prefixes like "DC ".
Summary: Map the key fields above for accurate FR submission to Kinsey's. ShipNode.ShipNode and Ship To Account are the most critical fields to verify.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • ShipNode.ShipNode is mapped to a valid two-digit DC value.
  • Ship To Account is configured in settings or mapped in the template.
  • Outbound Remote File Folder is set to the correct FTP path.
Troubleshooting
  • Upload errors? — Verify FTP credentials and folder path. Confirm the XML meets Kinsey's' schema requirements.
  • FR not marked processed? — Check job notifications for an error during upload; fix and re-run.
  • Missing SKU lines? — Confirm your mapping includes SKUs on each FR line.
  • ShipNode rejected? — Ensure ShipNode.ShipNode is exactly two digits (e.g., "01"). Values like "DC 01" or non-numeric strings will be rejected by Kinsey's.
  • Using Source Complete "C"? — The field is still mandatory. Include a valid two-digit DC even though Kinsey's determines the DC during sourcing.
  • Ship To Account failure? — Verify the value exists either in the mapping template or in job settings. If neither provides a value, the job will fail.
Operation Workflow
  • FR is posted on the FTP configured in connection settings.
  • File is posted as .xml.
  • If no error is received while uploading the file, the FR is marked as processed.
Operation Details
Feature Availability What to Expect
Fulfillment Request Number Supported FR number is mappable and sent as CustomerPONo.
Distribution Center (ShipNode) Supported (Mandatory) ShipNode.ShipNode must be present and formatted as two digits.
Ship To Account Source Supported (Mapping + Settings) If Ship To Account is mapped in the template, that value is used. If not mapped, the value from integration settings is used. If no value exists in either place, the Send Fulfillment Request job fails.
FR Item Association Supported Line items include SKU in the FR payload.
Customer Association Not Supported Customer record linking is not used.
Auto Acknowledgements Not Supported No acknowledgement file is received on upload.
Shipping Selection Not Supported Selection UI not supported, but supplier shipping method can be sent.
Custom Fields Not Supported FR focuses on standard header + item fields.
Attachments Not Supported Additional files are not transmitted with the FR.
Limitations Follow supplier's XML schema; errors during upload will prevent "processed" status.
Tip: Test with a single order first to verify ShipNode, Ship To Account, and FTP folder path before enabling automation.
 
 

Get Shipments

Introduction

Get Shipments (GS) retrieves shipment confirmations from Kinseys via FTP as .xml files and updates your orders with carrier, method, tracking, and item-level shipped quantities.

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

Note: Some shipments may not populate a carrier_number; related values can appear on Carton ID or BOL. Use mapping and rules to capture the best available identifiers.

Use this job to:

  • Fetch shipment XMLs from the supplier's FTP inbound folder.
  • Update orders with carrier, shipping method, tracking ID, and ship date.
  • Associate shipped items by SKU and support partial shipments where only a subset is shipped.

Each run follows this workflow:

  • 1Pull XML — GS reads files that match your Remote File Name Pattern from the configured Inbound Remote File Folder.
  • 2Parse — Carrier, method, tracking, carton/BOL, and line items (SKU & shipped qty) are parsed into your mapping template.
  • 3Apply Lookback — Only FRs created within the FR Lookback Period are considered (default 90 days).
  • 4Save — Shipment data posts back to the order; partials are supported.
Example: XML shows Carrier=UPS, Method=Ground, Tracking=1Z…, ShipDate=2025-08-17, and line with SKU=ABC-123, ShippedQty=2 → order gets updated accordingly.
Step 1: Connect an Integration

Choose Kinseys and your FTP (Basic Auth) connection.

Step 2: Configure Settings
  • Remote File Name Pattern * — File mask for shipment XMLs (e.g., kns_shipments_*.xml).
  • Inbound Remote File Folder * — FTP directory from which to read shipment files.
  • File Action — Read (leave files) or other actions per your policy.
  • Advanced → FR Lookback Period for Get Shipments — Max age of FRs eligible for shipment retrieval (default 90 days). Tooltip explains behavior.
Step 3: Define a Mapping Template

Use the recommended fields from the Mapping Utilities section below.

Step 4: Save & Schedule

Run manually or schedule (UTC).


Mapping Template (Recommended Fields)

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

Shipment Field Kinseys Field Notes
Carrier Carrier Text value in shipment header.
Method Shipping Method Supplier shipping method string.
Tracking ID Tracking ID Main tracking code; may be blank on some LTLs.
Carton ID / BOL Carton Id / Bol Use when tracking isn't provided.
Shipped At Ship Date Date value mapped to shipment timestamp.
PO Number Purchase Order Number Used to associate XML back to the FR/Order.
Item → SKU SKU Shipment line association is by SKU.
Item → Shipped Qty Shipped Quantity Supports partial shipments.
Item → UOM UOM Optional; for reporting/consistency.
Weight Actual/Estimated Weight If present, map to shipment weight.
Operation Workflow
  • Shipment is fetched via the FTP connection configured in settings.
  • File format is .xml; a sample file is referenced in the docs.
  • Carrier number may not be present; consider using Carton ID or BOL fields and mapping rules to preserve identifiers.
Summary: Map carrier, tracking, ship date, PO 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.
  • Remote File Name Pattern and Inbound Folder match the shipment XML location.
  • FR Lookback Period covers the age of your target FRs (default 90 days).
Troubleshooting
  • No shipments found? Verify the file pattern/folder and the Lookback window cover your target FRs.
  • Missing tracking? Check Carton ID/BOL fields and map to a custom attribute for reference if needed.
  • Item lines didn't attach? Ensure the supplier XML includes SKU and your template maps it to the line item.
Operation Details
Feature Availability What to Expect
Carrier & Methods Supported Carrier and method are available in the XML we receive.
Shipment Item Association Supported Item association is by SKU.
Partial Shipments Supported Multiple files/lines can incrementally complete fulfillment.
Invoice Information Not Supported Invoice/financials are not part of this feed.
Custom Fields Not Supported Standard shipment fields only.
Limitation Carrier number may be missing; map Carton Id/BOL and use rules as needed.
Tip: If tracking IDs are frequently missing, set up a rule to fall back to Carton ID or BOL as the tracking reference.
 
 

Get Invoices

Get Invoices retrieves invoice data from Kinsey's for your fulfilled orders. Each invoice is linked to a Fulfillment Request number (PO number) and contains one or more line items that break down the costs associated with that order.

Purpose of This Job

Pulls invoice data from Kinsey's API by Fulfillment Request number so you can reconcile what you were actually billed against what was ordered and shipped.

How It Works
  • For each fulfilled order, Flxpoint queries Kinsey's by PO number to retrieve the invoice.
  • Each invoice response contains a list of line items, each categorized by line_type: product, fee, shipping, or tax.
  • Flxpoint stores the invoice and line items against the original Fulfillment Request so they show up in your order history and accounting exports.
What Get Invoices Returns

Each invoice response includes:

  • po_number — the Fulfillment Request / PO number the invoice is tied to.
  • invoice_id — the unique invoice identifier from Kinsey's (e.g., INV2000009).
  • status — the payment status of the invoice (e.g., paid).
  • invoice_date — the date the invoice was issued.
  • items — a list of line items, each with a line_type that determines its content (see Mapping & Configuration below).
Tip: Schedule Get Invoices daily, off-hours. Kinsey's typically finalizes invoices some hours after shipment — running real-time won't give you newer data.
Invoice Line Types

Kinsey's returns up to four line types per invoice. Not all line types appear on every invoice — shipping and tax are conditional:

line_type Typical SKU Description Notes
product e.g., 1405114 The purchased item — SKU, description, quantity, and cost. Always present. Map SKU to Order Item SKU and total_cost to item cost.
fee e.g., HC185 Handling or service charges (e.g., "Handling Charge $1.85"). Always present. Map total_cost to a fee or handling charge field.
shipping FRT Freight/shipping cost (e.g., "Freight Out"). Present only for accounts set up as flat rate or third-party shipping. May be absent.
tax TAX Total tax applied to the order. Absent for most accounts. Only present when tax is charged.
Mapping Tips
  • Product lines → map to order item cost fields. Use the sku field to match the invoice line to the correct fulfillment item.
  • Fee lines (line_type: "fee") → map to a handling charge or additional cost field in your mapping template.
  • Shipping lines (line_type: "shipping") → map to shipping cost. If your account does not use flat-rate or third-party shipping, these lines will not appear — design your mapping to handle their absence gracefully.
  • Tax lines (line_type: "tax") → absent for most accounts. Only map this field if your account is configured to receive tax charges.
Example Invoice Response

Below is a representative invoice showing all four line types. In practice, most invoices will contain product and fee lines; shipping and tax lines are less common.

{
  "invoices": [
    {
      "po_number": "1000000-1",
      "invoice_id": "INV2000009",
      "status": "paid",
      "invoice_date": "2026-04-01T00:00:00",
      "items": [
        { "line_type": "fee",      "sku": "HC185",    "description": "Handling Charge $1.85", "quantity": 1, "total_cost": 1.85  },
        { "line_type": "product",  "sku": "1405114", "description": "Hi-Point C-9 Pistol",  "quantity": 1, "total_cost": 124   },
        { "line_type": "shipping", "sku": "FRT",      "description": "Freight Out",          "quantity": 1, "total_cost": 14.29 },
        { "line_type": "tax",      "sku": "TAX",      "description": "Total tax",             "quantity": 1, "total_cost": 7.44  }
      ]
    }
  ]
}
Common Issues
  • Invoice doesn't appear right after fulfillment: Kinsey's typically finalizes invoices some hours after shipment. Allow time.
  • Shipping line missing: If your account is not configured as flat-rate or third-party shipping, Kinsey's won't include the shipping line. This is expected — not a bug.
  • Tax line missing: Most accounts don't receive tax lines. Only tax-configured accounts get them.
  • Cost doesn't match expectation: The total in Flxpoint reflects whatever line types Kinsey's returned. If you expected shipping or tax and don't see it, confirm your Kinsey's account configuration.

Get Images

Get Images retrieves product images from Kinsey's for your listings. Use this to keep image assets in sync alongside catalog data from Get Inventory.

Purpose of This Job

Pulls product images from Kinsey's into your Flxpoint product records. Supported only via FTP for Images and Categories — make sure your Kinsey's connection has FTP credentials configured.

How It Works
  • Connects to Kinsey's image FTP endpoint using the credentials configured on your source.
  • Downloads product images by SKU and attaches them to the matching products in Flxpoint.
  • Runs on the recurring schedule you set — image refresh doesn't need to be as frequent as inventory.
Tip: Schedule Get Images weekly. Kinsey's image library doesn't change as fast as pricing or inventory.

The Get Images mapping is minimal — typically just SKU (to match images to existing products). Images are attached to the product record automatically; no per-image mapping is required.

  • SKU — required, used to match image files to existing products.
  • Image URL / file path — populated automatically from Kinsey's FTP.
Common Issues
  • No images appearing: Confirm Test Connection passes on the FTP credentials. Check that the Inbound Remote File Folder matches where Kinsey's delivers your image files.
  • Images attached to wrong products: SKU mismatch — confirm the SKU in your Flxpoint products matches Kinsey's exactly (case + formatting).
  • Old / stale images: Run the integration manually after Kinsey's confirms a refresh on their side.
Optional but recommended

You’re ready to automate this source

You’ve finished setting up this source. If you’d like, you can now put its operations on an automated schedule.

  • Select the operations to schedule (for example, Get Inventory, Get Orders, Send Fulfillment Requests, Get Shipments).
  • Pick how often and when they should run. You can edit or pause schedules anytime from the operations screen.

Tip: A daily schedule for key operations is a simple place to start.

How to schedule source operations in Flxpoint
Click the animation to view it larger.

 

 

Common issues and solutions for Kinsey's integration. Expand each item to learn more.

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

Contact Support

 

 

Related Articles

RSR as a Source

In this guide, you’ll learn how to set up your RSR feed in Flxpoint, from creatin...

Sports South as a Source

Sports South can be connected to Flxpoint as a  supplier source to automate  inve...

Lipseys as a Source

This document will cover how to connect Lipseys as a source and what integrations...

Zanders as a Source

Overview This document will cover how to connect Zanders to Flxpoint via FTP and ...