Concept One connects to Flxpoint as a source through a GIS EDI inventory feed. This guide explains how Flxpoint ingests the Concept One GIS EDI inventory file, and details the updated logic for handling the price segment (CTP03) — including how blank price values are now treated, how invalid price values are handled, and how this affects item validation, quantity management, and the completion status of the GIS job.
How to Connect
Configure Concept One as a Source
Concept One is an EDI feed-based integration. Flxpoint reads a GIS EDI inventory file that Concept One makes available, then parses each item, its quantity, and its price segment into your Flxpoint catalog.
Product Operations
Get Inventory imports your Concept One catalog data — items, quantities, and prices — from the GIS EDI inventory file. The section below covers how the price segment (CTP03) is handled, including the updated logic for blank and invalid price values.
Concept One — Get Inventory imports your catalog from the Concept One GIS EDI inventory file. On each run, the GIS job downloads the file, reads every item along with its quantity and its price segment (CTP03), and updates your Flxpoint catalog.
This page focuses on how Flxpoint now handles the price segment (CTP03) during import — specifically how blank and invalid price values affect whether an item is imported, validated, and counted toward the GIS job's completion status.
- 1Pick up the file: On each scheduled run, the GIS job retrieves the latest Concept One GIS EDI inventory file.
- 2Parse each item: For every item in the file, Flxpoint reads the identifier, the available quantity, and the price segment (CTP03).
- 3Validate and save: Each item is validated and then saved to your catalog. Quantity is updated for every successfully processed item.
- 4Complete the job: When the file has been fully processed, the GIS job reports a completion status that reflects how many items were imported, updated, or skipped.
How Flxpoint treats the price value found in the CTP03 price segment of each item.
| CTP03 Price Value | What Flxpoint Does | Item Result |
|---|---|---|
| Valid number | The price is saved to the item. | Item imported with price and quantity. |
| Blank / empty | The price is ignored — no price is saved for the item. | Item imported, quantity updated, price left unset. The item is not skipped. |
| Invalid (non-numeric) | An error is recorded for that item. | Item is skipped (price could not be read). |
| Scenario | Prior Behavior | Current Behavior |
|---|---|---|
| Blank CTP03 price | Item was skipped and archived. | Item is imported; price is simply not saved. |
| Invalid (non-numeric) CTP03 price | Item was skipped with an error. | No change — item is still skipped with an error. |
| Valid CTP03 price | Price saved. | No change — price saved. |
- The Concept One source credentials are saved and the GIS job is scheduled.
- A mapping template is selected for the Get Inventory operation.
- Items with a blank price appear in your catalog with quantity updated (price unset) — this is expected.
- The GIS job completion status shows the run finished, with any skipped items reported separately.
- An item is missing a price but everything else looks right: The price was blank in the GIS EDI file. This is expected — the item is imported and its quantity is updated, but no price is saved until a valid price is supplied in a later file.
- An item was skipped during the run: The price value for that item was invalid (non-numeric). Invalid prices still trigger an error and cause the item to be skipped. Confirm the source data has a numeric price (or a blank price) for that item.
- Quantities look out of date for items without prices: With the updated logic, blank-price items are no longer skipped, so their quantities update normally. If quantities still look stale, re-run / reprocess the latest GIS EDI file (see below).
- Applying the updated logic to past files: Reprocessing a GIS EDI file runs it through the current logic. Items that were previously skipped for a blank price will be imported with their quantity on reprocessing.
| Feature | Availability | What to Expect |
|---|---|---|
| Quantity | Supported | Imported and updated for every successfully processed item, including blank-price items. |
| Pricing (CTP03) | Supported | Saved when a valid number is supplied; left unset when blank; errors when invalid. |
| Blank price handling | Item kept | Item is imported with quantity; price is not saved. Item is not skipped or archived. |
| Invalid price handling | Item skipped | An error is recorded and the item is skipped for that run. |
| Reprocessing | Supported | Re-running a GIS EDI file applies the current price-handling logic. |
Troubleshooting
Common issues and solutions for the Concept One GIS EDI integration. Click any card to expand.
What's happening
The price segment (CTP03) for that item was blank in the GIS EDI inventory file.
How to fix it
- This is expected behavior. The item is imported and its quantity is updated — only the price is left unset.
- When a valid price is supplied in a later GIS EDI file, it will be saved on the next run.
What's happening
The price value for that item was invalid (non-numeric). Invalid prices still trigger an error and cause the item to be skipped for that run.
How to fix it
- Confirm the source file has a numeric price — or a blank price — for the affected item.
- A blank price is fine and will not skip the item; only an unreadable, non-numeric value does.
- Once the source data is corrected, reprocess the GIS EDI file to import the item.
What's happening
Under the prior logic, items with a blank price were skipped and archived, which could zero out their quantity even when the item was still available.
How to fix it
- The updated logic no longer skips or archives blank-price items.
- Reprocess the latest GIS EDI file to bring those items back with their quantity intact.
What's happening
Blank-price items are no longer skipped, so their quantities should update on every run. Stale quantities usually mean the most recent file hasn't been processed yet.
How to fix it
- Confirm the GIS job has run recently and completed.
- Reprocess the latest GIS EDI file to refresh quantities.
What's happening
A small number of items with invalid prices can be skipped while the rest of the file imports normally. The GIS job still completes successfully.
How to fix it
- Review the skipped items — they typically had invalid (non-numeric) prices.
- Correct the source data for those items, then reprocess the file if you need them imported sooner.
Still need help? Contact our support team.
Contact Support