Flxpoint Knowledge

Contact us

Crow Shooting as Source

Table of Contents

How To Connect Product Operations Order Operations 

Crow Shooting is a reliable supplier source, offering a variety of products for seamless integration into your catalog. By connecting Crow Shooting, you gain access to automated inventory updates, accurate stock tracking, and efficient order fulfillment. Setting up this source involves configuring API credentials, mapping product data, and defining inventory rules to ensure smooth operations.

 

How To Connect

📋 Phase 1: Create Crow Shooting Source +
Log into Flxpoint
Go to your Flxpoint dashboard and sign in.
Navigate to Sources
Select Sources from the left-hand menu.
Add New Source
Click + Add Source and choose Crow Shooting.
🔐 Phase 2: Configure Connection +
Select Integration
Under Integrations, click Start Creating Integrations and pick Crow Shooting.
Enter Credentials
Fill in:
  • Connection Name: e.g., "Crow Shooting API"
  • API WSDL URL: https://api.crowshootingsupply.com/asmx/mrx/orderV2.asmx
  • Security Code: Your Crow Shooting security token
  • Feed ID: Choose the correct feed from dropdown
  • Type: e.g., CRSH
  • Connection Type: HTTP or FTP
Tip: Double-check the WSDL URL and security code to avoid failures.
✅ Phase 3: Test & Save +
Validate Connection
Click Test Connection to confirm settings.
Save Integration
Once valid, hit Save Connection. Contact Crow Shooting support if tests fail.

 


Product Operations

Get Inventory (Primary) 

Supported | Crow Shooting

Introduction to Crow Shooting
Welcome to the Crow Shooting (CS) Get Inventory [Primary] integration guide! This integration syncs inventory data from Crow Shooting to your system. It ensures accurate product availability and details. Let’s get started!

The Crow Shooting Get Inventory [Primary] integration enables you to:
  • Sync inventory data from Crow Shooting to your system.
  • Update product details like availability, SKU, and categories.
  • Automate inventory management for firearms and related products.
This ensures your inventory reflects Crow Shooting’s latest stock levels.

The integration follows these steps:
  • 1 Connecting to CS: Establish a connection using FTP credentials to access your Crow Shooting system.
  • 2 Fetching Inventory Data: An FTP pull from the Crow Shooting FTP retrieves product and inventory feeds.
  • 3 Extracting Inventory Details: Extract SKU, availability, and category hierarchy from the FTP response.
  • 4 Mapping Data: Map Crow Shooting fields (e.g., SKU, Product Name) to your system’s fields using a mapping template.
  • 5 Syncing Data: Import the mapped data into your system, updating inventory records.
  • 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep inventory up-to-date.
Note: FTP failures pause the integration and trigger notifications.

Customize the integration with these settings:
  • Sync Frequency: Choose to sync inventory data for products within a specific time frame (e.g., last 24 hours).
  • Archive/Un-Archive Inventory: Enable to mark inventory as "archived" if not in the source feed, or "un-archive" if later added back.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
  • Mapping Template: Define how Crow Shooting fields sync to your system (e.g., SKU to Master SKU).
Note: Enable Archive/Un-Archive if you also sync Get Inventory [Secondary] to avoid discrepancies.

Follow these steps:
  • 1 Add the Integration: Go to Channels > Crow Shooting > Integrations, select “Get Inventory [Primary].”
  • 2 Connect to CS: Use your Crow Shooting FTP credentials (e.g., Host, Username, Password, Feed ID).
  • 3 Configure Settings:
    • Set sync frequency (e.g., last 24 hours).
    • Enable Archive/Un-Archive if needed.
    • Configure scheduling.
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates control which Crow Shooting inventory data is imported into your system.
Interface Overview
  • Screen labeled “Get Inventory [Primary]” at the top; name your template (e.g., “Get Source Products 2”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Crow Shooting fields (left), your system fields (right).
Mapping Options
  • Enable: Send the field (e.g., SKU).
  • Disable: Ignore the field (e.g., Inventory Count).
  • Required Fields: SKU, Availability.
SKU Mapping Requirement
The SKU field must be mapped to ensure proper inventory identification.
  • Required Field: SKU uniquely identifies the inventory item.
  • Error Scenario: Unmapped SKU may cause:
    Invalid request: Missing required field 'SKU' for inventory sync
  • Fix: Go to Channels > Crow Shooting > Templates > Get Inventory [Primary] > Field Mapping, enable SKU, save, and re-run sync.
Recommendation: Always enable SKU and Availability for reliable inventory syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Crow Shooting Inventory
Crow Shooting Field Maps To Example Purpose Status
Availability Availability T Indicates if the product is in stock Enabled
Inventory Count Quantity N/A Number of items in stock Disabled
MSRP MSRP N/A Manufacturer's suggested retail price Disabled
SKU Master SKU CS12345 Uniquely identifies the product Enabled
Crow Shooting Product
Crow Shooting Field Maps To Example Purpose Status
Product Name Title Firearm XYZ Product name for display Enabled
Category Hierarchy Category 1 Firearms > Rifles Organizes products into categories Enabled
UPC UPC 123456789012 Universal product code for identification Enabled
Weight Weight N/A Product weight in pounds Disabled
Practice Mapping
Try enabling/disabling Crow Shooting - SKU:

Be aware of these limitations:
  • FTP Access: Requires a paid Feed ID for full data access; contact Crow Shooting support for pricing tiers.
  • Data Scope: Only fetches data available via the Crow Shooting FTP feed (e.g., no inventory count or pricing).
  • Required Fields: SKU and Availability must be enabled.

Troubleshoot issues with these steps:
  • Connection Issues: Verify FTP credentials and connectivity to Crow Shooting.
  • FTP Errors: Ensure the Crow Shooting FTP server is accessible.
  • Missing Data: Check mapping template for enabled fields (e.g., SKU, Availability).
  • Feed ID Issues: Confirm your Feed ID is active; contact Crow Shooting support if needed.
  • Contact Support: Reach out to Crow Shooting support with error details.
Diagnostic Tip: Missing inventory data often results from disabled required fields.

Key information:
  • Date: As of 12:15 PM -04 on Friday, June 13, 2025, this integration is operational.
  • Required Fields: SKU and Availability must be enabled.
  • FTP Access: Monitor to avoid sync interruptions due to Feed ID issues.
Pro Tip: Enable all required fields to ensure accurate inventory syncing.

Conclusion
The Crow Shooting Get Inventory [Primary] integration automates inventory syncing, ensuring your system reflects accurate product details. Customize mappings and schedules to fit your workflow, streamlining inventory management. Happy syncing!
 
 

Get Inventory (Secondary) 

Supported | Crow Shooting

Introduction to Crow Shooting
Welcome to the Crow Shooting (CS) Get Inventory [Secondary] integration guide! This integration syncs secondary inventory data from Crow Shooting to your system. It ensures accurate pricing and stock levels for variant fields, complementing the Get Inventory [Primary] integration. Let’s get started!

The Crow Shooting Get Inventory [Secondary] integration enables you to:
  • Sync secondary inventory data from Crow Shooting to your system.
  • Update variant fields like SKU, Cost, MAP, MSRP, and Quantity.
  • Complement the Get Inventory [Primary] integration for full inventory coverage.
This ensures your system reflects Crow Shooting’s latest pricing and stock details for variants.

The integration follows these steps:
  • 1 Connecting to CS: Establish a connection using FTP credentials to access your Crow Shooting system.
  • 2 Fetching Inventory Data: An FTP pull from the Crow Shooting FTP retrieves secondary inventory feeds.
  • 3 Extracting Inventory Details: Extract SKU, Cost, MAP, MSRP, and Quantity from the FTP response.
  • 4 Mapping Data: Map Crow Shooting fields (e.g., SKU, Quantity) to your system’s variant fields using a mapping template.
  • 5 Syncing Data: Import the mapped data into your system, updating inventory variant records.
  • 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep variant data up-to-date.
Note: FTP failures pause the integration and trigger notifications.

Customize the integration with these settings:
  • Sync Frequency: Choose to sync inventory data for variants within a specific time frame (e.g., last 24 hours).
  • Archive/Un-Archive Inventory: Enable to mark inventory as "archived" if not in the source feed, or "un-archive" if later added back.
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
  • Mapping Template: Define how Crow Shooting fields sync to your system (e.g., SKU to Inventory Variant SKU).
  • Rules Application: Apply rules to modify incoming values (e.g., set Quantity to 0 if Availability is False).
Note: Use this integration alongside Get Inventory [Primary] to ensure full inventory syncing, especially for product details like Category Hierarchy and UPC.

Follow these steps:
  • 1 Add the Integration: Go to Channels > Crow Shooting > Integrations, select “Get Inventory [Secondary].”
  • 2 Connect to CS: Use your Crow Shooting FTP credentials (e.g., Host, Username, Password, Feed ID).
  • 3 Configure Settings:
    • Set sync frequency (e.g., last 24 hours).
    • Enable Archive/Un-Archive if needed.
    • Configure scheduling.
    • Set up rules for variant fields (e.g., adjust Quantity based on Availability).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates control which Crow Shooting inventory data is imported into your system’s variant fields.
Interface Overview
  • Screen labeled “Get Inventory [Secondary]” at the top; name your template (e.g., “Get Inventory Secondary 1”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Crow Shooting fields (left), your system variant fields (right).
Mapping Options
  • Enable: Send the field (e.g., SKU).
  • Disable: Ignore the field (e.g., MSRP).
  • Required Fields: SKU, Availability.
  • Direct Copy: Copy fields like Cost or MAP directly without modification.
SKU Mapping Requirement
The SKU field must be mapped to ensure proper inventory variant identification.
  • Required Field: SKU uniquely identifies the inventory variant.
  • Error Scenario: Unmapped SKU may cause:
    Invalid request: Missing required field 'SKU' for inventory variant sync
  • Fix: Go to Channels > Crow Shooting > Templates > Get Inventory [Secondary] > Field Mapping, enable SKU, save, and re-run sync.
Recommendation: Always enable SKU and Availability for reliable inventory variant syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Crow Shooting Inventory
Crow Shooting Field Maps To Example Purpose Status
Availability Availability T Indicates if the variant is in stock Enabled
Inventory Count Quantity N/A Number of items in stock Disabled
MSRP MSRP N/A Manufacturer's suggested retail price Disabled
SKU Inventory Variant SKU CS12345-V1 Uniquely identifies the variant Enabled
Cost Cost N/A Cost of the variant Disabled
MAP MAP N/A Minimum advertised price Disabled
Quantity Quantity N/A Stock quantity of the variant Disabled
Whole Sale Price Wholesale Price N/A Wholesale price of the variant Disabled
Rules Example
You can set rules to modify incoming values. For example:
  • Rule: If Availability = False, set Quantity to 0.
  • Action: Modifies the incoming Quantity value to ensure accurate stock representation.
Note: Rules help maintain data consistency, especially for variants with conditional stock updates.
Practice Mapping
Try enabling/disabling Crow Shooting - SKU:

Be aware of these limitations:
  • FTP Access: Requires a paid Feed ID for full data access; contact Crow Shooting support for pricing tiers.
  • Data Scope: Only fetches data available via the Crow Shooting FTP feed (e.g., no pricing or quantity data).
  • Required Fields: SKU and Availability must be enabled.
  • Dependency: Relies on Get Inventory [Primary] for complete product data syncing.

Troubleshoot issues with these steps:
  • Connection Issues: Verify FTP credentials and connectivity to Crow Shooting.
  • FTP Errors: Ensure the Crow Shooting FTP server is accessible.
  • Missing Data: Check mapping template for enabled fields (e.g., SKU, Availability).
  • Feed ID Issues: Confirm your Feed ID is active; contact Crow Shooting support if needed.
  • Contact Support: Reach out to Crow Shooting support with error details.
  • Primary Integration Check: Ensure Get Inventory [Primary] is also set up correctly, as this integration depends on it.
Diagnostic Tip: Missing variant data often results from disabled required fields or issues with the primary integration.

Key information:
  • Date: As of 12:15 PM -04 on Friday, June 13, 2025, this integration is operational.
  • Required Fields: SKU and Availability must be enabled.
  • FTP Access: Monitor to avoid sync interruptions due to Feed ID issues.
  • Complementary Role: Works best when paired with Get Inventory [Primary] for full product and variant syncing.
Pro Tip: Enable all required fields and use rules to ensure accurate variant syncing.

Conclusion
The Crow Shooting Get Inventory [Secondary] integration automates variant syncing, ensuring your system reflects accurate pricing and stock details. Use it alongside Get Inventory [Primary], customize mappings and schedules to fit your workflow, and streamline inventory management. Happy syncing!

 

 
 

 

Order Operations    

Send Fulfillment Requests

Supported | Crow Shooting

Introduction to Crow Shooting
Welcome to the Crow Shooting (CS) Send Fulfillment Requests integration guide! This integration sends purchase orders (fulfillment requests) to Crow Shooting, including billing, shipping, and item details. It ensures seamless order processing and fulfillment. Let’s get started!

The Crow Shooting Send Fulfillment Requests integration enables you to:
  • Send purchase orders to Crow Shooting with billing and shipping details.
  • Include fulfillment request items like SKU, Quantity, and Title.
  • Automate order processing for efficient fulfillment workflows.
This ensures your orders are accurately communicated to Crow Shooting for fulfillment.

The integration follows these steps:
  • 1 Connecting to CS: Establish a connection using FTP credentials to access your Crow Shooting system.
  • 2 Preparing Fulfillment Data: Gather billing, shipping, and purchase order data from your system.
  • 3 Mapping Data: Map your system’s fields (e.g., Billing Address, SKU) to Crow Shooting fields using a mapping template.
  • 4 Sending Fulfillment Requests: An FTP push sends the mapped data to Crow Shooting’s FTP server.
  • 5 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to ensure timely order processing.
Note: FTP failures pause the integration and trigger notifications.

Customize the integration with these settings:
  • Sync Frequency: Choose to sync fulfillment requests within a specific time frame (e.g., last 24 hours).
  • Out of Stock Option: Set actions for out-of-stock items (e.g., Backorder, Cancel, Hold).
  • Scheduling: Run manually or schedule (e.g., daily at 6 AM UTC).
  • Mapping Template: Define how your system’s fields sync to Crow Shooting (e.g., Billing Address to Bill Address1).
  • Rules Application: Apply rules to modify incoming values (e.g., set Last Name to "Unknown" if empty).
Note: Use the Out of Stock Option to manage inventory shortages effectively.

Follow these steps:
  • 1 Add the Integration: Go to Channels > Crow Shooting > Integrations, select “Send Fulfillment Requests.”
  • 2 Connect to CS: Use your Crow Shooting FTP credentials (e.g., Host, Username, Password, Feed ID).
  • 3 Configure Settings:
    • Set sync frequency (e.g., last 24 hours).
    • Choose an Out of Stock Option (e.g., Backorder).
    • Configure scheduling.
    • Set up rules for fields (e.g., handle missing Last Names).
  • 4 Create Mapping Template: Configure field mappings (see Mapping Template Details).
  • 5 Run the Integration: Start with Run Sync or schedule.

Mapping templates control which fulfillment request data is sent to Crow Shooting.
Interface Overview
  • Screen labeled “Send Fulfillment Requests” at the top; name your template (e.g., “Send Purchase Orders 1”).
  • Buttons: Delete, Duplicate, Save Mapping.
  • Columns: Your system fields (left), Crow Shooting fields (right).
Mapping Options
  • Enable: Send the field (e.g., Fulfillment Request Number).
  • Disable: Ignore the field (e.g., Estimated Dropship Fee).
  • Required Fields: Fulfillment Request Number, SKU.
  • Direct Copy: Copy fields like Bill Address1 or Ship To Address1 directly without modification.
Fulfillment Request Number Mapping Requirement
The Fulfillment Request Number field must be mapped to ensure proper order identification.
  • Required Field: Fulfillment Request Number uniquely identifies the purchase order.
  • Error Scenario: Unmapped Fulfillment Request Number may cause:
    Invalid request: Missing required field 'Fulfillment Request Number' for purchase order sync
  • Fix: Go to Channels > Crow Shooting > Templates > Send Fulfillment Requests > Field Mapping, enable Fulfillment Request Number, save, and re-run sync.
Recommendation: Always enable Fulfillment Request Number and SKU for reliable order syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Billing Address
Your System Field Maps To Example Purpose Status
Address Line 1 Bill Address1 123 Main St Primary billing address line Enabled
City Bill City Anytown Billing city Enabled
First Name Bill FirstName John Billing contact first name Enabled
Last Name Bill LastName Doe Billing contact last name Enabled
Postal Code Bill Zip N/A Billing postal code Disabled
Shipping Address
Your System Field Maps To Example Purpose Status
Address Line 1 Ship To Address1 456 Oak Ave Primary shipping address line Enabled
City Ship To City Othertown Shipping city Enabled
First Name Ship To FirstName Jane Shipping contact first name Enabled
Last Name Ship To LastName Smith Shipping contact last name Enabled
Country Ship To Country N/A Shipping country Disabled
Purchase Order
Your System Field Maps To Example Purpose Status
Fulfillment Request Number Purchase Order Number PO12345 Uniquely identifies the purchase order Enabled
Note Comment N/A Additional comments for the order Disabled
Source Shipping Method - Carrier Ship Carrier ID UPS Carrier for shipping Enabled
Purchase Order Item
Your System Field Maps To Example Purpose Status
SKU SKU CS12345 Uniquely identifies the item Enabled
Quantity Quantity 10 Number of items ordered Enabled
Cost Unit Price N/A Price per unit Disabled
Rules Example
You can set rules to modify incoming values. For example:
  • Rule: If Billing Last Name is empty, set to "Unknown".
  • Action: Modifies the incoming Billing Last Name to ensure a valid value.
Note: Rules help maintain data consistency, especially for required fields like names.
Practice Mapping
Try enabling/disabling Fulfillment Request Number:

Be aware of these limitations:
  • FTP Access: Requires a paid Feed ID for full data access; contact Crow Shooting support for pricing tiers.
  • Data Scope: Only sends data specified in the mapping template (e.g., no cost or weight data).
  • Required Fields: Fulfillment Request Number and SKU must be enabled.

Troubleshoot issues with these steps:
  • Connection Issues: Verify FTP credentials and connectivity to Crow Shooting.
  • FTP Errors: Ensure the Crow Shooting FTP server is accessible.
  • Missing Data: Check mapping template for enabled fields (e.g., Fulfillment Request Number, SKU).
  • Feed ID Issues: Confirm your Feed ID is active; contact Crow Shooting support if needed.
  • Contact Support: Reach out to Crow Shooting support with error details.
Diagnostic Tip: Missing order data often results from disabled required fields.

Key information:
  • Date: As of 11:30 AM -04 on Friday, June 13, 2025, this integration is operational.
  • Required Fields: Fulfillment Request Number and SKU must be enabled.
  • FTP Access: Monitor to avoid sync interruptions due to Feed ID issues.
Pro Tip: Enable all required fields and use rules to ensure accurate order syncing.

Conclusion
The Crow Shooting Send Fulfillment Requests integration automates purchase order submission, ensuring accurate communication of billing, shipping, and item details. Customize mappings and schedules to fit your workflow, streamlining order fulfillment. Happy syncing!
 
 

Get Shipments

Supported | Crow Shooting

Release Note — Partial Shipments & Multiple Tracking (Flag-Guarded)
Yes, partial shipments and multiple tracking numbers are supported. Behavior is controlled by the Import Multiple Tracking flag to avoid affecting existing accounts. When enabled, we import shipments for ORDER SHIPPED and for ORDER IN PROCESS when at least one line is fully shipped. Multiple tracking values (TrackingNumber…TrackingNumber10) are saved and displayed together.
Introduction to Crow Shooting Get Shipments Integration
This integration retrieves shipment data from Crow Shooting, including tracking numbers, ship dates, and item details. It keeps your orders updated with the latest shipment events, including partials across multiple packages or waves.

Use Get Shipments to:
  • Import shipments for fully-shipped lines, even when the order is still ORDER IN PROCESS.
  • Capture one or more tracking numbers per order (saved together, comma-separated).
  • Respect cancelled quantities and avoid duplicate imports when jobs re-run.

  • 1 Connect: Use your Crow connection (FTP/API as provisioned).
  • 2 Fetch: We pull order status/shipments and read tracking fields TrackingNumber…TrackingNumber10.
  • 3 Determine Eligibility: We compute shipped quantities and apply status rules (see below).
  • 4 Map & Save: Fields map into your shipment + shipment-items records; tracking values are stored together.
  • 5 Schedule/Run: Run on demand or on a schedule.
Heads-up: The enhanced logic is enabled only when the flag Import Multiple Tracking is ON. Turn it on to use partial shipments + multi-tracking.

Eligibility Rules
  • Statuses we import: ORDER SHIPPED (always) and ORDER IN PROCESS (when lines are fully shipped).
  • Shipped quantity per line: shipped = ordered − (allocated + cancelled). If ordered is missing, we skip that line.
  • Exclude fully cancelled lines: Example: ordered=2, cancelled=2 → excluded.
  • Include partials: Example: ordered=2, cancelled=1, allocated=1 → included (one ships, one cancelled).
Multiple Tracking Numbers

Crow may return multiple tracking values at the order level (TrackingNumber, TrackingNumber02…TrackingNumber10). We store all values and display them as a comma-separated list.

Duplicates & Re-runs

When jobs re-run, we avoid duplicates using a unique combination based on (PO/SKU, shipped_qty, tracking). If the supplier later adds a brand-new tracking for the same line after more quantity ships, we import that instance.

Status & Eligibility Matrix
OrderStatus Example outcome Import?
ORDER SHIPPED All shipped; one or more tracking values Yes
ORDER IN PROCESS Some lines shipped, others pending/held Yes (for fully shipped lines)
ORDER IN PROCESS Line fully cancelled (ordered=cancelled) No (excluded)
Worked Examples (from testing)
Case 1
Eligible in response: ABC-5 (Alloc 0, Ordered 5, Cancel 0), ABC-3 (Alloc 0, Ordered 3, Cancel 0)
Existing saved: ABC-5
Final: Save [ABC-3].
Case 2
Eligible: ABC-5 (0/5/0), BCA-3 (0/3/0)
Existing saved: ABC-5
Final: Save [BCA-3].
Case 3
Eligible: ABC-5 (0/5/0), BCA-3 (0/3/3) (fully cancelled)
Existing saved: ABC-5
Final: Save none (BCA fully cancelled; ABC already saved).

  • Import Multiple Tracking (flag): Turn ON to enable partial-shipment logic and multi-tracking capture.
  • Sync window / frequency: Choose last X hours and schedule as needed.
  • Mapping Template: Map Po Num → FR Number, Sku Id → SKU, Ship Date → Shipped At, Entity URL → Tracking URL.
Tip: Use this together with Get PO Acknowledgements for full visibility across “in process” → shipped.

  • 1 Add the integration: Channels → Crow Shooting → Get Shipments.
  • 2 Connect using your Crow credentials (FTP/API as provided).
  • 3 Toggle Import Multiple Tracking = ON.
  • 4 Create the mapping template (see details below).
  • 5 Run once, then set a schedule.

Interface Overview
  • Screen: Get Shipments → name your template.
  • Actions: Delete, Duplicate, Save Mapping.
  • Layout: Crow fields (left) → Your fields (right).
Recommended Field Mappings
Crow Shipments (header-level)
Crow Field Maps To Example Purpose Status
Po Num Fulfillment Request Number 295225303286-1 Identifies the FR/PO Enabled
Ship Date Shipped At 2025-08-27 Date of shipment Enabled
Tracking Number(s) Tracking Number 684867058853, 684867058842 All tracking values saved, comma-separated Enabled
Entity URL Tracking URL https://www.crowshootingsupply.com/ Carrier/portal tracking URL Enabled
Ship Method Carrier/Method FDX Optional Disabled
Total Amount Shipping Cost — Not used Disabled
Crow Shipment Items (line-level)
Crow Field Maps To Example Purpose Status
Sku Id SKU 254488 Identifies the item Enabled
Quantity Quantity — Derived; shipped qty is calculated server-side Disabled
Po Num & Sku Id should be enabled in all templates for reliable matching.
Practice Mapping
Try toggling Po Num:

  • Flag required: Partial shipments + multi-tracking require Import Multiple Tracking = ON.
  • Order-level tracking: Crow returns tracking at order level; we associate tracking to shipped lines for that import.
  • Missing ordered qty: Lines missing ordered are skipped for shipped-qty calculation.

  • Verify the connection and that Import Multiple Tracking is ON.
  • Check mapping template: Po Num, Sku Id, Ship Date, Entity URL.
  • For missed partials, confirm ordered, allocated, cancelled values in the supplier response.
  • Re-run the job to pick up newly shipped quantities with new tracking.
Diagnostic Tip: If an order looks “Partially Shipped” in app UI after a full cancel on one line, verify the cancel quantities and shipment imports. Fully cancelled lines are excluded by design.

  • Date: As of September 3, 2025, the enhanced logic is live (flag-guarded).
  • Required: Enable Po Num and Sku Id in your mapping.
  • Multiple tracking: Saved as a comma-separated list in the Tracking Number field.

Conclusion
Get Shipments handles partials and multiple tracking values safely. Turn on the flag, map the key fields, and schedule the job to keep orders current as shipments arrive in waves.
 
 

Get Fulfillment Requests Acknowledgements

Supported | Crow Shooting

Release Note — Acknowledgements Scope
Yes, acknowledgements are saved when OrderStatus is ORDER IN PROCESS or ORDER CANCELLED OR UNABLE TO FULFILL. We save one acknowledgement per FR (“one-and-done”); later allocation updates under the same status won’t create another acknowledgement.
Introduction to Crow Shooting — Get Fulfillment Request Acknowledgements
This integration retrieves purchase order acknowledgements and status from Crow so you can track confirmation numbers, cancellations, allocations, and backorders at the line level.

With Get Fulfillment Request Acknowledgements you can:
  • Store the Crow confirmation number for each PO.
  • Record order status and item-level outcomes (allocated, cancelled, backordered, held).
  • Keep the FR timeline current via a scheduled job or manual run.

  • 1 Connect: Select the Crow API WSDL (Prod) and provide the Security Code. Test & Save.
  • 2 Map: Map Crow’s Order Number to the FR Confirmation Number.
  • 3 Run: Execute on demand or schedule.
Note: The job also reads item-level fields like QtyAllocated, QtyCancelled, QtyBO, and QtyHeld to reflect mixed outcomes.

  • 1 Add the integration: Crow Shooting → Get Fulfillment Request Acknowledgements.
  • 2 Connect: choose API WSDL (Prod) + Security Code → Test → Save.
  • 3 Mapping: select or create a template (below).
  • 4 Automate: set Scheduled: Yes on Configure and save.

Interface Overview
  • Screen title: Get Fulfillment Request Acknowledgements → Mapping Templates.
  • Actions: Delete, Duplicate, Save.
  • Layout: From Value (Crow) → To Acknowledgement Field (Flxpoint).
Required Mapping
From Value (Crow) To Field (Flxpoint) Example Why it matters
Crow Order Number Confirmation Number 3001981363 Stores the confirmation identifier tied to the PO/FR.
Tip: You usually only need the Confirmation Number here.

When We Save an Acknowledgement
  • Statuses: We save when ORDER IN PROCESS or ORDER CANCELLED OR UNABLE TO FULFILL.
  • One-and-done: We save one acknowledgement per FR. If later Crow allocates more while status stays ORDER IN PROCESS, we do not save a second acknowledgement.
Line-Level Considerations
  • Allocated lines show QtyAllocated; cancelled lines show QtyCancelled and remain acknowledged as cancelled.
  • Backorders (QtyBO) and held lines (QtyHeld) are reflected but don’t trigger extra acknowledgements.
Examples
Scenario: 2 items on the FR. The job runs while status is ORDER IN PROCESS and only item A is allocated.
Result: We save the acknowledgement (covers the FR). If later item B becomes allocated while status stays ORDER IN PROCESS, we won’t save a second acknowledgement.

Status Meaning
ORDER CANCELLED OR UNABLE TO FULFILL Entire order fully cancelled.
ORDER IN PROCESS Order active; may include partial cancels/allocations.
ORDER RECEIVED - ITEMS ON BACKORDER Items remain on backorder.
ORDER SHIPPED Order shipped (tracking handled by Get Shipments).
ORDER NOT FOUND PO created but status not posted yet.

  • No acknowledgement saved: Verify status is eligible (IN PROCESS or CANCELLED/UNABLE).
  • Duplicate concerns: Remember we store one acknowledgement per FR by design.
  • Mapping issues: Ensure Confirmation Number mapping is present on the template.
  • Scheduling: Confirm the job is Scheduled and saved.

Conclusion
Acknowledgements capture the confirmation number and reflect line-level outcomes while preventing duplicates. Pair this with Get Shipments to cover the full flow from in-process to shipped.
 
 

 

 

 

 

Related Articles

Sports South as a Source

Sports South is a reliable supplier source that offers a wide range of sporting g...

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