Williams Trading as a Source

July 20, 2026

Summary

Williams Trading is a wholesale distributor of adult products and novelties. It uses a split credential model: Get Inventory (Primary) and Get Inventory (Secondary) need no connection at all — they pull publicly available data feeds automatically — while Send Fulfillment Requests and Get Shipments authenticate through a API connection (API Endpoint, Username, Password) plus a Customer Number configured separately in integration settings. Orders use Ship Via Code BESTRATE for shipping method.

What this integration does

Get Inventory (Primary)

Imports Williams Trading's full catalog — titles, images, categories, dimensions, pricing and stock. No connection required.

Get Inventory (Secondary)

A lighter, more frequent refresh of Cost, MAP, MSRP and Quantity only. No connection required.

Send Fulfillment Requests

Sends orders (Fulfillment Requests) to Williams Trading's API for dropship fulfillment.

Get Shipments

Pulls shipment confirmations — tracking, carrier and ship date — from Williams Trading's API.

How to connect - credentials you need

Williams Trading uses a split credential model. Get Inventory (Primary) and Get Inventory (Secondary) need no connection — they run automatically against publicly available data feeds. Send Fulfillment Requests and Get Shipments require a API connection: add a Williams Trading source, start configuring Send FR or Get Shipments, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

Get Inventory (Primary & Secondary) — No Connection Required

No credentials neededInfo

Get Inventory Primary and Secondary run against Williams Trading's publicly available data feeds automatically — no connection, username, or password is required for either operation.

Send Fulfillment Requests & Get Shipments — API

API EndpointRequired

The Williams Trading API endpoint, provided by Flxpoint.

API UsernameRequired

Your Williams Trading API username.

API PasswordRequired

Your Williams Trading API password.

A Customer Number (provided by Williams Trading) is also required for Send Fulfillment Requests, but it's entered separately in the Send FR integration settings — not on the API connection and not in the mapping template — to avoid duplicate mapping. For extended field-mapping guidance, contact support@flxpoint.com.

Important - read before configuring

GIP and GIS require no credentials — GIS uses public direct-download feeds from Williams Trading

Get Inventory Primary and Secondary do not require API credentials. GIS fetches two public direct-download feeds: the Product Stock Feed and the Amazon MAP Feed. GIS fields: SKU, Cost, MAP, MSRP, Quantity. No username/password or API key is needed for either inventory operation.

Send FR and Get Shipments use API — Customer Number now in settings, not mapping template

Send FR and Get Shipments connect to Williams Trading via a API. Required: API Username, API Password, and Customer Number (provided by Williams Trading). The Customer Number is now configured in Send FR integration settings — do not include it in the mapping template to avoid duplication.

Connection test authentication errors — verify your API credentials

When you run Test Connection, an authentication error means your API Username or API Password is incorrect — re-verify them with Williams Trading (case-sensitive). An XML / "content not allowed in prolog" parse error usually points to the same credential problem.

Ship Via Code for Send FR: use BESTRATE — map from Source Shipping Method → Shipping Code

Williams Trading requires a Ship Via Code with each order. The standard code is BESTRATE (Best Rate). Map this via your Send FR mapping template: Source Shipping Method → Shipping Code → BESTRATE using a fixed Value or Mapping Set. If you need a different carrier, confirm available Ship Via codes with Williams Trading. All Get Shipments carrier/method data comes from the Shipment → Shipping Method and Shipping Method Service fields.

Operations - fields to know

Get Inventory (Primary)Get Inventory (Secondary)Send Fulfillment RequestsGet Shipments

Field	Maps To — Notes
SKU	→ Product / Variant → SKU. Required. Primary identifier for the catalog item.
Title / Description	→ Product → Title / Description. Long and short descriptions from Williams Trading's catalog feed.
Cost	→ Pricing → Cost. Your Williams Trading dealer price.
MSRP	→ Pricing → MSRP. Calculated from Cost using Williams Trading's standard markup — not a separate feed column.
MAP	→ Pricing → MAP. Amazon Minimum Advertised Price, from the Amazon MAP feed (excluded when Williams Trading flags the item as Amazon-restricted).
Quantity	→ Inventory → Quantity. Current available stock.
UPC	→ Identifiers → UPC / Barcode.
Manufacturer	→ Identifiers → Manufacturer / Vendor.
Weight / Height / Width / Length	→ Shipping → Dimensions & Weight.
Category / Sub-Category	→ Product → Category / Subcategory. Built from Williams Trading's category hierarchy.
Images	→ Product → Images.

Field	Maps To — Notes
SKU	→ Inventory Variant → SKU. Required. Primary identifier.
Cost	→ Pricing → Cost. Dealer price from the Product Stock feed.
MSRP	→ Pricing → MSRP. Calculated from Cost using the same markup as Get Inventory Primary.
MAP	→ Pricing → MAP. From the Amazon MAP feed.
Quantity	→ Inventory → Quantity. Current available stock.
Full catalog fields	Not included in Secondary — titles, images, categories and identifiers come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost, MAP, MSRP and Quantity current.

Source Field	Maps To (Williams Trading) — Notes
Billing address (Address 1, City, State, Zip, Country, First/Last Name)	→ Bill To. Required. All billing fields must be mapped.
Shipping address (Address 1, City, State, Zip, Country, First/Last Name)	→ Ship To. Required. All shipping fields must be mapped.
Items: SKU, Name, Quantity	→ Order Line Items. Required. Sent per line item.
Reference	→ FR Number. Required.
Source Shipping Method	→ Ship Via Code. Required. Standard value is BESTRATE (Best Rate) via a fixed Value or Mapping Set.
Address 2, Email, Notes, Items: Price	Optional fields — map if available, not required for the order to send.
Customer Number	Entered in Send FR integration settings, not the mapping template — avoids duplicate mapping.

Field	Maps To — Notes
Tracking Number	→ Shipment → Tracking Number. Required.
Carrier	→ Shipment → Shipping Method.
Method	→ Shipment → Shipping Method Service.
Shipped At	→ Shipment → Shipping Date.
Note	→ Shipment → Shipping Notes.
Item SKU	→ Shipment Item → SKU. Required.
Item Quantity	→ Shipment Item → Shipped (not Quantity).
Fulfillment Request Number / Tracking URL	Typically Don't Map — Williams Trading's API response doesn't return a tracking URL, and FR association is handled automatically.
Custom Fields	Don't Map.

Common issues

Send FR failing — "XML parse error" or "Invalid Customer Specified"

Two common causes: (1) XML parse / prolog error — this usually means an incorrect API Username or Password; re-verify your credentials with Williams Trading carefully (case-sensitive). (2) Invalid Customer Specified — the Customer Number entered in integration settings is wrong or not recognized; verify your exact Customer Number with Williams Trading. Also confirm the required Send FR mapping fields (SKU, Quantity, Address fields, Ship Via Code) are all mapped and non-empty.

GIS feed not updating — feed unreachable or mapping mismatch

GIS uses public CSV feed URLs — no credentials required. If GIS runs but quantities/prices don't update: (1) verify the feed is reachable from your network — if it appears to be down, contact Williams Trading; (2) confirm your GIS mapping template has SKU correctly mapped to the SKU field in the feed — a mismatch means no existing variants get updated; (3) if Archive/Un-Archive is enabled in both GIP and GIS, disable it on GIS to avoid conflicts.

FAQs

What does GIS import from Williams Trading and how does it work without credentials?▸

GIS downloads two public CSV feeds directly (no individual connection or credentials required): the Product Stock Feed for Cost, MSRP, Quantity, SKU; and the Amazon MAP Feed for MAP pricing. Map these fields in the GIS template: Cost → Cost, MAP → MAP, MSRP → MSRP, Quantity → Quantity, SKU → SKU (required). Do not enable Archive/Un-Archive on GIS if GIP already has it enabled — this causes conflicts.

What are the required Send FR fields for Williams Trading API?▸

Required (must be mapped): Bill To Address 1, City, Country, First Name, Last Name, State, Zip (all billing address fields), Ship To Address 1, City, Country, First Name, Last Name, State, Zip (all shipping address fields), Items: SKU, Items: Name, Items: Quantity, Reference (FR Number), Ship Via Code (e.g., BESTRATE). Optional: Address 2, Email, Notes, Items: Price. Enter Customer Number (provided by Williams Trading) in integration settings — not the mapping template. Use Hold for X Hours or Send During Business Hours settings for order timing control.

What does Get Shipments return from Williams Trading?▸

Get Shipments retrieves from the API: header fields — Tracking Number, Carrier → Shipping Method, Method → Shipping Method Service, Shipped At → Shipping Date, Note → Shipping Notes. Item fields: SKU → SKU, Quantity → Shipped (not Quantity). Notable: Fulfillment Request Number and Tracking URL are both typically set to Don't Map — Williams Trading doesn't provide a tracking URL in the API response, and FR number association is typically handled automatically. All Custom Fields are also Don't Map.

Back to Adult & Lifestyle Sources