In this guide, you’ll learn how to set up your Promostandards feed in Flxpoint, from creating the source wizard to activating inventory and order operations. With this connection you’ll keep stock and pricing synchronized, place fulfillment requests, and ensure seamless routing through Promostandards.
Add Source and Establish Connection
Choose the right Source Type
For most Promostandards 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 the supplier 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).
- Yes (Recommended): You can route orders here.
- No: Routing/Shipping steps won't apply.
- Override: Auto Processing (Use Global / Auto Process / Do NOT Auto Process).
- Commit Stock + Inventory Management Options.
- Allow Backorders / Cancel Unacknowledged Items.
- Yes, Use Rate Shopping (Real-Time Estimates).
- No, Set Up via Rules.
Finish the Source Wizard by confirming your Ship From location and reviewing shipping behavior for Promostandards. For most Promostandards suppliers, you do not create a Source Shipping Method here—the supplier will choose the carrier and service on their side when they receive the Fulfillment Request.
- For typical Promostandards 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.
Only create a Source Shipping Method if:
- Your supplier has explicitly confirmed that their 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.
- Address, City, State/Code, Postal Code, Country/Code
- Optional: Contact Name, Phone, Email
To connect a Promostandards supplier in Flxpoint, you'll create a Promostandards Connection using your supplier-provided credentials. You will need to create a separate connection for each Service Type you plan to use (Product, Purchase Order, Shipment, Invoice).
- Connection Name — A descriptive name (e.g., Supplier X – Product).
- Company Code — Your company code provided by the supplier.
- API End Points JSON File (optional) — Upload a JSON file with custom webservice endpoints. If provided, only these endpoints will be used and the default Promostandards endpoint discovery will be skipped.
- Environment — Select the environment (e.g., Production or Sandbox).
- Password — The password provided by the supplier.
-
Service Type — Choose the service this connection is for:
- Product — for Inventory operations (Get Inventory [Primary] & [Secondary]).
- Purchase Order — for Send Fulfillment Requests.
- Shipment — for Get Shipments.
- Invoice — for Get Invoices.
- User Name — The user name provided by the supplier.
- Product connection → used by Get Inventory [Primary] and Get Inventory [Secondary].
- Purchase Order connection → used by Send Fulfillment Requests.
- Shipment connection → used by Get Shipments.
- Invoice connection → used by Get Invoices.
Product & Order Operations
Now that you’ve finished the wizard, you’ll see Promostandards has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your Promostandards stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to Promostandards and pulling back shipment/tracking data. All four use the same Promostandards 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 Promostandards 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)
In Flxpoint, Get Inventory (Primary) (GIP) is the job that imports Promostandards product data and quantities into your Global Inventory Pool. This integration connects to your supplier's Promostandards-compliant web services to fetch product catalog information, pricing, and availability.
Use GIP to keep your Promostandards supplier inventory current in Flxpoint: import the full product catalog with core details (titles/descriptions, categories, images, weights & dimensions), keep quantities current, and bring in generic pricing based on the selected price type (Customer, List, or Net).
The sections below walk through each step of the setup and configuration process.
Each run follows this workflow:
- 1Select Connection — Choose your Promostandards connection (Service Type: Product).
- 2Fetch Data — Flxpoint calls the supplier's Promostandards web services to retrieve product data, pricing (based on your selected Price Type), and inventory availability.
- 3Map Fields — Incoming data is 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 Promostandards source → Get Inventory (Primary):
Choose Promostandards and select (or create) a connection with Service Type set to Product.
Tip: Use Test ConnectionValidates credentials and endpoint availability before you save. after entering your credentials.
- FOB ID (required) — Enter the FOB ID provided by or agreed upon with your supplier. This identifies the shipping origin point used for inventory and pricing lookups.
-
Price Type (required) — Select which price to fetch from the supplier:
What does this do?
Fetch price based on price type.
Customer List Net
-
Fetch Inventory Base on FOBID (toggle) — When enabled, Flxpoint
will fetch the quantity based on the configured FOB ID only. When disabled, Flxpoint will
pull the sum of available quantities from all locations.
Recommendation: Enable this if you want inventory from a specific warehouse/location only. Leave disabled to get the total available quantity across all supplier locations.
-
Archive/Un-Archive Inventory (toggle) — When enabled, all inventory that is
not found in the source feed will be "archived" (quantity set to zero). If inventory is
later added back to the source feed, it will be "un-archived" (re-activated with mapped quantity).
Recommendation: We recommend that you do NOT enable this setting for this integration if you have already enabled it for Get Inventory [Secondary] on this source.
Use the recommended fields from the Mapping Utilities section below, then adjust for your catalog.
Run manually or enable a schedule (jobs run in UTC). The status page will show Connected, Configured, and Mapped once complete.
Starter field mapping for Promostandards (adjust per your template):
| Flxpoint Field | Promostandards Field | Notes |
|---|---|---|
| SKU | Product Id |
Unique product identifier from the supplier. |
| Title | Product Name |
Human-readable product name. |
| Description | Description |
Product description text. |
| Quantity | Quantity |
Sum of all locations or FOB-specific (based on config). |
| Price | Price |
Based on selected Price Type (Customer, List, or Net). |
| Category 1 | Product Category |
Top-level category. |
| Category 2 | Product Subcategory |
Second-level category. Two levels available to map. |
| Weight | Weight |
Available in pounds. |
| Dimensions | Dimensions |
Available in inches. |
| Images | Images |
Multi images are available. |
| Variations | Variants |
Multiple variants are available for product. |
- Variants are supported — multiple variants per product are available from the Promostandards feed.
- Generic Pricing is supported — pricing is fetched based on the Price Type you selected in configuration (Customer, List, or Net).
- Multi images are available for products, allowing you to map multiple product images.
- FOB-based inventory: Toggle "Fetch Inventory Base on FOBID" to control whether quantities come from a specific location or are summed across all.
- Connection shows Connected and passes Test Connection.
- Service Type is set to Product on the connection.
- Mapping template is selected and saved.
- FOB ID is entered and matches the value provided by your supplier.
- Price Type is set to the correct option (Customer, List, or Net).
- Archive is enabled in one integration only (Primary or Secondary, not both).
-
Prices are empty or unexpected:
- Verify your Price Type selection (Customer, List, or Net). Different types return different pricing from the supplier.
- Confirm with your supplier that pricing is available for the selected Price Type in their Promostandards feed.
-
Quantities are zero or missing:
- Check the FOB ID — an incorrect FOB ID may return zero inventory.
- If "Fetch Inventory Base on FOBID" is enabled, only that location's stock is returned. Try disabling the toggle to get the sum across all locations.
- Connection errors: Confirm Company Code, User Name, and Password with your supplier. Ensure the connection's Environment matches (Production vs. Sandbox).
- Items missing after a run: If Archive is enabled, SKUs absent from the feed will be archived (qty set to zero) until they reappear.
- Custom API endpoints not working: If you uploaded an API End Points JSON File in the connection, verify the JSON format is correct. When this file is provided, default Promostandards endpoint discovery is skipped.
| Feature | Availability | What to Expect |
|---|---|---|
| Custom Fields | Not Supported | — |
| Variations / Options | Supported | Multiple variants are available for product. |
| Generic Pricing (& Currency) | Supported | Fetched based on the selected Price Type (Customer, List, or Net). |
| Client Pricing (& Currency) | Not Supported | — |
| Quantity | Supported | From Promostandards API; FOB-based or sum of all locations. |
| Multiple Warehouses | Not Supported | — |
| Weights & Dimensions (& Units) | Supported | Dimensions are available in inch and weight is available in pounds. |
| Images | Supported | Multi images are available. |
| Categories | Supported | Two level categories are available to map. |
| Delta Feed vs Full Feed | Full Feed | This is a full product feed. |
| Archive Support | Supported | Archive missing SKUs; auto-restore when they return. |
| Limitations | — | — |
Get Inventory (Secondary)
Get Inventory (Secondary) is the incremental update job for Promostandards. It pulls pricing and quantity updates for existing variants in your Global Inventory Pool. This job is designed as a delta feed, complementing the Primary full catalog import.
Use Secondary for higher-frequency price/qty refreshes. Keep rich catalog fields (titles, images, categories, descriptions) in the Primary job.
The sections below walk through each step of the setup and configuration process.
Use this job to:
- Refresh pricing (based on Price Type) for existing SKUs.
- Update quantities (FOB-based or sum of all locations).
- Optionally create variants during the run (advanced setting).
Each run follows this workflow:
- 1Connection — Uses a Promostandards connection (Service Type: Product) to call the supplier's web services.
- 2Fetch & Map — Flxpoint retrieves price and quantity data from the Promostandards API, then maps the fields to your Inventory Variant fields.
- 3Write — Updates price/qty in the Global Inventory Pool.
Choose Promostandards and select (or create) a connection with Service Type set to Product.
Tip: You can reuse the same Product connection created for Get Inventory [Primary].
- FOB ID (required) — Enter the FOB ID provided by or agreed upon with your supplier.
-
Price Type (required) — Select which price to fetch from the supplier:
What does this do?
Fetch price based on price type.
Customer List Net
-
Archive/Un-Archive Inventory (toggle) — When enabled, all inventory that is
not found in the source feed will be "archived" (quantity set to zero). If inventory is
later added back to the source feed, it will be "un-archived" (re-activated with mapped quantity).
Recommendation: We recommend that you do NOT enable this setting for this integration if you have already enabled it for Get Inventory [Secondary] on this source.
- Fetch Inventory by Parent SKU (toggle) — When enabled, the inventory will be fetched using the Parent SKU (Product ID). Useful when your inventory is organized by parent product rather than individual variants.
- Fetch Inventory Based on FOBID (toggle) — When enabled, Flxpoint will fetch the quantity based on the configured FOB ID only. When disabled, Flxpoint will pull the sum of available quantities from all locations.
Expand Advanced Settings if needed:
- Allow Create Variant (toggle) — When enabled, allows creating new variants while running Get Inventory Secondary. Leave disabled if you only want to update existing variants.
Click Save and Proceed.
Use the "Secondary" mapping from the Mapping Utilities section below.
Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped.
Map only the fields you need for delta updates. Secondary targets Inventory Variant fields:
| Flxpoint Field | Notes |
|---|---|
| SKU | Primary identifier used to match existing variants. |
| Quantity | Sum of all locations or FOB-specific (based on config). |
| Cost | Wholesale/supplier cost. |
| MSRP | Manufacturer's suggested retail price. |
| Source List Price | Supplier's list price. |
| MAP | Minimum advertised price. |
The full list of fields available to map in the Secondary template:
| Category | Fields |
|---|---|
| Identifiers | SKU, Master SKU, MPN, UPC, GTIN, ASIN, Reference Identifier |
| Product Info | Title, Description |
| Pricing | Cost, MSRP, MAP, Source List Price, Dropship Fee, Shipping Cost |
| Inventory | Quantity, Allow Backorders, Archived, Bin Location |
| Dimensions | Weight, Weight Unit, Weight Unit (Abbreviated), Height, Length, Width, Dimension Unit, Dimension Unit (Abbreviated) |
| Media & Variants | All Images, All Options |
- Connection shows Connected and passes Test Connection.
- Service Type is set to Product on the connection.
- Mapping template is selected and saved.
- FOB ID is entered and matches the value provided by your supplier.
- Price Type is set to the correct option (Customer, List, or Net).
- Archive is off if already enabled in Primary.
-
Prices are empty or unexpected:
- Verify your Price Type selection (Customer, List, or Net).
- Confirm with your supplier that pricing is available for the selected Price Type.
-
Quantities are zero or missing:
- Check the FOB ID — an incorrect FOB ID may return zero inventory.
- If "Fetch Inventory Based on FOBID" is enabled, only that location's stock is returned. Try disabling the toggle to get the sum across all locations.
- Variants not being created: Ensure Allow Create Variant is enabled in Advanced Settings if you want Secondary to create new variants.
- Parent SKU mismatch: If "Fetch Inventory by Parent SKU" is enabled, verify the Product ID matches the parent SKU in your inventory pool.
- Unexpected archives: If Archive is enabled and a SKU is absent from the delta, it will be archived with qty=0 until it reappears.
- Connection errors: Confirm Company Code, User Name, and Password. Ensure the connection's Environment matches (Production vs. Sandbox).
| Feature | Availability | What to Expect |
|---|---|---|
| Custom Fields (Variants Only) | Not Supported | — |
| Generic Pricing (& Currency) | Supported | Fetched based on the selected Price Type (Customer, List, or Net). |
| Client Pricing (& Currency) | Not Supported | — |
| Quantity | Supported | From Promostandards API; FOB-based or sum of all locations. |
| Multiple Warehouses | Not Supported | — |
| Weights & Dimensions (& Units) | Supported | Available in the mapping template. |
| Delta Feed vs Full Feed | Supported (Delta) | This is a delta feed. |
| Archive Support | Supported | Toggle in configuration. |
| Limitations | — | — |
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.
Order Operations
Configure Flxpoint to route orders to vendors for fulfillment and import the shipment details, so they sync back to your sales channel and customer.
Send Fulfillment Requests
The Promostandards – Send Fulfillment Requests integration automates sending purchase orders (POs) to your Promostandards supplier for fulfillment. Flxpoint converts fulfillment request details — such as shipping addresses, item quantities, and order information — into the Promostandards Purchase Order format and submits them via the supplier's web service.
This integration uses a Promostandards connection with Service Type set to Purchase Order. Configuration involves selecting the connection, defining settings (FOB ID, hold time), and creating a mapping template for both order-level and item-level fields.
The sections below walk through each step of the setup and configuration process.
The Send Fulfillment Requests integration converts Flxpoint fulfillment requests into Promostandards purchase orders. The order is submitted to the supplier's Promostandards web service. Upon successful submission, a transaction ID is received and saved as the confirmation number.
The setup is completed in four steps.
Select Promostandards and choose (or create) a connection with Service Type set to Purchase Order.
Tip: Use Test ConnectionValidates credentials and endpoint availability before you save. after entering your credentials.
- FOB ID — Enter the FOB ID for this fulfillment operation (identifies the shipping origin point).
Expand Advanced Settings if needed:
- Hold for X Hours — Stops POs/FRs from sending for X hours. Useful if you want to review orders before sending them but don't want to hold orders for more than X hours.
- Send During Business Hours — Check "Only Send During Business Hours" to restrict sends to business hours only.
Click Save and Proceed.
Choose an existing template or create a new one. The template maps Flxpoint fulfillment request data to Promostandards order fields at two levels: Order-level (header) and Item-level (line items). Click Save and 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 Promostandards' Purchase Order schema. There are two groups of fields: Order-level (header) and Item-level (line items with shipping details).
| Promostandards Field | Required | Notes |
|---|---|---|
| Order Number | Yes | FR/PO number. Can send Flxpoint FR# as order number or customize via mapping. |
| Order Date | Yes | Date of the order. Map from Fulfillment Request → Generated At or Sent At. |
| Order Type | Yes | Type of order being placed. |
| Currency | Yes | Currency code for the order (e.g., USD). |
| Total Amount | Yes | Total order amount. |
| Sales Channel | Yes | Sales channel identifier. |
| Terms And Conditions | Yes | Terms and conditions for the order. |
| Promo Code | No | Optional promotional code. |
| Promostandards Field | Required | Notes |
|---|---|---|
| Part Id | Yes | SKU / product identifier sent with each line item. |
| Description | Yes | Item description. |
| Quantity | Yes | Number of units ordered. |
| Quantity UOM | Yes | Unit of measure for quantity. |
| Unit Price | No | Price per unit. |
| Customer Supplied | Yes | Whether the item is customer-supplied. |
| Allow Partial Shipments | Yes | Whether partial shipments are allowed for this item. |
| Promostandards Field | Required | Notes |
|---|---|---|
| CompanyName | Yes | Ship-to company name. |
| Attention To | No | Attention line on the shipment. |
| Address 1 | No | Ship-to address line 1. |
| Address 2 | No | Ship-to address line 2. |
| Address 3 | No | Ship-to address line 3. |
| City | No | Ship-to city. |
| Region | No | Ship-to state/region. |
| Postal Code | No | Ship-to postal/zip code. |
| Country Code | No | Ship-to country code. |
| No | Contact email for the shipment. | |
| Phone | No | Contact phone for the shipment. |
| Blind Ship | Yes | Whether to blind ship (no supplier branding on package). |
| Allow Consolidation | Yes | Whether to allow order consolidation. |
| Packing List Required | Yes | Whether a packing list is required. |
| Carrier | Yes | Shipping carrier. |
| Service | Yes | Shipping service level. |
| Comments | No | Order comments or special instructions. |
| Promostandards Field | Required | Notes |
|---|---|---|
| Decoration Id | No | Decoration/imprint identifier. |
| Location Id | No | Imprint location on the product. |
| Artwork Type | No | Type of artwork file. |
| File Name | No | Artwork file name. |
| File Location | No | URL or path to the artwork file. |
| Transport Mechanism | No | How artwork is delivered (e.g., URL). |
- Connection shows Connected and passes Test Connection.
- Service Type is set to Purchase Order on the connection.
- Mapping template is selected and saved.
- All required order-level fields are mapped (Order Number, Order Date, Order Type, Currency, Total Amount, Sales Channel, Terms And Conditions).
- All required item-level fields are mapped (Part Id, Description, Quantity, Quantity UOM, etc.).
- Shipping address fields are mapped from the fulfillment request.
-
FR not sending?
- Check if Hold for X Hours is set — orders may be held pending review.
- Check if Send During Business Hours is enabled and the current time is outside business hours.
- Connection errors? — Confirm Company Code, User Name, and Password. Ensure the connection's Environment matches (Production vs. Sandbox) and Service Type is Purchase Order.
- Missing required fields? — Verify all required fields are mapped in the template. Missing required fields will cause the submission to fail.
- No confirmation number? — The transaction ID is automatically received from the supplier upon successful submission and saved as the confirmation number. If missing, check the job notifications for errors.
- Shipping method issues? — Carrier and Service are required item-level fields. Each supplier company may have different shipping options available.
- FR data is converted to a Promostandards Purchase Order and submitted via the supplier's web service.
- Upon successful submission, a transaction ID is received in the response.
- The transaction ID is saved as the confirmation number in the database.
- The FR is marked as processed.
| Feature | Availability | What to Expect |
|---|---|---|
| Fulfillment Request Number | Supported | We can send Flx FR# as order number. This can be changed using mapping template. |
| Customer Association | Not Supported | — |
| FR Item Association | Supported | SKU is sent in request. |
| Auto Acknowledgements | Supported | We receive transaction ID in response. This is saved as confirmation number in db. |
| Shipping Selection | Supported | Source shipping methods can be sent. Each company may have different shipping options. |
| Custom Fields | Not Supported | — |
| Attachments | Not Supported | — |
| Limitations | — | — |
Get Shipments
Get Shipments (GS) retrieves shipment confirmations from the supplier via the Promostandards Shipment web service 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.
Use this job to:
- Retrieve shipment confirmations from the supplier's Promostandards Shipment API.
- Update orders with carrier, shipping method, tracking number, and ship date.
- Associate shipped items by SKU and support partial shipments where only a subset is shipped.
Each run follows this workflow:
- 1Connection — Uses a Promostandards connection (Service Type: Shipment) to call the supplier's web services.
- 2Fetch & Map — Flxpoint retrieves shipment data from the Promostandards API, then maps the fields to your Shipment and Shipment Item fields.
- 3Apply Lookback — Only FRs created within the FR Lookback Period are considered (default 3 Months).
- 4Save — Shipment data posts back to the order; partials are supported.
Choose Promostandards and select (or create) a connection with Service Type set to Shipment.
Tip: If you already have a Product connection for inventory, you will need a separate connection with Service Type set to Shipment (same credentials, different Service Type).
There are no main configuration fields for this operation. Expand Advanced Settings if needed:
-
FR Lookback Period for Get Shipments (dropdown) — Maximum age of Fulfillment Requests
eligible for shipment retrieval.
What does this do?
Sets the maximum age of FRs eligible for Get Shipments retrieval.
1 Month 2 Months 3 Months (default) 6 Months 12 Months
Click Save and Proceed.
Use the recommended fields from the Mapping Utilities section below.
Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped.
Map source fields from Promo Standards Shipment to populate your shipment object:
| Flxpoint Shipment Field | Recommended Source | Type | Notes |
|---|---|---|---|
| Carrier | Carrier |
Text | Carrier name from shipment response. |
| Fulfillment Request Number | Id |
Text | Shipment ID used to associate back to the FR/Order. |
| Method | Shipping Method |
Text | Supplier shipping method string. |
| Note | — | — | Optional; set to Don't Map by default. |
| Shipped At | Shipment Date |
Date | Date value mapped to shipment timestamp. |
| Shipping Cost | — | — | Optional; set to Don't Map by default. |
| Tracking Number | Tracking Number |
Text | Main tracking code from shipment response. |
| Tracking URL | — | — | Optional; set to Don't Map by default. |
Map source fields from Promo Standards Shipment Item to associate line items:
| Flxpoint Item Field | Recommended Source | Type | Notes |
|---|---|---|---|
| Quantity Required | Quantity |
Number | Shipped quantity; supports partial shipments. |
| SKU Required | Distributor Part Id |
Text | Item association is by SKU. |
| All Custom Fields | — | — | Optional; if set to "Direct Copy", all serial numbers associated to line item will import. |
The full list of source fields available from the Promostandards Shipment API:
| Source Group | Fields |
|---|---|
| Promo Standards Shipment | Carrier (T), Id (T), Shipment Date (D), Shipping Method (T), Supplier Part Id (T), Tracking Number (T) |
| Promo Standards Shipment Item | Distributor Part Id (T), Distributor Product Id (T), Purchase Order Line Number (T), Quantity (N), Supplier Part Id (T), Supplier Product Id (T) |
- Connection shows Connected and passes Test Connection.
- Service Type is set to Shipment on the connection.
- Mapping template is selected and saved.
- FR Lookback Period covers the age of your target FRs (default 3 Months).
-
No shipments found:
- Verify the FR Lookback Period covers the age of your target FRs. If FRs are older than the lookback window, they will not be matched.
- Confirm the connection is using Service Type Shipment.
-
Missing tracking number:
- Some suppliers may not return tracking data for all shipments. Confirm with your supplier that tracking numbers are available via the Promostandards Shipment endpoint.
-
Item lines didn't attach:
- Ensure the mapping template maps SKU (from Distributor Part Id) and Quantity in the Shipment Item section.
- Partial shipments not updating: Verify that both SKU and Quantity are mapped. Partial shipments require item-level association to increment shipped quantities.
- Connection errors: Confirm Company Code, User Name, and Password. Ensure the connection's Environment matches (Production vs. Sandbox).
| Feature | Availability | What to Expect |
|---|---|---|
| Carrier & Methods | Supported | Carrier and method are available in response. |
| Shipment Item Association | Supported | SKU is available in response. |
| Partial Shipments | Supported | Multiple responses can incrementally complete fulfillment. |
| Invoice Information | Not Supported | — |
| Custom Fields | Not Supported | — |
| Limitation | — | — |
Get Invoices
Get Invoices (GI) retrieves invoice data from the supplier via the Promostandards Invoice web service and creates or updates invoices on your purchase orders with line-item costs, shipping, handling, and tax amounts.
The sections below walk through each step of the setup and configuration process.
Use this job to:
- Retrieve invoices from the supplier's Promostandards Invoice API.
- Create invoice records on purchase orders with line-item costs, shipping, handling, and tax amounts.
- Associate invoiced items by SKU for accurate item-level costing.
Each run follows this workflow:
- 1Connection — Uses a Promostandards connection (Service Type: Invoice) to call the supplier's web services.
- 2Fetch & Map — Flxpoint retrieves invoice data from the Promostandards API, then maps the fields to your Invoice and Invoice Item fields.
- 3Apply Lookback — Only FRs created within the FR Lookback Period are considered (default 1 Month).
- 4Save — Invoice data is created on the associated purchase order.
Choose Promostandards and select (or create) a connection with Service Type set to Invoice.
Tip: If you already have a Product or Shipment connection, you will need a separate connection with Service Type set to Invoice (same credentials, different Service Type).
There are no main configuration fields for this operation. Expand Advanced Settings if needed:
-
FR Lookback Period for Invoice Processing (dropdown) — Defines the maximum age of
Fulfillment Requests (FRs) eligible for invoice generation. Only FRs created within this time frame will
be considered.
What does this do?
Sets the maximum age of FRs eligible for invoice retrieval. Default is 30 days.
1 Month (default) 2 Months 3 Months 6 Months 12 Months
Click Save and Proceed.
Use the recommended fields from the Mapping Utilities section below.
Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped.
Map source fields from Promo Standards Invoice to populate your invoice object:
| Flxpoint Invoice Field | Recommended Source | Type | Notes |
|---|---|---|---|
| Fee Cost | — | — | Optional; when mapped, last value per PO# becomes an additional fee invoice item. |
| Fulfillment Request Number | Purchase Order Number |
Text | Links the invoice back to the associated FR/Order. |
| Invoice Date | Invoice Date |
Date | Date the invoice was issued. |
| Invoice Number | Invoice Number |
Text | Unique identifier for the invoice. |
| Invoice Status | — | — | Optional; can be set via Option picker. |
| Other Cost | — | — | Optional; when mapped, last value per PO# becomes an additional other-cost invoice item. |
| Shipping Cost | Freight Amount |
Number | Available at order level. Maps as a separate shipping invoice item. |
| Tax Cost | Sales Tax |
Number | Available at order level. Maps as a separate tax invoice item. |
| Total Cost | Total Invoice Amount |
Number | Total invoice amount from the response. |
Map source fields from Promo Standards Invoice Item to populate line-item details:
| Flxpoint Item Field | Recommended Source | Type | Notes |
|---|---|---|---|
| All Custom Fields | — | — | Optional; "Direct Copy" imports all custom fields from the response. |
| Cost | Extended Price |
Number | Total cost for the line item (quantity × unit price). |
| Invoice Item Type | — | — | Optional; can be set via Option picker (e.g., Product, Shipping, Tax). |
| Per Unit Cost | Unit Price |
Number | Per-unit price from the invoice line. |
| Quantity | Quantity |
Number | Number of units invoiced for this line item. |
| SKU Required | Distributor Part Id |
Text | Item association is by SKU. |
| Title | Description |
Text | Optional; line item description from the invoice. |
The full list of source fields available from the Promostandards Invoice API:
| Source Group | Fields |
|---|---|
| Promo Standards Invoice | Freight Amount (N), Invoice Date (D), Invoice Number (T), Purchase Order Number (T), Sales Tax (N), Total Invoice Amount (N) |
| Promo Standards Invoice Item | Description (T), Distributor Part Id (T), Extended Price (N), Line Number (T), Quantity (N), Unit Price (N) |
- Connection shows Connected and passes Test Connection.
- Service Type is set to Invoice on the connection.
- Mapping template is selected and saved.
- FR Lookback Period covers the age of your target FRs (default 1 Month).
-
No invoices found:
- Verify the FR Lookback Period covers the age of your target FRs. If FRs are older than the lookback window (default 1 Month), they will not be matched.
- Confirm the connection is using Service Type Invoice.
-
Missing line-item costs:
- Ensure the mapping template maps Per Unit Cost, Cost, and Quantity in the Invoice Item section.
-
Items didn't associate:
- Ensure the mapping template maps SKU (from Distributor Part Id) in the Invoice Item section. Item association relies on SKU matching.
- Shipping/tax not appearing: Shipping, handling, and tax amounts are available at the order level. Map Shipping Cost and Tax Cost in the Invoice-level section (not the Item section).
- Voided invoices not imported: Only active invoices are downloaded. Voided invoices use a different service that is not supported by this operation.
- Connection errors: Confirm Company Code, User Name, and Password. Ensure the connection's Environment matches (Production vs. Sandbox).
| Feature | Availability | What to Expect |
|---|---|---|
| Invoice Format | Not Supported | Only active invoices are downloaded. Voided invoices use a different service. |
| Line Item Costs | Supported | Item-level pricing is available. Shipping, handling, and tax are at order level. |
| Item Association | Supported | SKU is available in response. |
| Limitation | — | — |
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.
Troubleshooting Common Errors
Common issues and solutions for Promostandards integration. Expand each item to learn more.
What's happening
The Promostandards connection cannot be established, Test Connection fails, or the job errors with an authentication or timeout message.
- Incorrect Company Code, User Name, or Password.
- Wrong Environment selected (Production vs. Sandbox).
- Service Type does not match the operation (e.g., using a Product connection for Get Shipments).
- API End Points JSON File is missing or contains invalid endpoint URLs.
How to fix it
- Verify your Company Code, User Name, and Password with the supplier.
- Confirm the Environment matches (Production for live data, Sandbox for testing).
- Check the Service Type matches the operation: Product for inventory, Order for FRs, Shipment for shipments, Invoice for invoices.
- If using an API End Points JSON File, validate the JSON structure and endpoint URLs.
- Click Test Connection after making changes to confirm the fix.
| Operation | Required Service Type |
|---|---|
| Get Inventory (Primary & Secondary) | Product |
| Send Fulfillment Requests | Order |
| Get Shipments | Shipment |
| Get Invoices | Invoice |
What's happening
The Primary inventory job runs but imports zero products, or catalog fields (titles, images, descriptions) are missing from the Global Inventory Pool.
- FOB ID is incorrect or doesn't match the supplier's FOB configuration.
- Mapping template is missing required fields (SKU, title, quantity).
- Archive is enabled and removing products not present in the current feed.
- The supplier's Product API endpoint is not returning data for the configured Company Code.
How to fix it
- Verify the FOB ID with the supplier — this must match their product catalog configuration.
- Review the mapping template and ensure SKU, Title, and Quantity are mapped.
- If Archive is enabled, confirm the API feed contains all expected SKUs. Disable Archive temporarily to test.
- Run the job manually and check the run log for errors or zero-record warnings.
- Click Test Connection on the Product connection to confirm API access.
What's happening
The Secondary delta job runs successfully but cost, quantity, or variant values remain unchanged in the Global Inventory Pool.
- Fetch by Parent SKU is enabled but the parent SKU field is not mapped or doesn't match.
- Fetch by FOB ID is enabled but the FOB ID is incorrect.
- Allow Create Variant is off, so new variants from the delta feed are silently skipped.
- Archive is enabled in both Primary and Secondary, causing conflicts.
How to fix it
- If using Fetch by Parent SKU, confirm the SKU field in the mapping matches what the supplier returns in the delta feed.
- Verify the FOB ID matches the supplier's configuration (same as Primary).
- Enable Allow Create Variant if new variants are expected from the supplier.
- If Archive is enabled in Primary, leave it off in Secondary to avoid conflicts.
- Run the job manually and check the run log for skipped records or warnings.
What's happening
Fulfillment requests are not marked as processed after the job runs, or the supplier's API rejects the order submission.
- Connection is using the wrong Service Type (needs Order).
- Required mapping fields (SKU, Quantity, Ship To address) are missing or empty.
- The supplier's Order endpoint is returning an error for the submitted data.
- FR has already been processed or is in a status that prevents resubmission.
How to fix it
- Confirm the connection uses Service Type Order and passes Test Connection.
- Review the mapping template — ensure all required fields (SKU, Quantity, Ship To Name, Address, City, State, Zip) are mapped.
- Check the job notifications and run log for specific error messages from the supplier.
- Verify the FR status allows processing — FRs in "Cancelled" or "Completed" status will be skipped.
- If the supplier returns a validation error, confirm the data formats match their requirements (e.g., state abbreviations, zip code format).
What's happening
The Get Shipments job runs but shipment data does not attach to orders, tracking numbers are blank, or item lines are not associated.
- Connection uses the wrong Service Type (needs Shipment).
- FR Lookback Period (default 3 Months) does not cover the age of your target FRs.
- Tracking number is not present in the supplier's response for some shipments.
- SKU in the shipment response does not match the SKU on the FR line item.
How to fix it
- Confirm the connection uses Service Type Shipment (separate from your Product connection).
- Increase the FR Lookback Period if FRs are older than the current window (default 3 Months).
- If tracking numbers are frequently missing, confirm with the supplier that tracking data is available via their Shipment endpoint.
- Ensure the mapping maps SKU (from Distributor Part Id) and Quantity in the Shipment Item section for item association.
- Check that Carrier, Tracking Number, and Shipped At are mapped at the shipment level.
What's happening
The Get Invoices job runs but invoices are not associated to Fulfillment Requests, or cost fields (shipping, handling, tax) are missing from the saved invoice.
- Connection uses the wrong Service Type (needs Invoice).
- FR Lookback Period (default 1 Month) does not cover the age of the target FRs.
- SKU in the invoice response does not match the SKU on the FR line item.
- Shipping and tax costs are mapped at the item level instead of the invoice (order) level.
- Voided invoices are expected but only active invoices are supported.
How to fix it
- Confirm the connection uses Service Type Invoice.
- Increase the FR Lookback Period if invoices post much later than shipments (default is only 1 Month).
- Confirm the invoice SKU matches the SKU used on the FR line item.
- Map Shipping Cost and Tax Cost at the invoice level (not the item level) — these are order-level amounts.
- Map Per Unit Cost, Cost, and Quantity at the item level for line-item pricing.
- Note: voided invoices use a separate service and are not downloaded by this operation.
Still need help? If you're experiencing issues not covered here, contact your Promostandards supplier or your Flxpoint account manager.
Contact Support