Kinsey's as a Source
July 2, 2026
Summary
Kinsey's is a wholesale distributor of archery, hunting, and outdoor sporting goods - bows, crossbows, arrows, firearms, optics, and related gear. As a Flxpoint source it supports catalog import (via Kinsey's API v2 or FTP), inventory and pricing sync, automated fulfillment-request submission, and shipment tracking. One connection - either FTP (Basic Auth) or a Kinsey's API Token - is created once in Get Inventory (Primary) and reused by every operation.
What this integration does
Get Inventory (Primary)
Imports the full Kinsey's catalog - titles, descriptions, brand, images, barcode, cost, MSRP/MAP and quantity
Get Inventory (Secondary)
Pulls the faster cost, MSRP and per-warehouse quantity delta feed to keep pricing and stock fresh between full imports
Send Fulfillment Requests
Converts fulfillment requests into Kinsey's XML purchase orders and uploads them to the FTP outbound folder
Get Shipments
Reads Kinsey's shipment XML and writes carrier, method, tracking and shipped quantities back to the order
How to connect - credentials you need
Inside your Kinsey's source, open Integrations → Get Inventory [Primary], click Start Creating Integrations, choose Kinseys, then in New Kinseys Connection enter the API Key Kinsey's provided. Click Test Connection → Save Connection.
API KeyRequired
The only detail needed to connect Kinsey's. FTP is no longer offered as a connection option, and no Group Code, User ID or Password is required.
Provided by Kinsey's.
One connection powers Get Inventory (Primary), Get Inventory (Secondary), Send Fulfillment Requests and Get Shipments - you don't create separate credentials per operation. If Test Connection fails, reconfirm the API Key with Kinsey's.
Important - read before configuring
FTP connection is revoked - the API is the only connection option
Currently the FTP connection is revoked and we have an API connection only for direct source connection. Connect using your API Key to pull cost, quantity and all other catalog data.
Map UPC to Product: Barcode - never to an Inventory field
UPC values live in the Kinsey's Products API as the Barcode field; they are not present in the Inventory API. Mapping UPC to any Inventory field leaves most items with a blank UPC.
The Products and Inventory APIs cover different item counts
The Products API returns roughly 29,000 items; the Inventory API roughly 20,000 variants. Products missing from the Inventory API still import, but without quantity, cost, MAP or MSRP - this is expected, not a sync error.
ShipNode.ShipNode is mandatory on every fulfillment request - exactly two digits
The ShipNode.ShipNode field must be present in every Send Fulfillment Requests mapping and formatted as exactly two digits (e.g., 01, 31). Values like DC 01 or a single digit are rejected and the request will not process - even when using Source Complete "C".
Mapping - fields to know
| Flxpoint Field | Kinsey's Source Field - Notes |
|---|---|
| SKU | → Inventory: Item Number or Product: North Item Number / South Item Number / Vendor Item Number. Required. Primary product identifier. |
| Parent SKU | → Parent Child SKU. Links variants to their parent product. |
| Variant: Title | → Product: Name. Required. Product display name. |
| Parent: Title | → Product: Parent Title. Parent-level product name. |
| Description | → Product: Description/Extended Text. Short or long description. |
| UPC | → Bar Code. Map here, not to Inventory: UPC - UPC lives only in the Products API. |
| Cost | → Price. Unit cost from the Inventory API. |
| Quantity | → Warehouse Quantity On Hand. Real-time stock; sums across the warehouses you select. |
| MSRP | → Msrp. Retail price. |
| MAP | → MAP Price. Minimum advertised price. |
| Weight | → Product: Weight. Shipping weight, in pounds. |
| Brand | → Product: Brand. Manufacturer / brand name. |
| All Images | → Direct Copy. All product images are copied directly - no per-field mapping needed. |
Connect over the API (Products API
/v2/Products for catalog data + Inventory API /v2/Inventory for stock, cost, MAP and MSRP). Select which warehouses to aggregate, and enable Archive on only one inventory job.| Flxpoint Field | Kinsey's Field - Notes |
|---|---|
| SKU | → Item Number. Primary identifier used to match existing products. |
| Quantity | → Current Quantity. Per-warehouse; Flxpoint aggregates across your selected warehouses. |
| Dealer Cost | → pricing-file column CI ("Promo Level 1 Dealer Cost"). From the separate price CSV. |
| MSRP | → pricing-file column AF ("Current Retail Price"). From the separate price CSV. |
| Warehouse Code | → Warehouse Code. Attributes quantity by location. |
Higher-frequency FTP (Basic Auth) delta feed that updates cost, MSRP and quantity only - keep titles, images and descriptions in Primary. Run it hourly, and leave Archive off here if it is already enabled on Primary.
| Business Value | Kinsey's FR Field - Notes |
|---|---|
| FR / PO Number | → CustomerPONo. Sent as the Fulfillment Request number. |
| Distribution Center (DC) | → ShipNode.ShipNode. Mandatory, exactly two digits (e.g., 01, 31) - required even with Source Complete "C". Never prefix with DC . |
| Ship-To Account | → ShipToAccount. Set in job settings or mapped in the template (mapping takes precedence). If neither provides a value, the job fails. |
| Shipping Method | → ParcelZone / carrier fields. Supplier shipping method can be passed; a selection UI is not supported. |
| Items | → line items (SKU). Each fulfillment-request line carries its SKU. |
Runs over an FTP (Basic Auth) connection. Set the Outbound Remote File Folder (where the XML fulfillment requests are written) and a default Ship To Account Number in the job settings. Each FR uploads as an
.xml file; if the upload returns no error, the FR is marked processed.| Shipment Field | Kinsey's Field - Notes |
|---|---|
| Carrier | → Carrier. Text value in the shipment header. |
| Method | → Shipping Method. Supplier shipping-method string. |
| Tracking ID | → Tracking ID. Main tracking code; may be blank on some LTL shipments. |
| Carton ID / BOL | → Carton Id / Bol. Use as a fallback when tracking isn't provided. |
| Shipped At | → Ship Date. Mapped to the shipment timestamp. |
| PO Number | → Purchase Order Number. Associates the XML back to the FR / order. |
| Item → SKU | → SKU. Shipment lines associate by SKU. |
| Item → Shipped Qty | → Shipped Quantity. Supports partial shipments. |
| Weight | → Actual/Estimated Weight. Map to shipment weight if present. |
Reads shipment
.xml files matching your Remote File Name Pattern from the Inbound Remote File Folder. Only FRs within the FR Lookback Period (default 90 days) are considered. Partial shipments are supported.Common issues
"The purchase order number sent in with this order already exists in our system. Duplicates are not allowed."
Flxpoint retried a fulfillment request Kinsey's had already accepted - the order processed on the first submission. Check the order timeline to confirm the original FR was accepted, then manually mark the FR as processed in Flxpoint to stop the retries.
Send Fulfillment Request fails - FR never marked as processed
Two common causes: (1)
ShipNode.ShipNode is missing, not two digits, or prefixed with DC - it must be exactly two digits like 01 or 31; and (2) no Ship To Account is set in either the mapping template or the job settings, which fails silently. Set both, then re-run.All Kinsey's products suddenly archived / showing out of stock
Usually Get Inventory (Secondary) stalled mid-run with Archive enabled, so it archived SKUs missing from the incomplete delta. Temporarily enable Archive on Primary to restore items, then investigate the Secondary run log. Never enable Archive on both jobs at once.
"Shipment Sync Error: Could not find Carrier Name for: ground_home_delivery"
Kinsey's returns carrier strings like
ground_home_delivery (FedEx Home Delivery) that don't auto-map. Add a shipping-carrier mapping in your source settings that maps ground_home_delivery to FedEx Ground or FedEx Home Delivery, matching your channel's expected carrier value.Tracking not updating on the channel after Kinsey's ships
On some LTL and flat-rate shipments the tracking ID isn't populated in the shipment XML. Map Carton ID or BOL as a fallback tracking reference in Get Shipments, and verify the Remote File Name Pattern and Inbound Folder match where Kinsey's deposits shipment files.
Items priced below cost / wrong cost after a pricing update
Cost refreshes on the Get Inventory (Secondary) schedule. If an order was placed before the next Secondary run, the old cost was used. Run Secondary hourly and confirm the price CSV maps column CI to Dealer Cost and AF to MSRP; if on FTP and costs are still wrong, confirm with Kinsey's that your pricing file hasn't been renamed or moved.
FAQs
Why are some Kinsey's items showing $0 or blank cost?▸
Cost comes from Kinsey's API - FTP is no longer offered as a connection option. If cost imports as $0, confirm your Kinsey's connection is using a valid API Key and reconfirm it with Kinsey's.
Why are UPC values blank on imported products?▸
Open your Get Inventory (Primary) mapping template and confirm the UPC (T) field maps to Product: Barcode, not to any Inventory API field. Note that not all Kinsey's products include a barcode in the Products API - those items always import with a blank UPC.
Do I need separate connection credentials for each operation?▸
No. One Kinsey's connection is reused across every operation - Get Inventory (Primary), Get Inventory (Secondary), Send Fulfillment Requests, Get Shipments, and the invoice/image jobs. Create it once in Get Inventory (Primary) and select it in each subsequent operation.
How should I handle shipping methods for Kinsey's flat-rate shipping?▸
For most Kinsey's accounts, don't configure a Source Shipping Method in the wizard - Kinsey's picks the carrier and service on their side when they receive the fulfillment request. If orders go on hold for a missing shipping method, leave the fields empty or use a dash. Only configure one if your Kinsey's rep has confirmed your account is set up to receive a shipping method via the API.
How often does Flxpoint's Kinsey's data update?▸
On an API connection, product and inventory data is pulled directly from Kinsey's API at each scheduled run. FTP connections route through Flxpoint's staging database, which typically refreshes weekly - switch to the API connection if you need fresher category or product data.
Can I enable Archive on both Get Inventory Primary and Secondary?▸
No - enable Archive in only one of the two jobs for a given source. Enabling it in both creates conflicts where one job archives items the other just restored, often dropping large numbers of products to zero quantity.