RSR as a Source

May 8, 2026

Summary

RSR Group connects to Flxpoint through its Direct Connect API using your rsrgroup.com dealer login. A single connection powers all four operations (Get Inventory Primary, Get Inventory Secondary, Send Fulfillment Requests, and Get Shipments) but RSR must manually approve Direct Connect API access (typically 2 to 3 business days, coordinated through Flxpoint Support) before data begins syncing.

What this integration does

Get Inventory (Primary)

Imports the full RSR catalog once daily: titles, descriptions, Dealer Price as Cost, quantity, two-level categories, weight/dimensions and identifiers

Get Inventory (Secondary)

A faster hourly feed that refreshes SKU, Cost (Dealer Price), Retail MAP, MSRP and quantity only

Send Orders

Sends Fulfillment Requests (orders) to RSR with End Consumer, Store Name and line SKUs/quantities

Get Shipments

Pulls RSR shipment confirmations back into Flxpoint: ship date, tracking number and shipped line items

How to connect: credentials you need

Add an RSR source and start configuring an operation; when Flxpoint prompts you, click + New Connection and enter these values, then click Test Connection → Save Connection. This single connection is reused by all four RSR operations.

Field	What to enter
API URL (Production)Required	The RSR Direct Connect production endpoint. Enter `https://www.rsrgroup.com/` exactly. Same endpoint for every RSR operation.
UsernameRequired	Your RSR website login: the same username you use to sign in at rsrgroup.com. Open rsrgroup.com
PasswordRequired	The password for your rsrgroup.com dealer login. If it isn't working, use Forgot Password on the RSR website to reset it before troubleshooting further in Flxpoint.
Dealer ID / account referenceOptional	Any RSR dealer ID or account reference you use internally. Optional: for your own reference; not required to connect.

New connections don't sync until RSR manually enables Direct Connect for your account: valid credentials alone are not enough. After saving the source, contact Flxpoint Support to facilitate approval (RSR's team is reachable at RSR's dealer-connect team (coordinated via Flxpoint Support)). Approval typically takes 2 to 3 business days and is required once per account; click Test Connection again once it's activated.

Important: read before configuring

RSR must manually approve your API access before any data syncs

Even with valid credentials, your RSR integration will not start syncing until RSR enables Direct Connect for your account. After configuring your source, contact Flxpoint Support to facilitate approval: RSR's team can be reached at RSR's dealer-connect team (coordinated via Flxpoint Support). This typically takes 2 to 3 business days and is required once per account.

Dealer and Fulfillment accounts must be set up as two separate Flxpoint sources

If you run both an RSR Dealer account (ships to your warehouse) and an RSR Fulfillment/Dropship account (ships direct to customers), create two separate RSR Sources: one per account, each with its own credentials. Add both to a single routing group and use Post Mapping Workflow filters to scope which products each source can fulfill. Never share one source for both account types.

Enable Archive / Un-Archive on only one job: Primary or Secondary, never both

Turning on Archive in both Get Inventory Primary and Secondary causes items to be archived and immediately restored on the same cycle, often producing unexpected zero-quantity drops. Enable Archive in one place only: typically Primary, so the full catalog run owns archival decisions.

Unique PO / FR reference required per order: RSR rejects duplicates for 12 months

RSR rejects any order that reuses a PO or FR number submitted within the past 12 months. To retry a failed order you must change the FR/PO reference before resubmitting. Always check your RSR dealer portal first to confirm whether the original order was actually received.

Mapping: fields to know

Get Inventory (Primary) Get Inventory (Secondary) Send Orders Get Shipments

Imports the full RSR catalog once daily: titles, descriptions, Dealer Price as Cost, quantity, two-level categories, weight/dimensions and identifiers

RSR Field	Maps To: Notes
SKU / Item Number	→ Product → SKU. Required. Primary product identifier.
Title / Name	→ Product → Title. Required. Readable product name.
Description (Enhanced)	→ Product → Description. Turn on Use Enhanced Description to bring in richer text.
Dealer Price	→ Pricing → Cost. Saved as Cost; currency is USD.
Quantity	→ Inventory → Quantity. Current stock level.
Weight	→ Shipping → Weight (lb). Provided in pounds.
Dimensions (L/W/H)	→ Shipping → Dimensions (in). Provided in inches.
Category Level 1 / Level 2	→ Categories → Level 1 / Level 2. Two category levels are available.
UPC / GTIN	→ Identifiers → UPC. Used when provided.
MPN	→ Identifiers → MPN. Manufacturer part number.
Brand / Manufacturer	→ Attributes → Brand.
Images	Not returned by the API: handled by the separate Get Inventory Images job (RSR FTP server). No manual setup required.

A faster hourly feed that refreshes SKU, Cost (Dealer Price), Retail MAP, MSRP and quantity only

RSR Field	Maps To: Notes
SKU	→ Inventory Variant → SKU. Required. Primary identifier.
Dealer Price	→ Pricing → Cost. Dealer price saved as Cost (USD).
Retail MAP	→ Pricing → MAP. Minimum Advertised Price.
MSRP	→ Pricing → MSRP. Manufacturer's suggested price.
Inventory On Hand	→ Inventory → Quantity. Required. Current available units.
Weights, dimensions, categories, images	Not included in Secondary: these come from Get Inventory Primary. Run Primary daily for full refreshes and Secondary hourly to keep Cost, MAP, MSRP and quantity current.

Sends Fulfillment Requests (orders) to RSR with End Consumer, Store Name and line SKUs/quantities

Source Field	Maps To (RSR): Notes
Fulfillment Request Number	→ PO / Reference. Required. Mappable FR#/PO#; must be unique per 12 months.
Shipping First / Last Name	→ End Consumer. Required. Each name part must be ≥ 2 characters.
Sales Channel Store Name / Company / Static	→ Store Name. Recommended. Your business/store identity; each part must be ≥ 2 characters.
Dealer Email (setting)	→ Email. Required. Configured in the job's Setup step, not on the connection.
Fill or Kill	→ FillOrKill. Optional. `Y` = ship all or cancel; blank/`N` allows partial shipments.
Hold for X Hours	→ Hold. Optional. Delays sending the order to RSR.
Order Items → SKU	→ Line SKU. Required. Sent to RSR per line item.
Order Items → Quantity	→ Line Qty. Required. Units requested.
Source Shipping Method → Shipping Code	→ Line ShipMethod. Optional. Maps an RSR shipping code (e.g. `2Day`, `Grnd`, `NDAS`) per line. If not mapped, RSR selects shipping automatically based on your account preferences.

Pulls RSR shipment confirmations back into Flxpoint: ship date, tracking number and shipped line items

RSR Field	Maps To: Notes
DateShipped	→ Shipment → Shipped At. When RSR marks the shipment as shipped.
TrackingNum	→ Shipment → Tracking Number. Required. No tracking URL, carrier, or method labels are returned by RSR.
PartNum	→ Shipment Item → SKU. Required. Associates the shipped line to your catalog.
ASNQty	→ Shipment Item → Quantity. Required. Quantity shipped for the line item.

Common issues

Connection failing: API access errors even though credentials look correct

The usual cause is that RSR has not yet enabled Direct Connect for your dealer account: valid credentials alone are not enough. Contact Flxpoint Support to request API permission enablement; the team coordinates with RSR at RSR's dealer-connect team (coordinated via Flxpoint Support). After activation (typically 2 to 3 business days) click Test Connection again. If credentials that previously worked now fail, contact RSR to confirm your API access is still active.

Send Fulfillment Request fails with a connection or timeout error (NoHttpResponseException)

RSR's server can drop the connection roughly 60 seconds after a place-order request (before Flxpoint gets confirmation) even though RSR already created the order. Flxpoint has a fail-safe: it re-checks RSR's order status 1 to 2 minutes later and, if the order was received, suppresses the error and marks the FR as sent. If it was not received, the failure surfaces: create a new FR number before resubmitting. Always check your RSR dealer portal first to avoid a duplicate PO.

"Store Name is invalid (each name part must be >= 2 characters)"

This is the most common Send FR validation error. Confirm Store Name is mapped to a field that reliably supplies a full business name: Sales Channel Store Name, Order Company/Organization, or a static fallback. Single-letter initials, placeholder text, or an unmapped Store Name all trigger it. End Consumer comes from Shipping First + Last Name: confirm those are not empty or single-character.

Duplicate PO error: order rejected by RSR

RSR rejects any order reusing a PO/FR reference submitted within the past 12 months. Before retrying, check your RSR dealer portal to confirm whether the original order was received. If it was, no resubmission is needed; if it wasn't, change the FR/PO reference to a new unique value first. This also applies when recovering from connection-timeout errors.

Ammunition orders failing: Error 86 "No items could be added to the order"

RSR requires ammunition to ship to a physical street address (PO Boxes are not accepted) and via FedEx Ground. Verify the order's shipping address is a valid street address and that FedEx Ground is used. Some sales channels default to address types that can populate PO Box-style values.

FFL information not reaching RSR on firearm orders

RSR requires FFL info for firearm orders but not for accessories. Verify the product is flagged Requires FFL in Flxpoint and that your RSR source is configured to collect and send FFL. For Dealer accounts, FFL details should never be sent: set the Dealer source's GIP mapping template to Requires FFL = False for all items so FFL isn't collected on dealer-routed orders. Confirm the source-level FFL setting matches the account type (Dealer vs. Fulfillment).

Order creation failed: "Got error response from RSR : 93, No valid items submitted"

RSR returns this when the account doesn't have permission to sell that item. If you believe the item should be sellable, confirm with RSR directly before resubmitting. Resubmitting the same order number will not work: if the initial submission fails, create a new FR number before trying again.

"Failed to Login" when connecting or syncing an RSR source

This shows when the API POS indicator "F" has not been enabled on RSR's end for your dealer account. Contact Flxpoint Support: the team will reach out directly to RSR's Direct Connect staff (RSR's dealer-connect team (coordinated via Flxpoint Support)) to get this setting enabled before the Flxpoint → RSR integration can be used.

FAQs

What credentials do I use to connect RSR in Flxpoint?

Use your RSR website login: the same username and password you use at rsrgroup.com. The API URL is https://www.rsrgroup.com/. The single connection is reused across all RSR operations; you do not need separate credentials for inventory vs. order operations. If your credentials aren't working, use the Forgot Password link on the RSR website to reset them before troubleshooting further in Flxpoint.

How do I get product images from RSR?

RSR product images are not available through the Direct Connect API. They are retrieved separately via the Get Inventory Images job, which pulls from RSR's FTP server (paths such as /ftp_images/rsr_number/ and /ftp_highres_images/rsr_number/). No manual setup is required: the job runs automatically once your RSR connection is active, and if RSR removes an image Flxpoint removes it too.

Some products are missing from my RSR catalog import. Why?

Missing items are most often caused by RSR's Authorized Reseller Program: some products are manufacturer-restricted and only appear in your feed once your account is enrolled for those brands. Log in to your RSR Dealer account, go to Online Catalog → Authorized Reseller Programs, and review your enrollments. Once enrollment is confirmed, the restricted items appear automatically in your Flxpoint feed.

Should I map a shipping method in my Send Fulfillment Requests template?

For most RSR accounts, no: RSR automatically selects the carrier and method based on your dealer preferences and the order. Only send a method if your RSR rep has confirmed your account is configured to receive one via the API. If you do, use RSR's shipping codes: 2Day, 3Day, NDAS, Grnd, 1Day, NDam, PRIO, FXGHD. If your account isn't configured to accept a method and you send one, RSR may override it and ship via its default.

Why doesn't Get Shipments show carrier or shipping method?

RSR's shipment API response includes a tracking number but does not return carrier or method labels: a constraint of the Direct Connect API, not a Flxpoint setting. You'll see the tracking number but the carrier/method fields stay blank. If a downstream channel requires carrier info, you can add a conditional rule in your Get Shipments mapping template to derive the carrier from the tracking number format.

What do the Store Name and End Consumer fields mean, and where do I map them?

RSR requires two name fields on every order: End Consumer (the customer receiving the shipment (mapped from Shipping First + Last Name) and Store Name (your business/store identity) mapped from Sales Channel Store Name, Order Company, or a static value). Both are required and each name part must be at least 2 characters. Leaving Store Name unmapped or set to a single character causes RSR to reject the order.

What does Fill or Kill do, and should I enable it?

Fill or Kill (set to Y in the Send Fulfillment Requests settings) tells RSR to cancel the entire order if it can't be fully fulfilled. Left blank or set to N, RSR ships whatever is available and partial shipments are supported. Most accounts leave it blank to allow partial fulfillment: only enable it if your business requires all-or-nothing processing.

RSR Group Recursive Image Fetching

What it does

Flxpoint provides an enhanced image fetching process for the RSR Group source integration. While primary images are initially pulled from standard directories, RSR moves images to manufacturer-specific folders after 28 days. To ensure your listings maintain high-quality imagery, Flxpoint uses a recursive fallback mechanism to locate these moved files.

Primary image fetching

By default, the integration first attempts to retrieve images from the following primary paths on the RSR server:

/new_images
/rsr_number

Recursive fallback mechanism

If an image is not found in the primary folders, the system triggers a deep scan of the manufacturer directories. This ensures that older products or items moved by RSR are still successfully imported.

How the fallback works

Trigger: The fallback scan runs when the downloadAll flag is enabled for the source.
Path: The system scans /ftp_images/manufacturers and all nested subfolders.
Logic: A recursive directory walker traverses alphabetical folders (e.g., A, B, C) and specific manufacturer subdirectories to find the matching SKU image.
Efficiency: The process checks for local existence first and skips images that have already been successfully downloaded to prevent redundant transfers.

Note: This process supports both FTP and FTPS connections to ensure secure traversal of the RSR file system.

Troubleshooting

Images are missing for older SKUs?

Ensure that your source configuration has the downloadAll flag set to true. If this flag is disabled, the system will only check the primary /new_images folder, which RSR clears every 28 days.

Slow inventory syncs during image updates?

Recursive scanning of deep directory structures takes more time than direct folder pulls. This is expected behavior during the initial build or when performing a full image refresh.

Back to Firearms & Tactical