Flxpoint Knowledge

Contact us

Orion Wholesale as Source

Table of Contents

How to Connect Product Operations Order Operations

Orion Wholesale is a leading wholesale distributor specializing in firearms, ammunition, outdoor gear, and tactical equipment for retailers across the United States. Known for their extensive inventory and reliable fulfillment services, Orion serves as a trusted supplier for gun stores, sporting goods retailers, and outdoor equipment dealers. Their robust API integration capabilities allow retailers to seamlessly sync inventory, automate order processing, and receive real-time shipment tracking updates. By connecting Orion Wholesale to Flxpoint, retailers can streamline their dropshipping operations and maintain accurate inventory levels across multiple sales channels.

 

How to Connect

📋 Phase 1: Creating Your Orion Wholesale Source +
Create Source in Flxpoint
Log into your Flxpoint account, navigate to the Sources tab, and click + Add Source to begin setting up your Orion Wholesale integration.
Configure Source Details
In the Create Source form:
  • Source Name: Enter "Orion Wholesale as Source" (or your preferred name)
  • Source Type: Select Vendor Warehouse as shown in the interface
  • Vendor Assignment: Choose Yes (Recommended) to enable vendor order fulfillment reporting and set up a vendor portal
Click Save & Next to proceed to the next step.
Benefits: Selecting "Yes" for vendor assignment provides better reporting capabilities and allows you to set up a vendor portal for Orion Wholesale.
Choose Integration Type
After creating your source, you'll see the Integrations section. Click Start Creating Integrations to begin. You can set up the following integrations:
  • Get Inventory (Primary): Main inventory feed from Orion Wholesale
  • Get Inventory (Secondary): Additional inventory data if needed
  • Send Fulfillment Requests: Send orders to Orion for fulfillment
  • Get Shipments: Retrieve tracking and shipment updates
🔐 Phase 2: Setting Up Orion Connection +
Obtain Orion API Credentials
To connect to Orion Wholesale, you'll need your API credentials. Contact Orion Wholesale support or your account manager to obtain:
  • API Key: Your unique API access key
  • Additional API Key: Secondary key if required
  • Any other authentication details specific to your Orion account
Important: Keep your API credentials secure and never share them publicly. These provide access to your Orion Wholesale account data.
Create New Orion Connection
In the integration setup, select Orion as your integration type. When prompted, click Create Connection and fill out the New Orion Connection form:
  • Connection Name: Enter a descriptive name (e.g., "Orion Main Connection")
  • API Key: Enter your primary Orion API key
  • API Key: Enter your secondary API key if provided
Click Test Connection to verify the credentials work, then Save Connection to proceed.
Troubleshooting: If the connection test fails, double-check your API keys and ensure your Orion account has API access enabled.
⚙️ Phase 3: Configure Integration Settings +
Configure Get Inventory Settings
In the Configure Settings step, you'll see options for inventory management:
  • Archive/Un-archive Inventory: Toggle Yes to enable automatic inventory archiving
  • This feature archives inventory not found in Orion's feed (sets quantity to zero) and un-archives it when it returns
  • Recommended setting: Yes - helps maintain accurate inventory levels
Note: Don't enable this setting if you already have Get Inventory (Secondary) enabled for this source, as noted in the interface.
Set Up Automation
Configure how the integration will run:
  • Manual vs Automated: Choose whether to run integrations manually or on a schedule
  • Scheduling: If automated, set your preferred sync frequency (hourly, daily, etc.)
  • Toggle Scheduled to Yes for automatic updates
Click Save and Proceed when configured.
🗺️ Phase 4: Field Mapping and Completion +
Define Mapping Template
In the Define a Mapping Template step:
  • Select an existing template from the dropdown (e.g., "Orion - Get Inventory [Primary] 1")
  • Or click Create New Mapping Template to build a custom mapping
  • Map essential fields like SKU, Price, Quantity, Description, and any other relevant product data
Configure Post Mapping Workflow
Set up workflow rules for your inventory data:
  • Workflow Status: Choose between Live or Draft
  • Live: Products will be immediately available in your system
  • Draft: Products will require manual approval before going live
  • Create workflow rules by clicking Create your first rule or Add Rule
Recommendation: Start with "Draft" mode for initial testing, then switch to "Live" once you're confident in the data mapping.
Complete Setup and Activate
Finalize your Orion Wholesale integration:
  • Review all settings in the summary view
  • Ensure all three steps show as completed: Connected ✓, Configured ✓, Mapped ✓
  • Click Save and Complete to activate the integration
  • Use Run Integration to perform a manual sync and test the setup
Next Steps: Monitor the integration status and check for any notifications. The initial inventory sync may take some time depending on your product catalog size.

 

 

Product Operations

Get Inventory (Primary)

Supported | Orion Wholesale – Get Inventory [Primary]

Introduction to Orion Wholesale – Get Inventory [Primary]
Yes, the Orion Wholesale – Get Inventory [Primary] integration allows you to pull live product, pricing, and quantity data from Orion’s API directly into your catalog. This keeps stock levels up‑to‑date and ensures accurate product information across your connected sales channels.

The Orion Wholesale – Get Inventory [Primary] integration is designed to:
  • Retrieve Orion’s full product catalog—including cost, sale price, and in‑stock quantities—via secure API calls.
  • Populate or update your products in Flxpoint, mapping Orion fields (e.g., Product Code, Quantity, Sale Price) to your catalog fields.
  • Optionally archive products that no longer appear in Orion’s feed, preventing outdated listings on your storefront.

The integration follows a three‑step API workflow:
  • Authenticate: Each request includes your x-connection-key header value supplied by Orion.
  • Call End‑points: The process cycles through Orion’s API methods:
    • get_catalog – fetches product basics.
    • get_catalog_inventory – returns live quantities.
    • get_product_categories and get_manufacturers – enrich category and brand data.
  • Merge & Map: The responses are merged by SKU, mapped with your template, and saved to your catalog. When Archive / Un‑Archive is enabled, any SKU missing from the feed is archived with quantity 0 until it reappears.
Base URL: https://orionflsales.com/api.php

Before your first run, adjust the following settings:
  • Connection Key: Enter the key supplied by Orion. It is sent as x-connection-key in the header.
  • Archive / Un‑Archive Inventory: When enabled, SKUs not returned by Orion will be archived (quantity 0) and automatically re‑activated if they return.
  • Scheduling: Toggle Scheduled to Yes if you want the job to run automatically (UTC‑based).
Tip: If you enable Archive / Un‑Archive here, do not enable it again in a Secondary feed for the same source.

Follow these steps to complete setup:
  • 1 Connect Integration: Choose Orion as the integration type and select or create your API connection with the key.
  • 2 Configure Settings: Toggle Archive / Un‑Archive Yes if desired, then click Save and Proceed.
  • 3 Define a Mapping Template: Select the default template (Orion – Get Inventory [Primary] 1) or build a new one.
  • 4 Post‑Mapping Workflow (Optional): Add rules to transform data after mapping.
  • 5 Test Run: Click Run Integration to verify that products import correctly.
  • 6 Enable Schedule: Switch Scheduled to Yes and click Update to automate future runs.

The setup screen displays three progress markers:
  • Connected – API connection established.
  • Configured – Settings saved.
  • Mapped – Mapping template assigned.
Under Automate, toggle Scheduled to enable or disable the job schedule.

Below are common field mappings you may use:
Field Maps To Example Purpose Status
Product Code (T) SKU OR‑12345 Product identifier Required
Quantity (N) On‑Hand Qty 15 Available stock Required
Sale Price (N) Cost 27.80 Your purchase cost Optional
Weight (N) Weight lb 1.2 Shipping weight Optional
Manufacturer (T) Brand Glock Brand name Optional
Tip: Use a rule to concatenate Category 1, Category 2, and Category 3 into a single Category field if needed.

Capability Status Notes
Custom Fields Not Supported —
Variations / Options Not Supported Single‑SKU only
Client Pricing Supported Price is returned in Sale Price field
Quantity Supported Pulled from get_catalog_inventory
Weights & Dimensions Supported Height, Length, Width, Weight fields available

  • 401 Unauthorized: Verify your connection key in the API header.
  • Empty Inventory: Ensure the key has catalog permissions and that SKUs have inventory in Orion.
  • Categories Missing: Orion returns categories as comma‑separated text; confirm your mapping rules split them correctly.

  • Current Status: Integration is fully operational and can be automated.
  • Archive / Un‑Archive applies to products missing from the latest feed.
  • All jobs run in UTC; adjust your schedule accordingly.

Conclusion
With Orion Wholesale – Get Inventory [Primary], you keep your catalog accurate by importing real‑time stock, pricing, and product data. Once configured and scheduled, this integration runs automatically—helping you maintain up‑to‑date listings without manual intervention.
 
 

Get Inventory (Secondary)

Supported | Orion – Get Inventory [Secondary]

Introduction to Orion – Get Inventory [Secondary]
The Orion – Get Inventory [Secondary] integration pulls delta-level inventory updates (SKU, quantity, sale price) from Orion Wholesale’s API into your catalog. Use it to update on-hand quantities and client pricing without touching your master catalog details. Secondary runs after the Primary sync – giving you fresher stock data while keeping product attributes intact.

  • Retrieve incremental inventory from Orion (productCode, quantity, salePrice).
  • Map incoming data to Flxpoint SKU, Quantity On Hand, and Client Price.
  • Automate stock & price refreshes without overriding catalog attributes.

  1. API Call – GET https://orionfflsales.com/api.php?method=get_catalog_inventory
    Header Connection-Key: {Your Key}
  2. Response – returns objects like:
    [
      { "productCode": "OR-1258", "quantity": 4, "salePrice": 279.95 }
    ]
  3. Mapping – productCode ➜ SKU, quantity ➜ Qty On Hand, salePrice ➜ Client Price.
  4. Catalog Update – Flxpoint adjusts stock / price (delta feed).
Delta feeds are lighter & faster – perfect for frequent syncs while Primary handles full catalog loads.

  • Connection Key – copy from your Orion portal.
  • Allow Create Variant – toggle Yes if new SKUs may appear as variants.
  • Archive/Un-Archive – keep OFF (Primary already controls archival).
  • Schedule – set frequency (hourly / daily) once you’re comfortable with sync speed.

  • 1Connect an Integration – choose Orion – API, paste your Connection Key, then Save and Proceed.
  • 2Configure Settings – confirm Allow Create Variant toggle and leave Archive disabled.
  • 3Define a Mapping Template – select Orion – Get Inventory [Secondary] 2 (or create new).
  • 4Schedule – enable job scheduling once test runs look good.

Core Field Mapping
Orion Field Maps To Example Purpose Status
productCode (T) Flxpoint Product → SKU OR-1258 Unique identifier Required
quantity (N) Flxpoint Product → Quantity On Hand 4 Current stock level Required
salePrice (N) Flxpoint Product → Client Price 279.95 Dealer cost / sale price Optional
Mapping Options
  • Field – point to Orion field (default).
  • Value – force a static value (e.g., set Quantity to 0 for close-outs).
  • Rules – create conditions (e.g., if quantity < 1 then set inventory to 0).

  • Feed Type – Delta feed (returns only SKU, quantity, salePrice).
  • Archive Support – Not supported; rely on Primary for archival.
  • Connection Error 401 – invalid Connection-Key.
Tip: If you see quantities that never change, double-check that Primary isn’t overwriting Secondary job runs.

  • 401 Unauthorized – confirm Connection Key.
  • No Data Returned – ensure method get_catalog_inventory is enabled for your key.
  • Stock Not Updating – check schedule logs; Secondary must finish after Primary.

Conclusion
Orion – Get Inventory [Secondary] gives you lightweight, frequent stock & price updates without altering core product data. Map the three key fields, schedule your job, and enjoy near-real-time inventory accuracy.
 
 

 


Order Operations

Send Fulfillment Requests

Supported | Orion – Send Fulfillment Requests

Introduction to Orion – Send Fulfillment Requests
The Orion – Send Fulfillment Requests integration converts your Flxpoint fulfillment requests (FRs) into Orion purchase orders (POs) and delivers them to Orion’s API for processing. It supports Customer, Dealer, and FFL order types, optional holds for manual review, and scheduling within business hours.

  • Generate Orion‑formatted POs from Flxpoint fulfillment requests.
  • Send POs to Orion’s endpoint with your x-connection-key header.
  • Automate order flow while keeping control via hold windows and business‑hour options.

  1. Collect Data – Flxpoint pulls FR header, shipping, and item details.
  2. Map Fields – Your mapping template aligns FR fields to Orion PO fields (see table below).
  3. Build JSON – The integration packages data like:
    { "method": "send_po", "orderType": "Customer", "poNumber": "FR-10234", "shipTo":{...}, "items":[{"productCode":"OR-112","qty":2}] }
  4. POST Request – POST https://orionfflsales.com/api.php with header x-connection-key.
  5. Processing + Notifications – Orion returns a success/failed status; Flxpoint logs the response and, if enabled, emails you.
Endpoint: https://orionfflsales.com/api.php  |  Method: send_po

  • Order Type – Choose Customer (default), Dealer, or FFL. Mapping template can override.
  • Hold for X Hours – Delay send to let staff review the PO.
  • Send During Business Hours – Restrict transmissions to your defined window.
  • Scheduling – Once mapped, enable the schedule to automate dispatch.

  • 1Connect – Select Orion – API, paste your connection key, click Save and Proceed.
  • 2Configure Settings – Pick Order Type, add hold or business‑hour rules if needed.
  • 3Create Mapping Template – Map FR → Orion PO fields (use starter template Send Purchase Orders 2).
  • 4Test Send – Click Run Integration with one order to verify acceptance.
  • 5Schedule – Toggle Scheduled = Yes and click Update.

Core Field Mapping
Flxpoint Field Orion PO Field Example Purpose Status
Fulfillment Request Number (T) PO Number FR‑10234 Order identifier at Orion Required
Shipping Address: Full Name (T) Ship To Name John Smith Recipient Required
Shipping Address: Address Line 1 (T) Ship To Address1 123 Elm St Street Required
Shipping Address: City (T) Ship To City Dallas City Required
Shipping Address: State Code (T) Ship To State TX State Required
Shipping Address: Postal Code (T) Ship To Zip 75201 ZIP Required
Source Shipping Method: Shipping Code (T) Ship Via Code UPS-GND Carrier/service Optional
Fulfillment Request: Note (T) Ship Instructions Leave at back door Special instructions Optional
FR Item: SKU (T) Item Number OR‑112 Product identifier Required
FR Item: Quantity (N) Quantity 2 Qty ordered Required
FR Item: Cost (N) Unit Price 139.98 Dealer cost Optional
Tip: Add a rule that concatenates Phone with Note to include customer contact info in Ship Instructions.

  • 401 Unauthorized – Verify x-connection-key.
  • Missing Order Type – Ensure template or settings supply orderType.
  • Hold Not Releasing – Double‑check Hold for X Hours isn’t blank or set too high.

  • Integration supports Customer, Dealer, FFL order types.
  • Jobs run on UTC schedule; adjust business‑hour window accordingly.
  • Price sent is Cost from FR Item; Retail is ignored.

Conclusion
Orion – Send Fulfillment Requests automates purchase‑order submission directly from Flxpoint, ensuring Orion receives accurate shipping and item data. Configure your mapping, select the proper order type, schedule the job, and let Flxpoint handle the rest.
 
 

Get Shipments

Supported | Orion – Get Shipments

Introduction to Orion – Get Shipments
The Orion – Get Shipments integration retrieves shipment confirmations from Orion Wholesale’s API and links them to your Flxpoint fulfillment requests. It imports tracking numbers, carriers, ship dates, and shipped quantities so your sales channels and customers stay informed.

  • Fetch shipment data for recently sent purchase orders / fulfillment requests.
  • Map Orion shipment headers and line items to Flxpoint shipment fields.
  • Automatically update FRs with carrier, tracking, and ship-date details.

  1. Select Date Window – Integration calls Orion for shipments created in the last X Days (configurable).
  2. API Call – GET https://orionfflsales.com/api.php?method=get_shipments&days={X} with header x-connection-key.
  3. Receive JSON Response – Example:
    [ { "purchaseOrderNumber":"FR-10234", "shipmentDate":"2025-08-01", "carrier":"UPS", "trackingNumber":"1Z999AA10123456784", "items":[{"sku":"OR-112","quantity":2}] } ]
  4. Match to FRs – The PO number aligns shipments to existing fulfillment requests (lookback period controls age).
  5. Create Shipment Records – Flxpoint writes shipment + item lines, closes FR if fully shipped.
Lookback Logic: Integration only considers FRs created within the FR Lookback Period (default 3 months).

  • Fetch Shipments for Last X Days – Choose 1-30 days (default 5). Controls the days query param.
  • FR Lookback Period – Limits how old an FR can be (30-180 days). Default is 90 days (3 months).
  • Scheduling – Enable a daily or hourly schedule after successful tests.

  • 1Connect Integration – Pick Orion – API, use your connection key, click Save and Proceed.
  • 2Configure Settings – Select fetch window (e.g., 5 days) and FR lookback period.
  • 3Create Mapping Template – Use Get Shipments 2 starter or build new mapping.
  • 4Run Test – Hit Run Integration to pull recent shipments and confirm mapping.
  • 5Schedule – Toggle Scheduled = Yes, click Update.

Shipment Header Fields
Orion Field Flxpoint Shipment Field Example Purpose Status
purchaseOrderNumber (T) Fulfillment Request Number FR-10234 Links shipment to FR Required
shipmentDate (D) Shipped At 2025-08-01 Date shipped Required
carrier (T) Carrier UPS Shipping carrier Required
carrierCode (T) Carrier Service Code 03 UPS code Optional
trackingNumber (T) Tracking Number 1Z999AA10123456784 Track shipment Required
Shipment Item Fields
Orion Item Field Flxpoint Shipment Item Field Example Status
sku (T) SKU OR-112 Required
quantity (N) Quantity 2 Required
Tip: If Orion returns multiple tracking numbers for one PO, the integration will create separate shipment records per tracking number.

  • No Shipments Found – Increase Fetch Shipments for Last X Days or verify Orion shipped orders recently.
  • 401 Unauthorized – Check connection key.
  • Shipments Not Linking – Ensure PO number in Orion matches FR Number exactly.

  • Default fetch window is 5 days; adjust as needed.
  • FRs older than lookback period are ignored.
  • Integration can be scheduled; all runs use UTC time.

Conclusion
Orion – Get Shipments keeps your customers informed with real-time tracking and carrier data. Configure the fetch window, map the fields, schedule daily runs, and let Flxpoint automatically close the loop on every order.
 
 

 

Related Articles

Order Routing Preview

The order routing preview tool allows you to see the impact your routing groups, ...

Importing Orders

This guide provides a comprehensive overview of importing orders in Flxpoint, det...

Fulfillment Requests

A fulfillment request (or fulfillment orders) represents an order/request placed ...