This operation connects to Essendant’s FTP server using your configured credentials and downloads a comprehensive XML (or CSV) product feed. It is the main source of product data, designed to create or update your entire catalog.

Key Details

• File Location & Naming:
  • Files are located in a specific directory on the FTP server.
  • File names may include timestamps or unique identifiers; ensure your system can dynamically locate the latest file.
• Fields Included:
  • Core Attributes: SKU, UPC/UNSPSC, product name, description.
  • Pricing Details: Retail and wholesale pricing.
  • Dimensions & Weight: Available if provided; useful for shipping calculations.
  • Categorization: Categories and subcategories to help organize products.
  • Images: URLs or file references to product images.
• Product Type Limitations:
  • Only simple products are supported—product variations and configurable options are not included.
• Processing Considerations:
  • If duplicate SKUs appear, the system ensures only one product record is created or updated.
  • Errors like “Unique Files” indicate file naming mismatches or folder configuration issues; check your FTP settings.

The secondary feed is designed for incremental updates, focusing on changes to pricing and stock levels. This lighter feed is ideal for frequent synchronization without re-importing every product attribute.

Key Details

• File Location & Structure:
  • Stored on the same FTP server but in a separate directory or with a different naming convention.
  • May be delivered as a delta file, containing only modified records.
• Fields Emphasized:
  • Cost Updates: Current cost and pricing adjustments.
  • Inventory Levels: Updated quantities available for sale.
• Processing Considerations:
  • The system maps these fields to the existing records in your catalog.
  • It’s designed to quickly reflect market changes without the overhead of a full catalog import.

When orders are placed, this operation generates an XML file containing all necessary order details and uploads it to Essendant’s FTP server for fulfillment processing.

Key Details

• File Generation:
  • The file is automatically created with a unique Fulfillment Request Number.
  • It must adhere to Essendant’s XML schema for orders.
• Data Included:
  • Order Header: Order ID, date, and customer reference.
  • Shipping Details: Customer’s name, address, city, state, postal code, and phone number.
  • Line Items: SKU, quantity, price per unit, and any applicable discounts.
  • Shipping Method: Indicates preferred carrier options (e.g., USPS, UPS, FedEx) with specific codes if required.
• Processing Considerations:
  • Once the file is uploaded, Essendant’s system confirms receipt automatically.
  • Errors in data mapping (such as invalid SKUs or missing shipping info) may result in order rejections, so validation on your side is essential.

After processing and shipping orders, Essendant places shipment files on the FTP server. This operation retrieves those files to update your system with shipping status and tracking details.

Key Details

• File Location & Format:
  • Shipment files are located in a dedicated FTP directory.
  • Typically formatted in XML, each file corresponds to one or more orders.
• Shipment Information Provided:
  • Order Identification: Matches back to the original Fulfillment Request.
  • Tracking Data: Includes tracking number, carrier, and shipping method.
  • Shipment Status: Provides a simple shipped/not-shipped flag.
• Processing Considerations:
  • Partial shipments are generally not supported; an order appears only when fully shipped.
  • Ensure your mapping template correctly links tracking information back to the order in your system.

This operation retrieves acknowledgement files from Essendant, confirming the receipt and processing status of each fulfillment request. These acknowledgements ensure that orders have been accepted and are in the queue for shipment.

Key Details

• File Handling:
  • Acknowledgement files are found in a separate FTP directory.
  • They are formatted in XML and may include multiple acknowledgements in one file.
• Fields Included:
  • Fulfillment Request Number: For matching against your sent orders.
  • Acknowledgement Status: Indicates if the order was fully accepted, partially accepted, or rejected.
  • Error Codes/Descriptions: If any issues occurred, detailed error messages are provided.
• Processing Considerations:
  • Your system should log these acknowledgements and trigger alerts for any rejected orders.
  • Partial acknowledgements require manual or automated follow-up.

Essendant generates invoices for fulfilled orders, which are uploaded to the FTP server. This operation downloads and processes these invoices to update your financial records.

Key Details

• File Location & Format:
  • Invoices are stored in a designated FTP directory.
  • Files are formatted in XML, with each invoice potentially covering multiple orders.
• Invoice Content:
  • Line Items: Detailed costs per SKU, including taxes, discounts, and additional fees.
  • Reference Fields: Fulfillment Request Numbers or Order IDs to tie charges back to the orders.
  • Summary Totals: Overall costs, taxes, and shipping charges.
• Processing Considerations:
  • Accurate field mapping is crucial to ensure that financial records in your system align with Essendant’s invoicing.
  • Discrepancies should be flagged for review to reconcile any differences in order totals.