Skip to content

Overview of Wholechain CSV Templates for Event Uploads

Introduction

Wholechain supports multiple supply chain event types, each requiring its own CSV template to ensure accurate and consistent data recording. The event types supported include:

  • Commission Event – Used when creating or initializing products or lots in your supply chain.
  • Aggregation Event – Used when grouping multiple lots or products into a single container.
  • Disaggregation Event – Used when separating lots or products from a previously aggregated container.
  • Receive Event – Used when logging the receipt of products or containers.
  • Ship Event – Used when recording when a product or lot is shipped from one location to another.
  • Transform Event – Used when a product undergoes a transformation, such as processing or repackaging.

Each of these events has its own dedicated CSV template that provides the necessary structure for recording supply chain data accurately. These individual templates are available for reference and use.

Combining Multiple Event Types into One CSV Template

While each event has its own CSV template, Wholechain allows you to combine multiple event types into a single CSV file. This means you can record Commission, Receive, Ship, Transform, or any combination of events within the same upload.

To do this, your CSV must include all required headers for each of the events you intend to log. If a field is required for more than one event (e.g., Type, EventTime, or ProductInstance-LotSerial), it only needs to be included once in the file.

How to Structure a Combined CSV Template

  1. Include all necessary headers for each event type you want to log

  2. Example: If your file includes Commission and Aggregation events, you must include the required headers for both.

  3. Ensure all mandatory fields are present

  4. Some fields, like Id, Type, BizStep, and EventTime, are required for multiple event types and should not be duplicated.

  5. Populate only the relevant columns for each event

  6. If a column applies only to Aggregation and not to Receive, you can leave it blank for Receive event rows.

Example of a Combined CSV Template

Id Type BizStep Disposition EventTime EventTimeZone PurchaseOrder InvoiceNumber ReadPoint ProductInstance-LotSerial ProductInstance-Quantity ProductInstance-Type ProductInstance-ProductId ShipFromLocation-Id ShipToLocation-Id Location-Id TlcSource-Name TlcSource-City TlcSource-State TlcSource-Country TlcSource-AddressLine1 TlcSource-AddressLine2 TlcSource-PostalCode TlcSource-Latitude TlcSource-Longitude
0001 receive urn:epcglobal:cbv:bizstep:receiving urn:epcglobal:cbv:disp:in_progress 2024-03-20T16:00:00+00:00 -05:00 1990091 12314154 RP789 123 190.75 Input raw_goods_000 supplier_000 processing_000 TLC_123 City Name State Name Country Name 123 Main St Apt 4B 12345 12.345678 98.765432
0002 transform urn:epcglobal:cbv:bizstep:assembling urn:epcglobal:cbv:disp:in_progress 2024-03-25T15:00:00+00:00 -05:00 1990091 12314154 RP790 123 180.75 Input raw_goods_000 processing_000 TLC_123 City Name State Name Country Name 123 Main St Apt 4B 12345 12.345678 98.765432
0002 transform urn:epcglobal:cbv:bizstep:assembling urn:epcglobal:cbv:disp:in_progress 2024-03-25T15:00:00+00:00 -05:00 1990091 12314154 RP790 456 180 Output finished_goods_000 processing_000 TLC_456 City Name State Name Country Name 123 Main St Apt 4B 12345 12.345678 98.765432
0004 ship urn:epcglobal:cbv:bizstep:shipping urn:epcglobal:cbv:disp:in_transit 2024-03-30T16:00:00+00:00 -05:00 1990091 12314154 RP791 456 180 Output finished_goods_000 processing_000 buyer_000 TLC_456 City Name State Name Country Name 123 Main St Apt 4B 12345 12.345678 98.765432

Download CSV Example

Conclusion

Wholechain provides flexibility in how you upload your supply chain events. You can choose to use separate CSV files for each event type or combine multiple events into one CSV file by including all necessary headers. This ensures a structured, accurate, and efficient data upload process tailored to your supply chain needs.

For details on individual event templates, refer to the dedicated documentation for Commission, Aggregation, Disaggregation, Receive, Ship, and Transform events.