Rothco is a well-known supplier of military, tactical, and outdoor products. When integrated as a source in Flxpoint, Rothco allows you to access and automate the management of their extensive product catalog. This includes syncing inventory, managing product data, and automating order fulfillment. Key requirements typically include API credentials like a token or API key to establish a secure connection. Once set up, Flxpoint can regularly update product listings and stock levels, ensuring your online store reflects accurate information from Rothco's catalog.
How to connect
🧭 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., Rothco as Source). Then choose the Source Type that best fits how this Source will be used.
After selecting the Source Type, click Save & Next.
Choose the right Source Type
Recommended
Vendor Warehouse
A vendor’s warehouse where you send Fulfillment Requests for wholesale and/or dropship fulfillment.
- You place POs/FRs to the supplier to fulfill orders to your customers.
- You don’t hold this inventory yourself.
Internal Warehouse
Your own warehouse or store where you keep physical inventory in stock for fulfillment.
- You stock and ship items from your facility.
- Pick/pack/ship is handled by your internal team.
External Warehouse
An external warehouse where you keep your inventory stocked, fulfilled by a 3PL partner.
- 3PL or external provider ships your owned inventory.
- You replenish inventory to that partner.
Product Data Source
A data source of rich product content (images, titles, descriptions). Not a physical fulfillment source.
- You only need content enrichment (no fulfillment from this source).
- Use to enhance product details, not to ship orders.
For Rothco: select Vendor Warehouse. This enables sending Fulfillment Requests to Rothco and using their inventory for routing.
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.
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.
Step 5 — Shipping Cost Estimations
Pick one:
- Yes, Use Rate Shopping (Real-Time Estimates).
- No, Set Up via Rules.
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 7 — Shipping Methods and Step 8 — Source Location in Phase 2 below, then return (if needed) to finalize.
🚚 Phase 2: Shipping Methods & Source Location (Finish the Wizard)
+
Goal
Ensure orders route to Rothco by creating Shipping Methods that your sales channel shipping options can map to. This is the routing trigger.
Step 7 — Shipping Methods
In the Wizard, click Add Method and create a minimal, reliable set:
- Name: Standard Ground Policy: Standard/Ground
- Name: Expedited (2-Day) Policy: Expedited/2-Day
- Name: Priority (Overnight) Policy: Priority/Overnight
Tip: If you used Rate Shopping earlier, you still need at least one method here so routing can match by Policy / channel shipping code.
Carrier / Method Fields
Leave Carrier/Method generic if unsure. Rothco will choose the best-fit service at fulfillment. The important part is the Policy matching your channel option.
Step 8 — Source Location (Ship From)
Enter the Ship From address:
- Address, City, State/Code, Postal Code, Country/Code
- Optional: Contact Name, Phone, Email
Finish the Wizard
Review Steps 7–8, then click Save and Complete. The wizard is now finished.
Next: Proceed to Phase 3 to create the Rothco Integration under Integrations.
🔌 Phase 3: Create the Rothco Integration (after the wizard)
+
Open Integrations
From your completed Source, go to Integrations and click Start Creating Integrations. Choose the operation you want to set up first (e.g., Get Inventory or Send Fulfillment Requests).
Select Rothco
Search Rothco in the catalog (Connector or Supplier tab). Select Rothco → Save and Proceed.
Create or Reuse a Connection
Choose an existing connection and click Test, or select Create New Connection.
Enter Credentials (Rothco)
The Rothco connection uses a single credential:
- API Key: paste the key from your Rothco API Portal.
How to get your Rothco API Key & move from Sandbox to Live
- Go to the API Portal Settings in your Rothco account.
- Switch the account to Sandbox Mode and save.
- Create a test order using the Dropship API; note the Order Confirmation ID from the API response.
- Send that Confirmation ID to Rothco for review/approval.
- After Rothco confirms, return to API Portal Settings and change to Live Mode.
- Copy your API Key from the portal and paste it here in the connection.
Tip: Keep the same key secure. If you rotate it in the Rothco portal, update the connection here and re-test.
Important: Orders submitted while in Sandbox Mode are NOT fulfilled. Switch to Live Mode only after your sandbox test is approved.
Test & Save
Click Test Connection. If successful, click Save Connection.
If test fails:
- Confirm the API Key is current and copied without extra spaces.
- If you just switched modes, wait a minute and retry the test.
- Verify your Rothco account has API access enabled in the portal.
Next step for orders (FLX users): After saving the connection, build your Send Fulfillment Requests integration. When you are ready for live orders, ensure your Rothco portal is in Live Mode.
✅ Phase 4: Mapping & Activation
+
Inventory Field Mapping
Configure mapping for Get Inventory: map SKU, Quantity, Price, Title, Description. Add transforms if needed.
SKU & Master SKU (Linking Strategy)
Use a normalized Master SKU to link products across sources and channels.
- Do NOT add prefixes in Source Inventory (keep supplier SKU exactly as provided by Rothco).
- Create any prefix in the Master SKU only (e.g., transform: "ROTH-" + [SupplierSKU]).
- If importing listings, link channel SKUs to the same Master SKU so publishing/updates sync correctly.
Activate & Monitor
Click Save and Complete. Monitor runs and notifications under Integrations.
No items? Confirm mapping saved, that the integration uses the correct Rothco Connection, then re-run.
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates.
Get Inventory (Primary)
Supported
Rothco – Get Inventory [Primary]
Introduction
Rothco – Get Inventory [Primary] imports your Rothco catalog into Flxpoint. You’ll (1) connect Rothco, (2) choose settings, and (3) select a mapping template. When a step is finished, you’ll see a check mark next to it.
- 1Connect Rothco: Select Rothco in the catalog and click Save and Proceed.
-
2Choose Settings:
-
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).
-
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.
- 3Select a Mapping Template: Choose Rothco Get Source Products 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.
Template Index
| Template | Use Case | What it Covers | Availability |
|---|---|---|---|
| Rothco Get Source Products 1 | Get Inventory (Primary) | Client pricing as Cost (USD), Quantity, two-level Categories, Weight/Dimensions (inches & pounds), identifiers (UPC/MPN), brand/title/description, product-level images, and option attributes (see below). | Available |
Field Mapping (Rothco Get Source Products 1)
This is a friendly overview of how common Rothco fields flow into Flxpoint.
| Rothco 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 | Product → Description | Text | No | Standard product copy. |
| Client / 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 (product level) | Media → Images | URLs | No | Multiple images supported at product level. |
|
Option/Variation Attributes (when present): Color, Size, Length, Waist Size, Width, Shoes Size, Head Size, Ring Size, Emblem, Orientation, Packaging, Piece, Chest Size |
Variants/Options → Attributes | Text | No | Used to create options/variants where applicable. |
Units: Dimensions are in inches and weight is in pounds. Add conversion rules if your channel expects other units.
Categories: Two category levels are available. If none are provided, a “General” category may be set.
Rules You Can Use
| Rule | Type | Input | When it Helps | What it Does |
|---|---|---|---|---|
| Convert ounce to pound | Conditional | Number | Normalizing weight inputs | Converts ounces to pounds wherever needed. |
| 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. |
| Set a string based on Main Category | Conditional | String | Adding category-based labels | Outputs a string value when the category matches your condition. |
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.
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 inputs into a single output (e.g., build a normalized Title). |
| Lists | Optional — available | Maintain reusable value lists (e.g., approved brands or categories). |
| Builders | Optional — available | Create a custom output structure if a channel needs it. |
Quick Checks
- Rothco is connected and saved on Step 1.
- Archive/Un-Archive is set the way you want (enable in one place only).
- A mapping template is selected (Rothco Get Source Products 1).
- Test first, then enable any schedules or live workflows.
Operation Details (What’s included)
| Feature | Availability | What to Expect |
|---|---|---|
| Client Pricing (& Currency) | Available | Dealer-specific price saved as Cost (USD). |
| Generic Pricing | Available | Generic pricing supported if present. |
| Quantity | Available | Imports current stock levels. |
| Weights & Dimensions | Available | Dimensions in inches; weight in pounds. |
| Images | Available | Multiple images available at product level. |
| Categories | Available | Two levels you can map (defaults to “General” if not provided). |
| Variations / Options | Available | Attributes such as Color/Size/Length/Width, Shoes Size, Head Size, Ring Size, Emblem, Orientation, Packaging, Piece, Chest Size. |
| Multiple Warehouses | Not included | Single-warehouse inventory in this feed. |
| Archive Support | Available | Automatically archive/un-archive based on the feed. |
| Feed Type | Full feed | The entire catalog is provided each run. |
| Custom Fields | Not included | — |
Get Inventory (Secondary)
Supported
Get Inventory [Secondary] — Rothco
Introduction
Rothco – Get Inventory [Secondary] brings in variant-level pricing and stock to enrich your catalog. You’ll (1) connect Rothco, (2) review a couple of settings, and (3) select a mapping template. When a step is finished, you’ll see a check mark next to it.
- 1Connect Rothco: Choose Rothco and click Save and Proceed.
- 2Configure Settings:
- 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. Use this in either Primary or Secondary (not both).
- Allow Create Variant — enable if you want Secondary to create product variants when new variant rows appear in the feed.
- 3Select a Mapping Template: Choose Rothco Get Inventory Secondary 2 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.
Template Index
| Template | Use Case | What it Covers | Availability |
|---|---|---|---|
| Rothco Get Inventory Secondary 2 | Get Inventory (Secondary) | Generic pricing (Price, MSRP, MAP), Client pricing (saved as Cost where applicable), Quantity, Variant SKU via Rothco Variation ID, and identifiers needed for variant rows. | Available |
Field Mapping (Rothco Get Inventory Secondary 2)
Friendly overview of common Rothco fields flowing into Flxpoint.
| Rothco Field | Flxpoint Field | Type | Required? | Notes for You |
|---|---|---|---|---|
| Rothco Variation ID / Item Variation Id | Product → SKU (variant) | Text | Yes | Used to import variant SKUs for Secondary rows. |
| Price | Pricing → Price | Number | No | Generic pricing. |
| MSRP | Pricing → MSRP | Number | No | Manufacturer suggested price. |
| MAP | Pricing → MAP | Number | No | Minimum advertised price. |
| Client/Dealer Price (when provided) | Pricing → Cost | Number | No | Saved as Cost for client-specific pricing. |
| Inventory | Inventory → Quantity | Number | Yes | Current stock level per variant row. |
| Rothco Item No | Identifiers → MPN or secondary identifier | Text | No | Use as an additional reference identifier when needed. |
| Item Index | — | Text | No | Optional helper field; map only if your workflow needs it. |
Prebuilt Rule: Import Variant SKUs via Rothco Variation ID — creates/aligns variant SKUs using the Variation Id in the incoming file.
Rules You Can Use
| Rule | Type | Input | When it Helps | What it Does |
|---|---|---|---|---|
| Import Variant SKUs via Rothco Variation ID | Filter / Transform | String | Populating or correcting variant SKUs from source rows | Sets the variant SKU using the Variation Id field on each row. |
| Fallback Cost from MAP (optional) | Conditional | Number | When Cost is missing but MAP exists | Writes MAP to Cost if Cost is empty (adjust to your policy). |
| Zero-out Negative Inventory | Conditional | Number | Normalize bad data from feed | Sets Quantity to 0 if incoming value < 0. |
Quick Checks
- Rothco is connected and saved on Step 1.
- Decide where to enable Archive/Un-Archive (Primary or Secondary — not both).
- Turn on Allow Create Variant if you expect new variant rows.
- Confirm the template Rothco Get Inventory Secondary 2 is selected.
- Test a manual run before enabling schedules.
Operation Details (What’s included)
| Feature | Availability | What to Expect |
|---|---|---|
| Generic Pricing (& Currency) | Available | Map, MSRP, Price fields are available. |
| Client Pricing (& Currency) | Available | Dealer/client price can be saved as Cost. |
| Quantity | Available | Quantity is available in the inventory field. |
| Archive Support | Available | Automatically archive/un-archive based on the feed. |
| Multiple Warehouses | Not included | Secondary does not handle multi-warehouse quantities. |
| Weights & Dimensions (& Units) | Not included | Use Primary if you need dimensions/weight. |
| Delta Feed vs Full Feed | Not included | This runs as a full feed import. |
| Custom Fields (Variants Only) | Not included | Variant-level custom attributes are not mapped here. |
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring a seamless integration between order processing and shipment tracking.
Send Fulfillment Requests
Supported
Send Fulfillment Requests — Rothco
Introduction
Send Fulfillment Requests places orders to Rothco via API using your selected Mapping Template. You will (1) connect the Rothco integration, (2) configure basic order options, and (3) select a mapping template to format the request and line items.
- 1Connect Rothco: Choose an existing Rothco connection or create a new one (enter your API Key) → Test → Save → Save and Proceed.
-
2Configure Settings:
- Billing Email (required): Dealer email for confirmations.
- Advanced → Hold for X hours: Pause sending for X hours.
- Send During Business Hours: Only transmit during business hours.
- 3Select a Mapping Template: Choose your Send Purchase Orders template → Save and Complete.
Rothco Sandbox → Live (required by Rothco)
- Go to the API Portal Settings page (Rothco).
- Switch to Sandbox Mode and save.
- Create a test order using the Dropship API and capture the order confirmation ID from the response.
- Share the confirmation ID with Rothco for review/approval.
- Once approved, return to the API Portal and change settings to Live Mode. Begin creating live orders.
Note: Your API key from Rothco is required in the Flxpoint connection.
Template Index
| Template | Use Case | What it Sends | Availability |
|---|---|---|---|
| Send Purchase Orders | Place order (Send FR) to Rothco | Order header + lines (FR/PO, Email, optional Hold, SKUs/qty) | Available |
Field Mapping (key fields)
| From (Source) | To (Rothco / Request) | Type | Required? | Notes |
|---|---|---|---|---|
| Fulfillment Request Number | PO / Reference | Text | Yes | Mappable (FR#/PO#) |
| Dealer Email (setting) | Text | Yes | Configured in Step 2 | |
| Hold for X Hours | Hold | Number | No | Delays sending |
| Order Items → SKU | Line SKU | Text | Yes | Sent to Rothco |
| Order Items → Quantity | Line Qty | Number | Yes | Units requested |
Mapping Rules
| Rule Name | Type | Input | Status | What it Does |
|---|---|---|---|---|
| If Dangerous Goods, force Ground | Conditional | String/Boolean | Example | Sets shipping preference to Ground (if your account supports sending a method) |
Sets, Lists & Builders
| Utility | Availability | How You Might Use It |
|---|---|---|
| Mapping Sets | Optional | Compose static notes or references |
| Lists | Optional | Allow/deny lists for conditional rules |
| Product Builders | Available (default) | Default builder matches on Master SKU |
Important: Many Rothco accounts use vendor selection for shipping; if your account allows sending a method,
use the codes below in your custom template or rules.
Collect Shipping Methods
| Code | Description |
|---|---|
| UPSCOL | UPS Collect |
| UPS3DC | UPS Collect (3 Day) |
| UPSXSC | UPS Express Saver Collect |
| UPSEXP | UPS Expedited Collect |
| UPSBAC | UPS 2nd Day Air (AM) Collect |
| UPSBLU | UPS 2nd Day Air Collect |
| UPSRDC | UPS Next Day Air Collect |
| FXE2CO | FedEx Collect |
| FXGC | FedEx Collect |
| FXSO | FedEx Collect |
| FXSPC | FedEx Smart Post Collect |
| FXITPC | FedEx International Priority Collect |
| FX3DCO | FedEx Express Saver Collect |
| DHLGRC | DHL Ground Collect |
| DHLCOL | DHL Express Collect |
Simple (Available Delivery Timeframes)
| Code | Name |
|---|---|
| UPS – Ground | Ground (1–5 Days) |
| UPS3DY | Three Day Air |
| UPSBLU | Two Day Air |
| UPSRED | Next Day Air |
| STANDARD | Standard delivery |
| TWODAY | Two Day delivery |
| THREEDAY | Three Day delivery |
Advanced (Available Carriers and Services)
| Code | Description |
|---|---|
| PRIOR | USPS Priority Mail |
| TRUCK | Truck |
| PICKUP | Pick up at Rothco |
| UPSSURE | UPS Sure Post |
| FXSP | FedEx Smart Post |
| FXSOPP | FedEx Standard Overnight |
| FXGHD | FedEx Ground Home Delivery |
Examples
Example — Always use UPS Ground (if allowed)
Map Shipping Method → static value UPS – Ground or code UPSSURE/FXGHD per your preference.
If your account does not accept a method, leave this unmapped; Rothco will select the best option.
Quick Checks
- Rothco connection selected and API key valid.
- Billing Email set; optional Hold reviewed.
- Correct Send Purchase Orders template selected.
Operation Details
| Capability | Status | Notes |
|---|---|---|
| Fulfillment Request Number | Supported | Mappable (FR#/PO#) |
| FR Item Association | Supported | Line SKU and Qty |
| Auto Acknowledgements | Supported | Receive confirmation on success |
| Shipping Selection | Varies by account | Use codes above only if enabled for your account |
| Custom Fields | Not Supported | — |
| Attachments | Not Supported | — |
Troubleshooting checklist
- Sandbox vs Live: Ensure Rothco has approved your Sandbox test and you’ve switched to Live.
- Duplicate PO: If blocked, change the FR/PO reference and retry.
- Shipping method errors: Remove method mapping if your account isn’t enabled to accept one.
Get Shipments
Supported
Rothco – Get Shipments
Introduction
Get Shipments pulls shipment confirmations for your Rothco orders. You’ll (1) connect Rothco, (2) choose how many days back to fetch (5/10/15/30), and (3) select the mapping template. Rothco returns tracking numbers and may also include Shipping Method/Shipping Code that you can map to your shipment fields.
- 1Connect Rothco: Choose your existing Rothco connection (or create a new one) → Save and Proceed.
-
2Configure Settings:
- Fetch Shipments for Days — required. Options: 5, 10, 15, 30.
- 3Select a Mapping Template: Choose Get Shipments 2 → 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 |
|---|---|---|---|
| Get Shipments 2 | Shipment confirmations from Rothco | Tracking Number, optional Shipping Method/Code; item-level SKU & quantity when provided. | Available |
Field Mapping (Get Shipments 2)
These mappings mirror the Mapping Templates view.
| Rothco Field | Flxpoint Shipment Field | Level | Type | Required? | Notes |
|---|---|---|---|---|---|
| Tracking Number | Shipment → Tracking Number | Header | Text | Yes | Primary tracking identifier. |
| Shipping Method | Shipment → Method | Header | Text | No | Human-readable method label when provided. |
| Shipping Code | Shipment → Carrier (or Note) | Header | Text | No | Vendor code; optionally map to Carrier or store in Note. |
| Part/SKU | Shipment Item → SKU | Item | Text | Yes (if item-level provided) | Associates shipped line back to catalog. |
| Quantity (ASNQty) | Shipment Item → Quantity | Item | Number | Yes (if item-level provided) | Qty shipped per line. |
| — | Shipment → Shipped At | Header | Date/Time | No | Use a rule to set a fallback if Rothco omits it. |
Rules You Can Use (Optional)
| Example Rule | Type | Input | When it Helps | What it Does |
|---|---|---|---|---|
| Normalize Tracking Number | Conditional | String | Clean/trim before export to channels | Uppercases, trims spaces, validates length. |
| Fallback ship date | Conditional | Date | Missing Shipped At | Sets today’s date when source is empty. |
Sets, Lists & Builders
| Utility | Availability | How You Might Use It |
|---|---|---|
| Mapping Sets | Optional — available | Assemble combined notes (e.g., “{{Carrier}} {{Method}}”). |
| Lists | Optional — available | Reference codes to translate Method labels. |
| Product Builders | Available (default) | Not commonly needed for shipments. |
Quick Checks
- Rothco connection is selected and saved in Step 1.
- Fetch Shipments for Days has a selected value (5/10/15/30).
- Template Get Shipments 2 is selected in Step 3.
- Map Shipping Method/Shipping Code if you want labels in channels; otherwise tracking alone is sufficient.
Operation Details
| Capability | Status | Notes |
|---|---|---|
| Tracking Number | Supported | Primary identifier returned by Rothco. |
| Carrier & Methods | Supported | Use Shipping Code/Shipping Method to populate labels. |
| Shipment Item Association | Supported | SKU and quantity when item-level data is present. |
| Invoice Information | Not Supported | Invoices are not included in the shipment response. |
| Custom Fields (CFs) | Not Supported | Standard shipment fields only. |
| Tracking URL | — | Build via channel/carrier if needed. |
FAQs
How far back should I fetch?
Most teams use 10–15 days. Increase to 30 days if you expect late confirmations.
Why is Carrier or Method blank?
Map Shipping Method and/or Shipping Code in the template; otherwise only tracking will populate.
Can partial shipments import?
Yes. Each shipment attaches to the order with its own items and quantities.