Crow Shooting as a Source
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.
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.
support@flxpoint.com.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. GIP also imports Product Name, Category Hierarchy, and UPC. GIS imports Cost, MAP, MSRP, Quantity, and Wholesale Price at the variant level.
| 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. |
| Field | Maps To — Notes |
|---|---|
| SKU | → Variant → SKU. Required. |
| Availability | → Inventory → Availability. Required. Must be enabled alongside SKU or the job fails. |
| InventoryCount | → Inventory → 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. |
| 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. |
| 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. |
| 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.
How do I set up the Crow Shooting connection?▸
How does Get Shipments handle multiple tracking numbers and partial shipments?▸
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.