Flxpoint Knowledge

Contact us

Essendant as Source

Table of Contents

How to Connect Product Operations Order Operations

Essendant is a wholesale distributor of office supplies, janitorial products, industrial goods, and business essentials. As a source in Flxpoint, it enables automated inventory synchronization, order fulfillment, and real-time stock updates, helping retailers efficiently manage their supply chain and streamline operations.

 

How to Connect

Step 1: Log into your Flxpoint account.
Step 2: Navigate to the Sources tab from the left-hand menu.
Step 3: Click + Add Source. Then select Configure Single Source to begin setup.
Step 4: If you see No integrations have been configured yet, click Start Creating Integrations. From the list of Custom Integrations or Standard Integrations, select Essendant.
Step 5: In the New Essendant Connection form, enter:
  • Connection Name (any friendly name)
  • FTP Host (e.g., mft.essendant.com)
  • FTP User (your Essendant FTP username)
  • FTP Password (your Essendant FTP password)
    • Step 6: Click Test Connection to verify your credentials. Then click Save Connection to finalize.
    Step 7: On the Configure Settings screen, specify:
  • Remote FTP Folder or File Name
  • Archive/Un-Archive Inventory (optional)
    • Click Save and Proceed when finished.
    Step 8: Under Define a Mapping Template, select or create your Essendant Mapping Template. Map Essendant’s fields (e.g., SKU, Quantity, Price) to Flxpoint’s corresponding fields. Click Save and Complete.
    Step 9: Your Essendant “Get Inventory” integration is now active. Flxpoint will begin retrieving product data from Essendant on your configured schedule.

     

     

    Product Operations

    The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates.

    Get Inventory (Primary)

    Essendant - Get Inventory [Primary]

    Operation Workflow:

    - FTP Download: The product feed is downloaded using your FTP credentials from the correct folder (e.g., /icaps/), ensuring the file name is mapped properly.
    - Product Files: Essendant may provide multiple product files (e.g., eob_individual_items.zip), each containing data for individual SKUs.
    - Vendor Feed: Additional vendor or sync files (e.g., /xml/SynCartPartsFeed) can be used to supplement or reconcile product data.
    - Partial Data: If your feed only includes certain categories or SKUs, you may need additional feed files from Essendant to get full coverage.
    - File/Folder Consistency: Ensure the folder and file name are not swapped (common setup mistake). If the job fails to download, confirm the folder path and filename match your Essendant FTP settings.

    Operation Details:

    - Custom Fields: Product notes and UNSPSC codes can be mapped to variant custom fields.
    - Variations/Options: Simple products are typically available; advanced variation sets may not be in the feed.
    - Generic Pricing & Currency: Supported; you can map cost or list price if provided.
    - Quantities: Essendant typically provides an available quantity per SKU.
    - Multiple Warehouses: Not supported; Essendant does not provide multi-warehouse data.
    - Images: Some categories may include image links; multiple images may be available for certain SKUs.
    - Categories: Up to three levels of categorization (Category1, Category2, Category3) may be provided.
    - Archive Support: SKUs no longer in the feed can be marked archived in Flxpoint if desired.
    - Limitations: Certain costs might be set as a percentage of MSRP or provided as net cost only.

    After retrieving the feed, Flxpoint will parse and update your inventory records accordingly. Verify that your folder paths, filenames, and field mappings are correct to avoid NullPointerExceptions or missing data errors.

    Mapping Template Overview

    When configuring how Essendant’s product feed maps into your Flxpoint inventory fields, you can choose from several mapping options:

    - Don’t Map: Ignore the field entirely.
    - Set to Empty: Force the field to be blank in Flxpoint.
    - Field: Copy data directly from an Essendant field (e.g., “SKU” → “Parent SKU”).
    - Value: Use a fixed or custom value for all products.
    - Mapping Set: Apply a predefined transformation or list (e.g., mapping your internal brand codes).
    - Rules: Conditional logic to map fields based on criteria (e.g., “If Category1 = ‘Furniture’, then set Type = ‘Office Furniture’”).

    Below are the common fields you’ll see in the Essendant feed, with examples of how you might map them into Flxpoint’s Inventory Parent and Inventory Variant records:


    1. Parent-Level Fields

    Parent SKU → Typically mapped from “SKU” in Essendant Products.
    All Attributes → You can choose “Direct Copy” to pull all attribute data if available.
    All Custom Fields → “Direct Copy” to capture any additional product info Essendant provides.
    All Images → “Direct Copy” if the feed includes image URLs or references.
    All Options → “Don’t Map” if Essendant does not provide advanced variant options, or “Direct Copy” if they do.
    Brand → Often mapped from “Manufacturer” in Essendant Products.
    Category1 / Category2 / Category3 → Mapped from the Essendant category fields, e.g., “Category1” → “Category 1.”
    Description / Title → You may combine “Description” and “ShortDescription” or keep them separate as needed.

    2. Variant-Level Fields

    Master SKU → Often the same as “Parent SKU,” but can differ if you have a separate Master/Child structure.
    SKU → Set to “Don’t Map” if you’re only using the parent SKU, or map to “SKU” if you handle variants separately.
    ASIN → “Direct Copy” if Essendant provides an ASIN-like identifier (usually not the case).
    Allow Backorders / Archived / Bin Location → “Don’t Map” or “Set to Empty” unless you have data for these.
    Cost → Mapped from “Cost” in Essendant if available. If Essendant does not provide cost, you may set a default or “Don’t Map.”
    Dropship Fee → “Field” if Essendant charges a dropship fee and it’s included in the feed, else “Don’t Map.”
    GTIN / UPC → “Field” from “UPC” or “UNSPSC” if you want to store that data in Flxpoint’s GTIN field.
    Height / Length / Width → Essendant may provide these as numeric fields. If you want to store them in Flxpoint, map accordingly.
    MAP / MSRP → Map from Essendant’s “MAP” or “MSRP” fields if provided.
    Quantity → “Don’t Map” at the variant level if you prefer to store quantity at the parent level. Alternatively, “Field” if each variant has a unique quantity.
    Reference Identifier → “Don’t Map” unless you have a second ID you want to track.
    Shipping Cost / Source List Price → Map only if Essendant includes shipping cost or list price in the feed.
    Weight / Weight Unit → If the feed has weight data, you can map it. If you only have approximate data, consider “Option” or a default value.

    The detailed mapping interface (as shown in your snippet) will let you configure each field. Be sure to keep an eye on the “Folder” and “File Name” settings for Essendant’s FTP connection to avoid download failures or missing data. Once configured, Flxpoint will parse and apply these mappings to each item in the feed, ensuring your product catalog is up to date.

    Common Issues & Tips

    - NullPointerException: If you see errors like “Cannot invoke java.io.File.getName() because this.inventoryFeed is null”, verify your FTP folder and file name are correctly entered. This typically occurs when Flxpoint can’t locate the feed.
    - Partial Data: If certain categories or SKUs are missing, check if you need additional Essendant feed files. Some accounts split product data across multiple zips.
    - Mapping Mistakes: If you see fields not populating in Flxpoint, ensure you used the correct mapping (e.g., “SKU” → “Parent SKU”). Also confirm you didn’t accidentally map the file name to the folder path or vice versa.
    - Additional Support: Contact Flxpoint support if you continue to experience issues or if you need help with advanced transformations, mapping sets, or scheduling updates.

     

     
     

    Get Inventory (Secondary)

    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.
     
     


     

    Order Operations

    It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.    

    Send Fulfillment Requests

    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.
     
     

    Get Shipments

    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.
     
     

    Get Fulfillment Acknowledgments

    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.
     
     

    Get Invoices

    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.
     
     

     

     

    Related Articles

    Entrenue as Source

    Entrenue is a wholesale distributor specializing in adult products, boutique plea...

    East Coast News as Source

    East Coast News is a wholesale distributor specializing in adult products, offeri...

    How can I help?