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: Creating Your Crow Shooting Source
+
Log into Flxpoint
Log into your Flxpoint account.
Navigate to Sources
Navigate to the Sources tab from the left-hand menu.
Add New Source
Click on + Add Source and follow the prompts.
🔐 Phase 2: Setting Up Crow Shooting Connection
+
Select Crow Shooting Integration
Click on Start Creating Integrations and select Crow Shooting from the available list.
Enter Connection Credentials
On the New Crow Shooting Connection screen, enter the following credentials:
- Connection Name: A custom name for this integration.
- API WSDL URL: Enter the API WSDL URL, e.g., https://api.crowshootingsupply.com/asmx/mrx/orderV2.asmx.
- Security Code: Enter the security code provided by Crow Shooting for authentication.
- Feed ID: Select the appropriate feed from the dropdown list.
- Type: Enter the value as mentioned in the product feed URL (e.g., CRSH).
- Connection Type: Choose between HTTP Connection or FTP as needed.
Tip: Ensure all credentials are entered accurately to avoid connection issues. The API WSDL URL and Security Code are required for sending fulfillment requests and getting shipments.
✅ Phase 3: Finalizing the Integration
+
Test and Save Connection
Click Test Connection to verify, then select Save Connection to complete the setup.
Note: If the connection test fails, double-check your credentials and contact Crow Shooting support if needed.
Product Operations
Crow Shooting provides multiple feeds for products, inventory, and attributes. The primary operation handles the full product data (including images, categories, attributes, flags, etc.), while the secondary operation can be used for inventory-only updates (quantity and price).
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.
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 08:53 PM -04, June 01, 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.
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 08:58 PM -04, June 01, 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
Submits orders to Crow Shooting via SOAP web service and then retrieves shipment data.
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.
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 09:04 PM -04 on Sunday, June 01, 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
Introduction to Crow Shooting
Welcome to the Crow Shooting (CS) Get Shipments integration guide! This integration retrieves shipment data from Crow Shooting, including tracking numbers, shipping addresses, and item details. It ensures your system stays updated with the latest shipment information. Let’s get started!
The Crow Shooting Get Shipments integration enables you to:
- Retrieve shipment data from Crow Shooting, including tracking numbers and shipping dates.
- Sync shipment item details like SKU, Stock Description, and Quantity.
- Keep your system updated with the latest fulfillment status for orders.
The integration follows these steps:
- 1 Connecting to CS: Establish a connection using FTP credentials to access your Crow Shooting system.
- 2 Fetching Shipment Data: An FTP pull from the Crow Shooting FTP retrieves shipment feeds.
- 3 Extracting Shipment Details: Extract Tracking Number, Ship Date, and SKU from the FTP response.
- 4 Mapping Data: Map Crow Shooting fields (e.g., Po Num, Sku Id) to your system’s fields using a mapping template.
- 5 Syncing Data: Import the mapped data into your system, updating shipment records.
- 6 Execution: Run manually with Run Sync or schedule (e.g., daily).
Pro Tip: Schedule regular syncs to keep shipment data up-to-date.
Note: FTP failures pause the integration and trigger notifications.
Customize the integration with these settings:
- Sync Frequency: Choose to sync shipment data within a specific time frame (e.g., last 24 hours).
- 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., Po Num to Fulfillment Request Number).
Note: Use this integration alongside Send Fulfillment Requests to track the full order lifecycle.
Follow these steps:
- 1 Add the Integration: Go to Channels > Crow Shooting > Integrations, select “Get Shipments.”
- 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).
- 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 shipment data is imported into your system.
Interface Overview
- Screen labeled “Get Shipments” at the top; name your template (e.g., “Get Shipments 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Crow Shooting fields (left), your system fields (right).
Mapping Options
- Enable: Send the field (e.g., Tracking Number).
- Disable: Ignore the field (e.g., Total Amount).
- Required Fields: Po Num, Sku Id.
- Direct Copy: Copy fields like Ship To Add 1 directly without modification.
Po Num Mapping Requirement
The Po Num field must be mapped to ensure proper shipment identification.
- Required Field: Po Num uniquely identifies the shipment.
-
Error Scenario: Unmapped Po Num may cause:
Invalid request: Missing required field 'Po Num' for shipment sync
- Fix: Go to Channels > Crow Shooting > Templates > Get Shipments > Field Mapping, enable Po Num, save, and re-run sync.
Recommendation: Always enable Po Num and Sku Id for reliable shipment syncing.
Complete Field Mappings
Below are the fields you can enable for syncing:
Crow Shooting Shipments
| Crow Shooting Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Ship Method | Carrier | N/A | Shipping carrier | Disabled |
| Po Num | Fulfillment Request Number | PO12345 | Uniquely identifies the shipment | Enabled |
| Ship Method | Method | N/A | Shipping method | Disabled |
| Note | Note | N/A | Additional shipment notes | Disabled |
| Ship Date | Shipped At | 2025-06-01 | Date of shipment | Enabled |
| Total Amount | Shipping Cost | N/A | Cost of shipping | Disabled |
| Tracking Number | Tracking Number | 1Z9999W999999999 | Tracking number for shipment | Enabled |
| Entity URL | Tracking URL | https://track.example.com | URL to track shipment | Enabled |
| Ship To Add 1 | Ship To Address 1 | 456 Oak Ave | Primary shipping address line | Enabled |
Crow Shooting Shipment Items
| Crow Shooting Field | Maps To | Example | Purpose | Status |
|---|---|---|---|---|
| Quantity | Quantity | N/A | Number of items shipped | Disabled |
| Sku Id | Sku | CS12345 | Uniquely identifies the item | Enabled |
Practice Mapping
Try enabling/disabling Po Num:
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 quantity or cost data).
- Required Fields: Po Num and Sku Id 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., Po Num, Sku Id).
- 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 shipment data often results from disabled required fields.
Key information:
- Date: As of 09:10 PM -04 on Sunday, June 01, 2025, this integration is operational.
- Required Fields: Po Num and Sku Id must be enabled.
- FTP Access: Monitor to avoid sync interruptions due to Feed ID issues.
Pro Tip: Enable all required fields to ensure accurate shipment syncing.
Conclusion
The Crow Shooting Get Shipments integration automates shipment data retrieval, ensuring your system reflects accurate tracking and fulfillment details. Customize mappings and schedules to fit your workflow, streamlining shipment management. Happy syncing!