Crow Shooting as a Source

July 17, 2026

Summary

Crow Shooting is a firearms, ammunition, and outdoor sporting goods distributor. Order operations (Send Fulfillment Requests, Get Shipments, Get Fulfillment Request Acknowledgements) connect through a Crow Shooting API using a Security Code and an account WSDL address; Get Inventory (Primary and Secondary) pull product and stock feeds over FTP or HTTP using Feed IDs Crow Shooting issues per account. Get Shipments supports partial shipments and multiple tracking numbers when Import Multiple Tracking is enabled, and Get Fulfillment Request Acknowledgements records one confirmation per order line for in-process and cancelled statuses.

What this integration does

Get Inventory (Primary)

Imports Crow Shooting's full product catalog with pricing and stock.

Get Inventory (Secondary)

Refreshes pricing, MAP, and quantity only, more frequently.

Send Fulfillment Requests

Sends orders to Crow Shooting and submits them for fulfillment.

Get Shipments

Pulls shipment tracking and status back from Crow Shooting.

Get Fulfillment Request Acknowledgements

Confirms which order lines Crow Shooting will fulfill or cancel.

How to connect: credentials you need

Crow Shooting uses two separate connections: one for order operations (Send Fulfillment Requests, Get Shipments, Get Fulfillment Request Acknowledgements) using your API WSDL URL and Security Code, and one for inventory (GIP/GIS) using either FTP (a single Feed ID) or HTTP (a Type code plus three separate feed IDs), as directed by Crow Shooting. Add the source, start configuring each operation, and when Flxpoint prompts you click + New Connection, enter the values Crow Shooting provided, then Test Connection → Save Connection.

Order Operations: Send FR, Get Shipments, Get FR Acknowledgements (API)

Field	What to enter
API WSDL URLRequired	The WSDL endpoint Crow Shooting provides for your account. Used by Send Fulfillment Requests, Get Shipments, and Get Fulfillment Request Acknowledgements.
Security CodeRequired	Your Crow Shooting security token, sent with every order-operation request. Test Connection fails immediately with an invalid Security Code.

Inventory (GIP/GIS): Connection Type: FTP

Field	What to enter
Feed IDRequired	The Feed ID Crow Shooting issues for FTP retrieval. Requires an active paid Crow Shooting subscription: without a valid Feed ID, GIP/GIS return no product or quantity data.

Inventory (GIP/GIS): Connection Type: HTTP

Field	What to enter
TypeRequired	Account type code Crow Shooting assigns (e.g., CRSH). Combines with each Feed ID to build the correct feed request.
Product Feed IDRequired	Feed ID for the product catalog feed (title, description, manufacturer, category, UPC, images).
Inventory Feed IDRequired	Feed ID for the price/quantity feed used by both GIP and GIS.
Attribute Feed IDRequired	Feed ID for the product attributes feed, joined to the catalog by SKU.

Choose FTP or HTTP for inventory as directed by Crow Shooting: FTP needs only the one Feed ID; HTTP needs a Type code plus three separate feed IDs (product, inventory, attribute). Both inventory connection types are independent from the API connection used for Send FR, Get Shipments, and Get Fulfillment Request Acknowledgements. For operation-specific setup and mapping guidance, contact support@flxpoint.com.

Important: read before configuring

Feed ID is required for GIP/GIS: requires a paid subscription from Crow Shooting

GIP and GIS use an FTP pull with a Feed ID provided by Crow Shooting. Feed IDs require a paid subscription: contact Crow Shooting support for pricing tiers and to obtain a Feed ID. Without a valid Feed ID, inventory sync will not retrieve product or quantity data. Keep the Feed ID active to avoid sync interruptions.

Enable Import Multiple Tracking flag for partial shipments and multi-tracking per order

Get Shipments supports partial shipments and returns up to 10 tracking values per order (TrackingNumber through TrackingNumber10). This enhanced logic is flag-guarded: it only activates when Import Multiple Tracking = ON in Get Shipments settings. Without this flag, only the primary tracking number is captured. Enable it to handle Crow's partial-ship workflows correctly.

Get Acknowledgements: one-and-done per FR: saves on ORDER IN PROCESS and ORDER CANCELLED only

Get Fulfillment Request Acknowledgements saves one acknowledgement per FR: subsequent status updates on the same FR do not create additional acknowledgements. Acknowledgements are only saved for ORDER IN PROCESS and ORDER CANCELLED OR UNABLE TO FULFILL statuses. ORDER SHIPPED is handled exclusively by Get Shipments. Configure and schedule both operations for full PO lifecycle visibility.

SKU and Availability are required in both GIP and GIS mapping templates

Both GIP and GIS have two required fields that must be enabled in the mapping template: SKU (maps to Master SKU or Inventory Variant SKU) and Availability. If either is not mapped, the job will fail with a "Missing required field" error. Note that Availability is a text status; the numeric quantity is a separate column called InventoryCount. GIP also imports Product Name, Category Hierarchy, and UPC. GIS imports Cost, MAP, MSRP, Quantity, and Wholesale Price at the variant level.

Operations: fields to know

Get Inventory (Primary)Get Inventory (Secondary)Send Fulfillment RequestsGet ShipmentsGet Fulfillment Request Acknowledgements

Imports Crow Shooting's full product catalog with pricing and stock.

Field	Maps To: Notes
SKU	→ Product / Variant → SKU. Required. Must be enabled in the mapping template or the job fails.
ProductName	→ Product → Title.
ProductDescription	→ Product → Description.
Manufacturer	→ Product → Manufacturer.
CategoryHierarchy	→ Product → Category.
UPC	→ Identifiers → UPC.
Weight	→ Shipping → Weight.
LargeImage	→ Product / Variant → Images. Images are a direct copy.
AttributeName / AttributeValue (separate attribute feed, joined by SKU)	→ Product → Attributes. One row per attribute; several rows can apply to the same SKU.
Availability (from the price/quantity feed, joined by SKU)	→ Inventory → Availability. Required. Must be enabled alongside SKU or the job fails with a missing-required-field error.

Refreshes pricing, MAP, and quantity only, more frequently.

Field	Maps To: Notes
SKU	→ Variant → SKU. Required.
Availability	→ Inventory → Availability. Required. Must be enabled alongside SKU or the job fails. Crow Shooting sends this as a text availability status, not a number, so it is not the field to map for stock levels.
InventoryCount	→ Inventory → Quantity. This is the numeric on-hand count. Map this one, not Availability, when you want quantity.
CurrentPrice	→ Pricing → Cost / Wholesale Price.
RegularPrice	→ Pricing → MSRP.
MapPrice	→ Pricing → MAP. Minimum advertised price.
Full catalog fields	Not included in Secondary: title, category, manufacturer, UPC, images and attributes come from Get Inventory (Primary). Run GIP daily and GIS more frequently for price/quantity accuracy.

Sends orders to Crow Shooting and submits them for fulfillment.

Source Field	Maps To (Crow Shooting): Notes
Fulfillment Request Number	→ PO Number. Tracked at Crow Shooting against the submitted cart/order.
SKU	→ Cart Item → SKU. Required.
Quantity	→ Cart Item → Quantity. Required.
Shipping Address → First Name, Last Name, Address 1, City, State, Postal Code	→ Ship To. Required. All six fields must resolve or the order is rejected before it reaches Crow Shooting.
Billing Address → First Name, Last Name, City, Postal Code	→ Bill To. Required.
Source Shipping Method	→ Ship Carrier ID & Ship Via. Required. Both must resolve to a valid Crow Shooting carrier or the order fails validation.
Payment Type (integration setting, default Credit Card)	Chooses Credit Card or Open Account billing on the submitted order: set once per integration, not per order.

Pulls shipment tracking and status back from Crow Shooting.

Field	Maps To: Notes
Po Num	→ Fulfillment Request Number. Lookup key matching the shipment to your order.
Sku Id	→ Shipment Item → SKU. Required. Matched against your Fulfillment Request line items.
Ship Date	→ Shipment → Shipped At.
Entity URL	→ Shipment → Tracking URL.
Tracking Number(s)	→ Shipment → Tracking Number. Required. Up to 10 values are combined into one field when Import Multiple Tracking is on.
Ship Method	→ Shipment → Ship Method / Carrier.
Shipped quantity (computed: ordered - allocated - cancelled)	→ Shipment Item → Quantity. Required. Lines with zero or negative shipped quantity are skipped.

Confirms which order lines Crow Shooting will fulfill or cancel.

Field	Maps To: Notes
Crow Order Number	→ Confirmation Number. Required. Saved once per Fulfillment Request; later status changes on the same FR don't create a second acknowledgement.

Flxpoint reads Crow Shooting's order status text to decide Acknowledged vs. Cancelled, and matches each acknowledgement line to your Fulfillment Request by SKU automatically: neither is a mapped field.

Common issues

GIP returning no data: missing products or empty inventory

Most GIP failures with Crow Shooting are Feed ID issues: (1) confirm your Feed ID is active: an expired or inactive Feed ID returns no data without an explicit error; (2) verify the Feed ID is entered exactly as provided by Crow Shooting (case-sensitive); (3) confirm with Crow Shooting support that your subscription tier includes the product catalog data you're expecting; (4) verify that both SKU and Availability are enabled in the mapping template. For "Diagnostic Tip": missing inventory data most often results from disabled required fields.

Partial shipments not importing or tracking numbers missing

Partial shipments and multi-tracking require Import Multiple Tracking = ON in Get Shipments settings. If this flag is off, only full shipments with a single primary tracking number are captured. To enable: go to Get Shipments → Configure Settings → toggle Import Multiple Tracking = ON → save. After enabling, re-run Get Shipments to capture any missed partial shipments. For orders where all lines were fully cancelled (ordered == cancelled), they are intentionally excluded: this is expected behavior, not a bug.

Get FR Acknowledgements failing when using Buyer's Item Number?

If your acknowledgment jobs fail when mapping SKU to the Buyer's Item Number, ensure you are using the latest integration logic. A fix is now live that allows the Get Fulfillment Request Acknowledgements job to successfully match order lines using this specific SKU mapping, mirroring the behavior in Get Shipments. If errors persist, verify your mapping template is correctly pointing to the intended SKU field.

Duplicate shipment lines or missing partial shipment data?

The shipment import process now automatically aggregates quantities for identical SKUs instead of creating separate shipment lines. This change ensures that if a single SKU is split across multiple fulfillment records at the source, Flxpoint merges them into a single line item with the combined quantity, preventing duplicate SKU lines and ensuring partial shipments sync correctly.

FAQs

How do I set up the Crow Shooting connection?

Go to Sources → + Add Source and complete the Source Wizard. After saving, go to Integrations → Get Inventory → Start Creating Integrations and select Crow Shooting. Connection fields: Connection Name (e.g., "Crow Shooting API"), API WSDL URL (the WSDL address Crow Shooting provides for your account), Security Code (your Crow Shooting security token), Feed ID (from Crow Shooting), Type (e.g., CRSH), and Connection Type (HTTP or FTP). Click Test Connection, then Save Connection.

How does Get Shipments handle multiple tracking numbers and partial shipments?

When Import Multiple Tracking = ON: Get Shipments imports for ORDER SHIPPED (always) and ORDER IN PROCESS when at least one line is fully shipped. Shipped quantity per line is computed as ordered − (allocated + cancelled). Multiple tracking values (TrackingNumber through TrackingNumber10) are stored as a comma-separated list in the Tracking Number field. Fully cancelled lines (ordered == cancelled) are excluded. Duplicate prevention: a unique combination of PO/SKU + shipped_qty + tracking prevents re-importing existing shipments on job re-runs. Required mapping: Po Num → FR Number, Sku Id → SKU, Ship Date → Shipped At, Entity URL → Tracking URL.

What does Get FR Acknowledgements save and when?

Get Fulfillment Request Acknowledgements retrieves Crow's order confirmation number and status. It saves an acknowledgement when OrderStatus is ORDER IN PROCESS or ORDER CANCELLED OR UNABLE TO FULFILL. It saves one acknowledgement per FR only: if the order later gets more allocations under the same IN PROCESS status, no second acknowledgement is created. Required mapping: Crow Order Number → Confirmation Number. Line-level fields (QtyAllocated, QtyCancelled, QtyBO, QtyHeld) are read for context but don't trigger additional acknowledgements.

What are the required fields for Send FR to Crow Shooting?

Required fields: Fulfillment Request Number → Purchase Order Number (must be enabled; missing this causes order identity failures), SKU → SKU, Quantity → Quantity, complete Billing Address (First Name, Last Name, Address1, City), complete Shipping Address (First Name, Last Name, Address1, City), Source Shipping Method - Carrier → Ship Carrier ID. Optional: Cost, Comment/Note, Country, Postal Code (disabled by default but recommended). Configure Out of Stock Option (Backorder, Cancel, or Hold) in settings. Use Rules for edge cases like empty Billing Last Name.

Back to Firearms & Tactical