HLC as a Source
Summary
HLC is a distributor of bicycles and cycling accessories, available as a source in Flxpoint for automated inventory and order fulfillment. The integration connects via API using either your HLC login credentials (Username + Password) or an HLC-issued Access Token — the same connection is reused across all operations. Get Inventory (Primary), Send Fulfillment Requests, and Get Shipments are supported; for operation-level mapping guidance contact support@flxpoint.com.
HLC supports two connection types — use the one your HLC representative confirms for your account. Add an HLC source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection. The same connection is reused across all HLC operations.
support@flxpoint.com.HLC credentials (login or API) required — obtain before configuring
The New HLC Connection screen accepts your HLC login credentials or API credentials as provided by HLC. These are separate from any HLC dealer website login. Contact your HLC account representative to confirm which credential type is required for your account and to request API access if needed. Without valid credentials, Test Connection will fail.
For extended operation details and mapping guidance, contact Flxpoint Support
The HLC integration documentation covers connection setup only. For field mapping recommendations, required Send FR fields, or Get Shipments configuration specific to HLC's API response format, contact support@flxpoint.com.
GIP daily for full catalog; GIS more frequently for price and quantity updates
Run Get Inventory Primary once daily to import the full HLC bicycle and accessories catalog. Use Get Inventory Secondary on a more frequent schedule (hourly or every few hours) to keep prices and quantities current between full catalog runs. Enable Archive/Un-Archive on one job only — enabling it on both GIP and GIS simultaneously creates conflicting archive states.
Test a single manual order before enabling automatic Send FR scheduling
Before scheduling automatic order sending, run one manual Fulfillment Request and confirm the order is received correctly at HLC. At minimum, map SKU, Quantity, and a complete ship-to address. Run a single order manually first — bicycle and cycling accessories shipments may have specific carrier or packaging requirements that affect accepted shipping method codes.
| Field | Maps To — Notes |
|---|---|
| Variant SKU | → Product / Variant → SKU. Required. Primary identifier for the catalog variant. |
| Price (Base) | → Pricing → Cost. HLC's base dealer price for the variant, saved as Cost. |
| Price (MSRP) | → Pricing → MSRP. Manufacturer's suggested retail price, when returned by HLC. |
| Price (MAP) | → Pricing → MAP. Minimum advertised price, when returned by HLC. |
| UPC / EAN | → Identifiers → Barcode. Universal or European product code for the variant. |
| MFGPartNumber | → Identifiers → Manufacturer Part Number / MPN. Manufacturer part reference. |
| Dimensions (Weight / Length / Width / Height) | → Shipping → Package Dimensions. Used for shipping rate and label calculations. |
| WarehousesQuantities (selected warehouse) | → Inventory → Quantity. Required. Available units summed across the warehouse(s) selected in your integration settings. |
| Images (Original format) | → Product / Variant → Images. Product images, filtered to the Original image format returned by HLC. |
| Attributes | → Product → Attributes / Options. Attributes shared across all variants of a product become Product Attributes; attributes unique to a specific variant become Variant Options. |
| Source Field | Maps To (HLC) — Notes |
|---|---|
| Fulfillment Request line → SKU | → Item → Sku. Required. Sent to HLC per line item. |
| Fulfillment Request line → Quantity | → Item → Quantity. Required. Units requested per line. |
| Fulfillment Request Number | → Order Options → PO Number. Your Flxpoint purchase order number, sent to HLC for reference. |
| Order Note | → Order Options → Note. Optional note text sent with the order. |
| Shipping address (name, street, city, state, zip, country) | → Delivery Address. Required. End-customer shipping address sent to HLC. |
| Signature Required | → Shipping Options → Signature Required. Whether a signature is required on delivery. |
| Language (connection setting) | → Shipping Options → Document Language. Language used for HLC-generated shipping documents on this order. |
| Field | Maps To — Notes |
|---|---|
| TrackingNumber | → Shipment → Tracking Number. Required. Package tracking number returned by HLC. |
| Carrier | → Shipment → Ship Method. Carrier name returned by HLC for the shipment. |
| TrakingUrl | → Shipment → Tracking URL. Carrier tracking link, when returned by HLC. |
| Item SKU / Quantity | → Shipment Item → SKU / Quantity. Required. Taken from the original Fulfillment Request — HLC does not return line-level ship detail, so Flxpoint records the full order as shipped. |
| Cart ID | → Fulfillment Request match. Used internally to link the HLC shipment back to the originating order — not a separately mapped field. |