Integrating to FLX EDI

Table of Contents

How to connect General EDI Guidelines Supported Transactions

This document provides comprehensive information on integrating with Flxpoint's EDI standard and guides you through the steps to get started.

Getting Started with Flxpoint EDI Integration
Before you begin exchanging documents with Flxpoint, follow these steps to set up your connection. Once you complete these steps, an EDI specialist will be assigned to assist you further.

How to connect

First, if you are a FLX customer, add your supplier or vendor as a source in your Flxpoint account. This step is essential to ensure that all related data and communications are linked to your account. Before you begin testing and exchanging documents with Flxpoint, make sure you have loaded an initial set of items with a SKU and their cost so we can send a test order. If you need any assistance, your EDI specialist is ready to help.

If you are both a FLX customer and vendor, please email Flxpoint’s EDI Team at connect@flxpoint.com. In your email, include the following information:

Vendor Company Name – For example, Acme Corp.
Vendor Interchange IDs – These should follow the format, for example, ZZ:12345678.
Document Types – Specify the types of documents you will be trading (such as 846 and 850).
FTP Hosting Details – If your vendor is hosting the FTP, include details such as the Host, Port, Username, Password, and the Inbound/Outbound Directories.

General EDI Guidelines

Standard Version: Flxpoint supports EDI using version 004010VICS. This is the industry-standard version that ensures compatibility and consistency across systems.

Interchange ID: Use the qualifier ZZ and an ID in the format FLX#####. This number represents your client’s unique Flxpoint AID. For example, simply using ZZ is acceptable when the complete identifier is already understood in context.

Connection Type: The EDI connection is established via SFTP. Flxpoint can either host the file for you or connect to your hosted FTP. (Please note that AS2 and VAN connections are not supported.)

Internal Vendor Number: During the initial setup, Flxpoint assigns you an internal vendor number. This identifier is a maximum of 10 characters long and is used for system tracking.

Delimiters: By default, Flxpoint uses the following delimiter settings (which can be customized per job if needed):

• Segment Terminator: ~ (Decimal 126 or HEX 7E)
• Element Separator: * (Decimal 42 or HEX 2A)
• Sub-element Separator: > (Decimal 62 or HEX 3E)

997 Acknowledgements: For every transaction that Flxpoint sends, you must return a 997 acknowledgement. Additionally, Flxpoint generates a 997 for each processed transaction, and you can find these in the “/out” directory on the FTP/SFTP. Remember that a 997 only confirms that the transaction was received—it does not verify the accuracy of the transaction content. If you encounter any issues, please contact Flxpoint support.

Supported Transactions

Please review the STEDI guide linked at the top of each of the following pages for more details:

846 - Inventory Advice

STEDI Guide: Inventory Advice Guide

Purpose: To inform the retailer of inventory availability with accurate levels.

Frequency: Process inventory data hourly or, if not feasible, at least daily.

Providing a valid quantity level is recommended; any value above 0 indicates the item is in stock.

A quantity > 0 confirms availability for purchase.

Suppliers may use a “safety net” algorithm (e.g., sending 0 for critically low stock).

A value of ‘1’ or higher in QTY02 indicates sufficient stock; ‘0’ indicates low or no stock.

Note: A ‘0’ quantity record does not affect pending orders.

LIN Segments (Line Item Identification)

Primary Identifier / Qualifier:

LIN02 – Qualifier must be SK (SKU).

LIN03 – Use a SKU or preferred product identifier.

Optional Identifiers:

LIN04 to LIN07 – Additional identifiers (only one mapped).

Additional qualifiers include UP (UPC) and EN (EAN).

Example: LIN**SK*XXX***UP*X***VP*XX~

PID Segments (Product / Item Description)

Optional Elements:

PID01 – Always “F” for Free-form Description.

PID02 – Always “08” for Product.

PID03 – Product Title.

Example: PID*F***08***XX~

QTY Segments (Quantity)

Mandatory Elements:

QTY01 – Always “33” for available stock.

QTY02 – Actual quantity available.

QTY03 – Always “EA” for Each.

Example: QTY*33***000*EA~

850 - Purchase Order

STEDI Guide: Purchase Order Guide

Purpose: To transmit new orders.

Frequency: Process Purchase Orders hourly or at least daily.

Suppliers must follow the shipping service level indicated in the TD5 segment.

BEG Segment (Beginning of Purchase Order)

BEG01 – Transaction Set Purpose: "00" for Original.

BEG02 – Purchase Order Code: "SA" for Stand-Alone Order.

BEG03 – Maximum length of 22 characters.

BEG05 – Date format: CCYYMMDD.

PO1 Segment (Baseline Item Data)

PO101 – Line Item starts at 1 and increments.

PO102 – Quantity Ordered (must be ≥1).

PO103 – Unit of Measure: “EA”.

PO104 – Unit Price in format ##.##.

PO105 – Qualifier: “SK” for SKU.

Example: PO1*XXXXX***000000*EA***00000000000**SK*XXXX*UP*XXXXXXXXXXXX~

TD5 Segment (Carrier Details)

The Carrier Name is optional; the Shipping Method is required.

TD512 – Service Level Code (Shipping Method).

Defaults: D3 (3 Day Select), ND (Next Day Air Saver), SI (Standard Ground), SP (SurePost).

Example: TD5*****XXXXX*******XX~

856 - Advanced Ship Notice (ASN)

STEDI Guide: Advanced Ship Notice Guide

Purpose: To provide detailed tracking and shipment configuration information so incoming orders can be processed efficiently.

Frequency: Process shipment data hourly or at least daily.

LIN Segments (Line Item Identification)

LIN01 – Line Item number starts at 1 and increments.

LIN02 – Qualifier options: UP (UPC), EN (EAN), SK (SKU), or BP (Buyer’s Part Number).

LIN03 – Product ID must match the identifier sent in the 850.

Example: LIN*0001*SK*ABC12345~

Shipment Methods

Shipment Level: One tracking number for one or more orders in a single shipment.

HL loops structure: Shipment > Order > Item.

Tracking number provided in the REF segment.

Example: REF*CN*XXXXXXXXX~

Structure:

HL*1****S*1~ HL*2*1*O*1~ HL*3*2*I*0~

Pack Level: Tracking numbers provided for each package.

HL loops structure: Shipment > Order > Pack > Item.

Tracking number provided in the MAN segment for each pack.

Example: MAN*CP*XXXX~

Structure:

HL*1**S*1~ HL*2*1*O*1~ HL*3*2*P*0~ HL*4*3*I*0~

Additional Shipping & Routing Details

FTP/EDI Transfer Specifics:

FTP Host: ftp.flxpoint.com

Port: 22 (SFTP)

Inbound Directory: /incoming

Outbound Directory: /out

Standard Operating Procedures:

Ensure ASN files are received and processed within scheduled intervals.

Verify HL loop sequencing and tracking mapping before live shipment.

Confirm FTP connectivity and directory permissions prior to go-live.

Troubleshooting & Support:

For FTP issues, email support@flxpoint.com.

For EDI mapping or ASN content queries, contact your dedicated FLX EDI specialist.

810 - Invoice

STEDI Guide: Invoice Guide

Purpose: To inform the Retailer of the cost they must pay for the order.

Frequency: Process invoice data hourly or at least daily.

Suppliers must invoice following retailer guidelines and agreed payment terms.

Line Items

IT106 – Qualifier can be UP, SK, or VP.

IT107 – Product ID must match the SKU from the 850.

Example: IT1*XXXXX*0000*EA*000*QT*SK*XXXX~

REF Segments

Three optional REF segments: Internal Vendor Number, Department Number, Invoice Number.

REF01 – “IA” (Internal Vendor), “DP” (Department), or “IV” (Invoice Number).

REF02 – Unique number provided by FLX or your invoice number.

Examples: REF*DP***0000~ | REF*IA***XXXXX~ | REF*IV***XXXXX~

SAC Segment (Service, Promotion, Allowance, Charge)

If shipping cost is provided, it must be sent in a SAC segment rather than as a line item.

Accepted SAC Codes in SAC02: AFEE (Fee), C310 (Discount), D240 (Freight), G821 (Shipping), H750 (Tax).

Example: SAC*A***XXXX***000000~

855 - Purchase Order Acknowledgement

STEDI Guide: PO Acknowledgement Guide

Purpose: To indicate which line items on a Purchase Order will be processed and shipped.

Frequency: Process acknowledgements hourly or at least daily.

BAK Segment (Beginning of PO Acknowledgement)

BAK01 – Must be “00” for Original.

BAK02 – Acknowledgment Type options:

AC – With Detail and Change.

AD – With Detail, No Change.

RD – Reject with Detail.

RJ – Rejected, No Detail.

BAK03 – Purchase Order Number must match the PO# from the 850.

Date Format – CCYYMMDD.

Example: BAK*00*RJ*XX***20230210~

PO1 Segment (Baseline Item Data)

PO101 – Line Item Number.

PO102 – Quantity Ordered.

PO103 – Unit of Measure: “EA”.

PO104 – Unit Price.

PO106 – Qualifier must be “SK” for SKU.

Example: PO1*0001***000000*EA***00000000000**SK*XXXXX***UP*XXXXXX~

ACK Segments (Line Item Acknowledgment)

ACK01 – Line Item Status Code options: IA, IQ, IR, R2, R4.

ACK02 – Quantity Accepted must be ≤ PO102.

ACK03 – Unit of Measure: “EA”.

Example: ACK*R4***00000000000*EA~

Flxpoint Knowledge

How to connect

General EDI Guidelines

Supported Transactions

Related Articles