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
📋 Phase 1: Creating Your Eldorado Source
+
Step 1: Log into your Flxpoint account
Navigate to the Sources tab in your Flxpoint dashboard.
Step 2: Add Eldorado Source
Click + Add Source (or Configure Single Source) to begin creating a new source for Eldorado.
Step 3: Enter Source Details
Provide basic source details (e.g., vendor name "Eldorado"), then click Save & Next.
⚙️ Phase 2: Source Wizard & Integration Setup
+
Step 4: Follow the Source Wizard
- 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 enabled, specify which vendor users can access your inventory/fulfillment requests.
- Order Fulfillment: Enable or disable this source for fulfilling sales orders, configure 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: Select Integration Process
Under Integrations, choose 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.
🔐 Phase 3: Connection Configuration
+
Step 6: Configure Connection Details
- For GIS/GIP (Get Inventory): In the New Eldorado Connection form, enter:
- Connection Name: e.g., "Eldorado Inventory"
- Feed URL: provided by Eldorado (inventory feed endpoint)
- Click Test Connection to validate
- For Send Fulfillment Requests or Get Shipments: In the New Eldorado Connection form, enter:
- Connection Name: e.g., "Eldorado Orders"
- API Token: provided by Eldorado (Order API)
- Click Test Connection to validate
Step 7: Save Connection
Once your credentials are validated, click Save Connection to store these details in Flxpoint.
Step 8: Configure Integration Settings
- For GIS/GIP: Specify file/folder paths for inventory feeds, choose archive options, and configure shipping/advanced settings as needed.
- For Send Fulfillment/Get Shipments: Specify any required paths for订单 or shipment files (if applicable), choose archive options, and configure shipping/advanced settings as needed.
- Click Save and Proceed to continue.
✅ Phase 4: Mapping & Activation
+
Step 9: Create Mapping Template
- Choose an existing mapping template or create a new one to map Eldorado fields (SKU, quantity, etc.) to Flxpoint fields.
- Configure any transformations (e.g., price markups, quantity adjustments).
Step 10: Activate Integration
Click Save and Complete. Your Eldorado integration is now active and will process data according to your 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)
Supported | Eldorado – Get Inventory [Primary]
Introduction to Eldorado – Get Inventory [Primary]
Welcome to the Eldorado (ELD) Get Inventory [Primary] integration guide! This integration retrieves detailed product data, pricing, and stock levels directly from Eldorado’s FTP server and internal S3 storage so your catalog stays accurate at all times. Let’s get started!
The Eldorado – Get Inventory [Primary] integration enables you to:
- Automate retrieval of product data (SKUs, descriptions, prices, quantities, images).
- Combine data from multiple Eldorado feeds into a single, unified record per SKU.
- Apply business logic to clean data, calculate shipping costs, and respect MAP pricing.
The integration follows these steps:
- 1 Connecting to Data Sources: Use the provided Feed URL to access Eldorado’s inventory feed and internal S3 buckets for supplemental files.
-
2 Downloading Feeds: Retrieve multiple files such as
products.xml
,inventory.xml
,products.csv
, and more. - 3 Parsing Data: Convert XML, CSV, and Excel data into structured formats for processing.
- 4 Mapping Data: Map Eldorado fields (e.g., PRODUCTSMODEL, QUANTITY) to your inventory fields via a template.
- 5 Syncing Data: Save batches of processed records to your system, updating Parent SKU, quantity, pricing, and attributes.
- 6 Execution: Run manually with Run Sync or schedule the job (e.g., daily at 08:00 UTC).
Pro Tip: Schedule the sync during low-traffic hours to avoid rate-limit errors on large catalogs.
Note: Eldorado throttles image downloads to one SKU every ~6 seconds. The sync pauses if limits are exceeded and resumes automatically.
Customize the integration with these settings:
- Feed URL: The URL provided by Eldorado to retrieve the inventory feed.
- Archive / Un-Archive Inventory: Toggle archive of SKUs not found in the feed (recommended: disabled for primary feeds).
- Scheduling: Run manually or schedule (e.g., daily at 08:00 UTC).
- Mapping Template: Define how Eldorado fields map to your inventory.
Note: Disable “Archive Inventory” if Eldorado is also used as a secondary inventory source to avoid zeroing out stock.
Follow these steps:
- 1 Add the Integration: In Flxpoint, go to Sources > Eldorado > Integrations and choose “Get Inventory [Primary]”.
- 2 Connect to Eldorado Feed: Enter the Feed URL provided by Eldorado, then click Test Connection.
-
3 Configure Settings:
- Toggle Archive / Un-Archive Inventory as needed.
- Set a schedule (e.g., daily at 08:00 UTC).
- 4 Create Mapping Template: Map PRODUCTSMODEL → Parent SKU and QUANTITY → Quantity (see Mapping Template Details).
- 5 Run the Integration: Click Run Sync or let the schedule trigger automatically.
Mapping templates control which Eldorado inventory data is imported into Flxpoint.
Interface Overview
- Screen labeled “Eldorado – Get Inventory [Primary]”. Name your template (e.g., “Eldorado Mapping 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Eldorado fields (left) and Flxpoint inventory fields (right).
Mapping Options
- Don't Map: Ignore the field (e.g., Cost if handled elsewhere).
- Set To Empty: Clear the field in Flxpoint.
- Field: Directly map an Eldorado field (e.g., PRODUCTSMODEL → Parent SKU).
- Value: Set a static value (e.g., Weight Unit → “pound”).
- Mapping Set: Apply a predefined mapping set (e.g., convert categories to Title Case).
- Rules: Add conditional logic (e.g., if Weight > 5 lbs, Shipping Cost = $11.50).
- Required Fields: Parent SKU, Quantity.
Parent SKU Mapping Requirement
The Parent SKU field must be mapped to identify each product uniquely.
- Required Field: Parent SKU (PRODUCTSMODEL).
-
Error Scenario:
Invalid request: Missing required field 'Parent SKU' for inventory sync
- Fix: Go to Sources > Eldorado > Templates > Get Inventory [Primary] > Field Mapping, map PRODUCTSMODEL → Parent SKU, save, and re‑run sync.
Recommendation: Always map Parent SKU and Quantity to prevent sync failures.
Complete Field Mappings
Below are common Eldorado fields you can map:
Product Details
Eldorado Field | Maps To | Example | Purpose | Status |
---|---|---|---|---|
PRODUCTSMODEL | Parent SKU | ABC123 | Unique product identifier | Required |
PRODUCTSNAME | Title | 100‑Piece Puzzle | Product name | Optional |
PRODUCTSWEIGHT | Weight | 1.5 | Shipping calculation | Optional |
Inventory & Pricing
Eldorado Field | Maps To | Example | Purpose | Status |
---|---|---|---|---|
QUANTITY | Quantity | 50 | Available stock | Required |
price | Cost | 15.00 | Cost price | Optional |
msrp | MSRP | 25.00 | Suggested retail price | Optional |
Practice Mapping
Try mapping Eldorado – Parent SKU:
Be aware of these limitations:
- FTP Rate Limits: Eldorado may limit concurrent connections; large catalogs can take several hours.
- Image Throttling: One image request per ~6 seconds.
- Required Fields: Parent SKU and Quantity must be mapped.
Troubleshoot issues with these steps:
-
Connection Issues: Verify FTP credentials and connectivity to
aphrodite.eldorado.net
. -
Missing Feeds: Ensure mandatory files (
products.xml
,inventory.xml
) are present. - Unmapped Required Fields: Check mapping template for Parent SKU and Quantity.
- Image Failures: Confirm the image‑grabber task is active and not rate‑limited.
- Contact Support: Reach out with log files if issues persist.
Diagnostic Tip: Most “No inventory found” errors are due to missing QUANTITY mapping.
Key information:
- Date: As of 03:00 PM -04, June 12, 2025, this integration is operational.
- Required Fields: Parent SKU and Quantity.
- FTP Limits: Monitor for rate‑limit warnings in the log.
Pro Tip: Map all optional pricing fields to unlock Flxpoint’s pricing rules.
Conclusion
The Eldorado – Get Inventory [Primary] integration automates inventory retrieval, ensuring your catalog reflects accurate product details, pricing, and stock levels. Customize mappings and schedules to fit your workflow, and keep your storefront up to date. Happy syncing!
Get Inventory (Secondary)
Supported | Eldorado – Get Inventory [Secondary]
Introduction to Eldorado Get Inventory [Secondary] Integration
This guide explains how to update your catalog with secondary data from Eldorado. The integration focuses on core inventory fields—SKU, quantity, cost, MSRP, and MAP—so your listings always reflect the latest stock and pricing.
The Eldorado Get Inventory [Secondary] integration enables you to:
- Pull SKUs, quantities, costs, MSRPs, and MAP prices automatically.
- Merge multiple data feeds into a single, reliable inventory record for every SKU.
- Apply MAP‑price priority rules (MSP.csv first, Eldorado.xlsx second) for compliance.
The process runs in five stages:
- 1Initialization: Connect to the provided Feed URL and create a temp folder for downloads.
-
2Download feeds: Retrieve
inventory.xml
,products.csv
,MSP.csv
(FTP) and the staticEldorado.xlsx
(S3). - 3Parse data: Load each file into in-memory maps keyed by SKU.
-
4Process & combine: For every SKU in
inventory.xml
:- Look up quantity (
inventory.xml
). - Fetch cost/MSRP (
products.csv
). - Determine MAP price (prefer
MSP.csv
, otherwiseEldorado.xlsx
). - Create an
EldoradoProduct
, convert toSourceVariantDto
.
- Look up quantity (
- 5Save: Batch 500 variants per insert, then save any remaining records.
Tip: Schedule the job daily at 08:00 UTC so cost and MAP changes flow in automatically.
Fine-tune the run with these settings:
- Feed URL: The URL provided by Eldorado to retrieve the inventory feed.
- Archive/Un-Archive Inventory: If enabled, SKUs missing from the feed are zeroed out. (Default: No)
- Allow Create Variant: Create new SKUs on-the-fly during secondary runs. (Default: No)
- Scheduling: Manual or automatic (e.g., every day at 08:00 UTC).
Note: Keep Archive/Un-Archive disabled to prevent accidental stockouts when running Secondary alongside Primary.
Step-by-step:
- 1Add the Integration: Channels ▸ Eldorado ▸ Get Inventory [Secondary].
- 2Connect Feed: Enter the Feed URL provided by Eldorado. Test and save.
- 3Configure settings: Toggle Archive/Un-Archive and Allow Create Variant, set a schedule.
- 4Create a mapping template: Map MODEL → SKU, QUANTITY → Quantity, Price → Cost, Msrp → MSRP, map_price → MAP.
- 5Run or schedule: Click Run Sync or wait for the next scheduled run.
Mapping controls which Eldorado fields sync to your variant records.
Interface Overview
- Template title at top — name it "Eldorado Inventory Secondary Mapping 1" (or similar).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Eldorado source fields (left) → Your variant fields (right).
Mapping Options
- Don't Map: Skip a source field entirely.
- Set To Empty: Clear the destination field.
- Field: Direct copy from Eldorado (e.g., MODEL → SKU).
- Value: Set a constant (e.g., Quantity = 0).
- Mapping Set: Transform (e.g., MAP adjustments).
- Rules: Add conditional logic (e.g., if Quantity < 0 then 0).
Key Field Mappings
Eldorado Field | Maps To | Example | Purpose | Status |
---|---|---|---|---|
MODEL | SKU | ABC123 | Primary identifier | Required |
QUANTITY | Quantity | 50 | Current stock | Required |
Price | Cost | 15 | Unit cost | Optional |
Msrp | MSRP | 25 | Retail price | Optional |
map_price | MAP | 20 | Minimum advertised | Optional |
Practice Mapping
Try mapping "Quantity":
If you also import Eldorado shipments, we can auto‑detect carrier/method from tracking numbers:
- 18‑digit tracking starting
1Z
withYW
in position 9 → UPS SurePost. - 18‑digit tracking starting
1Z
with03
in position 9 → UPS Ground. - Other
1Z
numbers → UPS (general). - 22‑digit starting
9400
→ USPS First Class. - 22‑digit starting
9405
→ USPS Priority Mail. - Other 22‑digit numbers → USPS (general).
- No match → Error (carrier unknown).
If something fails, check:
- FTP connectivity to
aphrodite.eldorado.net
. - All feeds present:
inventory.xml
,products.csv
,MSP.csv
,Eldorado.xlsx
. - Mapping template: MODEL → SKU etc. correctly mapped.
- S3 bucket access for
Eldorado.xlsx
. - MAP missing? Confirm SKU exists in either MAP file.
Diagnostic Tip: Missing MAP usually means the SKU is absent from both MAP sources.
Conclusion
With the mapping template in place and the job scheduled, your secondary Eldorado inventory stays accurate—even as costs or MAP rules change. Happy syncing!
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
The Eldorado - Send Fulfillment Requests integration automates the process of sending purchase orders (POs) to Eldorado for fulfillment. This integration takes your fulfillment requests from Flxpoint—details like shipping addresses, item quantities, and shipping methods—and maps them to Eldorado’s required purchase order format, then sends them via API. It ensures your orders are accurately communicated to Eldorado, streamlining your dropshipping process. The setup involves connecting to Eldorado’s API, configuring settings, mapping fields, applying custom rules, and sending the requests. Let’s walk through each step to get you started!
The Eldorado - Send Fulfillment Requests integration connects your Flxpoint system to Eldorado to:
- Send purchase orders to Eldorado by converting Flxpoint fulfillment requests into Eldorado’s required format.
- Map Flxpoint fields—like shipping addresses, item details, and shipping methods—to Eldorado’s purchase order fields for accurate order fulfillment.
- Automate the delivery of purchase orders to Eldorado via API, reducing manual effort and ensuring timely order processing.
This integration follows a clear, step-by-step process to send fulfillment requests from Flxpoint to Eldorado:
- Data Extraction: Pulls fulfillment request data from Flxpoint, including shipping addresses, item details (like SKU and quantity), and shipping methods.
- Field Mapping: Maps Flxpoint data to Eldorado’s purchase order fields, such as PO Number, Ship To Address, and Item Number, using a mapping template.
- API Delivery: Sends the formatted purchase order to Eldorado’s API endpoint (e.g., `https://api.eldorado.net/order`) for processing.
What Does the Fulfillment Request Data Look Like?
Let’s take a peek at a sample fulfillment request data structure from Flxpoint. This is what the integration maps and sends to Eldorado:
{
"FulfillmentRequest": {
"FulfillmentRequestNumber": "FR12345",
"GeneratedAt": "2025-06-13T10:35:00Z",
"TotalCost": 250.00,
"Note": "Urgent delivery requested"
},
"ShippingAddress": {
"AddressLine1": "123 Main St",
"AddressLine2": "Apt 4B",
"City": "Austin",
"StateCode": "TX",
"PostalCode": "78701",
"FullName": "Jane Doe",
"Phone": "512-555-1234"
},
"FulfillmentRequestItem": {
"SKU": "ELD12345",
"Quantity": 2,
"Cost": 125.00,
"POLineItemNumber": 1
},
"SourceShippingMethod": {
"Carrier": "UPS",
"Method": "Ground",
"ShippingCode": "UPS-GND"
}
}
"FulfillmentRequest": {
"FulfillmentRequestNumber": "FR12345",
"GeneratedAt": "2025-06-13T10:35:00Z",
"TotalCost": 250.00,
"Note": "Urgent delivery requested"
},
"ShippingAddress": {
"AddressLine1": "123 Main St",
"AddressLine2": "Apt 4B",
"City": "Austin",
"StateCode": "TX",
"PostalCode": "78701",
"FullName": "Jane Doe",
"Phone": "512-555-1234"
},
"FulfillmentRequestItem": {
"SKU": "ELD12345",
"Quantity": 2,
"Cost": 125.00,
"POLineItemNumber": 1
},
"SourceShippingMethod": {
"Carrier": "UPS",
"Method": "Ground",
"ShippingCode": "UPS-GND"
}
}
Understanding the Data: This data represents a fulfillment request in Flxpoint. For example,
"FulfillmentRequestNumber": "FR12345"
becomes the PO Number in Eldorado’s system, and "ShippingAddress"
fields like Address Line 1 and City are mapped to Eldorado’s Ship To fields. The integration ensures all necessary details are sent to Eldorado for fulfillment.
Let’s set up the integration by customizing a few key settings to match your needs:
-
API Connection Settings:
- Connection Name: Give your connection a name, like "EldoradoAPI_Fulfillment".
- API Token: Enter the API token provided by Eldorado.
- Test Connection: Click the Test Connection button to verify it works.
- Hold for X Hours: Delay submission (e.g., 24 h) for QA or fraud screening.
- Send During Business Hours: Restrict API calls to 09:00-17:00 in your warehouse timezone.
- Scheduling: Manual or scheduled (e.g., every hour or daily at 08:00 UTC).
What’s the API Token? The API Token is your secure key to authenticate with Eldorado’s API. Keep it confidential and test the connection to ensure it’s valid.
Scheduling Tip: Scheduling during off-peak hours can help avoid rate limits.
Scheduling Tip: Scheduling during off-peak hours can help avoid rate limits.
Follow these steps to get the Eldorado - Send Fulfillment Requests integration up and running:
- 1 Establish API Connection: Enter the API token provided by Eldorado (Connection Name, API Token). Click the Test Connection button to verify it works, then save.
- 2 Configure Advanced Settings (Optional): Enable "Hold for X Hours" if you need a delay for QA or fraud screening.
- 3 Set Business Hours (Optional): Toggle "Send During Business Hours" to restrict API calls to 09:00-17:00 in your timezone.
- 4 Create a Mapping Template: Head to the Mapping Dashboard ("Eldorado - Send Fulfillment Requests") to define how Flxpoint fields map to Eldorado’s purchase order fields (see the "Mapping Template" section below).
- 5 Configure Mapping Rules (Optional): Set up custom rules to transform data during mapping if needed (see the "Mapping Rules" section below).
- 6 Send the Fulfillment Requests: Click to send the requests manually, or set up a schedule for automatic sending.
The integration setup interface for “Eldorado - Send Fulfillment Requests” is where you begin connecting Eldorado to your Flxpoint system. Let’s explore what you’ll see and interact with when setting up this connection:
- Integration Title: At the top, you’ll see the integration name, “Eldorado - Send Fulfillment Requests,” clearly labeled to indicate which integration you’re configuring.
-
API Connection Settings Section: This section contains a form with fields to input your API credentials:
- Connection Name: A text field where you can name your connection.
- API Token: A text field to enter the token provided by Eldorado.
- Test Connection: A button to verify that your API token works and the connection to Eldorado’s server is successful.
-
Advanced Settings Section: This section includes optional fields:
- Hold for X Hours: A field to set a delay for QA or fraud screening.
- Send During Business Hours: A toggle to restrict API calls to business hours.
- Scheduling: Options for manual or scheduled sending.
-
Action Buttons: At the bottom, you’ll find buttons to manage your setup:
- Test Connection: A button to verify the API connection.
- Save: A button to save your configuration settings.
Next Steps
Once you’ve set up the integration connection, you’ll move on to defining how Flxpoint data maps to Eldorado’s purchase order fields in the "Mapping Template" section below.
The Mapping Template is where you define how Flxpoint’s fulfillment request data maps to Eldorado’s purchase order fields. This ensures Eldorado receives the order details in the format they expect, like shipping addresses and item quantities. Let’s break it down!
Mapping Fields
Below is a table of key fields you can map, complete with examples and purposes. The labels (T for text, N for numbers, D for dates) match what you’ll see in the dashboard:
Field | Maps To | Example | Purpose | Status |
---|---|---|---|---|
Fulfillment Request Number (T) | Eldorado PO: PO Number | FR12345 | Identifies the purchase order in Eldorado’s system | Required |
Shipping Address: Address Line 1 (T) | Eldorado PO: Ship To Address1 | 123 Main St | Specifies the primary address line for shipping | Required |
Shipping Address: Address Line 2 (T) | Eldorado PO: Ship To Address2 | Apt 4B | Provides additional address details (e.g., apartment number) | Optional |
Shipping Address: City (T) | Eldorado PO: Ship To City | Austin | Specifies the city for the shipping address | Required |
Shipping Address: State Code (T) | Eldorado PO: Ship To State | TX | Specifies the state for the shipping address | Required |
Shipping Address: Postal Code (T) | Eldorado PO: Ship To Zip | 78701 | Specifies the postal code for the shipping address | Required |
Shipping Address: Full Name (T) | Eldorado PO: Ship To Name | Jane Doe | Identifies the recipient’s name for shipping | Required |
Source Shipping Method: Shipping Code (T) | Eldorado PO: Ship Via Code | UPS-GND | Specifies the shipping method Eldorado should use | Optional |
Fulfillment Request: Note (T) | Eldorado PO: Ship Instructions | Urgent delivery requested | Provides special instructions for shipping (rule: adds phone number) | Optional |
Fulfillment Request Item: SKU (T) | Eldorado PO Item: Item Number | ELD12345 | Identifies the product to be fulfilled | Required |
Fulfillment Request Item: Quantity (N) | Eldorado PO Item: Quantity | 2 | Specifies the quantity of the item to be fulfilled | Required |
Available Source Fields
Flxpoint provides a comprehensive set of fields from the fulfillment request that you can map to Eldorado’s purchase order fields:
- Billing Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
- Fulfillment Request: Estimated Dropship Fee (N), Estimated Shipping Cost (N), Fulfillment Request Number (T), Generated At (D), Note (T), Sent At (D), Total Cost (N), Total Weight (lbs) (N).
- Fulfillment Request Item: Bin Location (T), Cost (N), MPN (T), PO Line Item # (N), Quantity (N), SKU (T), Subtotal (N), Title (T), UPC (T).
- Shipping Address: Address Line 1 (T), Address Line 2 (T), City (T), Company Name (T), Country (T), Country Code (T), Email (T), First Name (T), Full Name (T), Last Name (T), Phone (T), Postal Code (T), State (T), State Code (T).
- Source Shipping Method: Carrier (T), Description (T), Method (T), Shipping Code (T).
Let’s Break It Down: The "Fulfillment Request Number" is Flxpoint’s identifier for the order, like "FR12345", which maps to Eldorado’s "PO Number" to track the order. "Shipping Address: Address Line 1" ensures Eldorado knows where to ship the order, like "123 Main St".
Mapping Options
For each field mapping, you can choose from several options to customize how the data is handled:
- Field: Link a Flxpoint field (e.g., Fulfillment Request Number) to an Eldorado field (e.g., PO Number). This is the most straightforward way to map data.
- Value: Set a fixed value for the field (e.g., always set "Ship Via Code" to "UPS-GND"). Handy for applying the same value to all orders.
- Mapping Set: Use tools to combine or manipulate data (e.g., concatenate fields). You can create custom Mapping Sets in Flxpoint for more complex transformations.
- Rules: Add "if-then" logic to transform data during mapping (e.g., add the phone number to Ship Instructions). Check out the "Mapping Rules" section below for more details.
- Don’t Map: Skip the field entirely, leaving it unmapped in Eldorado’s system.
- Set to Empty: Clear the field in Eldorado’s system, removing any existing data for that field.
Try This: If you always use the same shipping method, select "Value" for the Ship Via Code field and enter "UPS-GND". Or, use a Rule to append the customer’s phone number to the Ship Instructions for better communication with Eldorado.
Summary
You’ve now mapped a total of 11 key fields from Flxpoint to Eldorado’s purchase order format, ensuring accurate order fulfillment. This setup covers essential details like the PO number, shipping address, and item quantities. Next, you can fine-tune your mappings with custom rules in the "Mapping Rules" section below.
Mapping Rules allow you to transform Flxpoint’s fulfillment request data as it’s being mapped to Eldorado’s purchase order fields. Whether you’re adding extra information, applying conditions, or formatting data, rules help you customize the data to meet Eldorado’s requirements. Think of them as a set of instructions the integration follows to "tweak" the data before sending it to Eldorado.
Configured Mapping Rules
Here are the rules currently set up for the Eldorado - Send Fulfillment Requests integration:
-
Add Phone number to Shipping Instruction (First Instance):
- Type: Conditional (String)
- Description: Appends the customer’s phone number from the Shipping Address to the Ship Instructions field.
- Logic: Always runs, with 2 actions modifying the Incoming Value (concatenates the phone number to the existing Ship Instructions).
- Timestamp: Created at 10:35 AM.
- Example: If Ship Instructions is "Urgent delivery requested" and the phone number is "512-555-1234", the result becomes "Urgent delivery requested - Phone: 512-555-1234".
Why Use Rules? Rules are like a personal assistant for your data. For example, "Add Phone number to Shipping Instruction" ensures Eldorado has the customer’s contact info directly in the Ship Instructions, making communication easier during delivery.
Creating a New Rule
Want to create your own rule? In the Mapping Dashboard, you’ll find a "Create New Rule" option that opens a form with the following fields:
- Rule Name: A text field where you can enter a friendly name to identify the rule later, such as "Format Ship To Name".
-
Rule Type: A dropdown menu with the following options:
- Conditional: Use logic to transform data (e.g., if Shipping Address: Country = "US", add a specific prefix to Ship To Name).
- Tier: Apply tiered logic, often for quantities or costs (e.g., if Quantity > 10, add a bulk order note to Ship Instructions).
-
Input Type: A dropdown menu with the following options:
- String: For text fields like Ship Instructions or Ship To Name.
- Number: For numeric fields like Quantity or Cost.
- Boolean: For true/false fields (e.g., a condition like "Is urgent?").
- Option Field: For fields with predefined options, like shipping methods (e.g., "UPS", "FedEx").
Notice: You won’t be able to change the rule type or input type once you create the rule, this is because mapping templates using the rule will be expecting to pass in and receive back the original input type the rule defines.
Once you’ve filled out the form, click the Create button to save your rule.
Try This: Create a rule named "Add Urgent Note". In the form, set the Rule Type to "Conditional" and the Input Type to "String". Add a condition: if Fulfillment Request: Note contains "urgent", append " - URGENT ORDER" to Ship Instructions. Then click "Create" to save the rule. This ensures Eldorado prioritizes urgent orders.
Here are some essential details to understand the Eldorado - Send Fulfillment Requests integration:
- Current Date and Time: As of 10:35 AM -04 on Friday, June 13, 2025, this integration is fully operational for sending fulfillment requests to Eldorado.
- Eldorado Integration: Sends purchase orders to Eldorado via API, including details like shipping addresses, item quantities, and shipping methods.
- Supported Features: Maps Flxpoint fulfillment request data to Eldorado’s purchase order fields, with custom rules for data transformation (e.g., adding phone numbers to shipping instructions).
Pro Tip: Test your API connection before saving to ensure smooth file uploads, and double-check your mapping rules in the Mapping Dashboard to ensure Eldorado receives accurate order details.
If something goes wrong with the integration, here are some steps to help you fix it:
- API Connection Failure: Double-check your API token and click to test the connection again.
- Data Mapping Errors: Review your custom rules (e.g., adding phone numbers to Ship Instructions) in the Mapping Dashboard to ensure they’re working as expected.
- Missing Order Details: Verify that your fulfillment requests in Flxpoint include all required fields (e.g., Fulfillment Request Number, Shipping Address) so the mapping works correctly.
- Rate Limit Issues: If you encounter rate limits, adjust the scheduling to spread out requests (e.g., every hour instead of all at once).
Conclusion
With the Eldorado - Send Fulfillment Requests integration, you can seamlessly send purchase orders to Eldorado, ensuring accurate and timely order fulfillment. By mapping Flxpoint data to Eldorado’s purchase order fields and applying custom rules, you can automate your dropshipping process with confidence.
Get Shipments
Supported | Educators Resource - Get Shipments
Introduction to Educators Resource Get Shipments Integration
This guide provides a detailed overview of the Educators Resource Get Shipments integration, designed to help you track and manage shipment confirmations for your orders. Whether you're new to shipment tracking or an experienced user, this section will guide you through retrieving shipment data—such as tracking numbers and SKUs—from Educators Resource via EDI (Electronic Data Interchange). The goal is to keep your order fulfillment process seamless and up to date, ensuring you can provide accurate shipping information to your customers. Let’s dive into the setup and configuration process.
The Educators Resource Get Shipments integration connects your system to Educators Resource to retrieve shipment confirmations (EDI 856 files), including:
- Product SKUs and UPCs to identify shipped items.
- Tracking numbers and shipment details to update your order status.
The integration follows a clear process to retrieve shipment data from Educators Resource:
-
Connecting via FTP: It connects to
edi.eduresource.com
via FTP to download EDI 856 files (shipment confirmations). The files are retrieved from the/outbound/
folder and processed into your system, with processed files moved to the/inbound/
folder. - Processing Shipment Data: The integration uses a mapping template to match Educators Resource’s shipment data (e.g., SKU, UPC Number) to your system’s shipment fields.
- Updating Your System: Once processed, the shipment data updates your order records with tracking numbers and other details. You can run the integration manually or schedule it to run automatically (e.g., daily at 8 AM UTC).
Note: Before retrieving shipments, you must have an EDI account set up with Educators Resource. If you need assistance with this, contact Flxpoint support, and we’ll coordinate with Educators Resource to set up your account.
You can customize the integration with the following settings:
-
Outbound Remote File Folder: Specify the folder where Educators Resource places EDI 856 files (default:
/outbound/
). -
Inbound Remote File Folder: Specify the folder where processed files are moved (default:
/inbound/
). - Our Sender/Receiver Qualifier and ID: Enter your qualifier and ID for EDI communication (e.g., ID: 630751670, unique to your account).
- Their Sender/Receiver Qualifier and ID: Enter Educators Resource’s qualifier and ID, provided during EDI setup.
- Scheduling: Choose to run the integration manually or on a schedule (e.g., daily at 8 AM UTC).
Follow these steps to configure the Get Shipments integration:
-
1 Connect the Integration: In your system, navigate to the "Get Shipments" section and select "Educators Resource." Configure the FTP connection by providing:
-
FTP Host:
edi.eduresource.com
(pre-filled). - FTP Protocol: Select FTP (default).
- FTP Port: Use port 21 (default).
- FTP User and Password: Enter the credentials provided by Educators Resource for your EDI account.
-
FTP Host:
-
2 Configure Settings: Adjust the following options as needed:
- Set the Outbound Remote File Folder to
/outbound/
and the Inbound Remote File Folder to/inbound/
. - Enter your Our Sender/Receiver Qualifier and ID (e.g., ID: 630751670, unique to your account).
- Enter the Their Sender/Receiver Qualifier and ID for Educators Resource, provided during EDI setup.
- Set a schedule for automatic runs, if desired (e.g., daily at 8 AM UTC).
- Set the Outbound Remote File Folder to
- 3 Create a Mapping Template: Define a mapping template to match Educators Resource’s shipment data to your system’s shipment fields. This step is detailed below.
- 4 Run the Integration: Start the integration manually or let it run on your configured schedule.
A mapping template defines how shipment data from Educators Resource is matched to your system’s shipment fields. For example, it determines whether the “UPC Number” from Educators Resource maps to your “UPC” 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 “Educators Resource Get Shipments” at the top. You can name your template (e.g., “Get Shipment 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 Educators Resource (e.g., “UPC Number,” “SKU”).
- Right Column (To Shipment Item Field): Lists the fields in your system (e.g., “UPC,” “SKU”).
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 used in your system (e.g., ignoring “UPC Number” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “SKU” to empty).
- Direct Copy / Field: Copy the data as-is from Educators Resource (e.g., copying “SKU” to “SKU”).
- Value: Set a specific value of your choice (e.g., setting “SKU” to a default value like “UNKNOWN”).
- Mapping Set: Transform the data using a predefined rule (e.g., converting a UPC format).
- Rules: Apply conditional logic (e.g., “If UPC Number is empty, set SKU to ‘MISSING’”). This is for advanced users and can be skipped if you’re new.
Available Source Fields
The following fields are available from Educators Resource’s EDI 856 files for mapping:
- Educators Resource Shipment Item: UPC Number (UP), SKU.
Complete Field Mappings
Below is a detailed table of key fields you can map to in your system, with explanations, examples, and suggested mappings:
Field | Maps To | Example | Purpose | Suggested Mapping |
---|---|---|---|---|
SKU | Shipment: SKU | INV_SRC_PENCIL_GRIP_55912_OUT165513805204051621220486.TXT | Identifies the shipped product | Direct Copy: SKU |
UPC | Shipment: UPC | 012345678905 | Universal Product Code for the product | Direct Copy: UPC Number (UP) |
Practice Mapping
To understand how mapping works, try mapping the “SKU” field for your shipment data:
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the FTP connection to
edi.eduresource.com
is working and that your credentials are correct. - Ensure the Outbound Remote File Folder (
/outbound/
) and Inbound Remote File Folder (/inbound/
) are correctly set. - Check your mapping template to ensure fields are correctly matched (e.g., “SKU” to “SKU”).
- Confirm that your EDI account is set up with Educators Resource. If not, contact Flxpoint support, and we’ll coordinate with Educators Resource to assist you.
Conclusion
With your mapping template configured and the integration running, your system will stay updated with the latest shipment data from Educators Resource. This includes SKUs, UPCs, and tracking information, ensuring your order records are accurate and your customers are informed. You’re now set to manage your shipments effectively!