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; optionally sum across selected warehouses.
• Bring in dealer pricing when available to you (client-specific pricing).

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.

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

• 1Connect 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.
• 2Configure 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.
• 3Define a Mapping Template — Use the recommended fields below, then adjust for your catalog.
• 4Save & Schedule — Run manually or enable a schedule (jobs run in UTC).

• 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.
• Status page shows: 1) Connected 2) Configured 3) Mapped — when each step is complete.

• 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”.

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

• 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.

You can enable a schedule so this job runs automatically and keeps your SPRichard data fresh. Schedules run in UTC. The status page will show Connected, Configured, and Mapped with the template (e.g., “SPRichard Get Source Products 1”) once complete.

• 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).

• 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. :contentReference[oaicite:4]{index=4} :contentReference[oaicite:5]{index=5} :contentReference[oaicite:6]{index=6}
• 3Write — Updates cost/qty in the Global Inventory Pool.

• 1Connect an Integration — Choose SPRichard and use FTP (Basic Auth) credentials.
• 2Configure 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). :contentReference[oaicite:7]{index=7}
  • Advanced > Allow Create Variant — toggle Yes to allow variant creation during Secondary runs.
• 3Define a Mapping Template — Use the “Secondary” mapping below.
• 4Save & Schedule — Run manually or enable scheduling (jobs run in UTC).

Map only the fields you need for delta updates. Field names below are drawn from your SPRichard Inventory Item schema & templates. :contentReference[oaicite:8]{index=8} :contentReference[oaicite:9]{index=9}

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

• 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. :contentReference[oaicite:13]{index=13}
• 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.

Enable a schedule to update cost/qty automatically. All schedules run in UTC. When ready, the status page will show Connected, Configured, and Mapped with your template (e.g., “Get Inventory 2”).

• Generate an XML Fulfillment Request (FR) for each eligible order.
• Transmit FRs to SPRichard via your configured FTP (Basic Auth) connection.
• Optionally delay or restrict sends using Hold for X hours and Only Send During Business Hours.

• 1Build XML — SFR builds the FR XML using your Mapping Template (CustomerPO/FR number, items/SKUs, etc.). :contentReference[oaicite:3]{index=3}
• 2Upload — The XML is posted to the Outbound Remote File Folder on the SPRichard FTP you configured.
• 3Status — If no error is received during upload, the FR is marked as processed. A sample FR is referenced in the docs/screens.

• 1Connect an Integration — Select SPRichard and choose your FTP (Basic Auth) connection.
• 2Configure Settings
  • Outbound Remote File Folder — Path on SPRichard FTP where XML FRs should be written.
  • Ship To Account Number — Your SPRichard ship-to account identifier required on the FR.
  • Advanced Settings
    • Hold for X hours — Temporarily hold FRs before sending (handy for manual review). Tooltip explains it limits the hold to X hours.
    • Only Send During Business Hours — Restrict sends to business hours only.
• 3Define a Mapping Template — Pick your template (e.g., Send Purchase Orders 2) or create a new one.
• 4Save & Complete — Run on demand or enable scheduling (runs in UTC).

Header fields and line items map from your order to SPRichard’s External Order schema. These commonly used fields are present in your mapping UI: Fulfillment Request Number (CustomerPO), various dealer reference fields, freight carrier/account, parcel zone/shipping method, etc. :contentReference[oaicite:4]{index=4}

• Outbound Remote File Folder * — required.
• Ship To Account Number * — required.
• Hold for X hours — Stops FRs from sending for X hours; useful for review.
• Only Send During Business Hours — If checked, SFR restricts the send window to business hours.

• FR is posted on the FTP configured in connection settings.
• File is posted as .xml.
• If no error is received while uploading the file, we mark the FR as processed.
• A sample FR file is attached/referenced in the internal docs.

• Upload errors? Verify FTP credentials/folder path and that XML meets SPRichard schema.
• 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. :contentReference[oaicite:12]{index=12}
• Shipping issues? Since selection is not supported, pass the supplier method via mapped fields instead. :contentReference[oaicite:13]{index=13}

You can enable a schedule for automatic sending. The status page will show Connected, Configured, and Mapped (e.g., template Send Purchase Orders 2). Schedules run in UTC.

• 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.

• 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. :contentReference[oaicite:1]{index=1}
• 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.

• 1Connect an Integration — Choose SPRichard and your FTP (Basic Auth) connection.
• 2Configure 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.
• 3Define a Mapping Template — Recommended fields below.
• 4Save & Schedule — Run manually or schedule (UTC).

Use these source fields from SP-Richard – Get Shipments and Get Shipment Items to populate your shipment object. :contentReference[oaicite:2]{index=2}

• 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.

• 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. :contentReference[oaicite:3]{index=3}
• Item lines didn’t attach? Ensure the supplier XML includes SKU and your template maps it to the line item.

Enable scheduling to pull shipments automatically; status shows Connected, Configured, and Mapped (e.g., template Get Shipments 2). Schedules run in UTC.

• 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.

• 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.

In the SPRichard source → Get Invoices:

• 1Connect an Integration — Select SPRichard and your existing FTP connection.
• 2Configure 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.
• 3Create a Mapping Template — Use the recommended mappings below.
• 4Save & Schedule — Run on demand or enable a schedule (UTC).

Suggested starting point for SPRichard invoice header and line items:

• 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.

• 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.

Enable a schedule to continuously capture new invoices from SPRichard. All schedules run in UTC.