FoodLogiQ offers 6 different methods for users to submit Critical Tracking Event data. This event data can represent various supply chain activity, including Harvesting (Aquaculture), Harvesting (Wild Caught), Landing, Shipping, Receiving and Transformation events.
As a prerequisite, suppliers and distributors will need to load their products and locations and share that information with their customers in FoodLogiQ. Companies will also need to evaluate which event submission method(s) will work best for their company to send traceability data to FoodLogiQ.
Data Submission Methods
FoodLogiQ Connect offers online and batch loading options for event data submission. This includes:
- Online Form (UI)
- .CSV Online Import
- .CSV via FTP
- EDI
- API
- FoodLogiQ Connect Mobile App
Note: For Harvesting (Aquaculture) and Landing Events we only offer the Online Form (UI) and API at this time.
Required Event Data Elements
All traceability events contain a core list of attributes, answering the, “WHO, WHAT, WHEN, and WHERE” of the event. This includes:
Name |
Details |
Date |
Date the event occurred |
GLN |
Global Location Number for the sender, receiver, or processor. These are the parties involved in the event. Can include manufacturing facilities, cooling sheds, distribution centers, grocery stores, restaurants, etc. |
GTIN |
Global Trade Item number for the products involved in the event. This is a 14 digit, globally unique number, and is represented as AI (01) in the GS1-128 barcode. |
Product Lot |
Alphanumeric lot or batch code of product. These are variable length up to 20 characters, and are represented as AI (10) on GS1-128 barcode. |
Product_Serial_Number |
Alphanumeric serial identifier of the product. These are variable length up to 20 characters, and is represented as AI (21) on GS1-128 barcode |
Product Quantity Units |
Unit of measure for product shipped. For most transactions, this will be "Case" |
Product Quantity Amount |
Numeric quantity of total cases shipped |
NOTE: One date from the list below is Required, which should be the date in the GS1-128 barcode: |
|
Production Date |
Represented as AI (11) on the GS1-128 barcode |
Packaging Date |
Represented as AI (13) on the GS1-128 barcode. Also known as "Pack Date" |
Best Before Date |
Represented as AI (15) on the GS1-128 barcode |
Sell By Date |
Represented as AI (16) on the GS1-128 barcode |
Expiration Date |
Represented as AI (17) on the GS1-128 barcode. Also known as "Use By" Date |
Farming Method
|
A combination of type of culture, unit, level of intensity, culture species and scale or size of exploitation as defined by the FAO. “Extensive”, “SemiIntensive”, “Intensive” Note: Only applicable for Harvesting (Aquaculture) Events |
Harvest Dates |
Calendar date on which the seafood was harvested from the farm/cultivation area Note: Only applicable for Harvesting (Aquaculture) Events |
Harvest Certification |
Name of harvest standards body which a particular harvest seafood is subject to and the unique identifier associated with the certified entity. Note: Only applicable for Harvesting (Aquaculture) Events |
Landing Dates |
Calendar start and end dates when seafood is discharged to a landing location. Note: Only applicable for Landing Events |
Landing Authorization |
Unique number associated with a regulatory document from the relevant authority, granting permission for the discharge of the wild capture of seafood to land by a fisher, fishing vessel, or transshipment vessel. Note: Only applicable for Landing Events |
The following attributes are examples of OPTIONAL fields. Please see your trading partner requirements for more information on any optional fields they may require. |
|
SSCC |
Serial Shipping Container Code. 18 numeric characters, created using a company's GS1 Prefix, and includes a check digit. |
Pallet ID |
License Plate Number (LPN) or Pallet Tag ID. Alphanumeric. Submitted as: palletId |
Bill of Lading (BOL) |
The Bill of Lading corresponding to a shipping or receiving event. Alphanumeric. Submitted as: billOfLading |
Invoice |
An Invoice Number corresponding to a receiving or shipping event. Alphanumeric. Submitted as: invoice |
Purchase Order (PO) |
A Purchase Order number corresponding to a receiving or shipping event. Alphanumeric. Submitted as: purchaseOrder |
No matter how you choose to submit event data, all of your events will be visible in FoodLogiQ from the Events page.
Comments
0 comments
Article is closed for comments.