• Import the full Kinseys catalog with core details (brand, title/description, categories, images, weight).
• Update dealer pricing and MSRP/Retail when available to your account.
• Keep on-hand quantities current by warehouse; sum when multiple locations are selected.

• 1Choose Connection — FTP (Basic Auth) or Kinseys API Token.
• 2Retrieve Data —
  FTP: Reads the latest CSV from your provider’s FTP (you supply folder + file pattern). API: Requests product, price, and qty using Group Code / User ID / Password.
  When API is connected, API price/qty is used; otherwise, FTP is used per your configuration.
• 3Map Fields — Match incoming columns to your Mapping Template.
• 4Persist — Values are saved to the Global Inventory Pool and flow to channels after your next push.

• 1Connect an Integration — Choose Kinseys, then create a connection.
  Connection Type
  • FTP (Basic Auth)
    Fields: Connection Name, FTP Host/Port, FTP User, FTP Password.
    Advanced: File Transfer Mode (Binary), Maintain Constant Connection, Use Unbuffered Private Data Channel (FTPS 534 policy only).
    Tip: Use Test Connection to validate credentials and folder visibility.
  • Kinseys API Token
    Fields: Connection Name, Group Code, User ID, Password.
    Use When: You need dealer pricing and direct price/qty from the API.
• 2Configure Settings
  • Remote File Name Pattern (FTP) — e.g., *.csv or an exact filename.
  • Inbound Remote File Folder (FTP) — e.g., /incoming/products.
  • File Action — set to Read for this job.
  • Warehouses — choose All or specific locations. Selected warehouses are summed for Available Quantity.
  • Archive/Un-Archive Inventory — Optionally archive SKUs missing from the feed and auto-restore when they reappear.
  Recommendation: Avoid enabling Archive on both this job and any secondary import for the same source.
• 3Create a Mapping Template — Start with the recommended fields below and adjust as needed.
• 4Save & Schedule — Run manually or set a schedule (jobs run in UTC).

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.

• Quantity (On-hand) FTP — ftp.sprich.com | user onhand | pass onhand | file sprfull.ezoh.
  This file is typically quantity-only.
• Pricing FTP (Customer-Specific) — Provided by KNS per customer; filename varies.
  Sample: JPR.x12_832_0724.csv  |  Specs: Price File Header List & Descriptions.xlsx.

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.

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.

• 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 → Cost, AF → 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 errors: Re-check host/port/user/pass; try Test Connection. For FTPS 534, toggle “Use Unbuffered Private Data Channel.”
• API credential errors: Confirm Group Code, User ID, Password and endpoint access.
• Missing qty: Ensure the same warehouse selection is used consistently and that the source returns non-zero Quantity.
• Items missing post-run: If Archive is enabled, SKUs absent from the feed are archived until they reappear.

• Create one supplier-ready XML order per eligible Fulfillment Request.
• Deliver the XML to Kinseys via FTP using your outbound folder path.
• Control timing with Hold for X hours and Only Send During Business Hours.

• 1Build XML — The job assembles an order XML using your Mapping Template (header + lines).
• 2Upload — The file is posted to your configured Outbound Remote File Folder on Kinseys’s FTP.
• 3Mark Sent — If the upload returns no error, the order is marked as sent/processed.

• 1Connect an Integration — Choose Kinseys and select your FTP (Basic Auth) connection.
• 2Configure Settings
  • Outbound Remote File Folder * — Remote path where order XML files will be written.
  • Ship To Account Number * — Required header value used by Kinseys to route the shipment.
  • Advanced
    • Hold for X hours — Delay sending for X hours to allow review or edits.
    • Only Send During Business Hours — Restrict transmissions to business hours.
• 3Select a Mapping Template — Pick an existing template (e.g., Send Orders 1) or create a new one.
• 4Save & Schedule — Run now or schedule (jobs run in UTC).

Enable scheduling so orders go out automatically. The status page will show Connected, Configured, and Mapped (e.g., template Send Orders 1). Schedules run in UTC.

• Upload failed? Re-check FTP host/port/user/pass and the outbound path; re-run after fixing.
• Supplier rejected? Validate required fields (PO number, ShipToAccount, SKU, Quantity) are Enabled and present.
• Missing lines? Ensure each item maps an SKU and Quantity and that they’re Enabled.
• Wrong shipping method? Map and Enable the supplier shipping method field (e.g., ParcelZone).

• 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.

• 1Pull XML — Reads files matching your Remote File Name Pattern from the configured Inbound Remote File Folder.
• 2Parse — Extracts carrier, method, tracking, carton/BOL, and line items (SKU & shipped qty) into your mapping template.
• 3Apply Lookback — Only Fulfillment Requests created within the FR Lookback Period are considered (default 90 days).
• 4Save — Posts shipment data back to the order; supports partials.

• 1Connect an Integration — Choose Kinseys and select your FTP (Basic Auth) connection.
• 2Configure Settings
  • Remote File Name Pattern * — Mask for shipment XML files (e.g., kns_shipments_*.xml).
  • Inbound Remote File Folder * — FTP directory to read shipment files from.
  • File Action — Read (leave files) or other actions per your policy.
  • Advanced → FR Lookback Period for Get Shipments — Maximum age of FRs to match (default 90 days).
• 3Define a Mapping Template — Use the recommended fields below.
• 4Save & Schedule — Run manually or schedule (UTC).

• Files are fetched over your configured FTP connection.
• Format is .xml; a sample file is referenced in internal docs.
• If tracking is absent, use Carton ID or BOL and map accordingly.

Enable scheduling to pull shipments automatically. The status page will show Connected, Configured, and Mapped (e.g., template Get Shipments 2). Schedules run in UTC.

Toggle each field to control what is saved to the shipment record. Only fields set to Enable will be imported.

• No shipments found? Confirm file pattern/folder and Lookback window cover targeted FRs.
• Missing tracking? Map Carton ID or BOL as alternates and surface them for customer notifications if needed.
• Lines didn’t attach? Ensure each line includes a mapped SKU and that it’s Enabled.