|

|
GemFind File Specifications... |
Click here to view a sample inventory file.
The field order is as follows: Cut
(Shape), Size,
Color, Clarity, Cost Per Carat, Certificate
Type, Depth %, Table
%, Girdle, Culet, Polish, Symmetry, Fluorescence,
Crown, Pavilion, Measurements, Comments, Stones, Certificate
#, Inventory Stock #
- Each diamond must be on a separate line.
- Each field should be separated with a comma.
- The Text Qualifier is a double quote "
- You can abbreviate the Cut Field (Abbreviations
List)
- Do not put commas or $ in the Cost Per Carat
Field.
- Size, Cost Per Carat, Depth & Table fields
must only contain numeric characters.
- Cut (Shape),
Size, Color, Clarity, Cost Per Carat cannot be
empty (null) or line will be rejected.
- Clarity field must contain one of the following:
Clarity FL, IF, VVS1, VVS2, VS1, VS2, SI1 ,SI2,
SI3, I1, I2, I3
- If there is a comma inside the field such as
in the comment field, you must enclose the field
in double quotes (").
- If you skip a field, you must have a comma in
it's place.
- For Depth % and
Table % these should only contain numeric fields.
- If your stone does not have a certificate, enter
N or None in certificate field.
- Don't put any price information in the Comments
field.

|
GemFind File Specifications
(matched pairs) |
Click
here to view a sample inventory file.
The field order is as follows: Cut
(Shape), Size,
Color, Clarity, Cost Per Carat, Certificate
Type, Depth %, Table
%, Girdle, Culet, Polish, Symmetry, Fluorescence,
Crown, Pavilion, Measurements, Comments, Stones,
Certificate #, Inventory Stock #, Pair
Stock #, Pair Separable
- Each diamond must be on a separate line.
- Each field should be separated with a comma.
- The Text Qualifier is a double quote "
- You can abbreviate the Cut Field (Abbreviations
List)
- Do not put commas or $ in the Cost Per Carat Field.
- Size, Cost Per Carat, Depth & Table fields must only
contain numeric characters.
- Cut (Shape),
Size, Color, Clarity, Cost Per Carat cannot be
empty (null) or line will be rejected.
- Clarity field must contain one of the following: Clarity
FL, IF, VVS1, VVS2, VS1, VS2, SI1 ,SI2, SI3, I1,
I2, I3
- If there is a comma inside the field such as in the comment
field, you must enclose the field in double quotes
(").
- If you skip a field, you must have a comma in it's place.
- For Depth % and Table %
these should only contain numeric fields.
- If your stone does not have a certificate, enter N or None
in certificate field.
- Matched Pairs : Enter stock number of matching
stone in Pair Stock # column, indicate Y or N
in Pair Separable column to indicate if pair is
separable.
- Don't put any price information in the Comments field.

|
Rapaport File Specifications... |
Click here to view a sample inventory file.
The field order is as follows: Cut
(Shape), Weight, Color, Clarity, Measurements,
Cut Grade, Lab, Price,
Depth %, Table %, Girdle Thin, Girdle Thick, Girdle
%, Culet Size, Culet Condition, Polish, Symmetry,
Fluorescence Intensity, Fluorescence Color, Crown
Height, Crown Angle, Pavilion Depth, Pavilion Angle,
Treatment, LaserInscription, Comments, Certificate
#, CertificateImage, VendorStockNumber, MatchedPairStockNumber,
IsMatchedPairSeparable, FancyColor, FancyColorIntensity,
FancyColorOvertone, ParcelStoneCount
- Each diamond must be on a seperate line.
- Each field should be separated with a
comma.
- The Text Qualifier is a double quote
"
- You can abbreviate the Cut Field (Click
Here For Abbreviations List)
- Do not put commas or $ in the Cost Per
Carat Field.
- Size, Cost Per Carat, Depth & Table
fields must only contain numeric characters.
- Cut (Shape),
Size, Color, Clarity, Price (per carat) cannot
be empty (null) or line will be rejected.
- Clarity field must contain one of the
following: Clarity FL, IF, VVS1, VVS2, VS1, VS2, SI1 ,SI2,
SI3, I1, I2, I3
- If there is a comma inside the field
such as in the comment field, you must enclose the field in
double quotes (").
- If you skip a field, you must have a
comma in it's place.
- For Depth
% and Table % these should only contain numeric fields.
- If your stone does not have a certificate,
enter N or None in certificate field.
- Matched Pairs : Enter stock number of
matching stone in Pair Stock # column, indicate Y or N in
Pair Separable column to indicate if pair is separable.
- Don't put any price information in the
Comments field.

|
PolyPlus File Specifications... |
Click here to view a sample inventory file.
The field order is as follows: Shape
(cut), Carat Weight, Color, Clarity, Price per Carat,
Lot #, Stock #, Lab, Certificate ID, Certificate Image,
Additional Image, Dimensions, Depth %, Table %, Crown
Angle, Crown %, Pavilion Angle, Pavilion %, Girdle
(thinnest), Girdle (thickest), Girdle %, Culet Size,
Culet Condition, Polish, Symmetry, Fluorescence Color,
Fluorescence Intensity, Enhancement Types, Remarks,
Availability, Is Active, Fancy Color Main Body, Fancy
Color Intensity, Fancy Color Overtone, Is Matched
Pair, Is Matched Pair Separable, Matching Stone Stock
#, Pavilion
- Each diamond must be on a seperate line.
- Each field should be separated with a
comma.
- The Text Qualifier is a double quote
"
- You can abbreviate the Cut Field (Click
Here For Abbreviations List)
- Do not put commas or $ in the Cost Per
Carat Field.
- Size, Cost Per Carat, Depth & Table
fields must only contain numeric characters.
- Shape (cut),
Carat Weight, Color, Clarity, Price per Carat
cannot be empty (null) or line will be rejected.
- Clarity field must contain one of the
following: Clarity FL, IF, VVS1, VVS2, VS1, VS2, SI1 ,SI2,
SI3, I1, I2, I3, N/A
- If there is a comma inside the field
such as in the comment field, you must enclose the field in
double quotes (").
- If you skip a field, you must have a
comma in it's place.
- For Depth
% and Table % these should only contain numeric fields.
- If your stone does not have a certificate,
enter N or None in certificate field.
- Matched Pairs : Enter stock number of matching stone in
Pair Stock # column, indicate Y or N in Pair Separable
column to indicate if pair is separable.
- Don't put any price information in the Comments field.
Accepted File Formats...
- TXT : Text files adhering to the specifications
above are acceptable.
- CSV : Comma separated value files
adhering to the specifications above are acceptable.
Microsoft Excel can easily export .CSV files.
|
|