ScriptServe - EDI 832 General Inventory Specifications

The below documentation outlines the requirements for an 832 EDI file that represents a Price Catalog, or in ScriptServe parlance, a General Inventory.

Preface

Before getting started, here are some things to know about EDI transmission that are specific to ScriptServe:

You can import your catalog as frequently as you'd like. We scan for new files on an hourly basis. Products that have different values since the last import will be overwritten with the new values, and products with the same values will not be changed.
ScriptServe can support multiple NDCs, as long as the SKU/product code is unique. In your ScriptServe inventory these duplicates will be displayed as completely separate products.

Your 832

Here is an example file that satisfies ScriptServe's requirements for an 832 EDI file that will successfully convert to a General Inventory: 832_example.edi

Read below for a breakdown of each segment and other details. All samples used below are based off the example file provided 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

These 6 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)
- BCT02 skip this; this is reserved for User 832
- BCT03 must be "2" (Version 2)
- BCT10 must be "00" (Original)

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).
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.