This document will cover how to connect Lipseys as a source and what integrations we support with Lipseys.
How To Connect
📋 Phase 1: Create Your Lipsey’s Source
+
Create Source in Flxpoint
Go to Sources → + Add Source. Name it “Lipsey’s”. Choose your preferred Source Type and (optional) assign a vendor for reporting.
Choose Integration Type
On the Source page, click Start Creating Integrations and add Get Inventory (Primary). You can add Send Orders and Get Shipments later if needed.
Tip: Start with the primary inventory feed first; add additional flows once quantities/prices are verified.
🔐 Phase 2: Set Up the Lipsey’s Connection
+
Open “New Lipsey’s Connection”
In Step 1 of the Get Inventory (Primary) setup, click + New Connection. Use a clear Connection Name (e.g., “Lipsey’s API”).
Enter Credentials
Fill the fields exactly as provided by Lipsey’s:
- Fulfillment Email
- Fulfillment Password
- Dealer Email
- Dealer Password
Heads up: You can store both Dealer and Fulfillment credentials in one connection so the job can use the correct account later.
⚙️ Phase 3: Configure Settings
+
Choose Account Type (Dealer vs Fulfillment)
In Step 2 (Configure Settings), select Account Selection for Job:
- Dealer — ships to your store (dealer). Required for items/brands that don’t allow dropship and generally exposes the full catalog you’re authorized for.
- Fulfillment — ships direct-to-consumer (dropship). Keeps the flow focused on dropship-eligible items.
Important: You must pick one account type for this source. You cannot run both at the same time. Choose Dealer if you also stock at your store; choose Fulfillment if you only dropship.
Archive/Un-Archive Inventory (Optional)
Toggle Archive/Un-Archive Inventory if you want items missing from Lipsey’s feed to be archived (qty set to 0) and automatically un-archived when they return to the feed. Avoid enabling this here if you already rely on it in a Secondary feed for the same source.
✅ Phase 4: Mapping & Activation
+
Define a Mapping Template
In Step 3, select or create your template (e.g., Get Source Products 1). Map required fields such as SKU, Quantity, Price, and product details. Configure any Post Mapping Workflow rules you need.
Run & Schedule
Click Save and Complete. From the integration overview, you can Run Integration on demand or set a schedule to keep quantities fresh (runs use UTC by default).
Verify: After the first run, spot-check a few SKUs to confirm quantities and pricing match Lipsey’s.
Product Operations
Get Inventory (Primary)
Supported | Lipseys
Introduction to Lipseys — Get Inventory [Primary]
This integration retrieves the Lipseys catalog (products, pricing, quantity, images, categories) through Lipseys’ API and maps it into your Source Inventory. Use it to keep your product data and availability up to date.
The Lipseys Get Inventory [Primary] integration enables you to:
- Download the full Lipseys item catalog and on-hand Quantity.
- Import pricing (Current Price) and core identifiers (Item Number, UPC, Manufacturer, Model).
- Pull images and dimensions (lbs/inches) for merchandising and shipping rules.
- 1 Connect to Lipseys: Create a connection with Fulfillment Email/Password and Dealer Email/Password. Use Test Connection and Save Connection.
- 2 Configure Settings: Choose Account selection for job (e.g., Dealer Credential) and set Archive/Un-Archive Inventory behavior.
- 3 Define a Mapping Template: Select or create Get Source Products, then map Lipseys fields (Item Number, UPC, Current Price, Quantity, etc.).
- 4 Run or Schedule: On the Configure page, enable Scheduled or click Run Integration to fetch the latest feed.
Tip: If you also run a Secondary feed, enable Archive/Un-Archive in only one of the two jobs to avoid flip-flopping inventory states.
- Account selection for job: Select which credential set issues the API requests (e.g., Dealer Credential).
- Archive/Un-Archive Inventory: When enabled, items missing from the latest feed are archived (qty=0); returning items are un-archived.
- Scheduling: Run manually or schedule periodic syncs to keep quantity and pricing fresh.
- Post Mapping Workflow: Optional rules that run after mapping (Live/Draft) for enrichment or gating.
Note: Archiving is useful for suppliers that remove items from their feed when unavailable; reappearing items will auto-restore.
Interface Overview
- Screen labeled Get Source Products; actions: Delete, Duplicate, Save.
- Layout: From Value (Lipseys Product fields) → To Inventory Parent Field.
Core Parent Mappings (Recommended)
| Lipseys Field | Maps To | Example | Notes |
|---|---|---|---|
| Item Number | Parent SKU | LP-12345 | Primary product identifier/SKU. |
| UPC | Barcode (UPC) | 123456789012 | Use for channel listings and dedupe. |
| Manufacturer | Brand | GLOCK | Shown on PDP; helpful for filters. |
| Model | Title | G19 Gen5 | Combine with Caliber for richer titles. |
| Description 1 / 2 | Description | Text | Long/short description fields. |
| Current Price | Cost | 499.00 | Sale price if available; falls back to regular Price when sale missing. |
| Quantity | Quantity | 12 | On-hand units from Lipseys. |
| Shipping Weight | Weight (lbs) | 3.5 | Weight is in lbs. |
| Item Length / Width / Height | Dimensions (in) | 10 x 2 x 8 | Dimensions are in inches. |
| Caliber Gauge, Capacity, Finish, etc. | Attributes | 9mm, 15, Black | Saved as direct copy attributes. |
Images
Images are built from the feed’s
imageName header:https://www.lipseyscloud.com/images/%s ← where %s is the value from
imageName
The mapping UI exposes Lipseys fields such as Item Number, UPC, Manufacturer, Model, Description, Current Price, Quantity, and more under Lipseys Product. :contentReference[oaicite:1]{index=1}
Tip: If you need to flag FFL items, add a custom field and rule on
fflRequired (string-boolean) in your mapping template.-
Base URL:
https://api.lipseys.com/ -
Auth Token: Generated via
/api/Integration/Authentication/Loginby passing username/password for each configured account (Fulfillment/Dealer). - Account Selection: The job uses the token for the account type chosen in config.
-
Catalog Feed: Items are downloaded via
/api/Integration/Items/CatalogFeed(single file contains all product data). -
Images: Use
https://www.lipseyscloud.com/images/%swithimageNamefrom feed. - Pricing: Map Current Price to Cost (sale price if present; otherwise regular Price will appear).
| Capability | Status | Notes |
|---|---|---|
| Custom Fields | NOT SUPPORTED | Attributes are saved as direct copy. |
| Variations / Options | NOT SUPPORTED | Feed is single-SKU items. |
| Generic Pricing (& Currency) | SUPPORTED | Single pricing available in the feed. |
| Client Pricing (& Currency) | NOT SUPPORTED | Per-client price not provided. |
| Quantity | SUPPORTED | Real-time stock from feed. |
| Multiple Warehouses | NOT SUPPORTED | No warehouse breakdown. |
| Weights & Dimensions (& Units) | SUPPORTED | Weight in lbs; dimensions in inches. |
| Images | SUPPORTED | Single primary image per product. |
| Categories | SUPPORTED | Two-level categories available. |
| Delta vs Full Feed | FULL FEED | A full file is available each run. |
| Archive Support | SUPPORTED | Use the Archive/Un-Archive toggle in config. |
| Limitations | — | If a length arrives in mm, it is converted to inches. |
- 1 Add the Integration: Source ➜ Lipseys ➜ Get Inventory [Primary].
- 2 Create Connection: Enter Connection Name, Fulfillment Email/Password, Dealer Email/Password ➜ Test Connection ➜ Save Connection.
- 3 Configure: Set Account selection for job (e.g., Dealer) and the Archive/Un-Archive Inventory toggle.
- 4 Mapping Template: Choose or create Get Source Products 1 and map core fields (see above).
- 5 Automate: On the Configure page, switch Scheduled to Yes or use Run Integration to sync immediately.
- Auth failures: Check both Fulfillment and Dealer credentials and re-Test Connection.
- Empty results: Verify the Account selection for job matches the account that has access to the feed.
-
Images not showing: Confirm you’re building URLs using
imageNamewith the Lipseys cloud pattern. - Unexpected archiving: If both Primary and Secondary are archiving, disable the toggle in one job.
- Mapping gaps: Make sure Item Number → Parent SKU, Current Price → Cost, Quantity → Quantity, and UPC/Brand/Model are mapped.
Diagnostic Tip: Use Post Mapping Workflow in Draft to test rules before turning them Live.
-
Endpoints:
/Authentication/Loginfor token,/Items/CatalogFeedfor items. - Units: lbs & inches (we convert any mm to inches automatically).
- Pricing: Use Current Price as Cost (sale); feed falls back to regular price when no sale.
- Scheduling: Set a reasonable cadence to keep quantities fresh and reduce stockouts.
Pro Tip: Include UPC, Manufacturer, Model, and key attributes for better channel matching and search relevance.
Conclusion
Lipseys Get Inventory [Primary] keeps your catalog and availability current using Lipseys’ API. Connect with the correct account, map core fields, and schedule the job for continuous, reliable updates.
Get Inventory (Secondary)
Supported | Lipseys
Introduction to Lipseys — Get Inventory [Secondary]
The Lipseys Get Inventory [Secondary] integration imports delta updates (price & quantity) via API. Pair it with the Primary catalog job to keep your Source Inventory continuously accurate.
This job focuses on:
- Updating Quantity and pricing without re-pulling the full catalog.
- Creating missing variants on-the-fly if you enable Allow Create Variant.
- Working with the same connection used by your Lipseys API token.
- 1 Connect: Choose your existing Lipseys API Token connection and click Save and Proceed.
- 2 Configure Settings: Toggle Archive/Un-Archive Inventory, select Account selection for job, and optionally enable Allow Create Variant.
- 3 Define a Mapping Template: Pick your template (e.g., Lipseys Get Inventory 2) mapping Variant fields such as SKU, Cost, Quantity, MSRP/MAP, UPC.
- 4 Run / Schedule: On the Configure page, switch Scheduled to Yes or use Run Integration for an on-demand delta refresh.
Tip: Enable archiving in either Primary or Secondary—never both—to avoid churn on item state.
- Archive/Un-Archive Inventory: Items missing from the delta feed are archived (qty=0); returning items are un-archived.
- Account selection for job: Choose which credential (e.g., Dealer Credential) generates the token for requests.
- Advanced Settings → Allow Create Variant: Creates missing variants during Secondary runs.
- Scheduling: Automate frequent runs to keep stock & pricing fresh.
Note: Secondary updates only price & quantity; catalog attributes/images come from the Primary job.
Interface Overview
- Screen: Get Inventory [Secondary] ➜ choose Mapping Template and Save and Complete.
- Layout: From Value (Lipseys Inventory) → To Inventory Variant Field.
Recommended Variant Mappings
| Lipseys Inventory Field | Maps To (Variant) | Example | Notes |
|---|---|---|---|
| Item Number | SKU | LP-12345 | Primary variant identifier. |
| Current Price | Cost | 499.00 | Sale price used as cost; regular Price is used if no sale is present. |
| Quantity | Quantity | 12 | On-hand units. |
| Price | MSRP | 549.00 | Use when you want a list/compare-at reference. |
| Retail Map | MAP | 539.00 | Optional; set only if you enforce MAP. |
| Upc | UPC | 123456789012 | Useful for channel sync & dedupe. |
The Secondary template exposes fields such as Item Number, Current Price, Price, Quantity, Retail Map, Upc for mapping to variant-level targets. :contentReference[oaicite:1]{index=1}
-
Base URL:
https://api.lipseys.com/ -
Token: Generated per configured account via
/api/Integration/Authentication/Loginand used according to Account selection for job. -
Delta Feed:
/api/Integration/Items/PricingQuantityFeedsupplies price & quantity changes only. - Pricing Rule: Map Current Price to Cost (sale price). If there’s no sale, regular Price is returned/displayed.
Secondary keeps data lean by only fetching what changes most: stock and pricing. Pair with Primary for full catalog attributes/images.
Endpoints and behavior as described above come from the Lipseys Secondary operation notes. :contentReference[oaicite:2]{index=2}
| Capability | Status | Notes |
|---|---|---|
| Custom Fields (Variants Only) | NOT SUPPORTED | Custom fields are not available in this delta job. |
| Generic Pricing (& Currency) | SUPPORTED | Current Price/Price available. |
| Client Pricing (& Currency) | NOT SUPPORTED | Per-client pricing not provided. |
| Quantity | SUPPORTED | Real-time stock from delta feed. |
| Multiple Warehouses | NOT SUPPORTED | No warehouse breakdown. |
| Weights & Dimensions (& Units) | NOT SUPPORTED | Provided only by Primary feed. |
| Delta Feed vs Full Feed | SUPPORTED | This job is a delta feed for price & quantity. |
| Archive Support | SUPPORTED | Use the Archive/Un-Archive toggle in settings. |
- 1 Add the Integration: Source ➜ Lipseys ➜ Get Inventory [Secondary].
- 2 Connect: Select your Lipseys API Token connection ➜ Save and Proceed.
- 3 Configure: Set Archive/Un-Archive, pick Account selection for job, expand Advanced Settings to toggle Allow Create Variant if needed.
- 4 Mapping Template: Choose Lipseys Get Inventory 2 and map the recommended variant fields.
- 5 Automate: On the Configure page, enable Scheduled or use Run Integration to fetch deltas now.
- No updates importing: Confirm Account selection for job matches the credential with feed access and that your mapping template targets Variant fields (SKU/Cost/Quantity).
- Unexpected archiving: Ensure only one of Primary/Secondary has archiving enabled.
- Cost not updating: Verify Current Price → Cost is mapped (not Retail Map) and re-run.
- Variants missing: Turn on Allow Create Variant to build variants during the delta job.
Diagnostic Tip: If a product appears in Primary but not in Secondary, it may simply have no recent price/qty change.
-
Endpoints: Auth via
/api/Integration/Authentication/Login; delta via/api/Integration/Items/PricingQuantityFeed. - Scope: Pricing & quantity only—attributes/images come from Primary.
- Best practice: Schedule Secondary more frequently than Primary for timely stock & price accuracy.
Conclusion
Lipseys Get Inventory [Secondary] delivers fast, lightweight updates for price and quantity. Connect, set your job options, map the variant fields, and schedule frequent runs to keep your catalog accurate throughout the day.
Order Operations
Send Fulfillment Requests
Supported | Lipseys
Introduction — Send Fulfillment Requests
Yes, Lipseys supports submitting Purchase Orders (POs) / Fulfillment Requests (FRs) via API.
Routing depends on restricted manufacturer status and whether the item is a firearm.
- Automate order submission for firearms and non-firearms.
- Enforce restricted manufacturer rules (Dealer account only).
- Map your FR Number and line items directly to Lipseys’ API.
- Receive auto acknowledgements and surface supplier errors on the FR.
-
Restricted manufacturer →
/api/Integration/Order/APIOrder(requires Dealer account). -
Non-restricted firearm →
/api/Integration/Order/DropShipFirearm. -
Non-restricted non-firearm →
/api/Integration/Order/DropShip. - Auth — Token is passed with the request per the selected account (Dealer vs Fulfillment).
Restricted manufacturers (partial): AAC, Browning, Gemtech, GLOCK, IWI, Q, Trijicon, Winchester, FN/FN America, HK, Ruger (incl. Ruger Firearms), Smith & Wesson / S&W Firearms, Springfield / Springfield Armory, Walther / Walther Arms, Beretta, Taurus, Sig/Sig Sauer, CRKT/Columbia River Knife & Tool, Holosun, Glock, and others as listed by Lipseys.
- Send All Orders To the Address — choose a stored address or leave as None.
- Select Approved Brands — check each brand you are authorized to order.
-
Advanced Settings
- Hold for X Hours — delay sending FRs for manual review.
- Only Send During Business Hours — limit submissions to working hours.
Header → To Lipseys – Purchase Order Field
| From Value (example) | Maps To | Notes |
|---|---|---|
| Order/FR Number | Fulfillment Request Number | Primary identifier used on API order. |
| Customer Name | Name | Recipient/Ship-to name. |
| Shipping Method Code | Shipping Code | If applicable; Lipseys may auto-select shipping. |
| Ship-To Address Line 2 | Shipping Address Line2 | Second address line when present. |
Header → Fulfillment Request fields
| From Value (example) | Maps To | Type | Notes |
|---|---|---|---|
| FR Number | Fulfillment Request Number | Text | Unique per FR. |
| Estimated Dropship Fee | Estimated Dropship Fee | Number | Optional. |
| Estimated Shipping Cost | Estimated Shipping Cost | Number | Optional. |
Line Items → To Lipseys – Purchase Order Item Field
| From Value (example) | Maps To | Notes |
|---|---|---|
| Variant SKU | Item Number (SKU) | SKU is sent as item number (required). |
| Quantity | Qty | Ordered quantity per line. |
Tip: Keep FR Number consistent across header and shipment flows to ensure downstream linkage.
| Capability | Status | Notes |
|---|---|---|
| Fulfillment Request Number | SUPPORTED | Flx FR# can be mapped from template. |
| Customer Association | NOT SUPPORTED | Customer IDs are not passed. |
| FR Item Association | SUPPORTED | SKU is sent as item number. |
| Auto Acknowledgements | SUPPORTED | Success/failure returned; errors printed on FR. |
| Shipping Selection | NOT SUPPORTED | Shipping is auto-selected by supplier. |
| Custom Fields | NOT SUPPORTED | Additional CFs/attachments not supported. |
| Attachments | NOT SUPPORTED | Files cannot be attached to FRs. |
- 1Connect your Lipseys API Token.
- 2Configure Approved Brands and Advanced Settings.
- 3Select your Send Purchase Orders 2 mapping template.
- 4Run on-demand or enable Scheduled on the Configure page.
- “Not Authorized” — Verify you are using the correct account type (Dealer vs Fulfillment).
- Restricted brand failed — Use Dealer account; restricted SKUs can’t be dropshipped.
- Shipping method not applied — Lipseys auto-selects shipping for FRs.
Conclusion. Configure Approved Brands, map FR header + item fields, and rely on the routing rules above to submit compliant orders to Lipseys.
Get Shipments
Supported | Lipseys
Introduction — Get Shipments
Yes, Lipseys supports retrieving daily shipment confirmations and tracking via API.
Tracking is linked back to the FR/PO you submitted during Send FR.
- Fetch shipment records for the previous business day.
- Record carrier/service and tracking number.
- Associate shipments to the original FR Number at the PO level.
- Endpoint:
/api/Integration/Shipping/OneDay. - Auth token used per configured account type.
- FR# is used to match the shipment back to the order.
API Restriction: Run once per day and target the previous day's invoices. Setting a lookback other than
1 day is ignored by the endpoint.-
Fetch Shipments Within Last X Days — set to
1(required by Lipseys). - Mapping Template — choose Lipseys Get Shipments 2 (or your copy).
- Scheduling — enable daily schedule to retrieve the prior day’s shipments.
| From Value (example) | To Shipment Field | Notes |
|---|---|---|
| Shipping Service | Carrier (via Rules) | Map service strings to canonical carriers (e.g., “FedEx Ground” → “FedEx”). |
| Tracking Number | Tracking Number | Primary tracking identifier. |
| FR Number | Fulfillment Request Number | Used to associate shipments to orders. |
Sample Rule (normalize carriers)
IF Shipping Service CONTAINS "FedEx" THEN Carrier = "FedEx"
ELSE IF Shipping Service CONTAINS "UPS" THEN Carrier = "UPS"
ELSE IF Shipping Service CONTAINS "USPS" OR "Postal" THEN Carrier = "USPS"
| Capability | Status | Notes |
|---|---|---|
| Carrier & Methods | SUPPORTED | Carrier & tracking are returned. |
| Shipment Item Association | SUPPORTED | SKU is present in response. |
| Partial Shipments | NOT SUPPORTED | Single shipment at PO level. |
| Invoice Information | NOT SUPPORTED | Not returned in feed. |
| Custom Fields (CFs) | NOT SUPPORTED | No CFs available. |
- No shipments returned — ensure you run the job the day after invoices are generated.
-
Lookback not honored — set “Fetch within X days” to
1. - Carrier values inconsistent — add normalization rules to map Shipping Service to Carrier.
Conclusion. Schedule this job daily to capture yesterday’s shipments and keep your orders updated with accurate tracking at the PO level.