Williams Trading is a wholesale distributor of adult products and novelties. Integrated with Flxpoint for seamless inventory and order processing.
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 Williams Trading.
Step 3: Provide basic source details (e.g., vendor name "Williams Trading"), 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., Williams Trading) 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 Williams Trading.
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 for Williams Trading. Choose one of the following:
Get Inventory [Primary] – No credentials are needed.
Get Inventory [Secondary] – No credentials are needed.
Send Fulfillment Requests – Credentials are required.
Get Shipments – Credentials are required (same as Send Fulfillment Requests).
If you see "No integrations have been configured for this process yet", click Start Creating Integrations.
Step 6: Configure the connection based on your chosen process:
For Get Inventory [Primary] and Get Inventory [Secondary]: No connection credentials are required. Simply proceed to the next step.
For Send Fulfillment Requests and Get Shipments: In the New Williams Trading Connection form, enter the following details:
Connection Name – A unique name (e.g., "Williams Trading API").
API Endpoint – The endpoint provided by Williams Trading (e.g.,
http://muffsandcuffs.com/WMS/webservices/SOAP/).
Username and Password – The API credentials provided by Williams Trading.
Customer Number – The customer number provided by Williams Trading. This field is now required. *(Tooltip: "Your Williams Trading Customer Number")*
Click Test Connection to verify that your credentials are correct.
Step 7:
For processes that require credentials (Send Fulfillment Requests and Get Shipments), after a successful test, click Save Connection to store these details in Flxpoint.
For Get Inventory [Primary] and Get Inventory [Secondary], you can skip this step.
Step 8: On the Configure Settings screen:
For Get Inventory [Primary] and Get Inventory [Secondary], specify any file/folder paths for the inventory feed (if applicable) and adjust archiving or advanced settings.
For Send Fulfillment Requests and Get Shipments, no additional file or FTP settings are needed. Ensure that your connection details—including the Customer Number—are correct.
Click Save and Proceed to continue.
Step 9: Next, select or create your Mapping Template under Define a Mapping Template. Map the vendor’s fields (SKU, quantity, etc.) to the corresponding Flxpoint fields. Note: Do not include the Customer Number field here since it is now configured at the integration level.
Step 10: Your Williams Trading integration 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 | Williams Trading - Get Inventory (Primary)
Introduction to Williams Trading Inventory Integration
This guide explains how to use the Williams Trading Get Inventory (Primary) integration to manage your product catalog. Whether you’re new to inventory management or an experienced user, this section will walk you through the process of syncing product data—like stock levels, prices, and descriptions—from Williams Trading into your system. The goal is to ensure your inventory stays accurate and up to date, so you can focus on running your business. Let’s explore how this works and how to set it up.
Purpose of This Integration
The Williams Trading Get Inventory (Primary) integration connects your system to Williams Trading to automatically update your product catalog. It retrieves essential information, including:
- Product details (such as names, descriptions, and images).
- Stock quantities (how many items are available).
- Pricing (how much each product costs).
This ensures your store or platform reflects the most current information from Williams Trading, helping you avoid overselling or displaying outdated prices.
How the Integration Works
The integration follows a straightforward process to bring data into your system:
1. Accessing Files: It connects to a location specified by Williams Trading (for example, an FTP server, API endpoint, or secure website). From there, it downloads any key files or feeds, such as:
-
WT_Inventory.csv: Contains stock quantities (e.g., 50 units of a particular product).
-
WT_Content.csv (if available): Includes product details (e.g., product names, descriptions, and images).
-
WT_Pricing.txt (or similar): Provides pricing information (e.g., wholesale cost, MSRP, or MAP).
2. Syncing Data: The integration imports this information into your system, updating or creating products in your catalog.
3. Keeping It Updated: You can run the integration manually or configure it to run automatically on a schedule (daily, weekly, etc.).
Note: If required files are missing or empty, the integration will fail and alert you that data is incomplete.
Configuration Options
You can customize how the integration behaves based on your needs:
- Handling Missing Products: If a product is removed from Williams Trading’s feed, you can choose to archive it (remove it from your active catalog) or set its quantity to 0 (mark as out of stock).
- Scheduling: Decide whether you want to run the integration manually or automatically on a schedule (e.g., every day at 8 AM).
- Images: Typically, product images are only downloaded and updated in the production environment. You can store these images in specific folders, such as
/Assets/Original_Images for main images and /Assets/Additional_Images for extras.
Setup Instructions
Follow these steps to set up the integration:
1. Add the Integration: In your system (using a platform like Flxpoint), add the Williams Trading integration. Depending on how Williams Trading provides their feed, you may need FTP credentials or an API token.
2. Configure Settings: Decide how to handle missing products and choose whether to run the integration manually or on a schedule.
3. Create a Mapping Template: Set up a mapping template to tell the system how to match Williams Trading data fields to your inventory fields. This step is described in detail below.
4. Run the Integration: Start it manually or let it run automatically based on your chosen schedule.
Pricing Details
Pricing may come from different sources:
- Default Pricing: The integration can use Williams Trading’s standard feed for cost or wholesale price.
- Custom Pricing (Optional): If you have negotiated or tiered pricing, a custom file (e.g.,
WT_CustomPrice.csv) might override the default. Access requires special credentials or file placement, supplied by Williams Trading.
Quantity Details
Stock levels typically come from the
WT_Inventory.csv file. For example, if the file lists 100 units for a product, your system will show 100 in stock. If multiple feeds exist (for instance, separate Amazon or Walmart feeds), you can configure your system to read from them if necessary.
Mapping Template Details
A mapping template outlines how to transform data from Williams Trading’s files into your system. For example, which field in Williams Trading’s feed should become the “Title” or “SKU” in your inventory? Below are some details:
Interface Overview
- The mapping screen might be labeled “Williams Trading Get Source Products” at the top. You can name your template something like “Williams Trading Mapping.”
- You’ll typically see buttons for Delete, Duplicate, and Save.
- Two columns:
- Left (From Value): Fields from Williams Trading (SKU, Cost, Title, etc.).
- Right (To Inventory Parent Field): Fields in your system (Parent SKU, Title, Price, etc.).
Mapping Options
Similar to other integrations, you can select from:
- Don’t Map: Ignore the field entirely.
- Set To Empty: Clear any existing data in that field.
- Direct Copy / Field: Copy data from the Williams Trading field directly.
- Value: Use a constant value for all products.
- Mapping Set: Apply a predefined transformation or mapping table.
- Rules: Use conditional logic to modify fields based on certain criteria (more advanced).
Available Source Fields
While exact fields vary, Williams Trading typically provides:
- Inventory File (WT_Inventory.csv): SKU, Quantity, etc.
- Content File (WT_Content.csv): Product Titles, Descriptions, Images, Dimensions, etc.
- Pricing File (WT_Pricing.txt / .csv): Cost, MSRP, MAP, etc.
Complete Field Mappings
Below is a sample list of the kinds of fields you can map. Replace examples with your actual feed’s field names:
Parent SKU: Groups variations (e.g., color/size).
- Example: “WT-PROD-001”
- Suggested Mapping: Map to “SKU” or unique “Product ID” from the feed using Direct Copy.
All Images: Product images for customer view.
- Example: “toyset.jpg”
- Suggested Mapping: Map feed’s image URL field to “All Images.”
Title: The product name as it appears in your store.
- Example: “Luxury Toy Set”
- Suggested Mapping: Direct Copy from the feed’s “Title” or “Short Description.”
UPC: Universal Product Code or EAN.
- Example: “123456789012”
- Suggested Mapping: Map the feed’s “UPC” field if available.
Weight: Numerical weight value.
- Example: “2.5”
- Suggested Mapping: Direct Copy from feed’s “Weight.”
Weight Unit: The unit for the weight (pound, ounce, gram).
- Example: “pound”
- Suggested Mapping: Set to a default value (e.g., “pound”) if feed doesn’t specify.
Width / Length / Height: Dimensions for shipping or listing.
- Example: “12” (Width), “5” (Height)
- Suggested Mapping: Direct Copy from feed’s dimension fields.
Cost: Your wholesale cost from Williams Trading.
- Example: “10.50”
- Suggested Mapping: Direct Copy from “Cost” field.
MSRP / MAP: Manufacturer’s suggested retail price or minimum advertised price.
- Example: “19.99”
- Suggested Mapping: Direct Copy from feed if provided.
Quantity: How many units in stock.
- Example: “100”
- Suggested Mapping: Direct Copy from feed’s “Quantity.”
Practice Mapping
Here’s a quick practice example—if you map the “Title” field:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Confirm that the required Williams Trading files (e.g.,
WT_Inventory.csv, WT_Content.csv, WT_Pricing.txt) are available and up to date. Missing files will halt the integration.
- Double-check your mapping template to ensure fields from Williams Trading match correctly (e.g., “Title” -> “Product Title”).
- If using a custom price file, verify it’s correctly named (e.g.,
If problems continue, contact support for additional help.
WT_CustomPrice.csv) and placed where the system expects it.
Conclusion
Once your mapping template is configured and the Williams Trading integration is running, your system will regularly update with the latest product data: details, stock levels, and pricing. This ensures your catalog is accurate and ready for customers without manual effort!
Get Inventory (Secondary)
Supported | William Trading - Get Inventory (Secondary)
Introduction to William Trading Get Inventory (Secondary) Integration
This guide provides a comprehensive overview of the William Trading Get Inventory (Secondary) integration, designed to help you retrieve and manage inventory data efficiently. Whether you're new to inventory management or an experienced user, this section will walk you through the steps to pull inventory details like stock quantities, pricing, and MAP (Minimum Advertised Price) from William Trading’s feeds. The goal is to keep your inventory up-to-date, ensuring your business operates smoothly. Let’s get started with the setup and configuration process.
Purpose of This Integration
The William Trading Get Inventory (Secondary) integration allows you to retrieve inventory data directly from William Trading’s feeds, helping you manage stock levels and pricing. This integration:
- Pulls stock quantities, pricing, and MAP data to keep your inventory accurate.
- Uses direct feed downloads to access a common feed shared across all users, eliminating the need for individual connections.
This ensures you have the latest inventory information, reducing the risk of overselling or pricing errors. How the Integration Works
The integration follows a straightforward process to retrieve inventory data from William Trading:
1. Direct Feed Download: It accesses two publicly available feeds from William Trading:
- Product Stock Feed:
http://downloads.williams-trading.com/export/williams/products_minimal.csv (contains stock quantities and pricing). - Amazon MAP Feed:
http://downloads.williams-trading.com/export/wholesale/map.csv (contains MAP pricing). 2. Mapping Inventory Data: A mapping template formats the feed data (e.g., SKU, quantity, cost, MAP, MSRP) into your system’s inventory fields.
3. Updating Inventory: Once configured, the integration updates your inventory automatically or manually, based on your settings. You can schedule the process to run at specific times (e.g., daily at 8 AM UTC).
Note: Since the feed is common to all users, no individual connection (e.g., username/password) is required. However, you’ll need to configure settings and a mapping template to ensure the data is correctly imported into your system. Configuration Options
You can customize the integration with the following settings:
- Archive/Un-Archive Inventory: Choose whether to archive inventory that’s not in the feed (default: No). If set to “Yes,” items not found in the feed will be marked as “archived” (i.e., quantity set to zero), which is helpful for keeping your system updated with only active stock.
- Allow Create Variant: Decide whether to create new variants while retrieving inventory (default: No). If set to “Yes,” new variants can be added based on the feed data.
- 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 Get Inventory (Secondary) integration:
1. Connect the Integration: In your system, navigate to the "Get Inventory (Secondary)" section and select "William Trading." Since this integration uses a direct feed download, no additional connection information (e.g., username/password) is required. The feed URLs are pre-configured:
- Product Stock Feed:
http://downloads.williams-trading.com/export/williams/products_minimal.csv - Amazon MAP Feed:
Simply save and proceed to the next step. http://downloads.williams-trading.com/export/wholesale/map.csv 2. Configure Settings: Adjust the following options as needed:
- Archive/Un-Archive Inventory: Decide whether to archive inventory not found in the feed. We recommend setting this to “No” if you’ve already enabled this feature in the primary "Get Inventory" integration on the source, as enabling it here could overwrite those settings.
- Allow Create Variant: Choose whether to allow the creation of new variants during inventory retrieval. Set to “Yes” if you want to add new variants from the feed; otherwise, keep it as “No.”
- 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 the feed data to your system’s inventory 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 the data from William Trading’s feeds is imported into your system’s inventory fields. For example, it determines whether the “Price” field from the feed matches your “Cost” 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 “William Trading Get Inventory (Secondary)” at the top. You can name your template (e.g., “Get Inventory Secondary 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 the William Trading feed (e.g., “Cost,” “Quantity,” “SKU”).
- Right Column (To Inventory Variant Field): Lists the fields in your system (e.g., “Cost,” “Quantity,” “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 imported into your system (e.g., ignoring “MAP” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “MSRP” to empty).
- Direct Copy / Field: Copy the data as-is from the feed (e.g., copying “Quantity” to “Quantity”).
- Value: Set a specific value of your choice (e.g., setting “Cost” to “0” for all items).
- 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 the William Trading feeds for mapping to your system’s inventory fields:
- William Trading Inventory Fields: Cost, MAP, MSRP, Quantity, SKU.
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations and suggested mappings:
Cost: The price of the product from the Product Stock Feed.
- Suggested Mapping: Map to “William Trading Inventory: Cost” using “Direct Copy.”
- Reason: This imports the product’s price into your system for accurate pricing.
MAP: The Minimum Advertised Price from the Amazon MAP Feed.
- Suggested Mapping: Map to “William Trading Inventory: MAP” using “Direct Copy.”
- Reason: Ensures compliance with William Trading’s MAP pricing requirements.
MSRP: The Manufacturer’s Suggested Retail Price from the Product Stock Feed.
- Suggested Mapping: Map to “William Trading Inventory: MSRP” using “Direct Copy.”
- Reason: Provides the suggested retail price for reference in your system.
Quantity: The available stock quantity from the Product Stock Feed.
- Suggested Mapping: Map to “William Trading Inventory: Quantity” using “Direct Copy.”
- Reason: Keeps your inventory quantities up-to-date to prevent overselling.
SKU: The unique identifier for the product from the Product Stock Feed.
- Suggested Mapping: Map to “William Trading Inventory: SKU” using “Direct Copy.”
- Reason: Ensures the correct product is matched in your system.
Practice Mapping To understand how mapping works, try mapping the “Quantity” field for your inventory:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the feed URLs are accessible:
http://downloads.williams-trading.com/export/williams/products_minimal.csv and http://downloads.williams-trading.com/export/wholesale/map.csv. If the feeds are down, contact William Trading or Flxpoint support. - Check your mapping template to ensure fields are correctly matched (e.g., “William Trading Inventory: Quantity” to “Quantity”).
- If inventory isn’t updating, ensure the “Archive/Un-Archive Inventory” setting aligns with your primary "Get Inventory" integration to avoid conflicts.
- Confirm that your schedule (if set) is running as expected. All processes use UTC time by default—adjust your schedule accordingly.
If the issue persists, contact Flxpoint support for assistance. Conclusion
With your mapping template configured and the integration running, you can now retrieve inventory data from William Trading seamlessly. Your stock levels and pricing will stay up-to-date, ensuring your business runs smoothly. You’re all set to manage your 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 | William Trading - Send Fulfillment Requests
Introduction to William Trading Send Fulfillment Requests Integration
This guide walks you through the William Trading Send Fulfillment Requests integration, designed to simplify your order fulfillment process. Whether you're new to order management or a seasoned user, this section will help you send purchase orders (POs) or fulfillment requests (FRs) to William Trading via their SOAP API. The goal is to ensure your orders are processed smoothly and efficiently, keeping your business on track. Let’s dive into the setup and configuration steps to get you started.
Purpose of This Integration
The William Trading Send Fulfillment Requests integration enables you to send purchase orders or fulfillment requests to William Trading, allowing them to process and ship your orders. This integration:
- Automates the submission of order details, such as product SKUs, quantities, billing/shipping addresses, and shipping methods.
- Uses a SOAP API to securely communicate with William Trading, ensuring accurate and timely order processing.
This helps streamline your supply chain, reduce manual effort, and minimize errors in order fulfillment. How the Integration Works
The integration follows a clear process to send fulfillment requests to William Trading:
1. Connecting via SOAP API: It connects to William Trading’s SOAP endpoint at
http://muffsandcuffs.com/WMS/webservices/SOAP/ using a username and password. The WSDL (Web Services Description Language) file is available at http://muffsandcuffs.com/WMS/webservices/SOAP/?wsdl. 2. Mapping Order Data: A mapping template formats your order data (e.g., SKU, quantity, billing/shipping addresses) into the structure required by William Trading’s API.
3. Sending Requests: Once configured, the integration sends fulfillment requests either manually or automatically based on your settings. You can schedule the process to run at specific times (e.g., daily at 8 AM UTC).
Note: You’ll need a William Trading account with API credentials (username, password, and customer number) to use this integration. If you need help obtaining these, contact Flxpoint support, and we’ll assist by coordinating with William Trading on your behalf. Configuration Options
You can customize the integration with the following settings:
- William Trading Customer Number: Enter your unique customer number provided by William Trading (e.g., EYEOPR001i). This is required for order processing.
- Hold for X Hours: Set a delay (in hours) before sending POs/FRs, giving you time to review orders if needed (e.g., hold for 2 hours).
- Send During Business Hours: Enable this to send requests only during business hours, ensuring timely processing by William Trading.
- 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 William Trading Send Fulfillment Requests integration:
1. Connect the Integration: In your system, navigate to the "Send Fulfillment Requests" section and select "William Trading." Set up the connection by providing:
- Host:
http://muffsandcuffs.com/WMS/webservices/SOAP/ (pre-filled). - API Username: Enter the username provided by William Trading (e.g., BYWilson).
- API Password: Enter the password provided by William Trading.
Test the connection to confirm it works. William Trading supports a "ping" test using random credentials to expect a 401 error, confirming the endpoint is active. Save the connection once successful. If you don’t have API credentials, contact Flxpoint support, and we’ll help coordinate with William Trading to set up your account. 2. Configure Settings: Adjust the following options as needed:
- Enter your William Trading Customer Number (e.g., EYEOPR001i), which is required for order submission.
- Set a Hold for X Hours delay if you want to review orders before sending (e.g., 2 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 William Trading’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
William Trading requires the shipping method to be included with the order. You can map your system’s shipping options to William Trading’s expected shipping codes. For example:
- Best Rate: Supplier Shipping Code:
Ensure your mapping template includes the appropriate shipping method for each order. If you’re unsure about available shipping methods, contact William Trading or Flxpoint support for assistance. BESTRATE, Supplier Shipping Carrier Name: Best Rate. Mapping Template Details
A mapping template defines how your order data is formatted for William Trading’s SOAP API. For example, it determines whether your “SKU” field matches their expected “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 “William Trading Send Fulfillment Requests” at the top. You can name your template (e.g., “Send Purchase Orders 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,” “Billing Address”).
- Right Column (To William Trading Field): Lists the fields required by William Trading (e.g., “SKU,” “Bill To Address 1”).
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 William Trading (e.g., ignoring “Cost” if not required).
- Set To Empty: Clear the field in the API request, leaving it blank (e.g., setting “Bill To Address 2” to empty).
- Direct Copy / Field: Copy the data as-is from your system (e.g., copying “SKU” to “SKU”).
- Value: Set a specific value of your choice (e.g., setting “Ship Via Code” to “BESTRATE” for all orders).
- Mapping Set: Transform the data using a predefined rule (e.g., mapping your shipping method to William Trading’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 William Trading’s API requirements:
- Billing Address Fields: Address Line 1, Address Line 2, City, Company Name, Country, Country Code, Email, First Name, Full Name, Last Name, Phone, Postal Code, State, State Code.
- Fulfillment Request Fields: Estimated Dropship Fee, Estimated Shipping Cost, Fulfillment Request Number, Generated At, Note, Sent At, Total Cost, Total Weight (lbs).
- Fulfillment Request Item Fields: Bin Location, Cost, MPN, PO Line Item #, Quantity, SKU, Subtotal, Title, UPC.
- Shipping Address Fields: Address Line 1, Address Line 2, City, Company Name, Country, Country Code, Email, First Name, Full Name, Last Name, Phone, Postal Code, State, State Code.
- Source Shipping Method Fields: Carrier, Description, Method, Shipping Code (e.g., BESTRATE).
Complete Field Mappings Below is a detailed list of key fields you can map to in William Trading’s API, with explanations, examples, and suggested mappings:
Bill To Address 1: The primary billing address line.
- Example: “1 Huron Drive”
- Suggested Mapping: Map to “Billing Address: Address Line 1” from your system using “Direct Copy.”
- Reason: This ensures William Trading has the correct billing address for the order.
Bill To Address 2: The secondary billing address line (optional).
- Example: “D”
- Suggested Mapping: Map to “Billing Address: Address Line 2” from your system using “Direct Copy,” or set to “Don’t Map” if not applicable.
- Reason: Provides additional billing address details if needed.
Bill To City: The city for the billing address.
- Example: “Portsmouth”
- Suggested Mapping: Map to “Billing Address: City” from your system using “Direct Copy.”
- Reason: Specifies the billing city for accurate order processing.
Bill To Country: The country for the billing address.
- Example: “United States”
- Suggested Mapping: Map to “Billing Address: Country” from your system using “Direct Copy.”
- Reason: Ensures the correct country is associated with the billing address.
Bill To Email: The email address for billing contact.
- Example: “dauthor00@gmail.com”
- Suggested Mapping: Map to “Billing Address: Email” from your system using “Direct Copy.”
- Reason: Provides a contact email for billing-related communication.
Bill To First Name: The first name of the billing contact.
- Example: “Byron”
- Suggested Mapping: Map to “Billing Address: First Name” from your system using “Direct Copy.”
- Reason: Identifies the billing contact for the order.
Bill To Last Name: The last name of the billing contact.
- Example: “Wilson”
- Suggested Mapping: Map to “Billing Address: Last Name” from your system using “Direct Copy.”
- Reason: Completes the billing contact’s name for the order.
Bill To State: The state for the billing address.
- Example: “Virginia”
- Suggested Mapping: Map to “Billing Address: State” from your system using “Direct Copy.”
- Reason: Specifies the billing state for accurate order processing.
Bill To Zip: The postal code for the billing address.
- Example: “23702”
- Suggested Mapping: Map to “Billing Address: Postal Code” from your system using “Direct Copy.”
- Reason: Ensures the correct postal code is used for billing.
Items: SKU: The unique identifier for the product.
- Example: “WTC100CP”
- Suggested Mapping: Map to “Fulfillment Request Item: SKU” from your system using “Direct Copy.”
- Reason: Allows William Trading to identify the product in their system.
Items: Name: The name or title of the product.
- Example: “Cloud 9 fresh + portable anal enema douche 3.3 oz ez squeeze bulb 2 pack”
- Suggested Mapping: Map to “Fulfillment Request Item: Title” from your system using “Direct Copy.”
- Reason: Provides a description of the product for clarity.
Items: Price: The price of the product.
- Example: “5.93”
- Suggested Mapping: Map to “Fulfillment Request Item: Cost” from your system using “Direct Copy.”
- Reason: Specifies the cost of the item for order verification.
Items: Quantity: The number of units to order.
- Example: “1”
- Suggested Mapping: Map to “Fulfillment Request Item: Quantity” from your system using “Direct Copy.”
- Reason: Tells William Trading how many units to ship.
Notes: Additional notes for the order.
- Example: “Test order”
- Suggested Mapping: Map to “Fulfillment Request: Note” from your system using “Direct Copy.”
- Reason: Allows you to include any special instructions or comments.
Reference: A reference number for the order.
- Example: “14737-2”
- Suggested Mapping: Map to “Fulfillment Request: Fulfillment Request Number” from your system using “Direct Copy.”
- Reason: Provides a unique identifier for tracking the order.
Ship To Address 1: The primary shipping address line.
- Example: “1 Huron Drive”
- Suggested Mapping: Map to “Shipping Address: Address Line 1” from your system using “Direct Copy.”
- Reason: Ensures William Trading ships to the correct address.
Ship To Address 2: The secondary shipping address line (optional).
- Example: “D”
- Suggested Mapping: Map to “Shipping Address: Address Line 2” from your system using “Direct Copy,” or set to “Don’t Map” if not applicable.
- Reason: Provides additional shipping address details if needed.
Ship To City: The city for the shipping address.
- Example: “Portsmouth”
- Suggested Mapping: Map to “Shipping Address: City” from your system using “Direct Copy.”
- Reason: Specifies the shipping city for accurate delivery.
Ship To Country: The country for the shipping address.
- Example: “United States”
- Suggested Mapping: Map to “Shipping Address: Country” from your system using “Direct Copy.”
- Reason: Ensures the correct country is associated with the shipping address.
Ship To First Name: The first name of the shipping contact.
- Example: “Byron”
- Suggested Mapping: Map to “Shipping Address: First Name” from your system using “Direct Copy.”
- Reason: Identifies the shipping contact for the order.
Ship To Last Name: The last name of the shipping contact.
- Example: “Wilson”
- Suggested Mapping: Map to “Shipping Address: Last Name” from your system using “Direct Copy.”
- Reason: Completes the shipping contact’s name for the order.
Ship To State: The state for the shipping address.
- Example: “Virginia”
- Suggested Mapping: Map to “Shipping Address: State” from your system using “Direct Copy.”
- Reason: Specifies the shipping state for accurate delivery.
Ship To Zip: The postal code for the shipping address.
- Example: “23702”
- Suggested Mapping: Map to “Shipping Address: Postal Code” from your system using “Direct Copy.”
- Reason: Ensures the correct postal code is used for shipping.
Ship Via Code: The shipping method for the order.
- Example: “BESTRATE”
- Suggested Mapping: Map to “Source Shipping Method: Shipping Code” from your system using “Mapping Set” to match William Trading’s shipping codes (e.g., “Best Rate” to
BESTRATE). - Reason: Ensures the correct shipping method is used for the order.
Practice Mapping To understand how mapping works, try mapping the “Bill To Address 1” field for your fulfillment request:
Troubleshooting
If the integration encounters an issue, here are some steps to resolve it:
- Verify that the SOAP API connection to
http://muffsandcuffs.com/WMS/webservices/SOAP/ is working and that your username and password are correct. An error like “org.xml.sax.SAXParseException; Content is not allowed in prolog” often indicates incorrect credentials—double-check with William Trading. - Ensure your William Trading Customer Number (e.g., EYEOPR001i) is correctly entered in the integration settings. An “Invalid Customer Specified” error means the customer number is incorrect or not recognized—verify with William Trading.
- Check your mapping template to ensure fields are correctly matched (e.g., “SKU” to “Items: SKU,” “Shipping Address: Postal Code” to “Ship To Zip”).
- Confirm that your William Trading account has the necessary permissions to create orders. If you suspect permission issues, contact William Trading or Flxpoint support for assistance.
- Ensure the items in your order (e.g., SKU: WTC100CP) are valid in William Trading’s system. Invalid items can cause order failures—verify with William Trading if needed.
If the issue persists, contact Flxpoint support for assistance. We can coordinate with William Trading (e.g., via their point of contact,) to resolve the issue. Conclusion
With your mapping template configured and the integration running, you can now send fulfillment requests to William Trading 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 | William Trading - Get Shipments
Introduction to William Trading Get Shipments Integration
This guide provides a detailed overview of the William Trading Get Shipments integration, designed to help you retrieve shipment details for your orders. Whether you're new to shipment tracking or an experienced user, this section will walk you through the steps to pull shipment information, such as tracking numbers, shipping methods, and item details, from William Trading via their SOAP API. The goal is to keep you informed about your order shipments, ensuring smooth operations. Let’s get started with the setup and configuration process.
Purpose of This Integration
The William Trading Get Shipments integration allows you to retrieve shipment details for orders processed by William Trading, helping you track and manage deliveries. This integration:
- Pulls shipment data, including tracking numbers, shipping methods, and item SKUs, to keep your records updated.
- Uses a SOAP API to securely communicate with William Trading, ensuring accurate and timely shipment information.
This helps you provide customers with tracking information and manage your fulfillment process effectively. How the Integration Works
The integration follows a clear process to retrieve shipment details from William Trading:
1. Connecting via SOAP API: It connects to William Trading’s SOAP endpoint at
http://muffsandcuffs.com/WMS/webservices/SOAP/ using a username and password. The WSDL file is available at http://muffsandcuffs.com/WMS/webservices/SOAP/?wsdl. 2. Mapping Shipment Data: A mapping template formats the API response data (e.g., tracking number, shipping method, SKU) into your system’s shipment fields.
3. Retrieving Shipments: Once configured, the integration retrieves shipment details automatically or manually, based on your settings. You can schedule the process to run at specific times (e.g., daily at 8 AM UTC).
Note: You’ll need a William Trading account with API credentials (username and password) to use this integration. If you need help obtaining these, contact Flxpoint support, and we’ll assist by coordinating with William Trading on your behalf. Configuration Options
There are no additional configuration settings required for this integration beyond the initial connection setup and mapping template. However, you can:
- 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 Get Shipments integration:
1. Connect the Integration: In your system, navigate to the "Get Shipments" section and select "William Trading." Set up the connection by providing:
- Host:
http://muffsandcuffs.com/WMS/webservices/SOAP/ (pre-filled). - API Username: Enter the username provided by William Trading (e.g., BYWilson).
- API Password: Enter the password provided by William Trading.
Test the connection to confirm it works. William Trading supports a "ping" test using random credentials to expect a 401 error, confirming the endpoint is active. Save the connection once successful. If you don’t have API credentials, contact Flxpoint support, and we’ll help coordinate with William Trading to set up your account. 2. Configure Settings: There are no additional settings to configure for this integration. Simply save and proceed.
3. Create a Mapping Template: Define a mapping template to match the API response 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.
Carrier & Methods
William Trading provides carrier and shipping method information via the SOAP API. You can map these to your system’s fields:
- Carrier: The shipping carrier used (e.g., “UPS”).
- Method: The shipping method (e.g., “Ground”).
Ensure your mapping template includes these fields to capture the correct carrier and method for each shipment. Mapping Template Details
A mapping template defines how the shipment data from William Trading’s SOAP API is imported into your system. For example, it determines whether the “Tracking Number” field from the API matches 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 “William Trading Get Shipments” at the top. You can name your template (e.g., “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 sections:
- Shipment Fields: Maps data related to the shipment (e.g., “Carrier,” “Tracking Number”).
- Shipment Item Fields: Maps data related to the items in the shipment (e.g., “SKU,” “Quantity”).
- Each section has two columns:
- Left Column (From Value): Lists the data fields from the William Trading API (e.g., “Shipping Method,” “SKU”).
- Right Column (To Shipment/Shipment Item Field): Lists the fields in your system (e.g., “Carrier,” “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 imported into your system (e.g., ignoring “Shipping Cost” if not needed).
- Set To Empty: Clear the field in your system, leaving it blank (e.g., setting “Note” to empty).
- Direct Copy / Field: Copy the data as-is from the 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 William Trading’s shipping method to your system’s format).
- 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 the William Trading API for mapping to your system’s shipment fields:
- William Trading Shipment Fields: Order Number, Problem Date, Reference Number, Shipper, Shipping Date, Shipping Method, Shipping Method Service, Shipping Notes, Tracking Number.
- William Trading Shipment Item Fields: Name, Quantity, Shipped, SKU.
Complete Field Mappings Below is a detailed list of key fields you can map to in your system, with explanations and suggested mappings:
Shipment Fields:
Carrier: The shipping carrier used for the shipment.
- Suggested Mapping: Map to “William Trading Shipment: Shipping Method” using “Direct Copy.”
- Reason: Identifies the carrier handling the shipment (e.g., “UPS”).
Fulfillment Request Number: The associated fulfillment request number (not typically mapped).
- Suggested Mapping: Set to “Don’t Map.”
- Reason: This field is often not needed for shipment tracking.
Method: The shipping method used.
- Suggested Mapping: Map to “William Trading Shipment: Shipping Method Service” using “Direct Copy.”
- Reason: Specifies the shipping method (e.g., “Ground”).
Note: Any additional notes about the shipment.
- Suggested Mapping: Map to “William Trading Shipment: Shipping Notes” using “Direct Copy.”
- Reason: Captures any special instructions or comments about the shipment.
Shipped At: The date the shipment was sent.
- Suggested Mapping: Map to “William Trading Shipment: Shipping Date” using “Direct Copy.”
- Reason: Provides the shipment date for tracking purposes.
Shipping Cost: The cost of shipping (not typically mapped).
- Suggested Mapping: Set to “Don’t Map.”
- Reason: This field is often not provided or needed for shipment tracking.
Tracking Number: The tracking number for the shipment.
- Suggested Mapping: Map to “William Trading Shipment: Tracking Number” using “Direct Copy.”
- Reason: Allows you to provide customers with tracking information.
Tracking URL: The URL for tracking the shipment (not typically mapped).
- Suggested Mapping: Set to “Don’t Map.”
- Reason: William Trading does not provide a tracking URL in the API response.
Shipment Item Fields:
All Custom Fields: Custom fields like serial numbers (not typically mapped).
- Suggested Mapping: Set to “Don’t Map.”
- Reason: William Trading does not provide serial numbers or custom fields in the API response.
Quantity: The quantity of items shipped.
- Suggested Mapping: Map to “William Trading Shipment Item: Shipped” using “Direct Copy.”
- Reason: Specifies how many units of the item were shipped.
SKU: The unique identifier for the item in the shipment.
- Suggested Mapping: Map to “William Trading Shipment Item: SKU” using “Direct Copy.”
- Reason: Matches the shipped item to your system’s inventory.
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 the SOAP API connection to
http://muffsandcuffs.com/WMS/webservices/SOAP/ is working and that your username and password are correct. An error like “401 Unauthorized” often indicates incorrect credentials—double-check with William Trading. - Check your mapping template to ensure fields are correctly matched (e.g., “William Trading Shipment: Tracking Number” to “Tracking Number”).
- Confirm that your William Trading account has the necessary permissions to access shipment data. If you suspect permission issues, contact William Trading or Flxpoint support for assistance.
- Ensure the schedule (if set) is running as expected. All processes use UTC time by default—adjust your schedule accordingly.
If the issue persists, contact Flxpoint support for assistance. We can coordinate with William Trading (e.g., via their point of contact, shenellj@williams-trading.com) to resolve the issue. Conclusion
With your mapping template configured and the integration running, you can now retrieve shipment details from William Trading seamlessly. Your tracking information will stay up-to-date, ensuring you can keep your customers informed. You’re all set to manage your shipments with ease!