Eldorado is a premier dropshipping source that streamlines product sourcing and order fulfillment for online retailers. With a broad catalog of trending products and a reliable logistics network, Eldorado empowers entrepreneurs to scale their businesses efficiently and confidently.
How to connect
Step 1: Log into your Flxpoint account and navigate to the Sources tab.
Step 2: Click on + Add Source (or Configure Single Source) to begin creating a new source for Eldorado.
Step 3: Provide basic source details (e.g., vendor name "Eldorado"), then click Save or Next to continue.
Step 4: Follow the Source Wizard prompts. You may see:
Vendor Setup: Indicate if this source is a vendor (e.g., Eldorado) or an internal warehouse. If vendor, choose whether to enable a Vendor Portal or use integrations.
Assign Vendor: Assign an existing vendor record or create a new one for Eldorado.
Configure Vendor Portal: If you enable a portal, specify which vendor users can access your inventory/fulfillment requests.
Order Fulfillment: Enable/disable this source for fulfilling sales orders, set up auto-processing, and define your inventory commit strategy.
Shipping Cost Estimations: Choose to use Rate Shopping or Estimates via Rules.
Real-Time Estimates: Optionally integrate with a rate-shopping provider (e.g., ShipEngine).
Order Routing Groups: Add this source to any relevant routing group to prioritize order fulfillment.
Shipping Methods: Define your shipping method name, default carrier code, and whether to use rate-shopped codes.
Source Location: Enter the “Ship From” address (street, city, state, country).
Integration Setup: Once these steps are completed, click Done to finalize your source.
Step 5: Under Integrations, select the process you want to configure:
(GIS: Get Inventory [Primary], GIP: Get Inventory [Secondary], Send Fulfillment Requests, or Get Shipments).
If you see "No integrations have been configured for this process yet", click Start Creating Integrations.
Step 6: Configure the connection based on the process:
For GIS or GIP (Get Inventory [Primary/Secondary]):
In the New Eldorado Connection form, use the Account Number and Partner Key fields.
Connection Name – a descriptive name (e.g., "Eldorado Get Inventory").
Account Number – provided by Eldorado.
Partner Key – provided by Eldorado.
Click Test Connection to ensure your credentials are valid.
For Send Fulfillment Requests or Get Shipments:
In the New Eldorado Connection form, enter your FTP credentials:
Connection Name – a unique name (e.g., "Eldorado FTP").
FTP Host – the FTP endpoint provided by Eldorado (e.g., aphrodite.eldorado.net).
FTP Port – typically 21 (or as provided by Eldorado).
FTP Username and FTP Password – your FTP login credentials.
Click Test Connection to ensure your credentials are valid.
Step 7: Once the appropriate credentials are validated, click Save Connection to store these details in Flxpoint.
Step 8: On the Configure Settings screen:
For GIS or GIP: Specify any file/folder paths (if applicable) for retrieving Eldorado’s inventory feed, decide whether to archive older data, and configure shipping/advanced settings as needed.
For Send Fulfillment Requests or Get Shipments: Specify the file/folder paths for order or shipment files, decide whether to archive older data, and configure any shipping or advanced settings as needed.
Click Save and Proceed to continue.
Step 9: Next, select or create your Mapping Template. Map Eldorado’s fields (SKU, quantity, etc.) to the corresponding Flxpoint fields. Click Save and Complete when finished.
Step 10: Your Eldorado integration for the selected process (GIS, GIP, Send Fulfillment Requests, or Get Shipments) is now active. Flxpoint will begin processing data according to your scheduled settings.
×
![]()
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)
Supported | Eldorado - Get Inventory [Primary]
Introduction to Eldorado Get Inventory [Primary] Integration
This guide provides a comprehensive overview of the Eldorado Get Inventory [Primary] integration, designed to help you efficiently source and manage product inventory from Eldorado. Whether you're new to inventory management or an experienced user, this section will walk you through the steps to connect to Eldorado's FTP server, download product feeds, process the data, and integrate it into your system. The goal is to ensure you have accurate and up-to-date inventory data to keep your business running smoothly. Let’s dive into the setup and configuration process.
Purpose of This Integration
The Eldorado Get Inventory [Primary] integration enables you to retrieve and process product inventory data from Eldorado, ensuring your system reflects the latest product details, pricing, and stock levels. This integration:
- Automates the retrieval of product data, including SKUs, descriptions, prices, quantities, and images.
- Processes and combines data from multiple sources to create a unified product record for each SKU.
- Applies business logic to clean data, calculate shipping costs, and determine pricing (e.g., MAP price).
This helps you maintain accurate inventory, streamline operations, and ensure your product listings are up to date. How the Integration Works
The integration follows a structured process to retrieve and process inventory data from Eldorado:
1. Connecting to Data Sources: Establishes connections to Eldorado’s FTP server (e.g.,
aphrodite.eldorado.net) and internal S3 storage for additional files. 2. Downloading Feeds: Downloads multiple files, including product details (
products.xml), inventory (inventory.xml), pricing (products.csv), and more from both FTP and S3. 3. Parsing Data: Reads and interprets the data from each file (XML, CSV, Excel formats) into structured formats for processing.
4. Processing & Combining: For each product in the main file (
products.xml), it extracts details, looks up additional data (e.g., price, quantity, images), applies business logic, and creates a unified EldoradoProduct record. 5. Saving Data: Saves batches of processed product records into your system.
6. Completing Tasks: Updates a list of product images that need further processing (e.g., downloading new images).
Note: You’ll need FTP credentials from Eldorado to access their server. If you don’t have these, contact your support team to assist with setup. Configuration Options
You can customize the integration with the following settings:
- FTP Host: The Eldorado FTP server address (e.g.,
aphrodite.eldorado.net). - FTP Port: Typically set to 21 (default for FTP).
- FTP Username and Password: Credentials provided by Eldorado for FTP access.
- Archive/Un-Archive Inventory: Choose whether to archive inventory not found in the source feed (default: No). Archiving sets the quantity to zero; un-archiving reactivates it with the mapped quantity.
- Scheduling: Set the integration to run manually or on a schedule (e.g., daily at 8 AM UTC).
Setup Instructions
Follow these steps to configure the Eldorado Get Inventory [Primary] integration:
1. Connect the Integration: In your system, navigate to the "Get Inventory [Primary]" section and select "Eldorado." Configure the FTP connection by providing:
- FTP Host:
aphrodite.eldorado.net (or as provided by Eldorado). - FTP Port: Use port 21 (default).
- FTP Username and Password: Enter the credentials provided by Eldorado.
Test the connection to ensure it works, then save it. If you don’t have FTP credentials, contact your support team for assistance. 2. Configure Settings: Adjust the following options as needed:
- Enable or disable Archive/Un-Archive Inventory based on your preference. It’s recommended to disable this if you’re using Eldorado for secondary inventory updates.
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
3. Define a Mapping Template: Create a mapping template to map Eldorado’s product data to your system’s fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Data Sources (Feeds)
The integration downloads and processes the following files:
- products.xml: From Eldorado FTP Server (XML). Contains core product details like SKU, name, description, dimensions, categories, manufacturer, and default image name.
- inventory.xml: From Eldorado FTP Server (XML). Provides current stock quantities for each SKU.
- products.csv: From Eldorado FTP Server (CSV). Contains cost price and MSRP per SKU.
- products_properties.csv: From Eldorado FTP Server (CSV). Contains additional attributes like color, packaging, etc.
- MSP.csv: From Eldorado FTP Server (CSV). Primary source for Minimum Advertised Price (MAP) per SKU.
- Eldorado.xlsx: From Internal S3 Storage (Excel). Contains restrictions and a secondary source for MAP price.
- cachedImages.csv: From Internal S3 Storage (CSV). Stores previously processed image URLs for faster retrieval.
- skuImageName.csv: From Internal S3 Storage (CSV). Maps SKUs to primary image filenames for tracking new images.
Mapping Template Details
A mapping template defines how Eldorado’s product data is mapped to your system’s inventory fields. For example, it determines how Eldorado’s “PRODUCTSMODEL” field maps to your “Parent SKU” field. This section explains how to set up and use a mapping template, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “Eldorado - Get Inventory [Primary]” at the top. You can name your template (e.g., “Eldorado Inventory Mapping 1”).
- There are three buttons: Delete (remove the template), Duplicate (make a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Lists the data fields from Eldorado’s files (e.g., “PRODUCTSMODEL,” “PRODUCTSNAME”).
- Right Column (To Inventory Parent Field): Lists the fields in your system (e.g., “Parent SKU,” “Title”).
Mapping Options For each field, you can choose how to handle the data. Here are the available options, with explanations:
- Don’t Map: Ignore the field. The data won’t be imported into your system (e.g., ignoring “Cost” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Weight” to empty).
- Direct Copy / Field: Copy the data as-is from Eldorado’s file (e.g., copying “PRODUCTSMODEL” to “Parent SKU”).
- Value: Set a specific value of your choice (e.g., setting “Weight Unit” to “pound” for all products).
- Mapping Set: Transform the data using a predefined rule (e.g., converting categories to CamelCase).
- Rules: Apply conditional logic (e.g., “If Weight > 5, set Shipping Cost to $11.50”). This is for advanced users and can be skipped if you’re new.
Available Source Fields The following fields are available from Eldorado’s files for mapping to your system’s inventory fields:
- Product Fields (products.xml): SKU (PRODUCTSMODEL), Title (PRODUCTSNAME), Description (PRODUCTSDESCRIPTION), UPC (ITEMUPC), MPN (ITEMVENDORNUMBER), Weight (PRODUCTSWEIGHT), Height (ITEMHEIGHT), Length (ITEMLENGTH), Width (ITEMDIAMETER), Manufacturer (MANUFACTURERSNAME), Categories (PRODUCTSTYPE), Image (PRODUCTSIMAGE).
- Inventory Fields (inventory.xml): Quantity (QUANTITY).
- Pricing Fields (products.csv): Cost (price), MSRP (msrp).
- Attributes (products_properties.csv): Color (prop_color), Packaging (prop_packaging), Flavor (prop_flavor), etc.
- MAP Price (MSP.csv, Eldorado.xlsx): MAP (map_price or MapPrice).
- Restrictions (Eldorado.xlsx): Restriction.
- Images (cachedImages.csv, products.xml): Image URLs (imageList), Image Filename (PRODUCTSIMAGE).
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations, examples, and suggested mappings:
Parent SKU: The unique identifier for the product.
- Source:
products.xml (PRODUCT > PRODUCTSMODEL). - Example: “ABC123”
- Suggested Mapping: Map to “PRODUCTSMODEL” using “Direct Copy.”
- Reason: This ensures your system can uniquely identify each product.
Title: The product name.
- Source:
products.xml (PRODUCT > PRODUCTSNAME). - Example: “100-Piece Puzzle”
- Suggested Mapping: Map to “PRODUCTSNAME” using “Direct Copy.” Special characters may be removed during processing.
- Reason: Provides the product name for your listings.
Description: The product description.
- Source:
products.xml (PRODUCT > PRODUCTSDESCRIPTION). - Example: “A fun 100-piece puzzle for kids.”
- Suggested Mapping: Map to “PRODUCTSDESCRIPTION” using “Direct Copy.” Special characters may be removed.
- Reason: Adds detailed product information to your listings.
UPC: The Universal Product Code.
- Source:
products.xml (PRODUCT > ITEMUPC). - Example: “012345678905”
- Suggested Mapping: Map to “ITEMUPC” using “Direct Copy.” Removes “null” values if present.
- Reason: Helps identify the product universally.
MPN (Manufacturer Part Number): The manufacturer’s part number.
- Source:
products.xml (PRODUCT > ITEMVENDORNUMBER). - Example: “PZ-100”
- Suggested Mapping: Map to “ITEMVENDORNUMBER” using “Direct Copy.” Removes “null” values.
- Reason: Provides an additional identifier for the product.
Weight: The product weight.
- Source:
products.xml (PRODUCT > PRODUCTSWEIGHT). - Example: “1.5”
- Suggested Mapping: Map to “PRODUCTSWEIGHT” using “Direct Copy.” Converted to a numerical format.
- Reason: Used to calculate shipping costs.
Weight Unit: The unit of measure for the weight.
- Source: Not directly provided; set manually.
- Example: “pound”
- Suggested Mapping: Set to “pound” using “Value.”
- Reason: Standardizes the weight unit for consistency.
Height, Length, Width: The product dimensions.
- Source:
products.xml (ITEMHEIGHT, ITEMLENGTH, ITEMDIAMETER). - Example: “10” (height), “12” (length), “8” (width).
- Suggested Mapping: Map to “ITEMHEIGHT,” “ITEMLENGTH,” and “ITEMDIAMETER” using “Direct Copy.”
- Reason: Provides dimensions for shipping and storage calculations.
Manufacturer: The product manufacturer.
- Source:
products.xml (PRODUCT > MANUFACTURERSNAME). - Example: “Clone A Willy”
- Suggested Mapping: Map to “MANUFACTURERSNAME” using “Direct Copy.” Data is cleaned (e.g., “&” to “&”, “clone-a-willy” to “Clone A Willy”).
- Reason: Identifies the product’s manufacturer.
Category 1, 2, 3: Product categories.
- Source:
products.xml (PRODUCT > PRODUCTSTYPE, 1st, 2nd, 3rd elements). - Example: “Toys” (Category 1), “Puzzles” (Category 2).
- Suggested Mapping: Map to “PRODUCTSTYPE” (1st, 2nd, 3rd elements) using “Direct Copy.” Converts to CamelCase (e.g., “toys” to “Toys”).
- Reason: Organizes products into categories. Category 3 is set only if unique from Category 2.
Quantity: The available stock quantity.
- Source:
inventory.xml (Product > QUANTITY, looked up by MODEL/SKU). - Example: “50”
- Suggested Mapping: Map to “QUANTITY” using “Direct Copy.”
- Reason: Updates your system with current stock levels.
Cost: The product cost price.
- Source:
products.csv (price, looked up by ITEM_NO/SKU). - Example: “15”
- Suggested Mapping: Map to “price” using “Direct Copy.” Errors if not found.
- Reason: Provides the cost for pricing calculations.
MSRP: The manufacturer’s suggested retail price.
- Source:
products.csv (msrp, looked up by ITEM_NO/SKU). - Example: “25”
- Suggested Mapping: Map to “msrp” using “Direct Copy.” Errors if not found.
- Reason: Provides the suggested retail price.
MAP Price (Minimum Advertised Price): The minimum advertised price.
- Source:
MSP.csv (MAP, primary) or Eldorado.xlsx (Map, secondary). - Example: “20”
- Suggested Mapping: Map to “MAP” (MSP.csv) or “Map” (Eldorado.xlsx) using “Direct Copy.” Prioritizes MSP.csv.
- Reason: Ensures compliance with minimum pricing rules.
Restriction: Any shipping or sales restrictions.
- Source:
Eldorado.xlsx (Restriction, looked up by ItemNo/SKU). - Example: “Not for sale in CA”
- Suggested Mapping: Map to “Restriction” using “Direct Copy.”
- Reason: Informs you of any sales or shipping limitations.
Images (List of Image URLs): Product image URLs.
- Source:
cachedImages.csv (imageList) or products.xml (PRODUCTSIMAGE). - Example: “https://www.eldorado.net/images/Xlarge/ABC123.jpg”
- Suggested Mapping: Map to “imageList” or “PRODUCTSIMAGE” using “Direct Copy.” Prioritizes cached images.
- Reason: Provides product images for your listings. New images are flagged for further processing.
Attributes (List of Key-Value Pairs): Additional product attributes.
- Source:
products_properties.csv (prop_color, prop_packaging, etc.). - Example: Key: “Color,” Value: “Blue”
- Suggested Mapping: Map to “prop_color,” “prop_packaging,” etc., using “Direct Copy.” Creates key-value pairs.
- Reason: Adds detailed attributes to enhance product listings.
Shipping Cost: The calculated shipping cost.
- Source:
products.xml (PRODUCTSWEIGHT, used for calculation). - Example: “$9.26” (for weight ≤ 1 lb).
- Suggested Mapping: Map to “PRODUCTSWEIGHT” and use “Rules” to calculate based on weight ranges (see below).
- Reason: Provides accurate shipping costs for each product.
Shipping Cost Calculation Logic The shipping cost is calculated based on the product’s weight using the following rules:
- Weight ≤ 1 lb: $9.26
- Weight > 1 lb to 2 lbs: $10.90
- Weight > 2 lbs to 3 lbs: $10.45
- Weight > 3 lbs to 4 lbs: $10.84
- Weight > 4 lbs to 5 lbs: $11.24
- Weight > 5 lbs: $11.50
- Default (if weight is missing): $9.26
Practice Mapping To understand how mapping works, try mapping the “Weight” field for your inventory:
Image Handling Notes
The integration manages product images as follows:
- Primary Source: Uses image URLs from
cachedImages.csv on S3 to avoid reprocessing. - Fallback: If not found in the cache, uses the image filename from
products.xml (PRODUCTSIMAGE). - Tracking New Images: New image filenames are recorded in
skuImageName.csv on S3 for further processing by a separate image grabber task. - Image Grabber: A separate process downloads images from
https://www.eldorado.net/images/Xlarge/[ImageFilename] and updates the cache. It also probes for additional images (e.g., skua.jpg, skub.jpg). - Throttling: Eldorado limits downloads to about one SKU every 6 seconds. The system processes approximately 19,000 SKUs.
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the FTP connection to
aphrodite.eldorado.net is working and that your credentials are correct. - Ensure all required files (
products.xml, inventory.xml, etc.) are available on the FTP server or S3. - Check your mapping template to ensure fields are correctly matched (e.g., “PRODUCTSMODEL” to “Parent SKU”).
- Confirm that your S3 storage is accessible and contains the necessary files (
cachedImages.csv, Eldorado.xlsx). - If image processing fails, ensure the image grabber task is running and not throttled by Eldorado’s rate limits.
If the issue persists, contact your support team for assistance. Conclusion
With your mapping template configured and the integration running, you can now retrieve and process inventory data from Eldorado seamlessly. Your product listings will stay up to date with accurate details, pricing, and stock levels, ensuring your customers have access to the latest inventory. You’re all set to manage your inventory with ease!
Get Inventory (Secondary)
Supported | Eldorado - Get Inventory [Secondary]
Introduction to Eldorado Get Inventory [Secondary] Integration
This guide provides a detailed overview of the Eldorado Get Inventory [Secondary] integration, designed to help you efficiently update your inventory with secondary data from Eldorado. This integration focuses on retrieving key inventory details such as SKU, quantity, cost, MSRP, and MAP price, ensuring your system reflects the latest stock and pricing information. Whether you're new to inventory management or an experienced user, this section will guide you through the setup, configuration, and mapping process to keep your inventory accurate and up to date. Let’s get started!
Purpose of This Integration
The Eldorado Get Inventory [Secondary] integration enables you to update your inventory with secondary data from Eldorado, focusing on essential fields like stock quantities and pricing. This integration:
- Automates the retrieval of inventory data, including SKUs, quantities, costs, MSRPs, and MAP prices.
- Combines data from multiple sources to create a unified inventory record for each SKU.
- Prioritizes MAP pricing sources to ensure compliance with pricing rules.
This helps you maintain accurate stock levels and pricing, ensuring your business operates smoothly without overstocking or underselling. How the Integration Works
The integration follows a streamlined process to retrieve and process secondary inventory data from Eldorado:
1. Initialization: Connects to Eldorado’s FTP server (e.g.,
aphrodite.eldorado.net) and creates a local temporary directory to store downloaded files. 2. Download Feeds: Downloads the following files:
- A static MAP price file (
Eldorado.xlsx) from an S3 bucket. - The latest inventory file (
inventory.xml), product price file (products.csv), and a dynamic MAP price file (MSP.csv) from the Eldorado FTP server. 3. Parse Data: Reads each downloaded file and converts the data into structured in-memory collections (maps) for easy lookup, using the product SKU as the key.
4. Process & Combine: Iterates through each product in the inventory file (
inventory.xml). For each SKU: - Looks up the corresponding cost and MSRP from
products.csv. - Looks up the MAP price, prioritizing
MSP.csv, then falling back to Eldorado.xlsx if needed. - Combines the SKU, quantity, cost, MSRP, and MAP price into a single
EldoradoProduct data object. - Transforms the
EldoradoProduct object into a standard SourceVariantDto object for your system. 5. Save Data: Collects
Note: You’ll need FTP credentials from Eldorado to access their server. If you don’t have these, contact your support team for assistance. SourceVariantDto objects into batches, saving them periodically (when a batch reaches 500 items) and saving any remaining items at the end. Configuration Options
You can customize the integration with the following settings:
- FTP Host: The Eldorado FTP server address (e.g.,
aphrodite.eldorado.net). - FTP Port: Typically set to 21 (default for FTP).
- FTP Username and Password: Credentials provided by Eldorado for FTP access.
- Archive/Un-Archive Inventory: Choose whether to archive inventory not found in the source feed (default: No). Archiving sets the quantity to zero; un-archiving reactivates it with the mapped quantity.
- Allow Create Variant: Enable this to allow creating variants while running Get Inventory [Secondary] (default: No).
- Scheduling: Set the integration to run manually or on a schedule (e.g., daily at 8 AM UTC).
Setup Instructions
Follow these steps to configure the Eldorado Get Inventory [Secondary] integration:
1. Connect the Integration: In your system, navigate to the "Get Inventory [Secondary]" section and select "Eldorado." Configure the FTP connection by providing:
- FTP Host:
aphrodite.eldorado.net (or as provided by Eldorado). - FTP Port: Use port 21 (default).
- FTP Username and Password: Enter the credentials provided by Eldorado.
Test the connection to ensure it works, then save it. If you don’t have FTP credentials, contact your support team for assistance. 2. Configure Settings: Adjust the following options as needed:
- Enable or disable Archive/Un-Archive Inventory. It’s recommended to disable this for secondary inventory updates to avoid unintended archiving.
- Enable or disable Allow Create Variant based on whether you want to create new variants during this process.
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
3. Define a Mapping Template: Create a mapping template to map Eldorado’s inventory data to your system’s fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Data Sources (Feeds)
The integration downloads and processes the following files:
- inventory.xml: From Eldorado FTP Server (FTP: /exports/xml, XML). Provides the primary list of SKUs and their quantities.
- products.csv: From Eldorado FTP Server (FTP: /exports/full, CSV). Provides SKU, cost (as 'Price'), and MSRP data.
- MSP.csv: From Eldorado FTP Server (FTP: /exports/full, CSV). Primary source for Minimum Advertised Price (MAP) per SKU.
- Eldorado.xlsx: From Internal S3 Storage (S3: dmx-assets-cloudfront/integration-files/eldorado, Excel). Provides a secondary/fallback source for MAP price and potentially other restriction data per SKU.
Mapping Template Details
A mapping template defines how Eldorado’s inventory data is mapped to your system’s inventory variant fields. For example, it determines how Eldorado’s “MODEL” field maps to your “SKU” field. This section explains how to set up and use a mapping template, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “Eldorado - Get Inventory [Secondary]” at the top. You can name your template (e.g., “Eldorado Inventory Secondary Mapping 1”).
- There are three buttons: Delete (remove the template), Duplicate (make a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Lists the data fields from Eldorado’s files (e.g., “MODEL,” “QUANTITY”).
- Right Column (To Inventory Variant Field): Lists the fields in your system (e.g., “SKU,” “Quantity”).
Mapping Options For each field, you can choose how to handle the data. Here are the available options, with explanations:
- Don’t Map: Ignore the field. The data won’t be imported into your system (e.g., ignoring “Cost” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “MAP” to empty).
- Direct Copy / Field: Copy the data as-is from Eldorado’s file (e.g., copying “MODEL” to “SKU”).
- Value: Set a specific value of your choice (e.g., setting “Quantity” to “0” for all products).
- Mapping Set: Transform the data using a predefined rule (e.g., adjusting MAP price based on priority).
- Rules: Apply conditional logic (e.g., “If Quantity < 0, set to 0”). This is for advanced users and can be skipped if you’re new.
Available Source Fields The following fields are available from Eldorado’s files for mapping to your system’s inventory variant fields:
- Inventory Fields (inventory.xml): SKU (MODEL), Quantity (QUANTITY).
- Pricing Fields (products.csv): Cost (Price), MSRP (Msrp).
- MAP Price (MSP.csv, Eldorado.xlsx): MAP (map_price or MapPrice).
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations, examples, and suggested mappings:
SKU: The unique identifier for the product.
- Source:
inventory.xml (PRODUCT > MODEL XML element). - Example: “ABC123”
- Suggested Mapping: Map to “MODEL” using “Direct Copy.” Removes any null/empty values.
- Reason: This ensures your system can uniquely identify each product for inventory updates.
Quantity: The available stock quantity.
- Source:
inventory.xml (PRODUCT > QUANTITY XML element). - Example: “50”
- Suggested Mapping: Map to “QUANTITY” using “Direct Copy.” Cleans text and parses to an integer.
- Reason: Updates your system with current stock levels.
Cost: The product cost price.
- Source:
products.csv (Price column, mapped to ProductPrice.price). - Example: “15”
- Suggested Mapping: Map to “Price” using “Direct Copy.” Skips the product if not found.
- Reason: Provides the cost for pricing calculations.
MSRP: The manufacturer’s suggested retail price.
- Source:
products.csv (Msrp column, mapped to ProductPrice.msrp). - Example: “25”
- Suggested Mapping: Map to “Msrp” using “Direct Copy.” Skips the product if not found.
- Reason: Provides the suggested retail price.
MAP (Minimum Advertised Price): The minimum advertised price.
- Source:
MSP.csv (map_price column, primary) or Eldorado.xlsx (MapPrice column, secondary). - Example: “20”
- Suggested Mapping: Map to “map_price” (MSP.csv) or “MapPrice” (Eldorado.xlsx) using “Direct Copy.” Prioritizes MSP.csv.
- Reason: Ensures compliance with minimum pricing rules. See MAP Price Determination Logic below.
MAP Price Determination Logic The MAP price is determined using data from two sources with the following priority rules:
1. Primary Source Check: Looks up the SKU in
MSP.csv (map_price column). If found, this value is used. 2. Fallback Source Check: If not found in
MSP.csv, looks up the SKU (as ItemNo) in Eldorado.xlsx (MapPrice column). If found, this value is used. 3. No Assignment: If the SKU is not found in either source, the MAP price remains unset (likely null).
Practice Mapping To understand how mapping works, try mapping the “Quantity” field for your inventory:
Carrier and Method Identification Logic (Optional)
If you’re using this integration in conjunction with Eldorado’s shipment tracking (e.g., Get Shipments), the system can optionally identify carriers and shipping methods based on tracking numbers. This logic is not enabled by default but can be implemented upon request. The rules are as follows:
- Tracking Number is 18 digits, starts with "1Z", and has "YW" at the 9th position: Carrier: UPS, Method: SurePost.
- Tracking Number is 18 digits, starts with "1Z", and has "03" at the 9th position: Carrier: UPS, Method: Ground.
- Tracking Number is 18 digits, starts with "1Z" (but doesn’t match above): Carrier: UPS, Method: UPS (General).
- Tracking Number is 22 digits, starts with "9400": Carrier: USPS, Method: First Class.
- Tracking Number is 22 digits, starts with "9405": Carrier: USPS, Method: Priority Mail.
- Tracking Number is 22 digits (but doesn’t start with "9400" or "9405"): Carrier: USPS, Method: USPS (General).
- Tracking Number doesn’t match any rules: Error: Cannot identify the carrier/method.
If you’d like to enable this logic, contact your support team to discuss implementation. Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the FTP connection to
aphrodite.eldorado.net is working and that your credentials are correct. - Ensure all required files (
inventory.xml, products.csv, MSP.csv, Eldorado.xlsx) are available on the FTP server or S3. - Check your mapping template to ensure fields are correctly matched (e.g., “MODEL” to “SKU”).
- Confirm that your S3 storage is accessible and contains the
Eldorado.xlsx file. - If MAP prices are missing, verify that the SKU exists in either
If the issue persists, contact your support team for assistance. MSP.csv or Eldorado.xlsx. Conclusion
With your mapping template configured and the integration running, you can now update your inventory with secondary data from Eldorado seamlessly. Your stock levels, costs, and pricing will stay accurate, ensuring your customers have access to the latest inventory information. You’re all set to manage your secondary inventory with ease!
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
Supported | Eldorado - Send Fulfillment Requests
Introduction to Eldorado Send Fulfillment Requests Integration
This guide provides a detailed overview of the Eldorado Send Fulfillment Requests integration, designed to streamline your order fulfillment process with Eldorado. Whether you're new to order management or an experienced user, this section will walk you through the steps to send purchase orders (POs) or fulfillment requests (FRs) to Eldorado via their API. The goal is to ensure your orders are processed efficiently, keeping your business running smoothly. Let’s get started with the setup and configuration process.
Purpose of This Integration
The Eldorado Send Fulfillment Requests integration allows you to send purchase orders or fulfillment requests to Eldorado, ensuring they can process and ship your orders. This integration:
- Automates the submission of order details, such as product SKUs, quantities, shipping addresses, and shipping methods.
- Uses Eldorado’s API to communicate securely, ensuring accurate and timely order processing.
This helps you manage your supply chain effectively, reducing manual work and minimizing errors. How the Integration Works
The integration follows a structured process to send fulfillment requests to Eldorado:
1. Initiation: Receives a list of internal purchase orders (POs) ready to be sent to Eldorado.
2. Configuration: Initializes the Eldorado API connection using your Account Number and Partner Key, and loads mapping rules for data transformation.
3. Connection Test (Ping): Performs a test call to the Eldorado API to verify connectivity and authentication. If the test fails, the process halts.
4. Order Processing: For each PO:
- Maps the PO data (header, addresses, items) into Eldorado’s required XML format (
XMLInputOrder) using a predefined mapping template. - Enriches the data with required API fields (e.g., Account Number, Partner Key, hardcoded values like "websites" for
enteredByCode and "API" for sourceCode). - Transforms the data into an XML string, removing specific root tags to match Eldorado’s requirements.
- Submits the XML string via an HTTP POST request to Eldorado’s Order API endpoint.
5. Response Handling: Processes the API response:
- If successful, updates the PO with the confirmation number and marks it as sent.
- If failed, logs the error and marks the PO as failed, continuing to the next PO.
6. Acknowledgement: Updates the status of successfully sent POs in your system (e.g., marking them as "Sent").
Note: You’ll need an Account Number and Partner Key from Eldorado to use their API. If you don’t have these, contact your support team for assistance. Configuration Options
You can customize the integration with the following settings:
- Account Number: Your Eldorado account number, provided by Eldorado.
- Partner Key: Your Eldorado partner key, provided by Eldorado.
- Hold for X Hours: Set a delay (in hours) before sending POs/FRs, allowing you to review orders if needed (e.g., 24 hours).
- Send During Business Hours: Enable this to send requests only during business hours, ensuring timely processing.
- Scheduling: Choose to run the integration manually or on a schedule (e.g., daily at 8 AM UTC).
Setup Instructions
Follow these steps to configure the Eldorado Send Fulfillment Requests integration:
1. Connect the Integration: In your system, navigate to the "Send Fulfillment Requests" section and select "Eldorado." Configure the API connection by providing:
- Account Number: Enter your Eldorado account number.
- Partner Key: Enter your Eldorado partner key.
Test the connection to ensure it works, then save it. If you don’t have these credentials, contact your support team for assistance. 2. Configure Settings: Adjust the following options as needed:
- Set a Hold for X Hours delay if you want to review orders before sending (e.g., 24 hours).
- Enable Send During Business Hours to send requests only during business hours.
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
3. Create a Mapping Template: Define a mapping template to match your order data to Eldorado’s required fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Shipping Methods
Eldorado supports various shipping methods, which you can map to your system’s shipping options. While specific shipping codes may vary, common examples include:
- Standard: Typically used for ground shipping.
- Expedited: For faster delivery options.
- 2nd Day: For guaranteed two-day delivery.
Ensure your mapping template includes the appropriate shipping method for each order, using the "Source Shipping Method" fields (e.g., Shipping Code, Method). Mapping Template Details
A mapping template defines how your order data is formatted for Eldorado’s API. For example, it determines whether your “SKU” field matches their expected “Code” field. This section explains how to set up and use a mapping template, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “Eldorado - Send Fulfillment Requests” at the top. You can name your template (e.g., “Eldorado Send FR 1”).
- There are three buttons: Delete (remove the template), Duplicate (make a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Lists the data fields from your system (e.g., “SKU,” “Quantity”).
- Right Column (To Eldorado Purchase Order Field): Lists the fields required by Eldorado (e.g., “Code,” “Quantity”).
Mapping Options For each field, you can choose how to handle the data. Here are the available options, with explanations:
- Don’t Map: Ignore the field. The data won’t be sent to Eldorado (e.g., ignoring “Cost” if not required).
- Set To Empty: Clear the field in the API request, leaving it blank (e.g., setting “Address Line 2” to empty).
- Direct Copy / Field: Copy the data as-is from your system (e.g., copying “SKU” to “Code”).
- Value: Set a specific value of your choice (e.g., setting “Quantity” to “1” for all items).
- Mapping Set: Transform the data using a predefined rule (e.g., mapping your shipping method to Eldorado’s shipping code).
- Rules: Apply conditional logic (e.g., “If Quantity > 100, set to 100”). This is for advanced users and can be skipped if you’re new.
Available Source Fields The following fields are available from your system for mapping to Eldorado’s API requirements:
- Fulfillment Request Fields: Fulfillment Request Number, Purchase Order Id, Generated At, Sent At, Total Cost, Total Weight (lbs), Note.
- Fulfillment Request Item Fields: SKU, Quantity, Cost, MPN, UPC, Title, PO Line Item #, Subtotal.
- Shipping Address Fields: Address Line 1, Address Line 2, City, State, State Code, Postal Code, Country, Country Code, First Name, Last Name, Full Name, Company Name, Email, Phone.
- Billing Address Fields: Same as Shipping Address fields (e.g., Address Line 1, City).
- Source Shipping Method Fields: Carrier, Method, Shipping Code, Description.
Complete Field Mappings Below is a detailed list of key fields you can map to in Eldorado’s API, with explanations, examples, and suggested mappings:
Code: The product’s SKU or item number.
- Source: Fulfillment Request Item > SKU.
- Example: “ABC123”
- Suggested Mapping: Map to “SKU” from Fulfillment Request Item using “Direct Copy.”
- Reason: This ensures Eldorado can identify the product in their system. Must match a valid Eldorado product model.
Quantity: The number of units to order.
- Source: Fulfillment Request Item > Quantity.
- Example: “10”
- Suggested Mapping: Map to “Quantity” from Fulfillment Request Item using “Direct Copy.”
- Reason: This tells Eldorado how many units to ship.
Address Line 1: The customer’s street address.
- Source: Shipping Address > Address Line 1.
- Example: “123 Main St”
- Suggested Mapping: Map to “Address Line 1” from Shipping Address using “Direct Copy.” Not to exceed 30 characters.
- Reason: Provides the primary address for shipping. Use Address Line 2 for additional space if needed.
Zip Code: The customer’s postal code.
- Source: Shipping Address > Postal Code.
- Example: “12345-6789”
- Suggested Mapping: Map to “Postal Code” from Shipping Address using “Direct Copy.” Not to exceed 10 characters (xxxxx-xxxx).
- Reason: Ensures accurate delivery location.
City: The customer’s city.
- Source: Shipping Address > City.
- Example: “New York”
- Suggested Mapping: Map to “City” from Shipping Address using “Direct Copy.”
- Reason: Part of the shipping address for accurate delivery.
State: The customer’s state.
- Source: Shipping Address > State.
- Example: “NY”
- Suggested Mapping: Map to “State” or “State Code” from Shipping Address using “Direct Copy.”
- Reason: Ensures the correct state for shipping.
Country: The customer’s country.
- Source: Shipping Address > Country.
- Example: “US”
- Suggested Mapping: Map to “Country” or “Country Code” from Shipping Address using “Direct Copy.”
- Reason: Specifies the country for international shipping.
Shipping Method: The shipping method for the order.
- Source: Source Shipping Method > Shipping Code or Method.
- Example: “Standard”
- Suggested Mapping: Map to “Shipping Code” or “Method” from Source Shipping Method using “Mapping Set” to match Eldorado’s shipping options.
- Reason: Ensures the correct shipping method is used for the order.
Practice Mapping To understand how mapping works, try mapping the “Quantity” field for your fulfillment request:
Carrier and Method Identification Logic (Optional)
If you’re using this integration with Eldorado’s shipment tracking (e.g., Get Shipments), the system can optionally identify carriers and shipping methods based on tracking numbers. This logic is not enabled by default but can be implemented upon request. The rules are as follows:
- Tracking Number is 18 digits, starts with "1Z", and has "YW" at the 9th position: Carrier: UPS, Method: SurePost.
- Tracking Number is 18 digits, starts with "1Z", and has "03" at the 9th position: Carrier: UPS, Method: Ground.
- Tracking Number is 18 digits, starts with "1Z" (but doesn’t match above): Carrier: UPS, Method: UPS (General).
- Tracking Number is 22 digits, starts with "9400": Carrier: USPS, Method: First Class.
- Tracking Number is 22 digits, starts with "9405": Carrier: USPS, Method: Priority Mail.
- Tracking Number is 22 digits (but doesn’t start with "9400" or "9405"): Carrier: USPS, Method: USPS (General).
- Tracking Number doesn’t match any rules: Error: Cannot identify the carrier/method.
If you’d like to enable this logic, contact your support team to discuss implementation. Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that your Account Number and Partner Key are correct and that the API connection test (ping) succeeds.
- Ensure your mapping template correctly matches fields (e.g., “SKU” to “Code,” “Address Line 1” to “Address Line 1”).
- Check that address fields meet Eldorado’s requirements (e.g., Address Line 1 ≤ 30 characters, Zip Code ≤ 10 characters).
- If a PO fails, review the error message in the logs (e.g., invalid SKU, API connectivity issue) and correct the data.
- Confirm that your scheduling settings (e.g., Hold for X Hours, Send During Business Hours) align with your operational needs.
If the issue persists, contact your support team for assistance. Conclusion
With your mapping template configured and the integration running, you can now send fulfillment requests to Eldorado seamlessly. Your orders will be processed efficiently, ensuring your customers receive their products on time. You’re all set to manage your fulfillment process with ease!
Get Shipments
Supported | Eldorado - Get Shipments
Introduction to Eldorado Get Shipments Integration
This guide provides a comprehensive overview of the Eldorado Get Shipments integration, designed to help you retrieve shipment data from Eldorado and update your system with tracking information. Whether you're new to shipment tracking or an experienced user, this section will walk you through the steps to connect to Eldorado’s API, retrieve shipment details, map the data to your system, and keep your customers informed about their orders. Let’s dive into the setup and configuration process.
Purpose of This Integration
The Eldorado Get Shipments integration enables you to retrieve shipment data from Eldorado, ensuring your system reflects the latest tracking information for orders. This integration:
- Automates the retrieval of shipment details, including tracking numbers, carrier codes, service codes, and shipment dates.
- Maps the retrieved data to your system’s shipment fields, such as Carrier, Method, Tracking Number, and Shipped At.
- Includes logic to identify carriers and shipping methods based on tracking numbers, enhancing tracking accuracy.
This helps you keep your customers updated with accurate shipment information, improving their experience and streamlining your operations. How the Integration Works
The integration follows a structured process to retrieve and process shipment data from Eldorado:
1. Initiation: Connects to Eldorado’s API using your Account Number and Partner Key.
2. Connection Test (Ping): Performs a test call to the Eldorado API to verify connectivity and authentication. If the test fails, the process halts.
3. Retrieve Shipments: Queries Eldorado’s API for shipment data, typically for a specified date range or order IDs.
4. Parse Data: Processes the API response, extracting shipment details such as Carrier Code, Service Code, Tracking Number, and Date Shipment into structured
EldoradoShipment objects. 5. Carrier and Method Identification: Applies logic to identify the carrier and shipping method based on the tracking number (see details below).
6. Map Data: Uses a mapping template to transform
EldoradoShipment objects into your system’s shipment fields (e.g., Carrier, Method, Tracking Number, Shipped At). 7. Save Data: Saves the mapped shipment data into your system, updating the relevant orders with tracking information.
Note: You’ll need an Account Number and Partner Key from Eldorado to access their API. If you don’t have these, contact your support team for assistance. Configuration Options
You can customize the integration with the following settings:
- Account Number: Your Eldorado account number, provided by Eldorado.
- Partner Key: Your Eldorado partner key, provided by Eldorado.
- Scheduling: Set the integration to run manually or on a schedule (e.g., daily at 8 AM UTC).
Note: There are no additional configurations required in Fixpoint for this integration, as indicated in the setup interface. Setup Instructions
Follow these steps to configure the Eldorado Get Shipments integration:
1. Connect the Integration: In your system, navigate to the "Get Shipments" section and select "Eldorado." Configure the API connection by providing:
- Account Number: Enter your Eldorado account number.
- Partner Key: Enter your Eldorado partner key.
Test the connection to ensure it works, then save it. If you don’t have these credentials, contact your support team for assistance. 2. Configure Settings: There are no additional settings to configure for this integration, as noted in the interface. However, you can:
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
3. Define a Mapping Template: Create a mapping template to map Eldorado’s shipment data to your system’s fields. This step is detailed below.
4. Run the Integration: Start the integration manually or let it run on your configured schedule.
Mapping Template Details
A mapping template defines how Eldorado’s shipment data is mapped to your system’s shipment fields. For example, it determines how Eldorado’s “Tracking Number” field maps to your “Tracking Number” field. This section explains how to set up and use a mapping template, with detailed options for each field.
Interface Overview
- The mapping screen is labeled “Eldorado - Get Shipments” at the top. You can name your template (e.g., “Eldorado Get Shipments 1”).
- There are three buttons: Delete (remove the template), Duplicate (make a copy), and Save (save your changes).
- The screen is divided into two columns:
- Left Column (From Value): Lists the data fields from Eldorado’s API response (e.g., “Carrier Code,” “Tracking Number”).
- Right Column (To Shipment Field): Lists the fields in your system (e.g., “Carrier,” “Tracking Number”).
Mapping Options For each field, you can choose how to handle the data. Here are the available options, with explanations:
- Don’t Map: Ignore the field. The data won’t be imported into your system (e.g., ignoring “Service Code” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Method” to empty).
- Direct Copy / Field: Copy the data as-is from Eldorado’s API (e.g., copying “Tracking Number” to “Tracking Number”).
- Value: Set a specific value of your choice (e.g., setting “Carrier” to “UPS” for all shipments).
- Mapping Set: Transform the data using a predefined rule (e.g., mapping “Carrier Code” to a standardized carrier name).
- Rules: Apply conditional logic (e.g., “If Tracking Number starts with ‘1Z’, set Carrier to ‘UPS’”). This is for advanced users and can be skipped if you’re new.
Available Source Fields The following fields are available from Eldorado’s API response for mapping to your system’s shipment fields:
- Eldorado Shipment Fields: Carrier Code (Text), Service Code (Text), Tracking Number (Text), Date Shipment (Date).
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations, examples, and suggested mappings:
Carrier: The carrier used for the shipment.
- Source: Eldorado Shipment > Carrier Code.
- Example: “UPS”
- Suggested Mapping: Map to “Carrier Code” using “Direct Copy” or “Mapping Set” to standardize carrier names (e.g., map to “UPS” based on tracking number logic).
- Reason: Identifies the carrier for tracking purposes. See Carrier and Method Identification Logic below for automatic identification.
Method: The shipping method used for the shipment.
- Source: Eldorado Shipment > Service Code.
- Example: “Ground”
- Suggested Mapping: Map to “Service Code” using “Direct Copy” or “Mapping Set” to standardize methods (e.g., map to “Ground” based on tracking number logic).
- Reason: Specifies the shipping method for customer updates. See Carrier and Method Identification Logic below for automatic identification.
Tracking Number: The tracking number for the shipment.
- Source: Eldorado Shipment > Tracking Number.
- Example: “1Z12345YW67890”
- Suggested Mapping: Map to “Tracking Number” using “Direct Copy.”
- Reason: Provides the tracking number for customer tracking.
Shipped At: The date the shipment was sent.
- Source: Eldorado Shipment > Date Shipment.
- Example: “2025-04-01”
- Suggested Mapping: Map to “Date Shipment” using “Direct Copy.”
- Reason: Updates your system with the shipment date for accurate order tracking.
Carrier and Method Identification Logic The integration includes logic to identify carriers and shipping methods based on tracking numbers, ensuring accurate mapping. The rules are as follows: This logic is automatically applied during the mapping process to enhance the accuracy of the Carrier and Method fields.
- Tracking Number is 18 digits, starts with "1Z", and has "YW" at the 9th position: Carrier: UPS, Method: SurePost.
- Tracking Number is 18 digits, starts with "1Z", and has "03" at the 9th position: Carrier: UPS, Method: Ground.
- Tracking Number is 18 digits, starts with "1Z" (but doesn’t match above): Carrier: UPS, Method: UPS (General).
- Tracking Number is 22 digits, starts with "9400": Carrier: USPS, Method: First Class.
- Tracking Number is 22 digits, starts with "9405": Carrier: USPS, Method: Priority Mail.
- Tracking Number is 22 digits (but doesn’t start with "9400" or "9405"): Carrier: USPS, Method: USPS (General).
- Tracking Number doesn’t match any rules: Error: Cannot identify the carrier/method.
Practice Mapping To understand how mapping works, try mapping the “Tracking Number” field for your shipment:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that your Account Number and Partner Key are correct and that the API connection test (ping) succeeds.
- Ensure your mapping template correctly matches fields (e.g., “Tracking Number” to “Tracking Number,” “Carrier Code” to “Carrier”).
- Check that the tracking number format aligns with the Carrier and Method Identification Logic to avoid errors in carrier/method assignment.
- If no shipment data is retrieved, confirm that there are shipments available for the queried date range or order IDs.
- If the integration fails to run on schedule, verify your scheduling settings (e.g., daily at 8 AM UTC).
If the issue persists, contact your support team for assistance. Conclusion
With your mapping template configured and the integration running, you can now retrieve shipment data from Eldorado seamlessly. Your system will stay updated with the latest tracking information, ensuring your customers are informed about their orders. You’re all set to manage your shipment tracking with ease!