Flxpoint Knowledge

Contact us

Rothco as a Source

Table of Contents

How to connect Product Operations Order Operations

In this guide, you'll learn how to set up Rothco as a source in Flxpoint — create the source, connect via API Key, and configure inventory, dropship orders, acknowledgments, and shipments. Rothco rolled out an updated API that Flxpoint already uses, so existing connections continue to work without setup changes; the older API version is being retired by Rothco on June 26, 2026.

 

 

Add Source and Establish Connection

Heads-up — Rothco API update: Rothco is rolling out an updated API and retiring the older version on June 26, 2026. Flxpoint has already moved this integration to the new API, so your existing Rothco connection continues to work without any setup changes. The newer integration adds a wider operation set — full catalog import, fast inventory refresh, dropship order submission, acknowledgments, and shipment confirmations with item-level quantities.

If Rothco issues you a replacement API Key during this transition, paste it into the API Key field below and click Test 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., Rothco). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most Rothco 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 Fulfillment Requests to Rothco so they ship directly to your customers (dropship).
  • 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 Rothco: select Vendor Warehouse. This enables sending Fulfillment Requests to Rothco 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. Vendor reporting and the optional vendor portal will be enabled.
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 proceed to Phase 3 to create your Rothco connection.
🚚 Phase 2: Shipping Methods & Source Location +
Goal

Finish the Source Wizard by adding at least one Shipping Method and confirming your Ship From location.

Step 1 — Shipping Methods
Add at least one shipping method (e.g., Standard Ground). Method names drive routing — the routing engine matches the shipping method on the order to the methods you configure here.
Tip: Many Rothco accounts use vendor-selected shipping (Rothco picks the carrier). If that's your setup, configuring method names is enough. See Send Fulfillment Requests → Shipping Codes Reference below for the carrier codes available if your account is configured to receive a specific shipping method via the API.
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.
🔑 Phase 3: Create Your Rothco Connection +
Goal

Rothco uses a single API Key for all operations. One connection covers inventory, orders, acknowledgments, and shipments — you don't need a separate connection per integration.

Step 1 — Open Get Inventory [Primary] and start
Inside your Rothco source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations. In the connector gallery, choose Rothco.
Step 2 — Select or Create a Rothco Connection
When the Select Connection dialog opens, pick an existing Rothco connection or click Create New.
Step 3 — Enter Your Rothco API Key
The Rothco connection requires a single API Key from your Rothco API Portal. The same key is reused by all Rothco operations — no separate keys for each integration.

How to get your Rothco API Key

  1. Sign in to your Rothco account and open API Portal Settings.
  2. Switch to Sandbox Mode and save.
  3. Place a test order through Rothco's dropship process; capture the Order Confirmation ID Rothco returns.
  4. Send that Confirmation ID to Rothco for approval.
  5. After approval, switch to Live Mode and copy your API Key.
For new accounts: Rothco needs to approve your account before live orders flow through. The Sandbox → test order → approval process is required once per account.
Paste the API Key into the API Key field, click Test Connection, then Save Connection.
Step 4 — (Optional) Multiple Rothco Accounts
If you operate separate Dealer and Fulfillment/Dropship accounts with Rothco, create two separate Rothco Sources — one per account, each with its own API connection. Add both sources to a single routing group; the routing engine will pick the correct account based on which source has the item in stock.
Tip: Use Post Mapping Workflow filters on each source to scope which products that source can fulfill if your accounts carry overlapping catalogs.
Next Configure Product & Order Operations 🚀
Now that your Rothco connection is saved, go to the Operations sections of this doc to set up the integrations you need: Get Inventory [Primary] and Get Inventory [Secondary] for catalog & pricing, Send Fulfillment Requests / Get FR Acknowledgments for orders, and Get Shipments for tracking.

 

Product Operations

Get Inventory (Primary)

Introduction

Rothco is a wholesale supplier of military, tactical, and outdoor gear. The Get Inventory (Primary) job imports your full Rothco catalog into Flxpoint — product titles, descriptions, categories, images, attributes (color, size, etc.), pricing, and inventory levels.

Use Get Inventory (Primary) to keep Rothco product data current in Flxpoint: import the full catalog with parent products and their variants, keep quantities, cost, MAP, and MSRP up to date, and identify items that are no longer available.

The sections below walk through each step of the setup and configuration process.

Note: Get Inventory (Primary) is the full catalog import. After each run, products and variants live in your Global Inventory Pool and can be mapped to downstream channels.

Each run follows this workflow:

  • 1Select Connection — Choose your Rothco connection (uses your Rothco API Key).
  • 2Fetch Catalog — Flxpoint pulls the full Rothco product catalog — categories, parent products, variants, attributes, pricing, inventory, and images.
  • 3Map Fields — Incoming data is matched to your Mapping Template (Rothco V2 GIP is the default).
  • 4Save to Global Inventory Pool — The pool is updated; changes flow to channels after your next push.

Follow these steps in your Rothco source → Get Inventory (Primary):

Step 1: Connect an Integration

Choose Rothco and select your existing Rothco connection (or create one — see How to Connect → Phase 3). Click Save and Proceed.

Step 2: Configure Settings
  • Archive / Un-Archive Inventory — When enabled, items absent from the latest feed are archived (qty set to 0) and re-activated automatically if they return. Enable in either Primary or Secondary — not both.

Click Save and Proceed.

Step 3: Define a Mapping Template

Choose Rothco V2 GIP (default) or build your own based on it. Click Save and Complete.

Step 4: Save & Schedule

Run manually first to verify the import. Then enable a schedule — daily is a good default for Primary (jobs run in UTC). The status page will show Connected, Configured, and Mapped with your template once complete.

About "99+" stock values: Rothco reports high-stock items as 99+. Flxpoint converts this to a numeric value automatically — no mapping rule needed.

Recommended Mapping (Rothco V2 GIP)

Starter field mapping for Rothco Get Inventory (Primary). Adjust per your template if needed.

Flxpoint Field Rothco Source Field Example Purpose Status
SKU (T) Inventory: SKU RTH-12345 Variant identifier Required
Parent SKU (T) Inventory: Product Line RTH-PL-100 Links variants to a parent product Required
Title (T) Inventory: Product Line Name Tactical Field Jacket Display title Required
Description (T) Inventory: Short Description Heavy-duty cotton field jacket Short description Optional
Cost (N) Inventory: Dealer Price 15.00 Dealer cost (USD) Required
MSRP (N) Inventory: MSRP 29.99 Manufacturer suggested retail price Optional
MAP (N) Inventory: MAP 25.00 Minimum advertised price Optional
Quantity (N) Inventory: Quantity 100 (or 99+ → numeric) On-hand quantity Required
Weight (N) Inventory: Weight 2.5 Product weight Optional
UPC (T) Inventory: UPC 012345678905 Barcode Optional
Primary Category (T) Inventory: Primary Category Outerwear Top-level category Optional
Sub Category (T) Inventory: Sub Category Field Jackets Second-level category Optional
Option Name 1–10 (T) Inventory: Specifications (Name) Color, Size Variant attribute names Optional
Option Value 1–10 (T) Inventory: Specifications (Value) Olive Drab, Large Variant attribute values Optional
Image (T) Inventory: Image https://... Product image URL Optional
Note on attributes: Rothco delivers product specifications as structured name/value pairs (e.g., "Color = Olive Drab", "Size = Large"). Each pair maps cleanly to one of the Option Name / Option Value columns in your template — you don't need to know the spec names ahead of time.
Available Source Fields

Product Data: SKU (T), Parent SKU (T), Title (T), Short Description (T), Long Description (T), Manufacturer (T), MPN (T), UPC (T), Cost (N), MSRP (N), MAP (N), Quantity (N), Weight (N), Image (T), Primary Category (T), Sub Category (T), Option Name 1–10 (T), Option Value 1–10 (T), Country of Origin (T), Restricted (T).

Mapping Options
  • Match It — Directly map a source field to a Flxpoint field.
  • Set It — Set a fixed/static value for a field.
  • Transform It (Mapping Set) — Apply a transformation or mapping set to the value.
  • Smart Rules — Use conditional logic to determine the mapped value.
  • Skip It (Don't Map) — Ignore the field entirely.
  • Skip It (Set to Empty) — Clear the field value on each sync.
Summary: Map SKU, Parent SKU, Title, Cost, and Quantity (the required fields) plus the attributes you need for downstream channels. Verify your Rothco connection passes Test Connection before running.

Quick Checks
  • Rothco connection is selected and the API Key passes Test Connection.
  • Archive / Un-Archive is enabled in either Primary or Secondary — not both.
  • Mapping template Rothco V2 GIP is selected and saved.
  • Run once manually first, then enable a daily schedule once verified.
Troubleshooting
  • Catalog not importing: Open the Rothco connection and click Test Connection. If it fails, paste a fresh API Key from your Rothco API Portal and retry.
  • Items missing from the import: Some products are restricted under Rothco's Authorized Reseller Program and won't appear until your Rothco account is approved for those brands. Open your Rothco Dealer Portal → Online Catalog → Authorized Reseller Programs to review your enrollments. Restricted items appear automatically in your feed once enrollment is confirmed — no Flxpoint configuration is needed.
  • Variants not linking to parents: Confirm Parent SKU is mapped and that your template uses the Rothco product line as the parent reference.
  • Page errors during the run: If an internal error occurs on a specific catalog page, Flxpoint skips that page (up to a small limit) instead of aborting the entire job. Check the job log for skipped pages and re-run if needed.
Operation Details
Feature Availability What to Expect
Custom Fields Supported Up to 100 custom fields, 10 summary fields.
Variations / Options Supported Up to 10 Option Name/Value pairs per variant.
Quantity Supported Includes high-stock 99+ values converted to numeric automatically.
Pricing Supported Cost, MSRP, MAP delivered cleanly — no string parsing.
Categories Supported Two-level (Primary + Sub).
Images Supported Linked to the parent product.
Archive / Un-Archive Supported Items absent from a run are archived; re-activated when they return. Enable in Primary or Secondary, not both.
Tip: Run Get Inventory (Primary) on a daily schedule for catalog updates, and pair it with Get Inventory (Secondary) on a more frequent schedule (hourly) to keep quantities and pricing fresh between full catalog runs.

Get Inventory (Secondary)

Introduction

The Rothco – Get Inventory (Secondary) integration is a fast, lightweight companion to the Primary import. It refreshes SKU, Cost, MAP, MSRP, and Quantity — without the overhead of re-importing the full catalog (titles, descriptions, categories, images).

The sections below walk through each step of the setup and configuration process.

Tip: This operation reuses the same Rothco connection (API Key) configured during Get Inventory (Primary) setup. No separate connection is needed.

Use this job to:

  • Refresh variant-level cost, MAP, and MSRP for existing SKUs.
  • Update quantities on a faster cadence than the Primary catalog import.

Each run follows this workflow:

  • 1Connection — Uses the existing Rothco connection to pull a lightweight inventory + pricing snapshot.
  • 2Parse & Map — Variant-level fields are matched to your Mapping Template (see Mapping Utilities below).
  • 3Write — Variant data in the Global Inventory Pool is updated. Catalog-level fields (titles, images, categories) are unchanged — those are managed by Primary.
Example: SKU RTH-12345 with cost 15.00, MSRP 29.99, MAP 25.00, and quantity 100 ⇒ Flxpoint updates the variant in seconds without touching titles, descriptions, or images.
Step 1: Connect Rothco

Choose Rothco and select the existing Rothco connection from Get Inventory (Primary). Click Save and Proceed.

Step 2: Configure Settings
  • Allow Create Variant (Optional) — Enable if you want Secondary to create new variants when it sees an unknown SKU. Default is OFF (let Primary handle catalog growth).

Click Save and Proceed.

Important: Enable Archive / Un-Archive in either Primary or Secondary — not both. Most teams keep it on Primary so the full catalog run owns archival decisions.
Step 3: Define a Mapping Template

Choose Rothco V2 GIS (default). Click Save and Complete.

Step 4: Save & Schedule

Run manually or enable a schedule. Schedules run in UTC. Hourly is a common cadence for Secondary so quantities and pricing stay fresh between Primary runs.


Recommended Mapping (Rothco V2 GIS)

Map the variant-level fields below for fast Secondary refreshes.

Flxpoint Field Rothco Source Field Example Status
SKU (T) Inventory Variant: SKU RTH-12345 Required
Quantity (N) Inventory Variant: Quantity 100 Required
Cost (N) Inventory Variant: Dealer Price 15.00 Required
MAP (N) Inventory Variant: MAP 25.00 Optional
MSRP (N) Inventory Variant: MSRP 29.99 Optional
Available Source Fields
  • Rothco Inventory Variant: SKU (T), Cost (N), MAP (N), MSRP (N), Quantity (N).
Mapping Options

Options include Field, Value, Mapping Set, Rules, Don't Map, and Set to Empty.

How Secondary Works With Primary
  • Primary: Full catalog import — product lines, attributes, categories, images, pricing.
  • Secondary: Fast refresh — SKU, quantity, cost, MAP, MSRP only.
  • Archive: Manage in one place (typically Primary) to avoid conflicts.
  • Cadence: Primary daily; Secondary hourly is a good starting point.
Summary: Secondary mapping focuses on variant-level fields including cost, quantity, MAP, and MSRP. Keep catalog-level fields (titles, images, descriptions, categories) in the Primary job.

Quick Checks
  • Connection reuses the same Rothco connection from Get Inventory (Primary) and shows Connected.
  • Mapping template Rothco V2 GIS is selected and saved.
  • Archive / Un-Archive is enabled on Primary or Secondary — not both.
  • SKU, Quantity, and Cost are mapped at minimum.
Troubleshooting
  • Data not refreshing: Open the Rothco connection and click Test Connection. If credentials are stale, paste a fresh API Key from your Rothco API Portal.
  • Quantities not updating: Confirm the Rothco V2 GIS template is selected and that SKU and Quantity are mapped.
  • Cost or MSRP not updating: Verify the mapping template includes Cost / MSRP and that the run isn't filtered to a subset of variants.
  • Archive conflicts: If items are getting archived unexpectedly, confirm only one of Primary or Secondary has Archive / Un-Archive enabled — never both.
Operation Details
Feature Availability What to Expect
Variant-Level Fields Supported SKU, Cost, MAP, MSRP, Quantity.
Connection Shared Reuses the Rothco connection from Get Inventory (Primary).
Scheduling Supported Run on demand or via recurring schedule (UTC).
Catalog-Level Fields Not Supported Titles, images, and descriptions belong in the Primary job.
Tip: Run Secondary on a more frequent schedule than Primary to keep cost, quantity, and pricing data fresh between full catalog syncs.

 

Order Operations

Send Fulfillment Requests

Introduction

The Rothco – Send Fulfillment Requests integration submits Flxpoint Fulfillment Requests (FRs) to Rothco as dropship orders. It uses your Rothco connection (API Key) and a Billing Email for order confirmations.

The sections below walk through each step of the setup and configuration process.

Send Fulfillment Requests submits Flxpoint FRs to Rothco as dropship orders. If the request is accepted, the FR is marked as processed.

The setup is completed in four steps.

Step 1: Connect Rothco

Select Rothco and choose your existing Rothco connection (or create one — see How to Connect → Phase 3).

Click Test Connection, then Save Connection. The same Rothco connection is reused across all operations — no separate connection is needed for orders.

Tip: If you operate separate Dealer and Fulfillment/Dropship accounts with Rothco, create two separate Rothco Sources — one per account, each with its own API connection. Add both sources to a single routing group.
Step 2: Configure Settings
  • Billing Email (Required) — Dealer email that receives order confirmations from Rothco.
  • Hold for X Hours (Optional, Advanced) — Delay sending POs to allow review (default: 0).
  • Send During Business Hours (Optional, Advanced) — Restrict order transmission to specified hours.
  • Use 'Get FR Acknowledgements' Process (Optional, Advanced) — Default OFF.
    • OFF (default): The FR is auto-acknowledged on a successful Send FR response.
    • ON: Send FR will not auto-acknowledge. Acknowledgment is handled by the Get FR Acknowledgments operation, which checks Rothco's actual order status (Confirmed / Fully Shipped / Closed) before marking the FR acknowledged.
    Turn this on only if you want acknowledgment driven by Rothco's status check rather than the immediate Send FR success response.

Click Save and Proceed.

Step 3: Define a Mapping Template

Choose Send Purchase Orders (default) or build your own based on it. Click Save and Complete.

Step 4: Save & Schedule

Run on demand or enable scheduling. Schedules run in UTC. The status page will show Connected, Configured, and Mapped.


The Mapping Template defines how Flxpoint FR data maps to Rothco's dropship order format. Header fields (PO/Reference, Billing Email, Ship To address) and line items (SKU, Quantity) must be mapped.

Recommended Mapping (Send Purchase Orders — key fields)
Flxpoint Field Rothco Field Example Status
Fulfillment Request Number (T) PO / Reference FR12345 Required
Billing Email (configured in Step 2) Billing Email orders@example.com Required
Full Name (T) Ship To Name John Doe Required
Address Line 1 (T) Ship To Address Line 1 123 Main St Required
Address Line 2 (T) Ship To Address Line 2 Apt 4B Optional
City (T) Ship To City Los Angeles Required
State (T) Ship To State CA Required
Postal Code (T) Ship To ZIP 90210 Required
Customer Email (T) Customer Email customer@example.com Required
SKU (T) Item: SKU RTH-12345 Required
Quantity (N) Item: Quantity 2 Required
Hold for X Hours (configured in Step 2) Hold 0 Optional
Required fields are strictly enforced. Rothco rejects orders with missing or empty values for Name, Address Line 1, City, State, ZIP, Customer Email, SKU, and Quantity. Map every required field and confirm your routing logic supplies non-empty values.
Available Source Fields
  • Fulfillment Request: FR Number, FR Notes, Custom Fields, Confirm To Email, Confirm To Name.
  • FR Item: SKU, Quantity, Unit Price, Custom Fields.
  • Shipping Address: Full Name, Address Line 1, Address Line 2, City, State, Postal Code, Country Code, Phone.
Let's Break It Down: Map shipping address fields, SKU, and quantity as required fields. The PO reference is your Fulfillment Request Number; Billing Email and (optionally) Hold are configured at the Settings step rather than the mapping template.
Shipping Codes Reference

Many Rothco accounts use vendor-selected shipping (Rothco picks the carrier on each order). Only use these codes if your Rothco account is explicitly configured to receive a shipping method on the order.

Code Carrier Description
UPS – Ground UPS Ground (1–5 Days)
UPS3DY UPS Three Day Air
UPSBLU UPS Two Day Air
UPSRED UPS Next Day Air
STANDARD — Standard delivery
TWODAY — Two Day delivery
THREEDAY — Three Day delivery
PRIOR USPS Priority Mail
FXGHD FedEx Ground Home Delivery
Summary: Map the key fields above for accurate FR submission to Rothco. Ship To fields, Customer Email, SKU, and Quantity are the most critical to verify.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Billing Email is set in the Configure Settings step.
  • Mapping template is selected and saved.
  • Required fields (Name, Address Line 1, City, State, ZIP, Customer Email, SKU, Quantity) are mapped and supply non-empty values.
  • FR/PO reference is unique — Rothco rejects duplicates.
Troubleshooting
  • Order rejected for missing fields: Rothco strictly enforces required fields. When a required field is missing or invalid, the Flxpoint job notification now shows the exact error text from the Rothco API — for example: Field "email" of required type "String!" was not provided. Use the error message in the job notification to identify which field is missing or invalid, then audit your mapping template to ensure that field is mapped and supplies a non-empty value for every order. Required fields are: Name, Address Line 1, City, State, ZIP, Customer Email, SKU, and Quantity.
  • Duplicate PO error: Rothco rejects POs that reuse an existing reference. If you need to retry an order, change the FR/PO reference and resend.
  • Order failed with a connection error: Check whether Rothco received the order in your dealer portal. If they did, no action is needed. If not, use a new FR/PO number before resubmitting.
  • Sandbox vs Live confusion: If your account was just set up, ensure Rothco approved your sandbox test and that you've switched to Live Mode in your Rothco API Portal, then paste the live API Key into Flxpoint.
  • Shipping method errors: If your Rothco account is not configured to receive a shipping method via API, remove the shipping-method mapping from your template — let Rothco pick the carrier.
  • Acknowledgment timing: If you turned on Use Get FR Acknowledgements process, the FR will not be marked acknowledged on a successful Send FR response — that happens in the separate Get FR Acknowledgments run.
Operation Details
Feature Availability What to Expect
FR Number Supported FR Number is sent as the Rothco PO/Reference.
Ship To Address Supported Full address including Address Lines 1–2, City, State, ZIP, Country, Customer Email.
FR Item Association Supported Line items include SKU and Quantity.
Hold for X Hours Supported Delay transmission for review.
Business-Hours-Only Sending Supported Restrict order transmission to a configured window.
Auto-Acknowledge on Success Default ON Toggle off via Advanced if you want status-based acknowledgment from Get FR Acknowledgments.
Multi-Account Routing Supported Use two separate Rothco Sources, one per account, in a single routing group.
Detailed Failure Reporting Supported Failures include the reason so you can resolve the order — for example: item unavailable, restricted item, hazmat-restricted, or field-validation errors from the Rothco API (e.g., Field "email" of required type "String!" was not provided). The exact Rothco API error text is now surfaced in the job notification.
Tip: Always test with a single order first to verify Ship To mapping, Customer Email, and connectivity before enabling automation across your routing group.

Get FR Acknowledgments

Introduction

The Rothco – Get FR Acknowledgments integration checks the status of your Rothco orders and acknowledges the corresponding Fulfillment Requests in Flxpoint when Rothco confirms receipt. A Fulfillment Request is acknowledged when Rothco's order status is Confirmed, Fully Shipped, or Closed. If Rothco's status is Cancelled, the FR is marked as cancelled in Flxpoint.

About auto-acknowledge: By default, Send Fulfillment Requests auto-acknowledges the FR when the order is successfully submitted. To use status-based acknowledgment instead, enable Use 'Get FR Acknowledgements' process in Send FR Advanced settings, then run this operation.

The sections below walk through each step of the setup and configuration process.

The setup is completed in three steps.

Step 1: Connect Rothco

Choose Rothco and select your existing Rothco connection. Click Test Connection, then Save and Proceed.

Step 2: Configure Settings

No additional settings are required for this operation. Click Save and Proceed.

Step 3: Define a Mapping Template

Choose Rothco - Get PO Ack (default). Click Save and Complete.

Important: If you want this operation to control acknowledgment, open Send Fulfillment Requests → Advanced and turn ON Use 'Get FR Acknowledgements' process. Otherwise the FR will already be auto-acknowledged on Send FR success and this operation will mostly mark closure / cancellation status changes.
Step 4: Save & Schedule

Run on demand or enable scheduling (UTC). A common cadence is every few hours so order status flows back into Flxpoint promptly.


Recommended Mapping (Rothco - Get PO Ack)

Maps Rothco's invoice / order data back to your Fulfillment Request.

Flxpoint Field Rothco Field Status
Fulfillment Request Number (T) Rothco Invoice / PO Number Required
Quantity (N) Invoice Item: Quantity Ordered Required
SKU (T) Invoice Item: SKU Code Required
Acknowledgment Logic
Rothco Order Status Action in Flxpoint
Confirmed FR marked as Acknowledged
Fully Shipped FR marked as Acknowledged
Closed FR marked as Acknowledged (invoice generated)
Cancelled FR marked as Cancelled in Flxpoint
Open / Hold / Partially Shipped No action — FR remains in current status
Summary: Map FR Number, SKU, and Quantity to the Rothco invoice fields. The status logic table above defines what happens for each Rothco order status.

FAQs
  • When does an FR get acknowledged? When Rothco's order status reaches Confirmed, Fully Shipped, or Closed.
  • What happens if Rothco cancels? The FR is marked as Cancelled in Flxpoint.
  • Do I need to turn off auto-acknowledge on Send FR? Only if you want acknowledgment driven by Rothco's order-status check rather than the Send FR success response. For most setups, leaving auto-acknowledge ON is the right choice; this operation will still pick up cancellations and closures.
Troubleshooting
  • FRs not getting acknowledged: Confirm the FR/PO number on the Rothco invoice matches your Fulfillment Request Number. Mapping mismatches are the most common cause.
  • Acknowledgment is happening twice: If you enabled Use Get FR Acknowledgements process on Send FR but the FR shows acknowledged immediately on send, re-check the Send FR Advanced setting — it must be ON for status-based ack to take over.
  • Cancellations not flowing back: Check that the mapping template is Rothco - Get PO Ack and that the run schedule is active. Without an active run, status changes won't arrive in Flxpoint.
Operation Details
Capability Status Notes
FR Acknowledgment Supported Triggers on Confirmed, Fully Shipped, or Closed.
FR Cancellation Supported Triggers when Rothco order status is Cancelled.
Mapping Template Required Use Rothco - Get PO Ack (default provided).
Auto-Acknowledge On by default (Send FR) Disable via Send FR Advanced if using this operation.
Custom Fields Not Supported Standard acknowledgment fields only.
Tip: If you don't need cancellation tracking and rely entirely on Send FR auto-acknowledge, this operation is optional. Enable it when you want order-status changes (cancellations, closures) to flow back into Flxpoint automatically.

Get Shipments

Introduction

The Rothco – Get Shipments integration retrieves shipment confirmations for your Rothco orders — including tracking number, shipped date, shipping method, and item-level shipped quantities. It uses your Rothco connection.

The sections below walk through each step of the setup and configuration process.

Note: This operation retrieves shipment confirmations from Rothco and updates your orders with tracking and item-level shipped quantities.

Use this job to:

  • Retrieve tracking numbers and carrier / shipping method for shipped Rothco orders.
  • Update orders with actual quantity shipped at the item level (not copied from the original PO).
  • Capture the shipped date for reporting and SLA tracking.

Each run follows this workflow:

  • 1Connect — Uses your Rothco connection to identify recently shipped orders.
  • 2Pull Detail — For each shipped order, Flxpoint retrieves the tracking number, shipping method, shipped date, and per-line-item shipped quantities.
  • 3Save — Shipment data posts back to the corresponding order; partial shipments attach with their own items and quantities.
Step 1: Connect Rothco

Choose Rothco and select your existing Rothco connection. Click Save and Proceed.

Step 2: Configure Settings
  • Fetch Shipments for Days (Required) — how many days back to look for shipments. Options: 5, 10, 15, or 30. Most teams use 10 or 15.

Click Save and Proceed.

Step 3: Define a Mapping Template

Choose Get Shipments 2 (default). Click Save and Complete.

Step 4: Save & Schedule

Run on demand or schedule periodic runs (UTC) — for example, every 2 hours — to keep tracking current.


Recommended Mapping (Get Shipments 2)

Map these Rothco shipment fields to your Flxpoint shipment object. Fields are split between header level (one per shipment) and item level (one per shipped line).

Flxpoint Field Rothco Field Level Status
Tracking Number (T) Shipment: Tracking Number Header Required
Shipped At (D) Shipment: Shipped At Header Optional
Method (T) Shipment: Shipping Method Name Header Optional
Carrier / Note (T) Shipment: Shipping Method Code Header Optional
Order / PO Reference (T) Shipment: PO Number Header Optional
Shipment Item: SKU (T) Shipment Item: SKU Code Item Required
Shipment Item: Quantity (N) Shipment Item: Quantity Shipped Item Required
About item-level quantities: Rothco's Quantity Shipped is the actual count picked and shipped on each line — not copied from the original PO. This means partial shipments report exactly what was sent, and follow-up shipments will complete the order with their own item rows.
Available Source Fields
  • Rothco Shipment (Header): Order Number, Order Status, PO Number, Shipped At, Shipping Method Code, Shipping Method Name, Tracking Number.
  • Rothco Shipment Item: Product Line Code, Quantity Ordered, Quantity Shipped, SKU Code.
Mapping Options

Options include Field, Value, Mapping Set, Rules, Don't Map, and Set to Empty.

Operation Workflow
  • On each scheduled run, Flxpoint identifies Rothco orders shipped within the configured window (5 / 10 / 15 / 30 days).
  • For each shipped order, Flxpoint retrieves shipment headers and per-item shipped quantities.
  • Partial shipments are supported — multiple shipments can attach to one order, each with their own items.
Summary: Map Tracking Number (header) and SKU / Quantity Shipped (item level). Add Method, Carrier, and Shipped At for richer reporting. Both header and item-level mappings are included in the default Get Shipments 2 template.

FAQs
  • How far back should I fetch? Most teams use 10 or 15 days. Increase to 30 if you expect late confirmations.
  • Why is carrier or method blank? Map both Shipping Method Name and/or Shipping Method Code in the template; otherwise only the tracking number populates.
  • Can partial shipments import? Yes. Each Rothco shipment attaches to the original order with its own items and quantities.
Troubleshooting
  • "No data" responses: The order may not have shipped yet. Confirm shipment status with Rothco and re-run after the shipment is dispatched.
  • Shipped At missing: Map Shipped At in your template. If Rothco omits the date for a particular shipment, the field will be empty — consider a fallback rule (e.g., use run-time date) if your downstream channel requires it.
  • Tracking not linking to the order: Confirm the shipment's PO/Reference matches your original Fulfillment Request Number. If your FR/PO references are unique per order this should link automatically.
  • Authentication errors: If the run fails with an auth error, click Test Connection on the Rothco connection and re-paste a fresh API Key from the Rothco API Portal if needed.
Operation Details
Capability Status Notes
Tracking Number Supported Primary identifier returned by Rothco.
Shipped At Supported Use a fallback rule if omitted on a particular shipment.
Carrier & Method Supported Shipping Method Code and Name are both available.
Item-Level Quantity Supported Actual quantity shipped per line, not copied from the PO.
Partial Shipments Supported Each shipment attaches to the order with its own items.
Invoice Information Not Supported Invoices are not part of this operation.
Custom Fields Not Supported Standard shipment fields only.
Tracking URL — Build via channel/carrier rules if needed.
Tip: Schedule this job to run frequently (e.g., every 2 hours) so your shipping carriers' tracking lands in Flxpoint promptly. If you operate two Rothco accounts, schedule Get Shipments on both sources.

 

Troubleshooting

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

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

Contact Support

Related Articles

Kinsey's as a Source

Kinsey's is a wholesale distributor of archery, hunting, and outdoor sporting goo...

RSR as a Source

In this guide, you’ll learn how to set up your RSR feed in Flxpoint, from creatin...

Sports South as a Source

Sports South can be connected to Flxpoint as a  supplier source to automate  inve...

Lipseys as a Source

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