Yes, Get Inventory (Primary) for CWR is supported!

The Get Inventory (Primary) integration for CWR enables seamless automation of inventory and pricing updates. This feature pulls product information, warehouse-specific quantities, and detailed product data from a primary source, ensuring your catalog stays accurate and up to date.

Connect Your Integration

1. Establish FTP Connection

• Connection Name: Example: CWR Inventory Connection
• FTP Protocol: FTP
• FTP Host: edi.cwrdistribution.com
• FTP Port: 21
• FTP Username: Provided by Supplier
• FTP Password: Provided by Supplier

Test Connection: Ensure connectivity and authentication are successful before saving.

×

Configure Your Settings

1. File Locations

• Inbound Remote File Folder: /out/inventory.csv and /out/catalog.csv
  • Inventory file provides SKU-level data for stock levels and pricing.
  • Catalog file contains additional product details such as dimensions and images.

2. Archive/Un-Archive Inventory

• Archive: Automatically archive inventory items missing from the latest feed, setting their quantity to 0.
• Un-Archive: Reactivates inventory once re-added to the feed, restoring mapped quantities.
  
  Recommendation: Enable this feature only if not conflicting with other integrations.

Mapping Template

1. Field Mapping

The mapping template translates data from CWR files into your inventory system. Key fields include:

• Parent SKU: Links product variants.
• Title: Product name or title.
• Description: Detailed product description.
• Categories: Includes up to three levels (e.g., Category One, Two, Three).
• Images: Maps product images (large size preferred).
• Dimensions: Length, width, height, weight, and units.
• Pricing: MSRP, MAP, and client-specific pricing tiers.
• Quantity: Warehouse-level stock availability.

2. Custom Rules

Custom mapping rules can be applied to adjust incoming data dynamically:

• Example Rule: Add custom prefixes or suffixes to SKUs for better identification.

Automation Features

1. Scheduled Job Setup

Enable job scheduling to automate inventory retrieval:

• Frequency: Daily, weekly, or custom intervals.
• Run Times: Example schedule: 2:00 AM, 6:00 AM, and 10:00 PM UTC.

2. Notifications

Receive alerts for job completion or errors.

Supported Operations

1. Full Feed Retrieval: Downloads inventory and catalog files for comprehensive updates.
2. Data Parsing: Reads and processes CSV data for SKU-level updates.
3. Multi-Warehouse Support: Aggregates quantities from multiple locations (if applicable).

Operation Workflow

File Retrieval:

• Download the inventory.csv file from /out/inventory.csv.
• Download the catalog.csv file from /out/catalog.csv.

Data Processing:

• Map SKU-level inventory data from inventory.csv.
• Enrich inventory data with product details from catalog.csv.

Update Inventory:

• Save processed data into your inventory system, updating quantities, pricing, and product attributes.

Limitations

• Custom Mapping Restrictions: Mapping templates are pre-configured for standard use cases and cannot be customized directly.
• Multiple Warehouses: Data includes a "Combined" warehouse column by default. Custom configurations may be needed to separate specific warehouse data.
   

Yes, Get Inventory (Secondary) for CWR is supported!

The Get Inventory (Secondary) integration for CWR automates the retrieval of inventory and pricing data from a secondary source. This process ensures that inventory data remains accurate and up to date by leveraging automated file retrieval and mapping.

Connect Your Integration

To begin, establish a connection to the CWR FTP server:

1. Establish FTP Connection

• Connection Name: Example: CWR Inventory Connection
• FTP Protocol: Choose FTP
• FTP Host: edi.cwrdistribution.com
• FTP Port: 21
• FTP Username: Provided by Supplier
• FTP Password: Provided by Supplier

Test Connection: Ensure the connection works before proceeding.

×

Configure Your Settings

1. File Locations

• Inbound Remote File Folder: Location where inventory data files are retrieved. Example: /out/inventory.csv.

2. Archive/Un-Archive Inventory

• Archive: Products not found in the current feed are archived with a quantity of 0.
• Un-Archive: Products re-added to the feed are automatically reactivated with their mapped quantities.
  
  Note: Avoid enabling this feature if it conflicts with existing integrations.

Define a Mapping Template

Mapping Details

The mapping template defines how fields in the inventory file are aligned with your system:

• SKU: Identifies products uniquely.
• Quantity: Specifies stock levels for products.
• Pricing: Supports mapping fields like price, map, and msrp.
• Client Pricing: Allows alignment of specific price tiers for clients.

Custom Rules

You can apply specific mapping rules to adjust data dynamically during import. For instance:

• Example Rule: Add ELC to incoming SKUs for custom identifiers.

Automation Features

1. Scheduled Job Setup

Enable automated inventory retrieval at specified intervals:

• Frequency: Daily, weekly, or custom schedules.
• Run Times: Example: 12:00 AM, 6:00 AM, and 12:00 PM UTC.

2. Notifications

Set up notifications for job success or failure.

Supported Operations

1. Inventory Retrieval: Pulls data from the CWR FTP source.
2. Mapping Template: Translates file data into usable formats for your system.
3. Multi-Warehouse Management: Supports aggregate quantities for multiple warehouse configurations.

Troubleshooting

• File Read Error:
  • Cause: Missing file or incorrect format.
  • Resolution: Verify FTP folder and file structure. Ensure the file aligns with expected headers like sku, qty, price.

Yes, Send Fulfillment Request is supported!

The Send Fulfillment Requests integration with CWR enables seamless automation of order submissions. This integration simplifies the process of fulfilling customer orders by transforming them into a format suitable for CWR and sending them for processing.

How It Works

Order Transformation:

• Orders are converted into a CSV file format with the following structure:
  • Order ID, Quantity, SKU, Name, Street Address, Address 2, City, State, Zip, Country, ShipVia, Comment for CWR, Packing Slip Comment, Signature Required
• Example:
  • For an order with two distinct items:
    • Row 1: Header (column names)
    • Row 2: Item 1 details
    • Row 3: Item 2 details

File Placement:

• Files are saved in the /in directory.
• File Naming Convention: CWR_{source_id}_{poID}.csv.

Automated Submission:

• The system automatically sends files to CWR's FTP for order processing.

Connect Your Integration

To begin, establish a connection:

• Integration Type: Select CWR.
• FTP Connection:
  • Enter the provided FTP credentials.
  • Use the Test Connection button to verify connectivity before proceeding.
    
     

×

Configure Settings

• Hold for X Hours:
  • Set a delay period before orders are sent for processing.
• Business Hours Restriction:
  • Optionally restrict order submissions to CWR’s business hours for faster handling.
    
     

Mapping Template

• Use the default mapping template or create a new one to match your order details with CWR’s requirements.
• Mapped Fields:
  • Order ID: Maps to the Fulfillment Request Number.
  • Quantity: Matches the order item quantity.
  • SKU: Links to the product identifier.
  • Address: Includes fields like Street Address, City, State, Zip, Country.
  • Shipping: Includes ShipVia, Packing Slip Comment, and Signature Required.

Automation Features

• Scheduled Submissions:
  • Automate the sending process at specific times.
• Notifications:
  • Get alerts for successful or failed submissions.

Troubleshooting

1. Error Sending Purchase Order:
   • Check FTP credentials.
   • Verify that all required fields in the mapping template are correctly configured.
2. File Disappearance:
   • Files might disappear shortly after being placed in the /in directory due to successful transmission.

Supported Features

• Fulfillment Request Number: Sent as the Order ID.
• Shipping Selection: Supports sending ShipVia details.
• FR Item Association: Maps SKUs and quantities for accurate fulfillment.

Limitations

• Custom Fields: Not supported.
• Customer Association: Only shipping information is included.
• Auto Acknowledgements: Not supported due to the FTP-based workflow.

Shipping Options for Fulfillment Requests

CWR offers a variety of flat-rate shipping options to streamline your fulfillment process. These options, along with their corresponding costs, transit times, and restrictions, are detailed on their website.

×

For the latest shipping information, please refer to the official CWR Shipping Update. You can use this resource to accurately configure shipping options in your fulfillment requests.

Yes, Get Shipments is supported!

The Get Shipments integration for CWR enables automated retrieval and processing of shipment details, ensuring smooth order fulfillment and accurate shipment tracking. This feature retrieves shipment data from the FTP server, parses it, and updates your system with shipment details linked to fulfillment requests.

Connect Your Integration

1. Establish FTP Connection

• Connection Name: Example: CWR Shipment Connection
• FTP Protocol: FTP
• FTP Host: edi.cwrdistribution.com
• FTP Port: 21
• FTP Username: Provided by Supplier
• FTP Password: Provided by Supplier

Test Connection: Ensure connectivity and authentication are successful before saving the configuration.
 

×

---

Configure Your Settings

1. File Locations

• Inbound Remote File Folder: /out/shipping
  • The shipping folder contains CSV files with shipment details.

2. Shipment Processing

• Group by Customer PO: Groups shipments by the customer PO field to associate shipments with fulfillment requests.
• Group by Tracking Number: Groups multiple shipments for the same order when applicable.
• Map Shipment Data: Links the shipment file fields (e.g., customer PO, tracking number) to the system fields via the mapping template.

---

Mapping Template

1. Field Mapping

The mapping template converts data from the CWR shipment files into your system. Key fields include:

• Customer PO: Matches the fulfillment request (FR#) with the shipment.
• Tracking Number: Enables tracking of the shipment.
• Carrier & Method: Identifies the shipping carrier and method used.
• Quantity: Records the number of items shipped.
• Invoice Information: Captures invoice data, if available.

2. Custom Rules

Custom rules can be applied to dynamically process shipment data:

Example Rule: Automatically link tracking number to order details for better tracking.

---

Automation Features

1. Scheduled Job Setup

Enable job scheduling to automate shipment retrieval:

• Frequency: Daily, weekly, or at custom intervals.
• Run Times: Example schedule: 3:00 AM, 6:00 AM, and 9:00 PM UTC.

2. Notifications

Receive alerts for job completion or errors.

---

Supported Operations

• Shipment Retrieval: Downloads shipment CSV files from the FTP server.
• Data Parsing: Reads and processes CSV data for shipment details.
• Partial Shipments: Supports partial shipments by grouping data.
• Invoice Information: Extracts invoice data from shipment files for reference.

---

Operation Workflow

File Retrieval:

1. Access the /out/shipping folder on the FTP server.
2. Download shipment files in CSV format.

Data Processing:

1. Group data by:
   • Customer PO: Associates shipments with fulfillment requests.
   • Tracking Number: Links multiple shipments for the same order.
2. Map fields (e.g., carrier, tracking number) via the mapping template.

Update System:

1. Save processed data into your system.
2. Update shipment details and link them to orders.

 

Limitations

1. Custom Fields: Mapping templates are pre-configured and do not support custom fields.
2. Multiple Tracking Numbers: Errors may occur if shipment files contain improperly grouped data.
3. Data Associations: Ensure FR# matches customer PO to avoid association errors.