Rothco as a Source
July 2, 2026
Summary
Rothco is a wholesale supplier of military, tactical, and outdoor gear. Connect it as a source with a single Rothco API Key from the Rothco API Portal - one connection covers full catalog import, fast inventory and pricing refresh, dropship order submission, and shipment tracking, all on Rothco's V2 API.
What this integration does
Get Inventory (Primary)
Imports the full Rothco catalog - product lines, variants, attributes, categories, images, pricing, and inventory levels
Get Inventory (Secondary)
Fast refresh of SKU, Cost, MAP, MSRP, and Quantity between full Primary runs - no catalog re-import
Send Fulfillment Requests
Submits Flxpoint Fulfillment Requests to Rothco as dropship orders using the same Rothco connection
Get Shipments
Pulls tracking number, shipped date, method, and item-level shipped quantities back into Flxpoint
How to connect - credentials you need
In your Rothco source, open Integrations → Get Inventory [Primary], click Start Creating Integrations, choose Rothco, then Create New connection. Paste your API Key, click Test Connection, then Save Connection. The same connection is reused by every Rothco operation.
API KeyRequired
The single API Key from your Rothco API Portal. New connections must use your Rothco API V2 Key - Flxpoint runs on Rothco's V2 API, so existing connections keep working ahead of Rothco's V1 retirement on June 26, 2026. The same key is reused by every Rothco operation.
One key covers inventory, orders, acknowledgments, and shipments - no separate keys per integration. Obtain it via Rothco's Sandbox → test order → approval → Live Mode flow (see below).
Billing EmailSetting
The Dealer email that receives order confirmations from Rothco. Entered in the Configure Settings step of Send Fulfillment Requests, not on the connection screen.
Required before submitting dropship orders.
New Rothco accounts must complete Rothco's Sandbox approval before live orders can flow: switch to Sandbox Mode, place a test dropship order, send the returned Order Confirmation ID to Rothco for approval, then switch to Live Mode and copy your API Key. If Test Connection fails, paste a fresh V2 API Key from your Rothco API Portal. When adding the source, choose Rothco - not Rothco (Legacy), which is hidden for new setups.
Important - read before configuring
One API Key covers all operations - no separate keys per integration
The same Rothco connection (API Key) is reused across Get Inventory (Primary), Get Inventory (Secondary), Send Fulfillment Requests, and Get Shipments. Create the connection once in Get Inventory (Primary) and simply select it in every other operation.
New accounts must complete Sandbox approval before live orders can flow
Rothco requires a test order placed in Sandbox Mode and approved by their team before your account can switch to Live Mode. Until approval is complete, live order submission fails. The flow is: switch to Sandbox → place a test order → send the Order Confirmation ID to Rothco → after approval, switch to Live Mode and copy the live API Key.
Enable Archive / Un-Archive on only one inventory job - Primary or Secondary, never both
Turning on Archive/Un-Archive in both Get Inventory (Primary) and Secondary makes items archive then immediately restore each cycle, which can drop products to zero quantity unexpectedly. Pick one job to own archival - typically Primary.
Restricted items won't appear until your account is enrolled in Rothco's Authorized Reseller Program
Some Rothco products are gated behind the Authorized Reseller Program and will not appear in your catalog import until your Rothco Dealer account is approved for those brands. Review your enrollments in the Rothco Dealer Portal under Online Catalog → Authorized Reseller Programs. Once enrollment is confirmed the items appear automatically - no Flxpoint configuration needed.
Mapping - fields to know
| Rothco Source Field | Maps To - Flxpoint Field |
|---|---|
| Inventory: SKU Code | → SKU. Variant identifier. Required. e.g. RTH-12345. |
| Inventory: Product Line Code | → Parent SKU. Links variants to a parent product. Required. |
| Inventory: Product Line Name | → Title. Display title. Required. |
| Inventory: Short Description | → Description. Short description. Optional. |
| Inventory: Price | → Cost. Dealer cost in USD. Required. |
| Inventory: MSRP Price | → MSRP. Manufacturer suggested retail price. Optional. |
| Inventory: MAP Price | → MAP. Minimum advertised price. Optional. |
| Variant Inventory Level | → Quantity. On-hand units. Required. High-stock 99+ is converted to a number automatically. |
| Inventory: Weight | → Weight. Product weight. Optional. |
| Inventory: UPC | → UPC. Barcode. Optional. |
| Inventory: Product Category 1 | → Primary Category. Top-level category. Optional. |
| Inventory: Product Category 2 | → Sub Category. Second-level category. Optional. Default template: Rothco V2 GIP. |
| Rothco Variant Field | Maps To - Flxpoint Field |
|---|---|
| Inventory Variant: SKU Code | → SKU. Variant identifier. Required. |
| Variant Inventory Level | → Quantity. On-hand units. Required. |
| Inventory Variant: Price | → Cost. Dealer cost in USD. Required. |
| Inventory Variant: MAP Price | → MAP. Optional. |
| Inventory Variant: MSRP Price | → MSRP. Optional. Reuses the same Rothco connection as Primary; default template Rothco V2 GIS. Catalog fields (titles, images, categories) belong to Primary. |
| Flxpoint FR Field | Maps To - Rothco Order Field |
|---|---|
| Fulfillment Request Number | → PO / Reference. Required. Must be unique - Rothco rejects duplicate references. e.g. FR12345. |
| Billing Email | → Billing Email. Required. Dealer email for order confirmations; set in the Configure Settings step, not the mapping template. |
| Full Name | → Ship To Name. Required. |
| Address Line 1 | → Ship To Address Line 1. Required. |
| Address Line 2 | → Ship To Address Line 2. Optional. |
| City | → Ship To City. Required. |
| State | → Ship To State. Required. |
| Postal Code | → Ship To ZIP. Required. |
| Customer Email | → Customer Email. Required. |
| SKU | → Item: SKU. Required. e.g. RTH-12345. |
| Quantity | → Item: Quantity. Required. |
| Hold for X Hours | → Hold. Optional; set in Configure Settings to delay transmission (default 0). |
| Shipping Method | Most Rothco accounts use vendor-selected shipping - leave this unmapped and let Rothco pick the carrier. Only map a code from Rothco's shipping-codes reference (e.g. UPS - Ground, FXGHD) if your account is configured to receive one. Default template: Send Purchase Orders. |
| Rothco Shipment Field | Maps To - Flxpoint Field |
|---|---|
| Shipment: Tracking Number | → Tracking Number (header). Required. |
| Shipment: Shipped At | → Shipped At (header). Optional; add a fallback rule if Rothco omits the date on a shipment. |
| Shipment: Shipping Method Name | → Method (header). Optional. |
| Shipment: Shipping Method Code | → Carrier / Note (header). Optional. |
| Shipment: PO Number | → Order / PO Reference (header). Optional; used to link the shipment to the original FR/PO. |
| Shipment Item: SKU Code | → Shipment Item: SKU (item). Required. |
| Shipment Item: Quantity Shipped | → Shipment Item: Quantity (item). Required. Actual quantity shipped per line - not copied from the PO; partial shipments report exactly what was sent. Default template: Get Shipments 2. |
Common issues
Connection failing or Test Connection returning an error
The usual causes are an incorrect, expired, or rotated API Key, or a new account still in Sandbox Mode. Open the Rothco connection and click Test Connection; if it fails, paste a fresh API Key from your Rothco API Portal. For new accounts, confirm you completed the Sandbox approval flow (test order → send Confirmation ID to Rothco → switch to Live Mode). If previously-working credentials now fail, contact Rothco to confirm your API access is still active.
Order rejected - required field missing or API validation error
Rothco strictly enforces required fields on every dropship order, and Flxpoint surfaces the exact Rothco API error in the job notification (e.g.
Field "email" of required type "String!" was not provided.). Read the error to find the failing field, then audit your Send Fulfillment Requests mapping template so it supplies a non-empty value for every order. Required fields: Ship To Name, Address Line 1, City, State, ZIP, Customer Email, SKU, and Quantity.Order submission failing - processing error with shipping method
Most Rothco accounts use vendor-selected shipping (Rothco picks the carrier), so no shipping method should be sent. Remove the shipping-method mapping from your Send Fulfillment Requests template entirely. Only map a method if your account is explicitly configured to receive one via the API, using a code from Rothco's shipping-codes reference (e.g.
UPS - Ground, FXGHD).Items missing from the catalog import
Most often caused by Authorized Reseller Program restrictions. Check your Rothco Dealer Portal under Online Catalog → Authorized Reseller Programs and review your brand enrollments - restricted items appear automatically once enrollment is confirmed. If items are still missing, check the job log for skipped catalog pages (Flxpoint skips pages with internal errors rather than aborting the run) and re-run the job.
Products unexpectedly archived / dropping to zero quantity
Almost always caused by Archive/Un-Archive being enabled on both Get Inventory (Primary) and Secondary - the two jobs conflict, one archiving items the other just restored. Confirm Archive is enabled on only one operation (typically Primary) and turn it off on Secondary if it's currently on.
Shipments or tracking not importing
First confirm the order actually shipped on Rothco's side - a "no data" response just means no shipment exists yet. If shipments exist but don't import, check that Tracking Number (header) and SKU + Quantity Shipped (item level) are mapped in your Get Shipments template. If carrier/method is blank, add Shipping Method Name and/or Shipping Method Code. If the shipment is older than your window, increase Fetch Shipments for Days to 15 or 30. If you run two Rothco accounts, confirm Get Shipments is scheduled on both sources.
FAQs
Do I need to do anything for the Rothco V2 API migration?▸
No action is required for existing connections. Flxpoint already migrated the Rothco integration to the V2 GraphQL API ahead of Rothco's V1 deprecation date (June 26, 2026), so your existing connection keeps working without setup changes. If Rothco issues a replacement V2 API Key during the transition, paste it into the API Key field and click Test Connection - that's the only step needed.
What does the "99+" quantity value mean in Rothco inventory?▸
Rothco reports high-stock items as
99+. Flxpoint automatically converts this to a numeric value during Get Inventory - no mapping rule or manual handling needed. The converted quantity appears in your Global Inventory Pool like any other number.Should I use auto-acknowledge on Send Fulfillment Requests, or the separate Get FR Acknowledgments operation?▸
For most setups leave auto-acknowledge ON (the default) - when Send Fulfillment Requests succeeds, the FR is automatically marked acknowledged. The separate Get FR Acknowledgments operation is only needed if you want acknowledgment driven by Rothco's actual order status (Confirmed / Fully Shipped / Closed). To use it, turn ON Use 'Get FR Acknowledgements' process under Send FR → Advanced Settings and run Get FR Acknowledgments on a schedule. Most accounts don't need this.
Can I operate separate Dealer and Fulfillment/Dropship Rothco accounts in Flxpoint?▸
Yes. Create two separate Rothco Sources - one per Rothco account - each with its own API connection. Add both sources to the same routing group and the routing engine picks the correct account based on which source has the item in stock. Use Post-Mapping Workflow filters on each source to scope which products each account can fulfill if the catalogs overlap.
How far back should I set the Fetch Shipments window in Get Shipments?▸
Most setups work well with 10 or 15 days. Set it to 30 if you expect late tracking confirmations or if Rothco sometimes ships several days after the FR is sent. The window controls how many days back Flxpoint looks for shipped Rothco orders on each run - orders shipped before the window aren't retrieved.
What happens when Rothco partially ships an order?▸
Rothco returns actual shipped quantities per line item, not copies of the original PO quantities. Get Shipments imports each shipment with its own items and quantities, so partial shipments attach to the original order as separate shipment records; the unshipped portion stays open until a follow-up shipment completes it. Get FR Acknowledgments uses the same ordered-vs-shipped comparison to mark partially cancelled items automatically when an order closes.