Lipsey’s is a leading firearms' distributor, providing licensed dealers with a wide range of firearms, ammunition, and shooting accessories from top manufacturers, including exclusive and limited-edition models.
How To Connect
📋 Phase 1: Create the Source
+
Open Fulfillment Sources
In Flxpoint, go to Connections > Fulfillment Sources and click + Add Source.
Name & Select from Directory
Name it Lipsey’s, then select Lipsey’s in the FLX Supplier Directory and click Continue.
Tip: Keep the source name simple (e.g., “Lipsey’s”) so reports and filters stay clean.
Save the Source
Click Save Connection to create the source record.
🔐 Phase 2: Connection & Credentials
+
Create a New Connection
When prompted to authenticate, click + New Connection and use a clear 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: Storing both Dealer and Fulfillment credentials in one connection is supported; the jobs will use what they need.
⚙️ Phase 3: Add Required Jobs
+
Add Integrations
From the source, click Start Creating Integrations and add:
- Get Inventory (Primary) — imports the product catalog and core attributes.
- Get Pricing & Quantity — keeps price and stock up to date.
- Send Orders — sends orders to Lipsey’s for fulfillment.
- Get Shipments — pulls tracking and shipment status.
Recommended order: Run Get Inventory (Primary) first, then enable Get Pricing & Quantity. Add Send Orders and Get Shipments after you’ve verified items and prices.
🧩 Phase 4: Mapping Template
+
Select or Create Template
In Get Inventory (Primary) Step 3, select or create your mapping template (e.g., Get Source Products 1).
Map Required Fields
At minimum, map:
- SKU (unique identifier)
- Quantity
- Price / Cost (as applicable)
- Title / Description
- UPC / GTIN (if available)
Tip: Use a consistent SKU prefix if needed (e.g., “LIP-”) to quickly identify items from this source.
✅ Phase 5: Run & Schedule
+
First Runs
Click Save and Complete, then Run Integration for Get Inventory (Primary). After items appear, run Get Pricing & Quantity.
Scheduling
Set a schedule for each job (runs use UTC). Many teams run Get Pricing & Quantity more frequently than the full inventory job.
Verify: Spot-check a few SKUs against Lipsey’s portal for price/qty accuracy before enabling Send Orders and Get Shipments.
Product Operations
Get Inventory and Pricing & Quantity
Supported | Lipseys
Introduction to Lipseys — Get Inventory and Pricing & Quantity
This guide merges the former Get Inventory [Primary] and Get Inventory [Secondary] into one experience. Use it to pull the full catalog (products, images, attributes) and keep pricing & quantity updated via a lightweight delta feed.
The Lipseys integration enables you to:
- Import the complete catalog (identifiers, attributes, images, dimensions, categories).
- Keep Current Price and Quantity fresh with fast delta updates.
- Map data into your Source Inventory using flexible parent/variant templates.
- 1 Connect: Create a connection with Fulfillment Email/Password and Dealer Email/Password. Use Test Connection then Save Connection.
-
2 Choose Job Type(s):
-
Catalog (Full): Uses
/api/Integration/Items/CatalogFeedto load products & media. -
Pricing & Quantity (Delta): Uses
/api/Integration/Items/PricingQuantityFeedfor rapid cost/stock updates.
-
Catalog (Full): Uses
- 3 Map Data: Use the Catalog (Parent) template for product info and the Pricing & Quantity (Variant) template for SKUs, cost, and quantity.
- 4 Run / Schedule: Execute on demand or schedule each job. Run Pricing & Quantity more frequently.
Tip: Enable Archive/Un-Archive Inventory in only one of the two jobs to avoid flip-flopping item states.
- Account selection for job: Choose which account (e.g., Dealer) issues the token for requests.
- Archive/Un-Archive Inventory: Items missing from a run are archived (qty=0); returning items are un-archived.
- Advanced → Allow Create Variant (for Pricing & Quantity): Creates missing variants on the fly.
- Scheduling: Set separate cadences; run Pricing & Quantity more often than Catalog.
- Post Mapping Workflow: Optional Live/Draft rules for enrichment or gating after mapping.
Note: Keep archiving toggled on exactly one job (Catalog or Pricing & Quantity).
- 1 Add the Integration: Source ➜ Lipseys ➜ Get Inventory and Pricing & Quantity.
- 2 Create Connection: Enter Connection Name, Fulfillment & Dealer credentials ➜ Test Connection ➜ Save Connection.
-
3 Configure Jobs:
- Catalog (Full): Select Account selection and set Archive/Un-Archive as desired.
- Pricing & Quantity (Delta): Select Account selection, optionally enable Allow Create Variant.
-
4 Mapping Templates:
- Catalog (Parent): Map product attributes, media, dimensions.
- Pricing & Quantity (Variant): Map SKU, Cost (Current Price), MSRP/Price, MAP, Quantity, UPC.
- 5 Automate: Toggle Scheduled per job or click Run Integration for immediate syncs.
Interface Overview
- Templates list actions: Delete, Duplicate, Save.
- Columns: From Value (Lipseys) → To Field (your Inventory).
- Enable/Disable toggles: Control which fields are sent. This is the key difference between Catalog (Parent) and Pricing & Quantity (Variant) templates.
Catalog (Parent) — Recommended Mappings
| Lipseys Field | Maps To (Parent) | Example | Notes |
|---|---|---|---|
| Item Number | Parent SKU | LP-12345 | Primary catalog identifier. |
| UPC | Barcode (UPC) | 123456789012 | Useful for channels & dedupe. |
| Manufacturer | Brand | GLOCK | Shown on PDP; filterable. |
| Model | Title | G19 Gen5 | Combine with attributes for richer titles. |
| Description 1 / 2 | Description | Text | Long/short descriptions. |
| Shipping Weight | Weight (lbs) | 3.5 | Units in lbs. |
| Item Length / Width / Height | Dimensions (in) | 10 × 2 × 8 | Units in inches. |
| Caliber Gauge, Capacity, Finish, … | Attributes | 9mm, 15, Black | Saved as direct-copy attributes. |
| imageName | Image URL | …/images/ABC.jpg | Use https://www.lipseyscloud.com/images/%s. |
Pricing & Quantity (Variant) — Recommended Mappings
| Lipseys Inventory Field | Maps To (Variant) | Example | Notes |
|---|---|---|---|
| Item Number | SKU | LP-12345 | Variant identifier. |
| Current Price | Cost | 499.00 | Sale cost; falls back to Price if no sale. |
| Price | MSRP | 549.00 | Optional compare-at/list reference. |
| Retail Map | MAP | 539.00 | Map only if you enforce MAP. |
| Quantity | Quantity | 12 | On-hand units. |
| Upc | UPC | 123456789012 | For channels & dedupe. |
Images (Catalog)
Build image URLs using the feed’s
imageName value:https://www.lipseyscloud.com/images/%s
Practice: Enable/Disable
Catalog (Parent): Toggle sending Model → Title
Pricing & Quantity (Variant): Toggle sending Current Price → Cost
Catalog (Full)
-
Base URL:
https://api.lipseys.com/ -
Auth:
/api/Integration/Authentication/Login(per selected account). -
Feed:
/api/Integration/Items/CatalogFeed(single file with products, attributes, images). - Units: Weight in lbs; dimensions in inches (mm converted to inches).
Pricing & Quantity (Delta)
-
Base URL:
https://api.lipseys.com/ - Auth: same login endpoint, token per account selection.
-
Feed:
/api/Integration/Items/PricingQuantityFeed(price & quantity changes only). - Rule: Map Current Price to Cost; fallback to regular Price when no sale.
| Capability | Status | Notes |
|---|---|---|
| Custom Fields | NOT SUPPORTED | Attributes saved as direct copy. |
| Variations / Options | NOT SUPPORTED | Feed is single-SKU items. |
| Generic Pricing (& Currency) | SUPPORTED | Current Price/Price available. |
| Client Pricing (& Currency) | NOT SUPPORTED | Per-client pricing not provided. |
| Quantity | SUPPORTED | Real-time stock from feeds. |
| Multiple Warehouses | NOT SUPPORTED | No warehouse breakdown. |
| Weights & Dimensions (& Units) | SUPPORTED | From Catalog feed. |
| Images | SUPPORTED | From Catalog feed (primary image per product). |
| Delta vs Full Feed | SUPPORTED | Use Catalog for full; Pricing & Quantity for deltas. |
| Archive Support | SUPPORTED | Toggle in configuration (use on one job only). |
- Auth failures: Re-check Fulfillment & Dealer credentials, then Test Connection.
- No updates: Confirm the job type matches your goal (Catalog vs Pricing & Quantity) and templates target the correct Parent/Variant fields.
- Cost not updating: Verify Current Price → Cost is enabled in the Variant template.
- Unexpected archiving: Ensure archiving is enabled in only one job.
-
Images missing: Confirm image URLs are built with
imageNameand the Lipseys cloud pattern. - Variants missing: Enable Allow Create Variant in the Pricing & Quantity job.
Diagnostic Tip: Test Post Mapping Workflow in Draft before going Live.
-
Endpoints:
/api/Integration/Authentication/Login,/api/Integration/Items/CatalogFeed,/api/Integration/Items/PricingQuantityFeed. - Units: lbs & inches (mm auto-converted to inches).
- Pricing: Use Current Price for Cost (sale); fallback to Price otherwise.
- Scheduling: Run Pricing & Quantity more frequently to minimize stockouts and stale prices.
Pro Tip: Include UPC, Manufacturer, Model, and key attributes for better channel matching and search relevance.
Conclusion
Get Inventory and Pricing & Quantity unifies full-catalog import and delta updates for Lipseys. Connect once, map Parent and Variant templates with the proper enable/disable settings, then schedule each job for dependable, up-to-date products, pricing, and availability.
Order Operations
Send Orders
Supported | Lipseys
Introduction to Send Orders
Submit orders to Lipseys via API. Routing depends on restricted manufacturer status and whether the item is a firearm. The integration returns acknowledgements and surfaces errors on the order record.
The Lipseys Send Orders integration enables you to:
- Automate submission for firearms and non-firearms.
- Respect restricted-manufacturer rules (Dealer account required).
- Map your Order Number and line items directly to Lipseys.
- Receive auto-acks and surface supplier errors on the order.
The integration follows these steps:
-
1 Authenticate: Obtain a token via
/api/Integration/Authentication/Loginfor the selected account (Dealer or Fulfillment). -
2 Route: Based on brand and item type:
-
Restricted manufacturer →
/api/Integration/Order/APIOrder(requires Dealer account). -
Non-restricted firearm →
/api/Integration/Order/DropShipFirearm. -
Non-restricted non-firearm →
/api/Integration/Order/DropShip.
-
Restricted manufacturer →
- 3 Build Payload: Include Order Number (your reference), ship-to, and lines (Item Number, Qty).
- 4 Map & Send: Use the mapping template to align your header/line fields to Lipseys and submit.
- 5 Receive Ack: Success or error details are returned and shown on the order.
- 6 Execution: Run on-demand or schedule (e.g., every 15–60 minutes).
Pro Tip: Maintain an Approved Brands list to avoid restricted-brand failures.
Note: Token/account selection determines which endpoints you can access.
Customize the integration with these settings:
- Send All Orders To the Address: Choose a stored address or leave None.
- Select Approved Brands: Check each brand you are authorized to order.
- Account Selection for Job: Dealer vs Fulfillment (impacts routing eligibility).
-
Advanced Settings:
- Hold for X Hours: Delay submissions for manual review.
- Only Send During Business Hours: Restrict to working hours.
- Scheduling: Run manually or schedule at your preferred cadence.
Note: Restricted brands require a Dealer token and the
APIOrder endpoint.
Follow these steps:
- 1 Add the Integration: Source > Lipseys > Integrations > Send Orders.
- 2 Create/Select Connection: Use your Lipseys credentials to generate a token.
- 3 Configure Settings: Approved Brands, Account selection, Advanced Settings, Scheduling.
- 4 Create Mapping Template: Map Order header and line fields (see details below).
- 5 Run: Click Run Sync or enable scheduling.
Mapping templates control which order data is sent to Lipseys.
Interface Overview
- Screen labeled “Send Orders”; name your template (e.g., “Lipseys Send Orders 1”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Your fields (left) → Lipseys fields (right).
Mapping Options
- Enable: Send the field (e.g., Order Number).
- Disable: Ignore the field.
- Required Fields: Order Number, Item Number (SKU), Quantity.
Order Number Requirement
The Order Number must be mapped to identify the order.
- Required Field: Order Number uniquely identifies the order on Lipseys.
-
Error Scenario: Unmapped Order Number may cause:
Invalid request: Missing required field 'Order Number' for order submission
- Fix: Go to Source > Lipseys > Templates > Send Orders > Field Mapping, enable Order Number, save, and re-run.
Recommendation: Always enable Order Number and Item Number (SKU) for reliable order syncing.
Complete Field Mappings
Header
| Your Field | Maps To | Type | Notes |
|---|---|---|---|
| Order Number | Fulfillment Request Number | Text | Primary identifier sent on the order. |
| Customer/Recipient Name | Name | Text | Ship-to name. |
| Shipping Method Code | Shipping Code | Text | Optional; Lipseys may auto-select shipping. |
| Address Line 2 | Shipping Address Line2 | Text | Optional second address line. |
| Estimated Dropship Fee | Estimated Dropship Fee | Number | Optional. |
| Estimated Shipping Cost | Estimated Shipping Cost | Number | Optional. |
Lines
| Your Field | Maps To | Type | Notes |
|---|---|---|---|
| Variant SKU | Item Number | Text | Required. Your SKU → Lipseys Item Number. |
| Quantity | Qty | Number | Required. Ordered quantity per line. |
Practice Mapping
Try enabling/disabling Order Number:
Be aware of these limitations:
- Shipping Selection: Not supported; Lipseys may auto-select shipping.
- Attachments/Custom Fields: Not supported on orders.
-
Restricted Brands: Require Dealer token and
APIOrder.
- “Not Authorized”: Ensure correct account type (Dealer vs Fulfillment) and token.
- Restricted brand failed: Use Dealer account; restricted SKUs cannot be dropshipped.
- Shipping method not applied: Lipseys auto-selects shipping; mapping is optional.
- Line rejects: Verify Item Number (SKU) is valid for Lipseys.
Diagnostic Tip: Log and review the response; errors are echoed back on the order.
Key information:
-
Endpoints:
/api/Integration/Authentication/Login,/api/Integration/Order/APIOrder,/api/Integration/Order/DropShip,/api/Integration/Order/DropShipFirearm. - Required Fields: Order Number, Item Number (SKU), Quantity.
- Brand Rules: Use Approved Brands to prevent restricted routing errors.
Pro Tip: Schedule sends shortly after inventory/pricing syncs to reduce cancellations.
Conclusion
Send Orders automates compliant order submission to Lipseys. Configure routing via account/brand rules, map required fields, and schedule sends for smooth, auditable purchasing.
Get Shipments
Supported | Lipseys
Introduction to Get Shipments
Retrieve daily shipment confirmations and tracking via API. Tracking links back to the order you submitted during Send Orders.
The Lipseys Get Shipments integration enables you to:
- Fetch shipment records for the previous business day.
- Capture carrier/service and tracking number.
- Associate shipments to the original Order Number.
The integration follows these steps:
-
1 Authenticate: Obtain a token via
/api/Integration/Authentication/Login. -
2 Fetch: Call
/api/Integration/Shipping/OneDayto retrieve the prior day’s shipments. - 3 Map: Normalize carrier/service, store tracking, and link by Order Number.
- 4 Execution: Run daily on a schedule.
API Restriction: The endpoint returns only the previous day’s invoices; lookbacks other than
1 day are ignored.
Customize the integration with these settings:
-
Fetch Within Last X Days: Set to
1(required by Lipseys endpoint). - Mapping Template: Choose “Lipseys Get Shipments 2” (or your copy).
- Scheduling: Enable daily schedule to retrieve the prior day’s shipments.
Note: Normalize service strings (e.g., “FedEx Ground”) to canonical carriers to keep reporting tidy.
Follow these steps:
- 1 Add the Integration: Source > Lipseys > Integrations > Get Shipments.
- 2 Select Connection: Use your Lipseys token-enabled connection.
-
3 Configure Settings: Set lookback to
1day and scheduling to daily. - 4 Create Mapping Template: Configure field mappings (see details below).
- 5 Run: Start with Run Sync or let the schedule run.
Mapping templates control which shipment data is imported.
Interface Overview
- Screen labeled “Get Shipments”; name your template (e.g., “Lipseys Get Shipments 2”).
- Buttons: Delete, Duplicate, Save Mapping.
- Columns: Lipseys shipment fields (left) → your system fields (right).
Mapping Options
- Enable: Send the field (e.g., Tracking Number).
- Disable: Ignore the field.
- Required Fields: Tracking Number, Order Number (for association).
Complete Field Mappings
Shipment Header
| Lipseys Field | Maps To | Notes |
|---|---|---|
| Shipping Service | Carrier (via rules) | Normalize strings to FedEx/UPS/USPS, etc. |
| Tracking Number | Tracking Number | Primary tracking identifier. |
| FR / Order Number | Order Number | Used to link shipment to the originating order. |
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"
Be aware of these limitations:
- Lookback: Endpoint returns only the previous day; custom ranges are ignored.
- Partial Shipments: Not supported (single shipment at PO level).
- Invoice Details: Not returned in this feed.
- Custom Fields: Not supported.
- No shipments returned: Run the job the day after invoices are generated.
-
Lookback not honored: Ensure “Fetch within X days” is set to
1. - Carrier values inconsistent: Add normalization rules for Shipping Service → Carrier.
Diagnostic Tip: Log raw responses to validate carrier/service text patterns before writing rules.
Key information:
-
Endpoint:
/api/Integration/Shipping/OneDay. -
Auth: Token from
/api/Integration/Authentication/Login. - Schedule: Run daily after Lipseys invoices are posted.
Pro Tip: Pair with Send Orders so tracking writes back promptly to the originating order.
Conclusion
Get Shipments retrieves yesterday’s shipments with carrier and tracking details. Schedule it daily and use mapping rules to keep tracking tidy and correctly linked to orders.