Promostandards as a Source

July 17, 2026

Summary

Promostandards is an industry-standard API used by promotional products suppliers. The connection uses Company Code, User Name, Password, Environment, and a critical Service Type selector — you'll create a separate connection for each Service Type you use (Product for GIP/GIS, Purchase Order for Send FR, Shipment for Get Shipments, Invoice for Get Invoices), typically reusing the same credentials. The integration imports the full product catalog (GIP), refreshes pricing and quantity more frequently (GIS), sends fulfillment requests, and pulls back shipment and invoice confirmations; for operation-level mapping guidance contact support@flxpoint.com.

What this integration does

Get Inventory (Primary)

Imports the full product catalog — title, pricing, images, categories.

Get Inventory (Secondary)

A lighter, more frequent refresh of pricing and quantity only.

Send Fulfillment Requests

Sends fulfillment requests (purchase orders) to the supplier for dropship.

Get Shipments

Pulls shipment confirmations — tracking number and ship date — into Flxpoint.

Get Invoices

Imports supplier invoices — line items, shipping, tax and totals.

How to connect - credentials you need

Promostandards uses one connection type, but you'll create a separate connection for each Service Type you need — Product, Purchase Order, Shipment, and Invoice — reusing the same Company Code, User Name and Password. Add a Promostandards source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection. Repeat for each operation, changing only the Service Type.

Company CodeRequired

The company code your Promostandards supplier assigned to your account.

User NameRequired

Your Promostandards API username, provided by your supplier.

PasswordRequired

Your Promostandards API password, provided by your supplier.

EnvironmentRequired

Toggles Production vs Sandbox. Use Sandbox to verify setup, then switch to Production before go-live — credentials can differ between environments.

Service TypeRequired

Selects which Promostandards service this connection uses: Product (for GIP/GIS), Purchase Order (for Send FR), Shipment (for Get Shipments), or Invoice (for Get Invoices). Create one connection per Service Type.

API End Points JSON FileOptional

Optional file upload if your supplier requires custom API routing configuration; most accounts can leave this blank.

Company Code, User Name and Password are typically identical across all four Service Type connections — only the Service Type field changes per operation. If your supplier requires custom API routing, upload the optional API End Points JSON File on the connection; otherwise Flxpoint resolves routing automatically from your Company Code. For extended field-mapping guidance, contact support@flxpoint.com.

Important - read before configuring

Create one connection per Service Type — same credentials, different Service Type per operation

Each Promostandards operation requires a connection with a matching Service Type: Product → GIP + GIS; Purchase Order → Send FR; Shipment → Get Shipments; Invoice → Get Invoices. Your Company Code, User Name, and Password are typically the same across all four — only the Service Type field changes. Using a Product connection for Send FR (which needs Purchase Order) will cause the job to fail with a connection type error.

FOB ID and Price Type are required for GIP and GIS — confirm values with your supplier

FOB ID identifies the shipping origin used for inventory lookups — enter the value provided by or agreed upon with your supplier. Price Type controls which price is fetched: Customer, List, or Net. An incorrect FOB ID returns zero inventory. A wrong Price Type returns empty or unexpected pricing. Confirm both values with your Promostandards supplier before your first GIP run.

Enable Archive/Un-Archive on one inventory job only — Primary or Secondary, not both

Archive on GIP and GIS simultaneously causes conflicts — products alternate between archived and active states unpredictably. Enable Archive on one job only. If both GIP and GIS are scheduled, enable Archive on GIP and leave it disabled on GIS. GIS is a delta feed focused on price/quantity updates; Primary handles full catalog archival.

Send FR returns a transaction ID as the confirmation number — all required fields must be mapped

Send FR submits to the supplier's Promostandards Purchase Order web service and receives a transaction ID in the response, saved as the confirmation number. Required order-level fields: Order Number, Order Date, Order Type, Currency, Total Amount, Sales Channel, Terms And Conditions. Required item fields: Part Id, Description, Quantity, Quantity UOM, Customer Supplied, Allow Partial Shipments, Blind Ship, Allow Consolidation, Packing List Required, Carrier, Service. Missing any required field causes the submission to fail.

Operations - fields to know

Get Inventory (Primary)Get Inventory (Secondary)Send Fulfillment RequestsGet ShipmentsGet Invoices

Field	Maps To — Notes
Part Id	→ Variant → SKU. Required. Variant-level identifier for the specific part.
Product Name	→ Product → Title. Product title shown in your catalog.
Description	→ Product → Description. Supplier's product description text.
Category / Sub Category	→ Product → Category (1/2). Two levels of supplier category.
Price (per Price Type)	→ Pricing → Cost. Required. Price returned for the Price Type configured on the connection (Customer, List, or Net).
Quantity Available	→ Inventory → Quantity. Required. Available units, scoped by FOB ID when Fetch Inventory Based on FOBID is enabled.
Dimensions, Weight, Color/Size	→ Variant → Dimensions / Options. Depth, height, width, weight and any color/size options the supplier provides.
Primary Image / Media Content	→ Product / Variant → Images. Product-level and, where available, per-variant images.

Field	Maps To — Notes
Part Id	→ Inventory Variant → SKU. Required. Primary identifier.
Quantity Available	→ Inventory → Quantity. Required. Current available units.
Price (per Price Type)	→ Pricing → Cost. Price returned for the connection's configured Price Type.
Full catalog fields	Not included in Secondary — titles, categories, images and identifiers come from Get Inventory (Primary). Run Primary for the full catalog and Secondary more frequently to keep Quantity and Cost current.

Source Field	Maps To (Promostandards) — Notes
Order Number, Order Date, Order Type, Currency, Total Amount, Sales Channel, Terms And Conditions	→ Purchase Order. Required. Order-level fields sent with every request.
Fulfillment Request line → Part Id, Quantity, Quantity UOM, Description	→ Line Item. Required. Sent per line item to the supplier's Purchase Order service.
Shipping address / Ship-to contact	→ Ship To. Required. End-customer shipping address and contact details.
Source Shipping Method	→ Carrier / Service. Freight carrier and service level sent with the order.
Allow Partial Shipments, Blind Ship, Allow Consolidation, Packing List Required	→ Shipment instructions. Fulfillment handling flags required by the Purchase Order service.
Supplier response → transaction ID	→ Confirmation Number. Saved on the Fulfillment Request once the supplier accepts the order.

Field	Maps To — Notes
Id	→ Fulfillment Request Number. Required. Links this shipment back to the originating Fulfillment Request.
Tracking Number	→ Shipment → Tracking Number. Required.
Carrier / Shipment Method	→ Shipment → Carrier / Ship Method. Carrier and method returned by the supplier.
Shipment Date	→ Shipment → Shipped At.
Distributor Part Id	→ Shipment Item → SKU. Required. Associates the shipped line to your catalog.
Quantity	→ Shipment Item → Quantity. Required. Supports partial shipments.

Field	Maps To — Notes
Invoice Number / Invoice Date	→ Invoice → Number / Date.
Shipping Amount	→ Invoice → Shipping Cost. Mapped at the invoice (order) level.
Tax Amount	→ Invoice → Tax Cost. Mapped at the invoice (order) level.
Invoice Amount	→ Invoice → Total Cost.
Distributor Part Id	→ Invoice Item → SKU. Required.
Invoice Quantity	→ Invoice Item → Quantity. Required.
Unit Price	→ Invoice Item → Per Unit Cost.
Extended Price	→ Invoice Item → Cost.

Common issues

Connection failing — wrong Service Type for the operation

The most common Promostandards error is using a connection with the wrong Service Type. Each operation requires a specific Service Type: GIP/GIS → Product; Send FR → Purchase Order; Get Shipments → Shipment; Get Invoices → Invoice. If you see a connection or authentication error on an operation, first confirm the connection's Service Type matches the operation. Open the connection → check the Service Type field → create a new connection with the correct Service Type if needed (use the same credentials, just change Service Type).

GIP returning zero products or prices — FOB ID or Price Type incorrect

Zero products after GIP most often means the FOB ID doesn't match what the supplier has configured — an incorrect FOB ID returns no inventory. Zero or unexpected prices means the Price Type (Customer/List/Net) doesn't match what's available on the supplier's Promostandards feed. To fix: (1) confirm the exact FOB ID with your supplier; (2) confirm which Price Type is active for your account on the supplier's system; (3) if "Fetch Inventory Based on FOBID" is ON and returning zero, try disabling it to get the sum across all locations. Run GIP manually after each change and check the run log.

FAQs

How do I create connections for each Promostandards operation?▸

In your Promostandards source, go to Integrations → Get Inventory [Primary] → Start Creating Integrations → Promostandards → Create New Connection. Fill in: Connection Name (e.g., "Supplier X – Product"), Company Code, Environment (Production or Sandbox), Password, Service Type: Product, User Name. Click Test Connection → Save Connection. Repeat for each operation, changing only the Service Type: Purchase Order for Send FR, Shipment for Get Shipments, Invoice for Get Invoices. Optionally upload an API End Points JSON File if your supplier requires custom API routing configuration.

What does GIP import from Promostandards and what settings are required?▸

GIP calls the supplier's Promostandards Product web service and imports: SKU (Product Id), Title (Product Name), Description, Quantity (FOB-based or sum of all locations), Price (based on Price Type), Category 1/2 (two levels), Weight (lbs), Dimensions (inches), Images (multi-image supported), Variations (multiple variants per product). Required settings: FOB ID (shipping origin from supplier), Price Type (Customer/List/Net). Optional: Fetch Inventory Based on FOBID (toggle ON for single location, OFF for sum of all). GIS is a delta feed of the same Product connection — maps only SKU, Quantity, Cost, MSRP, MAP.

What does Get Shipments map and what is the FR Lookback Period?▸

Get Shipments uses Service Type: Shipment. Required mapping: Id → Fulfillment Request Number (links shipment to FR), Tracking Number → Tracking Number. Recommended: Carrier, Shipping Method, Shipment Date → Shipped At. Item-level: Distributor Part Id → SKU (required), Quantity → Quantity (required — supports partial shipments). FR Lookback Period controls how far back FRs are eligible for shipment matching — default is 3 months. Increase if FRs are older than 3 months.

What does Get Invoices import and how does it differ from Get Shipments?▸

Get Invoices uses Service Type: Invoice and is separate from Get Shipments. Invoice-level fields: Invoice Number, Invoice Date, Freight Amount → Shipping Cost, Sales Tax → Tax Cost, Total Invoice Amount → Total Cost. Item-level: Distributor Part Id → SKU, Quantity, Unit Price → Per Unit Cost, Extended Price → Cost. FR Lookback Period defaults to 1 month (shorter than Get Shipments). Map Shipping Cost and Tax Cost at the invoice (order) level — not at the item level. Voided invoices are not supported.

Back to General Supplier Integrations