Orion Wholesale as a Source

July 17, 2026

Summary

Orion Wholesale is a firearms, ammunition, outdoor gear, and tactical equipment distributor connected via a single-key API integration. It supports Get Inventory (Primary and Secondary), Send Fulfillment Requests (Customer, Dealer, or FFL order types), and Get Shipments, all authenticated through one Connection Key. Products are simple (no variations); FFL-regulated orders require valid FFL license details, and extended field-mapping guidance is available from support@flxpoint.com.

What this integration does

Get Inventory (Primary)

Imports Orion's full firearms/tactical catalog — products, pricing, and categories.

Get Inventory (Secondary)

Lightweight delta refresh of SKU, quantity, and price only.

Send Fulfillment Requests

Sends orders to Orion for dropship fulfillment — Customer, Dealer, or FFL.

Get Shipments

Pulls Orion shipment confirmations — ship date and tracking.

How to connect - credentials you need

Orion Wholesale uses a single API connection. Add an Orion source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your Connection Key, then Test Connection → Save Connection.

Connection KeyRequired

Your Orion Wholesale API connection key, provided by Orion. Sent securely with every request Flxpoint makes to authenticate your account.

For FFL order-type configuration, category-splitting mapping rules, or other operation-specific setup, contact support@flxpoint.com.

Important - read before configuring

Connection Key is your sole credential — authenticates every Orion request

All Orion Wholesale operations authenticate using a single Connection Key obtained from your Orion portal. It is sent securely with every request Flxpoint makes to Orion. Keep it secure — it controls access to your entire Orion account. If the key is rotated or revoked, all four operations will return 401 Unauthorized errors until the connection is updated with the new key.

Send FR supports Customer, Dealer, and FFL order types — set in integration settings or mapping

When configuring Send Fulfillment Requests, choose the Order Type: Customer (default), Dealer, or FFL. This can be set in the integration settings as a default, or overridden per order via the mapping template. FFL order type is required for FFL-regulated firearm dropship orders. Confirm the correct order type with Orion before going live — using the wrong type may cause orders to route incorrectly or be rejected.

Enable Archive/Un-Archive on GIP only — not on both GIP and GIS

Archive/Un-Archive in GIP archives any SKU absent from Orion's feed (sets quantity to 0) and auto-reactivates it when it returns. Do not enable this on both GIP and GIS simultaneously — this is explicitly noted in the Orion integration settings. GIS is a delta feed (quantity and price only) and should run with Archive disabled. Enable Archive only on GIP.

Get Shipments default fetch window is 5 days — adjust if shipments from older orders are missing

Get Shipments looks back a configurable number of days to find new shipments — controlled by the Days setting (default: 5 days). If shipments for recent orders are not pulling, increase this value. The FR Lookback Period (separate setting, default 90 days) controls how old an FR can be to receive a shipment update. If Orion returns multiple tracking numbers for one PO, Flxpoint creates a separate shipment record per tracking number.

Operations - fields to know

Get Inventory (Primary)Get Inventory (Secondary)Send Fulfillment RequestsGet Shipments

Field	Maps To — Notes
product_code	→ Product / Variant → SKU. Required. Primary identifier from Orion's catalog.
quantity	→ Inventory → Quantity. Required. On-hand units, merged in from Orion's inventory data.
description	→ Product → Title. Product name.
product_manufacturer	→ Product → Brand. Manufacturer name, resolved from Orion's brand list.
product_categories	→ Product → Category 1 / 2 / 3. Comma-separated string — split into levels with a mapping rule (see Common Issues).
upc_code / manufacturer_sku / image_urls	→ Identifiers & Images → UPC, Manufacturer SKU, Photos. Barcode, manufacturer part reference, and product images, when returned.

Field	Maps To — Notes
product_code	→ Inventory Variant → SKU. Required. Matches the SKU from Get Inventory Primary.
quantity	→ Inventory → Quantity. Required. Current on-hand units.
sale_price	→ Pricing → Cost. Updated dealer price, when returned.
Full catalog fields	Not included in Secondary — titles, categories, images and identifiers come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost and Quantity current.

Source Field	Maps To (Orion) — Notes
Fulfillment Request Number	→ Purchase Order Number. Required. Sent to Orion as the PO Number — must match exactly for Get Shipments to link back.
FR Item SKU	→ Product Code. Required. Must match Orion's product code per line item.
FR Item Quantity	→ Quantity. Required. Units requested per line.
Shipping address (Name, Address, City, State, Postal Code)	→ Ship To. Required. End-customer shipping address sent to Orion.
Source Shipping Method	→ Shipping Method Code. The shipping method sent to Orion for the order.
Order Type	→ Order Type. Required. Customer, Dealer, or FFL — set as a default in integration settings or mapped per order.
FFL License Info (for FFL orders)	→ License Number & FFL Address. Required for FFL orders. Overrides the ship-to address with the receiving FFL's license and address.

Field	Maps To — Notes
purchase_order_number	→ Shipment → Linked PO / FR Number. Required. Must match the PO Number sent on the original Fulfillment Request.
date_shipped	→ Shipment → Shipped At. When Orion marks the shipment shipped.
tracking_identifier	→ Shipment → Tracking Number. Required. Package tracking number. Multiple tracking numbers on one PO create separate shipment records.
shipping_carrier / shipping_carrier_code	→ Shipment → Ship Method / Carrier Code. Carrier name and code (e.g. a UPS service code) returned by Orion.
Item quantity (per SKU, resolved from product ID)	→ Shipment Item → SKU / Quantity. Required. Associates the shipped line to your catalog and units shipped.

Common issues

401 Unauthorized — all Orion operations failing

A 401 error on any Orion operation means the Connection Key is invalid, expired, or not yet provisioned for your account. To fix: (1) open the Orion connection in Flxpoint and confirm the Connection Key is entered correctly — no leading/trailing spaces; (2) log into your Orion portal and verify the key is still active; (3) if the key has been rotated, copy the new key and update the Flxpoint connection; (4) confirm your Orion account has full API access enabled for catalog, inventory, and order operations. Contact Orion support if API access was not explicitly provisioned for your account.

Categories missing or not mapping correctly after GIP

Orion returns categories as comma-separated text in a single field (e.g., "Handguns, Pistols, Semi-Automatic"). If categories are not mapping to individual Category 1/2/3 fields as expected: add a mapping rule to the GIP template that splits the comma-separated category string and maps each part to the appropriate category level. Without this rule, the entire comma-separated string will be imported as Category 1. The exact splitting logic depends on how Orion formats your category data — review a sample product in the job log to see the raw value before building the rule.

Send FR failing — missing Order Type or PO Number mismatch

Two common Send FR failures: (1) Order Type not set — the orderType field in the Orion PO payload must be Customer, Dealer, or FFL; confirm it is configured in integration settings or mapped in the template; (2) PO Number mismatch — Get Shipments links shipments by matching Orion's purchaseOrderNumber to the Flxpoint FR Number; if Send FR uses a different value for PO Number (e.g., a channel order number instead of the FR Number), shipments will not link back. Always map Fulfillment Request Number → PO Number in Send FR. Also confirm the ship-to address has all required fields (Name, Address1, City, State, Zip).

FAQs

What does GIP import from Orion?▸

GIP pulls Orion's full catalog in one run — product basics, live quantities, category data, and brand/manufacturer data — merged together by SKU. Core mappings: Product Code → SKU (required), Quantity → On-Hand Qty (required), Sale Price → Cost (optional), Weight → Weight lb, Manufacturer → Brand. Height, Length, Width, and Weight fields are also available. Simple products only — no variations. Categories return as comma-separated text; use a mapping rule to split them if needed.

What are the required fields for Send Fulfillment Requests to Orion?▸

Required Send FR mappings: Fulfillment Request Number → PO Number, Ship To Full Name, Ship To Address Line 1, Ship To City, Ship To State Code, Ship To Postal Code, FR Item SKU → Item Number (must match Orion's productCode), FR Item Quantity. Optional: Ship Via Code (carrier/service), Ship Instructions/Note, Unit Price (Cost from FR). The Order Type (Customer, Dealer, or FFL) must be configured — either as a setting default or via mapping. Hold for X Hours and Send During Business Hours are available for review windows and scheduling control.

How does GIS (Secondary) differ from GIP for Orion?▸

GIS is a lighter, delta-only refresh — it returns just SKU, quantity, and sale price for items already in your catalog, not full catalog attributes. Map these to: productCode → SKU (required), quantity → Quantity On Hand (required), salePrice → Client Price (optional). GIS does not return catalog attributes, descriptions, images, categories, or brand data — those only come from GIP. Leave Archive/Un-Archive disabled on GIS. The Allow Create Variant toggle is available if new SKUs may appear as variants during GIS runs.

What does Get Shipments return and how are multiple tracking numbers handled?▸

Get Shipments returns: purchaseOrderNumber (links to FR — required), shipmentDate (Shipped At), carrier, carrierCode (optional, e.g., UPS service code "03"), trackingNumber (required), and per-item sku and quantity. If Orion returns multiple tracking numbers for a single PO, Flxpoint creates separate shipment records per tracking number. Configure the fetch window (Days) and FR Lookback Period in the integration settings. PO Number in Orion must match the FR Number exactly for the shipment to link correctly.

Back to Firearms & Tactical