Flxpoint Knowledge

Contact us

SPRichards as Source

Table of Contents

How To Connect Product & Order Operations Product Operations Order Operations Troubleshooting Common Errors

SP Richards is a leading wholesale distributor of office supplies, furniture, and business products. As a source in Flxpoint, it provides reliable inventory data, automated updates, and integration options to streamline product management and order fulfillment for ecommerce businesses.
 

 

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., SP Richards as Source). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most SP Richards 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 SP Richards 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 SP Richards: select Vendor Warehouse. This enables sending Fulfillment Requests to SP Richards 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 SP Richards. For most SP Richards accounts, you do not create a Source Shipping Method here—SP Richards will choose the carrier and service on their side when they receive the Fulfillment Request.

Step 1 — Shipping Methods (Skip for SP Richards)
When the wizard opens the Shipping Methods step for this Source:
  • For typical SP Richards 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? SP Richards automatically selects the shipping method based on your account preferences, order details, and carrier availability. Sending a method from Flxpoint is not required and may conflict with how SP Richards is configured to ship your orders.

Only create a Source Shipping Method if:
  • Your SP Richards 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 SP Richards credentials you'll use for all SP Richards integrations.
🔐 Phase 3: Create Your SP Richards Connection +
Goal

To connect SP Richards in Flxpoint, you'll gather the credentials required to create an SP Richards Connection. SP Richards supports two connection types—FTP (Basic Auth) and SP Richards API Token. This connection is created once and powers all SP Richards operations.

Step 1 — Open Get Inventory [Primary] and start
Inside your SP Richards source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations. In the connector gallery, choose SPRichard. If you don't see it, use Not Listed? → Request a custom integration.
Step 2 — Choose your Connection Type
In New SPRichard Connection, select one of:
  • FTP (Basic Auth) — for file pickup over FTP.
  • SPRichard API Token — direct API auth (Group Code + User ID + Password).
Step 3a — If you choose FTP (Basic Auth)
Fill the form exactly as provided by SP Richards:
  • Connection Name
  • FTP Protocol: FTP
  • FTP Host
  • FTP Port
  • FTP User
  • FTP Password
  • File Transfer Mode: Binary file type
Expand Advanced Settings if needed:
  • Maintain constant connection: Optional
  • Use unbuffered private data channel: Only for resolving specific FTPS errors
Click Test Connection → Save Connection.
Step 3b — If you choose SPRichard API Token
Enter:
  • Connection Name
  • Group Code
  • User ID
  • Password
Then Test Connection and Save Connection.
Note: These fields match the "New SPRichard Connection" modal exactly.
Step 4 — How Flxpoint uses this connection
One connection, all operations: This single SP Richards Connection is reused by all SP Richards integrations you'll configure later, including: Inventory [Primary], Inventory [Secondary], Fulfillment Requests, and Shipments. You don't need separate credentials for each operation.
Next Configure Product & Order Operations 🚀
Now that your SP Richards Connection is saved, go to the Operations section of this doc to set up the SP Richards integrations you need (Inventory and Order operations). Each operation will let you select the SP Richards Connection you just created.

 


Product & Order Operations

Now that you’ve finished the wizard, you’ll see SPRichards has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your SPRichards stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to SPRichards and pulling back shipment/tracking data. All four use the same SPRichards 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 SPRichards 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)

Introduction

In Flxpoint, Get Inventory (Primary) (GIP) is the job that imports SPRichard product data and quantities into your Global Inventory Pool. This job supports two connection methods (FTP or API token) and lets you aggregate quantities across selected warehouses.

Use GIP to keep SPRichard inventory current in Flxpoint: import the full SPRichard catalog with core details (brand, titles/descriptions, categories, images, weight), keep quantities current by optionally summing across selected warehouses, and bring in dealer pricing when available to you (client-specific pricing).

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

Note: GIP is the import process. After each run, products/quantities live in the Global Inventory Pool and can be mapped to downstream channels.
SPR Pricing & Missing Cost Note: SPR often provides two different feeds:
  • Quantity feed (hardcoded): ftp.sprich.com → user onhand, pass onhand, file sprfull.ezoh (typically quantity-only).
  • Pricing feed (customer-specific): Credentials/file provided by SPR per customer. File names vary (e.g., JPR.x12_832_0724.csv) and contain your dealer pricing.
If you connect only to the quantity feed, costs will appear empty. Obtain your pricing FTP (or use the API) to import cost/MSRP.

Each run follows this workflow:

  • 1Select Connection — Choose FTP (Basic Auth) or SPRichard API Token when creating your connection.
  • 2Fetch Data —
    FTP: Flxpoint reads the latest CSV from your provider's FTP folder (you supply folder + filename pattern). API: Flxpoint requests product, quantity, and price from SPRichard's API using your Group Code / User ID / Password.
    When API is used, price/qty is read from the API; otherwise, the FTP feed is used, per your configuration.
  • 3Map Fields — Incoming columns are matched to your Mapping Template.
  • 4Save to Global Inventory Pool — The pool is updated; changes flow to channels after your next push.
Example: If you select Dallas and Phoenix warehouses and they report 4 and 7 units, the available quantity shown in Flxpoint will be 11.

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

Step 1: Connect an Integration

Choose SPRichard and create a connection.

Connection Type
  • FTP (Basic Auth)
    Fields: Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password.
    Advanced: File Transfer Mode (Binary), Maintain Constant Connection (optional), Use Unbuffered Private Data Channel (for FTPS 534 policy only).
    Tip: Use Test ConnectionValidates credentials and folder visibility before you save. after entering your credentials.
  • SPRichard API Token
    Fields: Connection Name, Group Code, User ID, Password.
    Use Case: Preferred when you need dealer pricing and direct price/qty from the API.
Step 2: Configure Settings
  • Remote File Name Pattern (FTP only) — e.g., *.csv or an exact filename.
  • Inbound Remote File Folder (FTP only) — e.g., /incoming/products.
  • File Action — set to Read for GIP.
  • Warehouse — choose All or select specific locations. What does this do? Available Quantity will be the sum from the selected Warehouses. 
    ALL ATLANTA BALTIMORE BIRMINGHAM BOSTON CHARLOTTE CHICAGO COLUMBUS DALLAS DENVER EDMONTON GRAND RAPIDS HOUSTON INDIANAPOLIS KANSAS CITY LOS ANGELES MIAMI NEW YORK PHOENIX PITTSBURGH SALT LAKE CITY SAN ANTONIO SEATTLE ST. LOUIS VANCOUVER
  • Archive/Un-Archive Inventory — Enable to archive items missing from the feed and auto-restore them if they reappear.
    Recommendation: Don't enable Archive on both Primary and Secondary for the same source.
Step 3: Define a Mapping Template

Use the recommended fields from the Mapping Utilities section below, then adjust for your catalog.

Step 4: Save & Schedule

Run manually or enable a schedule (jobs run in UTC). The status page will show Connected, Configured, and Mapped with the template (e.g., "SPRichard Get Source Products 1") once complete.


Recommended Mapping (Starter)

Starter field mapping for SPRichard (adjust per your template):

Flxpoint Field SPRichard Field Notes
SKU Sku / Catalog Sku Unique product identifier.
Title Description 1 (fallback: Description 2/3) Human-readable product name.
Brand Brand Name / Manufacturer Name Normalize as needed.
Quantity Quantity Aggregated when multiple warehouses are selected.
Client Price Dealer Price Dealer-specific pricing when available.
MSRP Retail Price or column AF per pricing file Map from pricing file when available.
Cost column CI per pricing file "Promo Level 1 Dealer Cost."
Category 1 Department Name Top-level category.
Category 2 Class Name / Subclass Name Second-level category.
Weight Weight Pounds.
UPC Upc Barcode (if present).
Attributes Product Specifications, Marketing Text, etc. Bring as custom attributes.
Images (Image URL fields if provided) Single primary image supported.
Also available to map: Department/Class/Subclass Numbers, UNSPSC, No Return, UPS Shippable, Country of Origin, and more.
Pricing Feed Details (SPR)
Feeds You May Receive from SPR
  • Quantity (On-hand) FTP — ftp.sprich.com | user onhand | pass onhand | file sprfull.ezoh.
    Typically contains quantities only.
  • Pricing FTP (Customer-Specific) — Credentials + file name are provided per customer by SPR (name varies).
    Sample: JPR.x12_832_0724.csv | Specs: "Price File Header List & Descriptions.xlsx".
Required for costs: Connect your pricing FTP (or use SPR API). If you only connect to onhand, cost/MSRP will import as empty.
Column Mapping (Pricing File)
Flxpoint Target SPR Column Description
Wholesale Cost CI — "Promo Level 1 Dealer Cost" Dealer/contract cost used as item cost.
MSRP AF — "Current Retail Price" Retail/MSRP reference.
When to use API: If SPR confirms your FTP pricing file is unavailable or delayed, request API credentials (Group Code, User ID, Password) and switch the connection to API to fetch price & quantity directly.
Operation Workflow & Notes
  • Rich content (long descriptions/specs) can be sourced from Etilize FTP when provided. Use your assigned FTP host/folder and file pattern.
  • Multiple warehouses are supported in configuration (sum of selected warehouses shows as Available Quantity).
  • API vs FTP: When the API connection is used, price/qty is read from the SPRichard API; otherwise FTP is used for price/qty.
Summary: Map the core fields above and verify your pricing source (FTP file or API) to ensure cost, MSRP, and quantity import correctly.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Warehouse selection matches your fulfillment needs (All or specific locations).
  • Archive is enabled in one integration only (Primary or Secondary, not both).
  • If using FTP: Remote File Name Pattern and Inbound Folder are set correctly.
  • If using API: Group Code, User ID, and Password are confirmed with SP Richards.
Troubleshooting
  • Costs are empty:
    • Confirm you have a pricing FTP from SPR (customer-specific credentials) or use the API. The onhand FTP (ftp.sprich.com / onhand/onhand) is typically quantity-only.
    • Verify you're pulling the correct pricing file (name varies; example JPR.x12_832_0724.csv) and mapping CI to Cost, AF to MSRP per "Price File Header List & Descriptions.xlsx".
    • If SPR confirms the FTP file no longer carries pricing, request API credentials (Group Code, User ID, Password) and switch the connection to API.
  • FTP auth / connection errors: Re-check host, port, username/password, and try Test Connection. For FTPS 534 policy failures, toggle "Use Unbuffered Private Data Channel."
  • API credential errors: Confirm Group Code, User ID, and Password. Ensure your account has access to price/qty endpoints.
  • No quantities or mismatches: Verify selected Warehouse options and that the source file/API returns non-zero Quantity.
  • Items missing after a run: If Archive is enabled, SKUs absent from the feed will be archived (qty set to zero) until they reappear.
Customer Action (when costs missing): Contact SP Richard to request the correct pricing FTP credentials/file or API credentials for pricing access.
Operation Details
Feature Availability What to Expect
Custom Fields Supported Extra product attributes saved as variant custom fields.
Variations / Options Not Supported Simple products only.
Generic Pricing (& Currency) Not Supported Use client/dealer price when applicable.
Client Pricing (& Currency) Supported Dealer price per account.
Quantity Supported From API/FTP; sums across selected warehouses.
Multiple Warehouses Supported Select in configuration to aggregate.
Weights & Dimensions (& Units) Supported Weight only, in pounds.
Images Supported Single image per product (additional via custom fields if provided).
Categories Supported Two-level structure for mapping.
Delta vs Full Feed Full Feed This is a full product feed.
Archive Support Supported Archive missing SKUs; auto-restore when they return.
Tip: Run a manual sync first to verify field mapping and pricing data before enabling a recurring schedule.
 
 

Get Inventory (Secondary)

Introduction

Get Inventory (Secondary) is the incremental update job for SPRichard. It typically pulls a compact file containing cost, MSRP, and quantity by warehouse, and updates your Global Inventory Pool accordingly. This job is designed as a delta feed (cost/qty only), complementing the Primary catalog import.

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

Tip: Use Secondary for higher-frequency price/qty refreshes. Keep rich catalog fields (titles, images, long descriptions) in the Primary job.

Use this job to:

  • Refresh dealer cost and MSRP for existing SKUs.
  • Update quantities and aggregate across the warehouses you select.
  • Optionally create variants during the run (advanced setting).

Each run follows this workflow:

  • 1Connection — Uses an FTP (Basic Auth) connection to retrieve the inventory feed (e.g., sprfull.ezoh) and, if configured, a separate price file (CSV). The price file headings specify which columns hold cost/MSRP.
  • 2Parse & Map — The file includes warehouse codes and quantities for each SKU. Mapping then targets only the fields listed in "Recommended Mapping (Secondary)." Fields like Item Number, Current Quantity, and MSRP come from your SPRichard Inventory Item schema.
  • 3Write — Updates cost/qty in the Global Inventory Pool.
Example: SKU ABC-123 has cost 12.10, MSRP 19.99. Phoenix shows 4, Dallas shows 6 ⇒ Flxpoint quantity becomes 10 when both warehouses are selected.
Step 1: Connect an Integration

Choose SPRichard and use FTP (Basic Auth) credentials.

Step 2: Configure Settings
  • Remote File Name Pattern — e.g., sprfull*.ezoh or your provider's exact filename.
  • Inbound Remote File Folder — the source directory for the feed.
  • File Action — set to Read.
  • Archive/Un-Archive Inventory — Archiving removes SKUs not present in this delta. Recommendation: if archiving is already enabled in the Primary job, leave it off here to avoid conflicts.
  • Warehouse — Select All or specific locations (available quantity is the sum of selected warehouses; the UI tooltip confirms this).
  • Advanced > Allow Create Variant — toggle Yes to allow variant creation during Secondary runs.
Step 3: Define a Mapping Template

Use the "Secondary" mapping from the Mapping Utilities section below.

Step 4: Save & Schedule

Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped with your template (e.g., "Get Inventory 2").


Recommended Mapping (Secondary)

Map only the fields you need for delta updates. Field names below are drawn from your SPRichard Inventory Item schema & templates.

Flxpoint Field SPRichard Field Notes
SKU Item Number Primary identifier used to match existing products.
Quantity Current Quantity Per-warehouse quantities; Flxpoint aggregates based on selections.
Dealer Cost Price file column CI "Promo Level 1 Dealer Cost" From the separate price CSV.
MSRP Price file column AF "Current Retail Price" From the separate price CSV.
Warehouse Code Warehouse Code Used to attribute quantity by location.
Warehouse Codes (Examples)

The inventory feed encodes quantity per warehouse. Common codes include:

001: Atlanta, GA002: Charlotte, NC003: Miami, FL 004: Tampa, FL005: Dallas, TX006: Memphis, TN 007: Kansas City, MO008: Houston, TX009: Columbus, OH 010: Paul, MN011: Denver, CO012: Richmond, VA 013: Oklahoma City, OK014: Street, Fort, OR015: San Antonio, TX 016: Birmingham, AL017: New Orleans, LA018: St. Louis, MO 019: Baltimore, MD020: Orlando, FL022: Greensboro, NC 023: Philadelphia, PA024: Indianapolis, IN026: Nashville, TN 027: Jacksonville, FL028: Seattle, WA029: Syracuse, NY 030: Sacramento, CA031: Los Angeles, CA033: Salt Lake City, UT 034: Boston, MA035: Chicago, IL036: Phoenix, AZ 037: New York, NY038: Pittsburgh, PA039: Grand Rapids, MI
Summary: Secondary mapping focuses on cost, quantity, and warehouse code only. Keep catalog-level fields (titles, images, descriptions) in the Primary job.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Warehouse selection matches your fulfillment needs.
  • Archive is off if already enabled in Primary.
  • Remote File Name Pattern and Inbound Folder are set correctly.
Troubleshooting
  • FTP connection fails: Verify host/port and credentials; try Test Connection. For FTPS 534 policy issues, use the unbuffered private data channel setting.
  • Missing or zero quantities: Confirm the file contains the warehouse codes you selected and that Current Quantity is non-zero.
  • Price not updating: Ensure the price CSV column mapping uses CI (Dealer Cost) and AF (Current Retail Price).
  • Unexpected archives: If Archive is enabled and a SKU is absent from the delta, it will be archived with qty=0 until it reappears.
Operation Details
Feature Availability What to Expect
Custom Fields (Variants Only) Not Supported Secondary focuses on price/qty only.
Generic Pricing (& Currency) Not Supported Use dealer pricing.
Client Pricing (& Currency) Supported Mapped to dealerPrice, available in USD.
Quantity Supported From feed; aggregated across chosen warehouses.
Multiple Warehouses Supported Select locations in config; quantity sums across selections.
Weights & Dimensions (& Units) Not Supported Not provided in the delta file.
Delta Feed vs Full Feed Supported (Delta) Only cost and quantity are saved.
Archive Support Supported Toggle in configuration.
Tip: Run Secondary on a more frequent schedule than Primary to keep cost and quantity data fresh between full catalog syncs.
 
 
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

It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.

Send Fulfillment Requests

Introduction

The SP Richards – Send Fulfillment Requests integration automates sending purchase orders (POs) to SP Richards for fulfillment. Flxpoint converts fulfillment request details — such as shipping addresses, item quantities, and distribution center codes — into SP Richards' required XML format and uploads the file to your configured FTP outbound folder.

This integration uses an FTP (Basic Auth) connection configured during inventory setup. Configuration involves selecting the connection, defining settings (outbound folder, Ship To Account), and creating a mapping template that includes the mandatory ShipNode.ShipNode field.

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

The Send Fulfillment Requests integration converts Flxpoint fulfillment requests into SP Richards purchase orders in XML format. The XML is uploaded via FTP to SP Richards' inbound folder. If no error is received during upload, the FR is marked as processed.

The setup is completed in four steps.

Step 1: Connect an Integration

Select SPRichard and choose your existing FTP (Basic Auth) connection. This is the same connection used for inventory operations. If you need a new connection, enter:

  • Connection Name
    Internal reference name (e.g., SP Richards FTP).
  • FTP Protocol
    FTP.
  • FTP Host
    Provided by SP Richards.
  • FTP Port
    Provided by SP Richards.
  • FTP User
    Your FTP username.
  • FTP Password
    Your FTP password.
  • File Transfer Mode
    Binary file type.

Click Test Connection, then Save Connection once successful.

Tip: You do not need a separate connection. Reuse the same SP Richards FTP connection created during inventory setup.
Step 2: Configure Settings
  • Outbound Remote File Folder * — required. The path on the SP Richards FTP where XML FRs should be written.
  • Ship To Account Number * — Your SP Richards ship-to account identifier used on the FR.
    • If a Ship To Account is mapped in the template, that mapped value is used.
    • If it is not mapped, the value configured here is used.
    • If no Ship To Account value is available from either source, the Send Fulfillment Request job will fail.

Expand Advanced Settings if needed:

  • Hold for X hours — Temporarily hold FRs before sending (useful for manual review).
  • Only Send During Business Hours — Restrict sends to business hours only.

Click Save and Proceed.

Step 3: Define a Mapping Template

Choose an existing template (e.g., Send Purchase Orders 2) or create a new one. Click Save and Complete.

Required: Your mapping template must include ShipNode.ShipNode as a two-digit DC value (e.g., "01", "31"). This field is mandatory even when using Source Complete "C". Do not prefix with "DC ".
Template tip: If the DC is constant, set a constant value like "01". If it varies by product or region, add a transform/rule that always outputs two digits.
Step 4: Save & Complete

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 fulfillment request data maps to SP Richards' External Order XML schema. Header fields and line items map from your order to SP Richards' required format.

SP Richards Requirement — ShipNode (DC)
  • Mandatory field: XML must include ShipNode.ShipNode.
  • Format: exactly two digits, with leading zero if needed (e.g., "01", "31"). Do not send "DC 01".
  • Source Complete "C": even though SP Richards sources the order (DC not chosen from this value), the field is still required and must be valid.
Example (valid): <ShipNode><ShipNode>01</ShipNode></ShipNode>
Example (invalid): <ShipNode><ShipNode>DC 01</ShipNode></ShipNode>
Recommended Mapping (Key Fields)
Business Value SP Richards FR Field Notes
FR / PO Number CustomerPONo Mappable in template; used as the Fulfillment Request Number.
Distribution Center (DC) ShipNode.ShipNode Mandatory. Exactly two digits (e.g., "01", "31"). Required even with Source Complete "C".
Ship-To Account ShipToAccount Configured in job settings. Can also be mapped in template (mapping takes precedence over settings).
Shipping Method ParcelZone / Carrier fields Can pass supplier shipping method; selection UI not supported.
Items Line Items (SKU) SKU is sent with each FR line.
Ship To Account Source SUPPORTED (Mapping + Settings) If Ship To Account is mapped in the template, that value is used. If not mapped, the value from integration settings is used. If no value exists in either place, the Send Fulfillment Request job fails.
Ship To Account (Optional Mapping)
  • You can also map Ship To Account in this template when you need different ship-to accounts per rule (for example, per warehouse, brand, or channel).
  • When present in the mapping, this value takes precedence over the Ship To Account configured in the job settings.
  • If neither the mapping nor the job settings provides a Ship To Account, the Send Fulfillment Request job will fail.
Tip: If your DC varies by product or region, set ShipNode.ShipNode via a mapping rule or transformation that yields a two-digit string. Avoid prefixes like "DC ".
Summary: Map the key fields above for accurate FR submission to SP Richards. ShipNode.ShipNode and Ship To Account are the most critical fields to verify.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • ShipNode.ShipNode is mapped to a valid two-digit DC value.
  • Ship To Account is configured in settings or mapped in the template.
  • Outbound Remote File Folder is set to the correct FTP path.
Troubleshooting
  • Upload errors? — Verify FTP credentials and folder path. Confirm the XML meets SP Richards' schema requirements.
  • FR not marked processed? — Check job notifications for an error during upload; fix and re-run.
  • Missing SKU lines? — Confirm your mapping includes SKUs on each FR line.
  • ShipNode rejected? — Ensure ShipNode.ShipNode is exactly two digits (e.g., "01"). Values like "DC 01" or non-numeric strings will be rejected by SP Richards.
  • Using Source Complete "C"? — The field is still mandatory. Include a valid two-digit DC even though SP Richards determines the DC during sourcing.
  • Ship To Account failure? — Verify the value exists either in the mapping template or in job settings. If neither provides a value, the job will fail.
Operation Workflow
  • FR is posted on the FTP configured in connection settings.
  • File is posted as .xml.
  • If no error is received while uploading the file, the FR is marked as processed.
Operation Details
Feature Availability What to Expect
Fulfillment Request Number Supported FR number is mappable and sent as CustomerPONo.
Distribution Center (ShipNode) Supported (Mandatory) ShipNode.ShipNode must be present and formatted as two digits.
Ship To Account Source Supported (Mapping + Settings) If Ship To Account is mapped in the template, that value is used. If not mapped, the value from integration settings is used. If no value exists in either place, the Send Fulfillment Request job fails.
FR Item Association Supported Line items include SKU in the FR payload.
Customer Association Not Supported Customer record linking is not used.
Auto Acknowledgements Not Supported No acknowledgement file is received on upload.
Shipping Selection Not Supported Selection UI not supported, but supplier shipping method can be sent.
Custom Fields Not Supported FR focuses on standard header + item fields.
Attachments Not Supported Additional files are not transmitted with the FR.
Limitations Follow supplier's XML schema; errors during upload will prevent "processed" status.
Tip: Test with a single order first to verify ShipNode, Ship To Account, and FTP folder path before enabling automation.
 
 

Get Shipments

Introduction

Get Shipments (GS) retrieves shipment confirmations from SPRichard via FTP as .xml files and updates your orders with carrier, method, tracking, and item-level shipped quantities.

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

Note: Some shipments may not populate a carrier_number; related values can appear on Carton ID or BOL. Use mapping and rules to capture the best available identifiers.

Use this job to:

  • Fetch shipment XMLs from the supplier's FTP inbound folder.
  • Update orders with carrier, shipping method, tracking ID, and ship date.
  • Associate shipped items by SKU and support partial shipments where only a subset is shipped.

Each run follows this workflow:

  • 1Pull XML — GS reads files that match your Remote File Name Pattern from the configured Inbound Remote File Folder.
  • 2Parse — Carrier, method, tracking, carton/BOL, and line items (SKU & shipped qty) are parsed into your mapping template.
  • 3Apply Lookback — Only FRs created within the FR Lookback Period are considered (default 90 days).
  • 4Save — Shipment data posts back to the order; partials are supported.
Example: XML shows Carrier=UPS, Method=Ground, Tracking=1Z…, ShipDate=2025-08-17, and line with SKU=ABC-123, ShippedQty=2 → order gets updated accordingly.
Step 1: Connect an Integration

Choose SPRichard and your FTP (Basic Auth) connection.

Step 2: Configure Settings
  • Remote File Name Pattern * — File mask for shipment XMLs (e.g., spr_shipments_*.xml).
  • Inbound Remote File Folder * — FTP directory from which to read shipment files.
  • File Action — Read (leave files) or other actions per your policy.
  • Advanced → FR Lookback Period for Get Shipments — Max age of FRs eligible for shipment retrieval (default 90 days). Tooltip explains behavior.
Step 3: Define a Mapping Template

Use the recommended fields from the Mapping Utilities section below.

Step 4: Save & Schedule

Run manually or schedule (UTC).


Mapping Template (Recommended Fields)

Use these source fields from SP-Richard – Get Shipments and Get Shipment Items to populate your shipment object.

Shipment Field SPRichard Field Notes
Carrier Carrier Text value in shipment header.
Method Shipping Method Supplier shipping method string.
Tracking ID Tracking ID Main tracking code; may be blank on some LTLs.
Carton ID / BOL Carton Id / Bol Use when tracking isn't provided.
Shipped At Ship Date Date value mapped to shipment timestamp.
PO Number Purchase Order Number Used to associate XML back to the FR/Order.
Item → SKU SKU Shipment line association is by SKU.
Item → Shipped Qty Shipped Quantity Supports partial shipments.
Item → UOM UOM Optional; for reporting/consistency.
Weight Actual/Estimated Weight If present, map to shipment weight.
Operation Workflow
  • Shipment is fetched via the FTP connection configured in settings.
  • File format is .xml; a sample file is referenced in the docs.
  • Carrier number may not be present; consider using Carton ID or BOL fields and mapping rules to preserve identifiers.
Summary: Map carrier, tracking, ship date, PO number, and line-level SKU/quantity to get full shipment visibility in Flxpoint.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Remote File Name Pattern and Inbound Folder match the shipment XML location.
  • FR Lookback Period covers the age of your target FRs (default 90 days).
Troubleshooting
  • No shipments found? Verify the file pattern/folder and the Lookback window cover your target FRs.
  • Missing tracking? Check Carton ID/BOL fields and map to a custom attribute for reference if needed.
  • Item lines didn't attach? Ensure the supplier XML includes SKU and your template maps it to the line item.
Operation Details
Feature Availability What to Expect
Carrier & Methods Supported Carrier and method are available in the XML we receive.
Shipment Item Association Supported Item association is by SKU.
Partial Shipments Supported Multiple files/lines can incrementally complete fulfillment.
Invoice Information Not Supported Invoice/financials are not part of this feed.
Custom Fields Not Supported Standard shipment fields only.
Limitation Carrier number may be missing; map Carton Id/BOL and use rules as needed.
Tip: If tracking IDs are frequently missing, set up a rule to fall back to Carton ID or BOL as the tracking reference.
 
 

Get Invoices

Introduction

In Flxpoint, Get Invoices imports supplier invoice documents from SPRichard so you can reconcile costs and post billable charges back to your orders.

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

What it does: Fetches invoice .XML files from SPRichard over FTP and saves invoice headers, line items, and costs into Flxpoint for the related Fulfillment Requests (FRs).

Use this job to:

  • Capture official invoice totals (merchandise, shipping/freight, handling, tax, fees) for accounting.
  • Associate invoice lines to FR items using the supplier SKU.
  • Support downstream reporting and margin analysis across shipments and orders.

Each run follows this workflow:

  • 1Connect — Use SPRichard connection (FTP Basic Auth). The job uses the FTP host, user, and password defined in the connection.
  • 2Read Files — Job reads inbound .xml invoices from the Inbound Remote File Folder using your Remote File Name Pattern.
  • 3Map — Invoice header and item fields are mapped via your Mapping Template (see recommendations below).
  • 4Save — Flxpoint creates/updates PO Invoices linked to your FRs within the selected lookback window.
Example: If an invoice shows Merchandise = $100, Freight = $12, Tax = $8, and references SKU SPR-12345, the job will save an invoice totaling $120 with a shipping (freight) charge and associate the line to SKU SPR-12345.

In the SPRichard source → Get Invoices:

Step 1: Connect an Integration

Select SPRichard and your existing FTP connection.

Step 2: Configure Settings
  • Remote File Name Pattern — Pattern for invoice files (e.g., inv_*.xml).
  • Inbound Remote File Folder — Folder on the SPRichard FTP where invoices are deposited.
  • File Action — Typically Read.
  • FR Lookback Period for Invoice Processing — Only FRs created within this window are eligible for invoice association (default 30 days). What's this? Defines the maximum age of FRs considered by the job. Choose a larger window if invoices post much later than shipment. 
Step 3: Create a Mapping Template

Use the recommended mappings from the Mapping Utilities section below.

Step 4: Save & Schedule

Run on demand or enable a schedule (UTC).


Mapping Template (Recommended Fields)

Suggested starting point for SPRichard invoice header and line items:

Flxpoint Invoice Field SPRichard Field (XML) Notes
Invoice Number InvoiceNumber / Invoice Document Number Primary invoice identifier.
Invoice Date InvoiceDate Date type.
Invoice Status Static: Unpaid or Paid Optional — can be set via option in template.
Ship Method (Header) ShipMethod / ShipCode If present at header; otherwise map per line as needed.
Shipping Cost FreightCost Saved as Shipping charge item.
Handling Cost HandlingCost Saved as Handling fee item.
Other Cost OtherCost Saved as Other fee item.
Tax Cost TaxCost Saved as Tax charge.
Total Cost TotalCost Optional header total; line-level Extended Amounts should still be mapped.
Item: SKU Item/Sku Used for item association to FR line.
Item: Description Item/Description Optional but helpful for review.
Item: Shipped Qty Item/ShippedQuantity Numeric.
Item: Extended Amount Item/ExtendedAmount Line extended cost.
Item: Retail Price (Optional) Item/RetailPrice Only if provided and needed.
Tip: Header-level Shipping/Handling/Other costs are added as separate invoice items. If SPRichard sends these values on multiple rows for the same invoice, the last value encountered becomes the saved header charge.
Summary: Map the invoice header fields (number, date, costs) and line-level SKU/quantity/amount to get complete invoice data in Flxpoint.

Quick Checks
  • Connection shows Connected and passes Test Connection.
  • Mapping template is selected and saved.
  • Remote File Name Pattern and Inbound Folder match the invoice XML location.
  • FR Lookback Period covers the age of your target FRs (default 30 days).
Troubleshooting
  • No files found? Confirm the Inbound Remote File Folder and Remote File Name Pattern match what SPRichard is dropping on FTP.
  • Invoices not linking to FRs? Ensure the FR was created within the Lookback Period and that SKU in the invoice matches the SKU used on the FR line.
  • Missing costs? Map Freight/Handling/Tax/Other at the header (recommended) and verify values are present in the XML.
Operation Details
Feature Availability What to Expect
Invoice Format Supported XML files over FTP.
Line Item Costs Supported Extended Amount available at line level.
Item Association Supported SKU is provided for linking to FR items.
Limitations None documented beyond standard feed availability/timeliness.
Tip: If invoices post much later than shipments, increase the FR Lookback Period to ensure older FRs are still eligible for invoice association.
 
 
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 SP Richards integration. Expand each item to learn more.

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

Contact Support

 

 

Related Articles

Meyer as a Source

Meyer Distribution is a source that provides a wide range of automotive and RV pa...