Flxpoint Knowledge

Contact us

RSR as a Source

Table of Contents

Add Source and Establish Connection Product & Order Operations Product Operations Order Operations Troubleshooting Common Errors

In this guide, you’ll learn how to set up your RSR feed in Flxpoint, from creating the source wizard to activating inventory and order operations. With this connection you’ll keep stock and pricing synchronized, place fulfillment requests, and ensure seamless routing through RSR.

 

Add Source and Establish Connection

🧭 Phase 1: Launch the Source Wizard +
Open Sources and start the Wizard
Go to Sources (building icon) → + Add Source → Configure Single Source. This opens the Source Wizard.
Step 1 — Create Source
Enter a clear name (e.g., RSR as Source). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most RSR setups, we recommend Vendor Warehouse. Use the other options only if they better match how you store and ship inventory.

  • Vendor Warehouse (Recommended): You send POs/FRs to RSR so they ship directly to your customers.
  • Internal Warehouse: You stock items and ship from your own facility.
  • External Warehouse: A 3PL or external partner ships your owned inventory.
  • Product Data Source: Content-only source to enrich product details (no fulfillment).
For RSR: select Vendor Warehouse. This enables sending Fulfillment Requests to RSR and using their inventory for routing.
After selecting the Source Type, click Save & Next.
Step 2 — Vendor Set-Up
Choose Yes (Recommended) to Assign Vendor → Confirm. You’ll enable Vendor reporting and optional portal.
Step 3 — Order Fulfillment
Decide if this source is eligible to fulfill orders:
  • Yes (Recommended): You can route orders here.
  • No: Routing/Shipping steps won’t apply.
Click Confirm.
Step 4 — Order Fulfillment Settings
Use Defaults or No, Customize. You’ll see:
  • Override: Auto Processing (Use Global / Auto Process / Do NOT Auto Process).
  • Commit Stock + Inventory Management Options.
  • Allow Backorders / Cancel Unacknowledged Items.
Click Save & Next.
Step 5 — Shipping Cost Estimations
Pick one:
  • Yes, Use Rate Shopping (Real-Time Estimates).
  • No, Set Up via Rules.
If using real-time, acknowledge you have valid dimensions, weight, and source address. Click Save & Next.
Step 6 — Order Routing Groups
Enable on all routing groups? Select Yes or No, Customize. Optionally mark Default Order Routing Group. Save & Next.
Reminder: Complete Step 1 — Shipping Methods and Step 2 — Source Location in Phase 2 below, then return (if needed) to finalize.
🚚 Phase 2: Shipping Methods & Source Location (Finish the Wizard) +
Goal

Finish the Source Wizard by confirming your Ship From location and reviewing shipping behavior for RSR. For almost all RSR accounts, you do not create a Source Shipping Method here—RSR will choose the carrier and service on their side when they receive the Fulfillment Request.

Step 1 — Shipping Methods (Skip for RSR)
When the wizard opens the Shipping Methods step for this Source:
  • For typical RSR setups, do not click “Add Method” and do not configure a Shipping Method on this screen.
  • Leave the list of methods empty and continue to the next step in the wizard.
Why? RSR automatically selects the shipping method based on your dealer account preferences, order details, and carrier availability. Sending a method from Flxpoint is not required and may conflict with how RSR is configured to ship your orders.

Only create a Source Shipping Method if:
  • Your RSR representative has explicitly confirmed that your account is configured to receive a shipping method via the API, and you plan to map it in your Send Fulfillment Request template; or
  • You are using Rate Shopping with a provider that requires a Source Shipping Method for routing.
Step 2 — Source Location (Ship From)
Enter the Ship From address:
  • Address, City, State/Code, Postal Code, Country/Code
  • Optional: Contact Name, Phone, Email
This address is used for routing logic, rate shopping (if enabled), and reporting.
Finish the Wizard
Review Steps 1–2, then click Save and Complete. The wizard is now finished.
Next: Proceed to Phase 3 to gather the RSR credentials you’ll use for all RSR integrations.
🔐 Phase 3: Gather Your RSR Credentials +
Goal

To connect RSR in Flxpoint, you’ll first ensure your dealer login is active and gather the credentials required to create a single RSR Connection. This connection is created once and powers all RSR operations.

Step 1 — Confirm your RSR dealer portal access
Go to rsrgroup.com and sign in with your dealer credentials. Make sure:
  • You can log in successfully without errors.
  • Your account is active and has access to the RSR Dealer Portal.
If you cannot log in, reset your password or contact RSR to restore access before continuing in Flxpoint.
Step 2 — Gather your RSR API credentials
When you later configure the RSR operations in the Operations section, Flxpoint will prompt you to select or create an RSR Connection. Collect these details now and keep them handy:
  • API URL (Production): https://www.rsrgroup.com/
  • Username: your RSR website login (same as used on rsrgroup.com)
  • Password: your RSR website login password
  • Optional: any RSR dealer ID or account reference you use internally.
How Flxpoint uses this connection: this single RSR Connection is reused by all RSR integrations you’ll configure later, including: Inventory [Primary], Inventory [Secondary], Fulfillment Requests, and Shipments. You don’t need separate logins for each operation.
Next Configure Product & Order Operations 🚀
Now that you have a working RSR login and your credentials ready, go to the Operations section of this doc to set up the RSR integrations you need (Inventory and Order operations). When prompted, select or create the RSR Connection using the credentials you just collected.

 

Product & Order Operations

Now that you’ve finished the wizard, you’ll see RSR has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your RSR stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to RSR and pulling back shipment/tracking data. All four use the same RSR connection and credentials you just set up so you can simply choose the operations that match your workflow.

 

Product Operations

Get Inventory Primary imports your RSR catalog including metadata such as attributes, images, titles and description. We recommend running this once daily to import any new items. Get Inventory Secondary is a faster, more efficient operation to import more frequent pricing and quantity updates. We recommend running this hourly. 

Get Inventory (Primary)

Supported
Introduction

RSR – Get Inventory [Primary] imports your RSR catalog into Flxpoint. You’ll (1) connect RSR, (2) choose a few settings, and (3) select a mapping template. When a step is finished, you’ll see a check mark next to it.

On this section
Setup Steps
  • 1Connect RSR: Select RSR and click Save and Proceed.
  • 2Choose Settings:
    • Use Enhanced Description — import enhanced product descriptions from the RSR FTP feed.
    • Archive/Un-Archive Inventory — items not present in the latest feed are archived (qty set to 0). If they return later, they are automatically un-archived.
      Tip: Turn this on in either Primary or Secondary (not both).
    Click Save and Proceed.
  • 3Select a Mapping Template: Choose RSR Get Source Product 1 and click Save and Complete.
What you’ll see
  • Three steps on the page: Connect an Integration, Configure Settings, Define a Mapping Template.
  • Each completed step shows a check mark.
RSR Source Setup — Approval Requirement

Even if you enter your RSR API credentials in Flxpoint successfully, your integration will not start syncing until RSR manually approves the connection.

⚠️ Why approval is required

  • RSR must authorize your API connection before allowing access to live data feeds.
  • This ensures proper account validation and POS indicator setup for your reseller status.

✅ What You Should Do

  • You: After configuring your RSR Source in Flxpoint, contact the Flxpoint Support Team.
  • Flxpoint: The Support Team will reach out to RSR to facilitate approval and confirm the POS Indicator.
  • RSR: Once RSR confirms approval, your Flxpoint RSR Source will be activated and begin syncing automatically. This usually takes about 48 hours.
Configuring Different Account Types

Many merchants use multiple RSR accounts to meet specific dealer or manufacturer requirements — such as maintaining both a Dealer and a Fulfillment account.

💡 Example Scenario

You sell items that must be shipped to your warehouse or brick and mortar address already on file with RSR (ordered via your Dealer Account), while other non-restricted items can ship directly to customers (ordered via your Fulfillment / Dropship Account). This requirement is usually driven by the manufacturer.

To manage this properly, you must separate your accounts in Flxpoint.

Scenario Recommended Configuration
You operate both Dealer and Fulfillment / Dropship accounts Create two separate RSR Sources — one for each account, each with its own credentials.

Watch the video tutorial at the top of this page or click here.
You need account-level routing Orders are routed by leveraging routing groups, routing priorities and potentially shipping policies.
You only have a single account Configure one RSR Source as normal — no special routing required.
⚠️ Important:
  • Avoid using one shared RSR Source for multiple account types. This may lead to SKU duplication, incorrect routing, or order sync issues.
  • If you’re unsure which setup applies to your business, contact Flxpoint Support or your Project Manager for a quick configuration review.
On this section
Template Index
Template Use Case What it Covers Availability
RSR Get Source Product 1 Get Inventory (Primary) Client pricing as Cost (USD), Quantity, two-level Categories, Weight/Dimensions (inches & pounds), identifiers, brand, title, description. Available
Field Mapping (RSR Get Source Product 1)

This is a friendly overview of how common RSR fields flow into Flxpoint.

RSR Field Flxpoint Field Type Required? Notes for You
SKU / Item Number Product → SKU Text Yes Primary product identifier.
Title / Name Product → Title Text Yes Readable product name.
Description (Enhanced) Product → Description Text No Turn on Use Enhanced Description to bring richer text.
Dealer Price Pricing → Cost Number Yes Saved as Cost. Currency is USD.
Quantity Inventory → Quantity Number Yes Current stock level.
Weight Shipping → Weight (lb) Number No Provided in pounds.
Dimensions (L/W/H) Shipping → Dimensions (in) Number No Provided in inches.
Category Level 1 Categories → Level 1 Text No Top-level category (two levels available).
Category Level 2 Categories → Level 2 Text No Sub-category.
UPC / GTIN Identifiers → UPC Text No Use when provided.
MPN Identifiers → MPN Text No Manufacturer part number.
Brand / Manufacturer Attributes → Brand Text No —
Images — — — Handled by Get Inventory Images (see FAQs).
Units: Dimensions are in inches and weight is in pounds. If your store expects different units, add a conversion rule.
Categories: Two category levels are available and can be mapped.
Rules You Can Use
Rule Type Input When it Helps What it Does
Set to true based on Main Category Conditional Boolean Flagging items by category Turns a target flag to true when the category matches your condition.
Convert ounce to pound Conditional Number Normalizing weight inputs Converts ounces to pounds wherever needed.
Set to true based on Main Category Conditional String Adding category-based labels Sets a string output based on the category condition you choose.
Create your own rule: Go to Mapping Utilities → Mapping Rules, click Create New Rule, pick Conditional, and choose the Input Type (String/Number/Boolean).
Note: After creation, the rule’s type and input can’t be changed.
Sets, Lists & Builders
Utility Availability How You Might Use It
Mapping Sets Optional — available Combine or format multiple inputs into a single output field.
Lists Optional — available Maintain reusable value lists (e.g., approved brands or categories).
Builders Optional — available Create a custom product/output structure if your channel needs it.
On this section
Quick Checks
  • RSR is connected and saved on Step 1.
  • Turn on Use Enhanced Description if you want richer copy.
  • For automatic cleanup of old items, enable Archive/Un-Archive in Primary or Secondary (one place only).
  • Confirm a mapping template is selected (e.g., RSR Get Source Product 1).
  • Test first, then enable any schedules or live workflows.
Images (handled by “Get Inventory Images”)

Flxpoint automatically manages all product images for your RSR integration — there’s no need for any manual setup.

💡 How it works:
  • Once your RSR connection is active, Flxpoint continuously pulls the most up-to-date product images from RSR’s servers and associates them with your products.
  • If RSR removes an image or it becomes unavailable, Flxpoint automatically removes that image from your catalog to prevent broken thumbnails or blank placeholders.
🪄 What This Means for You
  • ✅ No manual setup required — image handling is fully automated.
  • ✅ Always up-to-date — Flxpoint syncs RSR images regularly to reflect product changes.
  • ✅ Error prevention — outdated or missing images are removed automatically to keep your product listings clean and accurate.
Understanding Authorized Reseller Program (Missing Items in Feed)

If you recently migrated from the RSR FTP feed to the RSR API feed, you may notice that some products are missing. This is expected and typically relates to RSR’s Authorized Reseller Program.

⚠️ Why certain items don’t appear in your feed

  • Some items are restricted by manufacturers and can only be sold by authorized resellers.
  • These restricted items will not be included in your API feed until your account is approved for the relevant Authorized Reseller Program.
✅ How to Verify
  • Log in to your RSR Dealer account.
  • Go to Online Catalog → Authorized Reseller Programs.
  • Review which programs your account is currently enrolled in.
  • If you see missing SKUs that fall under restricted categories, contact your RSR representative to confirm eligibility and request enrollment if needed.
🟩 Note:

These restricted products will appear automatically in your Flxpoint feed once your RSR account is approved for the relevant Authorized Reseller Program. No additional configuration is needed in Flxpoint.

 
 

Get Inventory (Secondary)

Supported
Introduction

RSR – Get Inventory [Secondary] is a companion import to Primary. It’s ideal for refreshing stock and pricing, or for bringing in a streamlined set of RSR fields (SKU, inventory, MAP/MSRP, cost). You’ll (1) connect RSR, (2) pick one simple setting, and (3) select a mapping template.

  • 1Connect RSR: Choose your existing RSR API connection (or create a new one) → click Save and Proceed.
  • 2Configure Settings:
    • Allow Create Variant — optional. Turn on if you want the Secondary import to create variants while it runs.
    Click Save and Proceed.
  • 3Select a Mapping Template: Choose RSR – Get Inventory [Secondary] 2 → click Save and Complete.
What you’ll see
  • Three steps: Connect an Integration → Configure Settings → Define a Mapping Template.
  • A check mark appears next to each step after you finish it.
Template Index
Template Use Case What it Covers Availability
RSR – Get Inventory [Secondary] 2 Get Inventory (Secondary) SKU, Quantity, Cost (Dealer Price), MAP, MSRP. Use with the simple “Allow Create Variant” setting if needed. Available
Field Mapping (RSR – Get Inventory [Secondary] 2)

These mappings mirror what you see in the Mapping Templates view.

RSR Field Flxpoint Field Type Required? Notes for You
SKU Inventory Variant → SKU Text Yes Primary identifier.
Dealer Price Pricing → Cost Number Yes Dealer price saved as Cost (USD).
Retail MAP Pricing → MAP Number No Minimum Advertised Price.
MSRP Pricing → MSRP Number No Manufacturer’s suggested price.
Inventory On Hand Inventory → Quantity Number Yes Current available units.
Rules You Can Use
Example Rule Type Input When it Helps What it Does
Tag clearance items by category or price Conditional String/Number Marking products for store collections Sets a label or flag when your condition matches (e.g., MAP < MSRP by 20%).
Normalize cost values Conditional Number Pricing cleanup Rounds or converts inputs to your preferred format.
Append variant detail to title Conditional String Helpful when using “Allow Create Variant” Builds a variant label (e.g., adds color/size text) during import.
How to add a rule: Go to Mapping Utilities → Mapping Rules, click Create New Rule, pick Conditional, and choose the Input Type (String/Number/Boolean).
Note: After creation, a rule’s type and input can’t be changed.
Sets, Lists & Builders
Utility Availability How You Might Use It
Mapping Sets Optional — available Combine or format multiple inputs into a single output (e.g., build a composite title).
Lists Optional — available Reusable value lists for conditions (e.g., approved brands or restricted categories).
Product Builders Available (default provided) A default builder is present and matches on Master SKU. Create a new one if your channel needs a custom structure.
Quick Checks
  • RSR API connection is selected and saved in Step 1.
  • Decide whether to enable Allow Create Variant (helpful if variants should be created during import).
  • Confirm the template RSR – Get Inventory [Secondary] 2 is selected in Step 3.
  • Test first, then enable schedules or live workflows as needed.
How Secondary works with Primary
  • Primary is your fuller import (rich fields, categories, dimensions, etc.).
  • Secondary focuses on quick inventory and price updates (SKU, qty, MAP, MSRP, cost).
  • Images: not part of Secondary. Use the Get Inventory Images integration for image downloads.
  • Archive behavior: If you use automatic archiving, keep it in one place (commonly Primary) to avoid conflicts.
FAQs

Can I create variants during Secondary?
Yes. Toggle Allow Create Variant in Configure Settings.

What fields are updated?
SKU, Quantity (Inventory On Hand), Cost (Dealer Price), MAP, and MSRP.

Do I need Mapping Sets/Lists?
They’re optional tools you can add any time to format values or drive conditions.

Operation Details (What’s included)
Feature Availability What to Expect
Client Pricing (& Currency) Available Dealer-specific price is saved as Cost (USD).
Quantity Available Imports current stock levels (Inventory On Hand).
MAP / MSRP Available MAP and MSRP values are included in the template.
Weights & Dimensions Not included in Secondary Handled in Primary template (inches & pounds).
Categories Not included in Secondary Two levels available via Primary template.
Images (in GIS) Not included Use the separate Get Inventory Images integration to download images.
Custom Fields Not included Attributes are saved at the parent level.
Variations / Options Optional Enable Allow Create Variant if you want Secondary to create variants while it runs.
Multiple Warehouses Not included —
Feed Type Full feed The catalog slice covered by Secondary is provided each run.
Archive Support Supported (recommend manage in one place) Commonly managed via Primary to avoid conflicts.
Image paths (handled by “Get Inventory Images”):
  • /ftp_images/rsr_number/
  • /ftp_highres_images/rsr_number/
  • /ftp_images/new_images/
  • /ftp_highres_images/new_images/
If a product’s image file is missing from FTP but still referenced, the system removes that image entry to prevent broken thumbnails.
 
 
Optional but recommended

Keep your catalog up to date automatically

After configuring Get Inventory Primary and Get Inventory Secondary, you can schedule both jobs so items, inventory, and pricing update for you.

  • Schedule Primary to import new and updated items.
  • Schedule Secondary after Primary to refresh stock and pricing.
  • Adjust the cadence anytime if your supplier changes their update frequency.
How to schedule Get Inventory operations in Flxpoint
Click the animation to view it larger.

 

 

Order Operations

Configure Flxpoint to route orders to vendors for fulfillment and  import the shipment details, so they sync back to your sales channel and customer.

 

Send Fulfillment Requests

Supported

RSR — Send Fulfillment Requests

Introduction

Send Fulfillment Requests places orders to RSR via their Direct Connect API using your selected Mapping Template. You’ll (1) connect RSR, (2) set a few order options (email, fill-or-kill, holds), and (3) pick a mapping template to format the request and line items.

On this section
Setup Steps
  • 1 Connect RSR: Select the existing RSR API connection → click Save and Proceed.
  • 2 Configure Settings:
    • Email (required): Dealer email address that RSR should use.
    • Fill or Kill (optional): set to Y if you want RSR to cancel the order when it cannot fully fill it.
    • Advanced → Hold for X hours: pause sending for X hours before RSR receives the order.
    • Advanced → Send During Business Hours: only transmit during business hours.
    Click Save and Proceed.
  • 3 Select a Mapping Template: choose Send Purchase Orders 2 → click Save and Complete.
Order Routing with Dealer and Fulfillment Accounts as Separate Sources
Goal: Each RSR account should only handle the products intended for it.
Result: Orders automatically route to the correct RSR account without routing workflows, as long as your sources and Post Mapping filters are set up correctly.
  1. Set up both sources.
    Create two separate sources in your account:
    • RSR – Dealer Source
    • RSR – Fulfillment Source
    Each source connects to its own RSR account and holds only the items meant for that account.
  2. Apply Post Mapping Workflows to each source.
    Navigation: Source → Integrations → Get Inventory [Primary] → Post Mapping Workflow. These workflows restrict which items are imported into each source.
    📦 Fulfillment Source – Post Mapping Workflow Example

    Restrict this source to dropship/fulfillment items only. Typical rules include:

    • Zero-quantity rules for restricted brands.
    • Brand-based allow filters to keep only dropship-eligible brands.
    Example Post Mapping Workflow for the RSR Fulfillment source (dropship items only).
    RSR Fulfillment Post Mapping Workflow example
    🏬 Dealer Source – Post Mapping Workflow Example

    Restrict this source to dealer-eligible items only. Common rules include:

    • Blocking all dropship-only items from the dealer feed.
    • Brand-based allow lists for dealer-only brands.
    Example Post Mapping Workflow for the RSR Dealer source (dealer items only).
    RSR Dealer Post Mapping Workflow example
  3. Build inventory and link to listings.
    Once each source is properly filtered:
    • Map inventory to Products.
    • Link Products to Listings.
    If a listing is linked to the Dealer Source, all orders for that listing will route to RSR Dealer.
  4. Add both sources to one routing group.
    Go to Settings → Orders → Order Routing → Routing Groups and include both:
    • RSR – Dealer Source
    • RSR – Fulfillment Source
    Example routing group with both RSR Dropship and RSR Fulfillment as preferred sources.
    Order Routing Group with RSR Dealer and RSR Fulfillment sources

    No routing workflow rules are required in this setup.

  5. Let the routing engine choose the correct account.
    The routing engine decides which RSR account to use based on which source has the item in stock:
    • If the item exists in the Dealer Source, the order routes to RSR Dealer.
    • If the item exists in the Fulfillment Source, the order routes to RSR Fulfillment.
    Routing is not based on brand rules or routing workflows; it is driven by source separation and Post Mapping filters.
Final outcome: Each RSR account receives only the products intended for it, listings stay cleanly mapped, and orders route automatically to the correct RSR account with no extra routing workflows to maintain.
On this section
Template Index
Template Use Case What it Sends Availability
Send Purchase Orders 2 Place order (Send FR) to RSR Order header + lines (FR#/PO, Email, Fill/Kill, optional Hold, End Consumer, Store Name, SKUs/qty) Available
Order Operations → Place Order (Send FR)

Overview
Flxpoint creates the RSR place-order request using your Send FR Mapping Template. RSR requires End Consumer and Store Name as separate fields.

Field mapping (required / recommended)

  • End Consumer Name → from Shipping First + Last.
  • Store Name → map from Sales Channel → Store Name, Order → Company/Organization, or a static value.
  • Fallback: if Store Name isn’t mapped, we derive it from shipping name (legacy behavior).
  • Validation: each name part must be ≥ 2 characters; otherwise the request is blocked.
Field Mapping (key fields)
From (Source) To (RSR / Request) Type Required? Notes
Fulfillment Request Number PO / Reference Text Yes Mappable (FR#/PO#).
Shipping First/Last Name End Consumer Text Yes ≥ 2 characters per part.
Sales Channel Store Name / Company / Static Store Name Text Recommended Business/store identity.
Dealer Email (setting) Email Text Yes Configured in Setup Step 2.
Fill or Kill FillOrKill Option No Y = all or cancel.
Hold for X Hours Hold Number No Delays sending.
Order Items → SKU Line SKU Text Yes Sent to RSR.
Order Items → Quantity Line Qty Number Yes Units requested.
Mapping Rules
Rule Name Type Input Status What it Does
If FFL required, billing Name Conditional String Configured Sets billing name when FFL is required.
If FFL required, set billing phone Conditional String Configured Sets billing phone when FFL is required.
Create your own rules: Mapping Utilities → Mapping Rules → Create New Rule → Conditional → choose Input (String / Number / Boolean).
Note: after creation, a rule’s type and input can’t be changed.
Sets, Lists & Builders
Utility Availability How You Might Use It
Mapping Sets Optional — None created yet Compose custom references/notes.
Lists Optional — None created yet Allow / deny lists for rule conditions.
Product Builders Available (default) Default builder matches on Master SKU.
On this section
1️⃣ Understanding RSR shipping behavior
RSR handles shipping differently from most suppliers. In almost all RSR integrations:
  • For standard Fulfillment Request (FR) submissions, Flxpoint does not send a shipping method to RSR.
  • RSR selects the shipping service on their side based on your account preferences, order details, and carrier/service availability.
  • RSR’s internal shipping rules determine the final carrier and method.

In this default setup:

  • Do not create a Shipping Method in your RSR Source solely for RSR’s benefit.
  • Do not map a Shipping Method field in your Send FR template.
  • RSR automatically selects the most appropriate carrier / method for each order.

Only continue to the Shipping Method setup if your RSR representative has confirmed that your account is configured to receive a shipping method via the API.

2️⃣ When should you create a Shipping Method?
  • Your RSR dealer account explicitly allows you to send a shipping method via a custom Send Fulfillment Request template; or
  • Rate Shopping is enabled for this account/source and your rate-shopping provider requires a Source Shipping Method for routing.

If RSR has not enabled method selection for your account and you are not using Rate Shopping in a way that depends on it, you can skip creating a Shipping Method in this Source.

3️⃣ Creating Shipping Methods (only if your account can send a method)

If your account supports sending a method, configure Source Shipping Methods inside your RSR Source.

  • Navigation: Connections → Fulfillment Sources → [Your RSR Source] → Shipping Methods.
  • Click Add Method to open the Create Shipping Method screen.
Create Shipping Method screen inside your RSR Source (Connections → Fulfillment Sources → [RSR Source] → Shipping Methods → Add Method).
Create Shipping Method screen in Flxpoint

Complete the fields as follows:

  • Name → A clear label (for example, UPS Ground, FedEx 2-Day).
  • Shipping Code → One of RSR’s accepted codes (see table below).
  • Packages → Usually Best Fit, so Flxpoint can use predefined package sizes.
  • Carrier / Method → Choose the closest matching service to the RSR option you’ll request.

Expand Advanced only if needed:

  • Shipping Label Code (if you also purchase labels from Flxpoint).
  • Default Carrier Code.
  • Custom Carrier/Service Name if you want a more readable internal label.

Click Save to add the method.

4️⃣ RSR Shipping Codes (reference)

These are the codes RSR recognizes. Use them only if your RSR account allows sending shipping methods.

Carrier Method Supplier Shipping Code Supplier Shipping Carrier Name
FedEx FedEx 2 Day 2Day 2 Day
FedEx FedEx 3 Day 3Day 3 Day
FedEx Next Day Air NDAS Next Day Air Saver
FedEx Ground Grnd FedEx Ground
FedEx Standard Overnight 1Day Standard Overnight
UPS 2nd Day Air AM (2DM) 2Day 2nd Day Air AM
UPS 3 Day Select (3DS) 3Day 3 Day Select
UPS Ground Grnd UPS Ground
UPS Next Day Air (1DA) 1Day Next Day Air
UPS Next Day Air Early AM (1DM) NDam Next Day Early AM
UPS Next Day Air Saver (1DP) NDAS Next Day Air Saver
USPS Priority PRIO USPS Priority
5️⃣ Examples (only if your account can send a method)

Example 1 — Always request UPS Ground
In your custom Send FR template, map Shipping Method → static value Grnd.

Example 2 — Choose by order weight
Add a Conditional Rule:

  • If Total Weight < 1 lb → set Shipping Method = PRIO (USPS Priority).
  • Else → set Shipping Method = Grnd.

If your RSR setup does not accept a shipping method, leave this field unmapped—RSR will select the best option on their side.

On this section
Quick Checks
  • RSR API connection selected in Setup Step 1.
  • Email set; Fill or Kill and Hold reviewed.
  • Template Send Purchase Orders 2 selected in Setup Step 3.
  • Store Name mapped to a reliable business identity field.
Validation & Common Errors
  • Name length: each part of End Consumer and Store Name must be ≥ 2 characters.
    RSR validation: Store Name is invalid (each name part must be >= 2 characters).
    RSR validation: End Consumer name is invalid (each name part must be >= 2 characters).
  • “Duplicate Order”: a unique PO can be submitted once per year. Change PO/FR number and retry.
  • Error 86: “No items could be added to the order.” Ammunition requires a street address (forces FedEx Ground).
Operation Details
Capability Status Notes
Fulfillment Request Number Supported Mappable (FR#/PO#).
Customer Association Not Supported Not used in this request.
FR Item Association Supported Line SKU is sent.
Auto Acknowledgements Supported Receive WebRef on success.
Shipping Selection Not Supported RSR auto-selects shipping for standard FRs.
Custom Fields Not Supported Custom fields aren’t available.
Attachments Not Supported Files aren’t sent.
Limitations — Street addresses for ammunition; unique PO per year.
Troubleshooting checklist
  • Check 1 – “Store Name” mapped? If not, fallback may cause RSR to flag it.
  • Check 2 – Name length Ensure each name part ≥ 2 characters.
  • Check 3 – Name placement End Consumer = Shipping name; Store Name = business identity.
 
 

Get Shipments

Supported
Introduction

RSR – Get Shipments pulls shipment confirmations for your RSR orders. You’ll (1) connect RSR, (2) set how many days back to fetch, and (3) select the mapping template. RSR supports partial shipments; tracking numbers are returned. Carrier/method details are not included by RSR.

  • 1Connect RSR: Choose your existing RSR API connection (or create a new one) → click Save and Proceed.
  • 2Configure Settings:
    • Fetch Shipments Within Last X Days — required. Typical value: 7.
    Click Save and Proceed.
  • 3Select a Mapping Template: Choose RSR Get Shipments 2 → click Save and Complete.
What you’ll see
  • Three steps: Connect an Integration → Configure Settings → Define a Mapping Template.
  • A check mark appears next to each step after you finish it.
Template Index
Template Use Case What it Covers Availability
RSR Get Shipments 2 Shipment confirmations from RSR Shipped At date, Tracking Number, Item SKU, Item Quantity (ASNQty). No carrier/method labels in response. Available
Field Mapping (RSR Get Shipments 2)

These mappings mirror the Mapping Templates view.

RSR Field Flxpoint Shipment Field Level Type Required? Notes
DateShipped Shipment → Shipped At Header Date/Time No When RSR marks the shipment as shipped.
TrackingNum Shipment → Tracking Number Header Text Yes Tracking URL is not returned by RSR.
PartNum Shipment Item → SKU Item Text Yes Associates the shipped line to your catalog.
ASNQty Shipment Item → Quantity Item Number Yes Quantity shipped for the line item.
Rules You Can Use (Optional)
Example Rule Type Input When it Helps What it Does
Normalize Tracking Number Conditional String Clean/trim values before export to channels Removes spaces, uppercases, or validates length.
Fallback ship date Conditional Date Missing or null DateShipped Sets today’s date if RSR omits ship date.
Sets, Lists & Builders
Utility Availability How You Might Use It
Mapping Sets Optional — available Assemble or format values (e.g., build a combined note).
Lists Optional — available Reference lists for conditional rules (e.g., carriers that need special handling on your channel).
Product Builders Available (default provided) Not commonly needed for shipments; default builder is fine.
Quick Checks
  • RSR API connection is selected and saved in Step 1.
  • Fetch Shipments Within Last X Days has a value (e.g., 7).
  • Template RSR Get Shipments 2 is selected in Step 3.
  • Remember: RSR doesn’t send carrier/method labels—only the tracking number.
Operation Details
Capability Status Notes
Carrier & Methods Not Supported RSR returns tracking number only (no carrier/method labels).
Shipment Item Association Supported SKU (PartNum) is returned on items.
Partial Shipments Supported Orders can arrive in multiple shipments from RSR.
Invoice Information Not Supported Invoices are not included in the shipment response.
Custom Fields (CFs) Not Supported Only standard shipment fields are provided by RSR.
Limitation — Tracking URL is not provided by RSR.
FAQs

Why don’t I see carrier or method?
RSR’s response includes a tracking number but no carrier/method labels.

Will partial shipments import?
Yes. Each RSR shipment will attach to the original order with its own items and quantities.

How far back should I fetch?
Most teams use 7–14 days. Increase if you expect late confirmations.

 
 
Optional but recommended

You’re ready to automate this source

You’ve finished setting up this source. If you’d like, you can now put its operations on an automated schedule.

  • Select the operations to schedule (for example, Get Inventory, Get Orders, Send Fulfillment Requests, Get Shipments).
  • Pick how often and when they should run. You can edit or pause schedules anytime from the operations screen.

Tip: A daily schedule for key operations is a simple place to start.

How to schedule source operations in Flxpoint
Click the animation to view it larger.

 

 

Troubleshooting Common Errors

Common issues and solutions for RSR integration. Expand each item to learn more.

Still need help? If you’re experiencing issues not covered here, contact RSR support or your Flxpoint account manager.

Contact Support

 

 

 

 

 

Related Articles

Kinsey's as a Source

Overview Integrating Kinsey's as a source in Flxpoint allows you to access a wide...

Sports South as a Source

Sports South is a reliable supplier source that offers a wide range of sporting g...

Lipseys as a Source

This document will cover how to connect Lipseys as a source and what integrations...

Zanders as a Source

Overview This document will cover how to connect Zanders to Flxpoint via FTP and ...