ScriptServe - EDI 832 Price/Sales Catalog Specifications

The 832 EDI file represents your Price/Sales Catalog with customer-specific pricing that you send to ScriptServe.

Direction: You send 832 files to ScriptServe to set customer-specific pricing. Send these as needed to maintain pricing for individual pharmacy customers.

Example 832 Price/Sales Catalog

Here is an example 832 User EDI file that meets ScriptServe's requirements: 832_user_example.edi

Key Points for 832 User Files

Frequency: Send as needed - we scan for new files every 15 minutes
Updates: Products with changed values will be updated; unchanged products remain the same
Multiple NDCs: Supported as long as each SKU/item number is unique
File Naming: Use unique filenames with timestamps (e.g., "832_user_20250131_1430.edi")
Segment Terminators: We support both ~ (tilde) and newline (\n) characters as segment terminators
Customer-Specific: Use N1*BY segment to specify the Customer ID or DEA number for targeted pricing

File Format Details

The example below shows the structure of a User 832 file. All samples are based on the example file above:

Header Segments

ISA*00*          *00*          *ZZ*WHOLESALE      *ZZ*SCRIPTSERVEPROD         *170725*0400*U*00401*000000030*0*P*~
GS*SC*WHOLESALE*SCRIPTSERVEPROD*20170725*0400*30*X*004010~
ST*832*0030~
BCT*PC**2******00~
DTM*007*20250131~
N1*DS*WHOLESALE MEDICAL INC*11*RK0236403~
N1*BY**91*123456~

These 7 header lines are used on our end to determine things like the type of EDI file is what we're expecting, who this file is intended for, etc.

Here are some important details about the information that needs to be provided in these segments:

ISA: make sure the ISA states your vendor name and "SCRIPTSERVEPROD" as shown in the example.
ST: ensure that the value of ST01 is 832. ST02 can have any value.
BCT:
- BCT01 must be "PC" (Price Catalog)
- BCT03 must be "2" (Version 2)
- BCT10 must be "00" (Original)
N1*BY: Use this segment to specify the buyer/customer identification. Include either your Customer ID in your system or the pharmacy's DEA number in the fourth field (N104) so we can map this catalog to the specific pharmacy on ScriptServe. The qualifier "91" indicates "Assigned by Seller".

Any segments not detailed above are required, but don't worry too much about the values you use for those, as they are likely ignored by our parser.

Line Item Segments


      LIN**VC*111226*N4*46672005310
G53*021
DTM*036*20190824
PID*F*RX***Butalbital,APAP&Caff Tabs WHT
PO4*1*1*EA
CTP**AWP*.00
CTP**NET*35.99
N9*ZZ*32

The above 8 lines represent a line item/product, and these are the required segments:

LIN: Use this segment to specify SKU (VC) and NDC (N4).
G53: Use this segment to specify maintenance type. This line is currently ignored, as we do changes only if there is a difference since last upload. Any value is accepted for this segment.
DTM: Use this segment to specify Expiry Date (036) for the product in the format YYYYMMDD (e.g. 20201225). If an item does not have an expiry date, use DTM*036*ZZZ and we will set the expiration date to 1 year from now.
PID: Use this segment to specify Product/Item Description, specifically the product name.
PO4: Use this segment to specify Item Physical Details. This line is currently ignored, since we currently get this information from a third party source on a per-product basis. Any value is accepted for this segment.
CTP**AWP: Use this segment to specify Average Wholesale Price. This line is currently ignored, since we currently get this information from a third party source on a per-product basis. Any value is accepted for this segment.
CTP**NET: Use this segment to specify Unit Price.
N9*ZZ: Use this segment to specify Quantity.

Footer Segments

CTT*1584
SE*11114*0030
GE*1*30
IEA*1*000000030

These segments are required, but ultimately ignored by our parser.