Flxpoint Help Center
All DocsContact support

ALMS Marketplace as a Source

July 17, 2026

Summary

ALMS Marketplace is a pre-built supplier integration in Flxpoint that uses a dual credential model: inventory operations (Get Inventory Primary and Secondary) connect via a Feed URL, while order operations (Send Fulfillment Requests and Get Shipments) connect via a separate API Token generated in your ALMS Marketplace account. You'll need to create both connection types before configuring all four supported operations; for operation-level mapping guidance contact support@flxpoint.com.

Get Inventory (Primary)
Imports ALMS Marketplace's full catalog: products, pricing, and images.
Get Inventory (Secondary)
Refreshes pricing, cost, and quantity on existing variants more frequently.
Send Fulfillment Requests
Sends Fulfillment Requests to ALMS Marketplace via the API Token connection.
Get Shipments
Pulls shipment tracking and carrier confirmations back from ALMS Marketplace.

ALMS Marketplace uses two separate connections — a Feed URL connection for inventory operations and an API Token connection for order operations. Add an ALMS Marketplace source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the credential for that operation's connection type, then Test ConnectionSave Connection. Repeat for the second connection type before configuring the remaining operations.

Feed URL Connection (GIP / GIS)
Feed URLRequired
The URL to ALMS Marketplace's inventory feed. Used by Get Inventory (Primary) and Get Inventory (Secondary).
API Token Connection (Send FR / Get Shipments)
API TokenRequired
Your ALMS Marketplace API token, generated from your ALMS Marketplace account (Settings → API Access). Used by Send Fulfillment Requests and Get Shipments.
Create both connection types before configuring all four operations — GIP and GIS use the Feed URL connection, Send FR and Get Shipments use the API Token connection. Selecting the wrong connection type for an operation will cause it to fail. For extended field mapping guidance, contact support@flxpoint.com.

Two separate connections required — Feed URL for inventory, API Token for order operations

GIP and GIS use a connection with a Feed URL (the URL to ALMS Marketplace's inventory feed API). Send FR and Get Shipments use a connection with an API Token from your ALMS Marketplace account (Settings → API Access → generate or copy your token). Create both connections before configuring all four operations.

GIP imports a full catalog: SKU, Title, Description, UPC, MPN, Manufacturer, Quantity, Cost, MSRP, Price, Categories, Dimensions, Images

GIP retrieves a full product record per SKU including: Product Sku (Parent SKU), Title, Description, UPC, EAN, MPN, Manufacturer, Category 1/2/3, Image URLs, Quantity, Cost, MSRP, Price, Estimated Dropship Fee, Estimated Shipping Cost, Height, Length, Width, Weight. GIS is a delta feed focused on variant-level updates: SKU, Cost, MAP, MSRP, Price, Quantity, Shipping Cost. Enable Allow Create Variant in GIS settings if new variants may appear.

Send FR: State or State Code must be mapped — at least one is required

When configuring Send FR, the shipping address requires either State (full name, e.g., "California") or State Code (abbreviation, e.g., "CA") — at least one must be mapped. If neither is present in the mapping template, the order submission will fail with a validation error. Also map: Order Number (FR Number), SKU, Quantity, Address Line 1, City, Postal Code, Country.

Get Shipments: Return PO Number links shipment back to the FR — required mapping

Get Shipments retrieves: Carrier, Method, Note, Return PO Number, Shipped At, Shipping Cost, Tracking Number, Tracking URL, Shipment ID. The critical linking field is Return PO Number → Fulfillment Request Number — this connects the incoming shipment record to the correct FR in Flxpoint. Without this mapping, shipments will not associate to orders. Shipment item fields: SKU, Quantity, External Order Item ID.


FieldMaps To — Notes
Product SkuProduct → Parent SKU. Groups variants under one catalog product.
SkuVariant → SKU. Required. Primary identifier for the catalog item.
Title / DescriptionProduct → Title / Description. Product-level catalog copy.
UPC / EAN / MPNIdentifiers. Barcode and manufacturer part reference fields.
Manufacturer / Category 1-3Product → Manufacturer / Categories. Brand and category classification.
Cost / MSRP / PricePricing. Your ALMS Marketplace cost and suggested resale pricing.
QuantityInventory → Quantity. Available units for the variant.
Images / Height, Length, Width, WeightProduct/Variant → Images, Dimensions. Catalog images and shipping dimensions.
FieldMaps To — Notes
SkuVariant → SKU. Required. Primary identifier.
CostPricing → Cost. Current dealer cost.
MAPPricing → MAP. Minimum advertised price.
MsrpPricing → MSRP.
PricePricing → Price.
QuantityInventory → Quantity. Current available units.
Estimated Shipping CostShipping → Estimated Shipping Cost.
Full catalog fieldsNot included in Secondary — title, categories and identifiers come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost, MAP, MSRP, Price and Quantity current.
Source FieldMaps To (ALMS Marketplace) — Notes
Fulfillment Request NumberOrder Number. Required. Sent to ALMS Marketplace as the order reference.
Fulfillment Request line → SKUOrder Item → SKU. Required. Sent per line item.
Fulfillment Request line → QuantityOrder Item → Quantity. Required. Units requested per line.
Shipping address → Address Line 1, City, Postal Code, CountryShip To. Required. End-customer shipping address fields.
Shipping address → State or State CodeShip To → State / State Code. Required — at least one. Order submission fails validation if neither is mapped.
Ship-to contact / company nameShip To Contact. Contact name/company for the shipment.
FieldMaps To — Notes
Tracking NumberShipment → Tracking Number. Required. Package tracking number.
Return PO NumberShipment → Fulfillment Request Number. Required. Critical linking field — connects the shipment back to the FR; without it, shipments import as orphaned records.
Carrier / MethodShipment → Carrier / Ship Method. Carrier and shipping method returned by ALMS Marketplace.
Shipped AtShipment → Shipped At. When ALMS Marketplace marks the shipment shipped.
Shipping CostShipment → Shipping Cost. Cost of the shipment.
Item SKUShipment Item → SKU. Required. Associates the shipped line to your catalog.
Item Quantity / External Order Item IDShipment Item → Quantity / External Order Item ID. Required (Quantity). Units shipped and channel order-item reference.

Send FR failing — State/State Code missing or API Token connection not selected
Two common Send FR failures: (1) State/State Code not mapped — ALMS Marketplace requires at least one of these shipping address fields; check your Send FR template and confirm either State (full name) or State Code (abbreviation) is mapped from the Flxpoint fulfillment request's shipping address; (2) Wrong connection selected — Send FR requires the API Token connection, not the Feed URL connection; confirm the correct connection is selected in the Send FR Connect step. Check the job log for the specific validation error after each failed run.
Get Shipments not linking to FRs
If Get Shipments runs successfully but shipments don't attach to orders: confirm Return PO Number → Fulfillment Request Number is mapped in the Get Shipments template — this is the critical linking field. Without it, shipments are imported as orphaned records with no FR association. Also confirm the API Token connection is selected (not the Feed URL connection) for Get Shipments. After fixing the mapping, re-run Get Shipments to reimport unlinked shipments.

How do I set up the two ALMS Marketplace connections?
Go to Sources → + Add Source and complete the Source Wizard. After saving, go to Integrations → Get Inventory → Start Creating Integrations → ALMS Marketplace. For GIP/GIS: on the New ALMS Marketplace Connection screen, enter your Connection Name and Feed URL (the ALMS inventory API URL). Test Connection and Save. For Send FR/Get Shipments: create a second connection with a descriptive name (e.g., "ALMS Marketplace Fulfillment") and enter your API Token (from ALMS Marketplace Settings → API Access). Test Connection and Save. When configuring each operation, select the correct connection type.
What does GIS (Secondary) map for ALMS Marketplace?
GIS uses the same Feed URL connection as GIP but focuses on variant-level updates only: Sku → SKU (required), Cost → Cost, MAP → MAP, Msrp → MSRP, Price → Price, Quantity → Quantity, Estimated Shipping Cost → Shipping Cost. Additional available fields: Estimated Dropship Fee, Height, Length, Width, Weight. Enable Allow Create Variant in GIS settings if new SKUs may appear between full GIP runs. Leave Archive disabled on GIS if GIP already has it active.
© 2026 Flxpoint. All rights reserved.