Shipment Specifications

In Logicbroker the shipment's purpose is to provide all information related to shipping ordered items. This will include quantities shipped, tracking information, container codes (GS1-128 if required) and carrier information.

Not all shipments require a GS1-128 code and label, which will be supplied in the ShipmentLine.ShipmentInfo.ContainerCode field. In most cases the ShipmentLine.ShipmentInfo.TrackingNumber will be used to identify each unique package/carton.

When Logicbroker receives a shipment against your order, it will affect the status of that order. If all quantities on the order are shipped the status of the order will automatically update to Ready to Invoice (600) or Complete (1000) if no invoice is required. It is important that the PartnerPO on the shipment matches the order and that each shipment line matches a line on the order. See Matching shipments to the order below.  

The structure shown below in Field Descriptions follows Logicbroker's standard schema across all document formats; this includes JSON, EDI, XML, CSV, and Portal. The EDI segments are listed next to each field to indicate what field maps to the standard 856 EDI from the Logicbroker schema.

Consolidated Shipments

Logicbroker supports suppliers sending in consolidated shipments (1 shipment for multiple orders). To send in a consolidated 856, you will need to indicate multiple order loops within the document. Logicbroker will create individual 856s based on that information and send the shipments to retailers as individual shipments per order. For any retailer that has test cases, suppliers can test sending consolidated shipments using those test cases. 

Matching shipments to the order

Logicbroker checks every shipment against its order before sending it to your retailer. These checks apply to every format: JSON, XML, EDI, CSV and Portal.

How shipment lines are matched to order lines

• The PartnerPO must match the PO number of an existing order. If Logicbroker finds no order with that PO number, the shipment fails with Original Order Not Found.
• Logicbroker matches each shipment line to an order line by its item. A line matches when its SupplierSKU, UPC or PartnerSKU is the same as on the order line. Logicbroker ignores upper and lower case, and spaces before or after the value.
• If you send a LineNumber (LIN01 in EDI), Logicbroker uses it to pick the right order line. Send it exactly as it appears on the order. For example, 1.0 and 1 are not the same line number.
• If the same item is on more than one order line (for example, lines 1.0 and 1.1), send a separate shipment line for each order line with that line's quantity. Do not combine them into one shipment line.
• Logicbroker ignores shipment lines that do not match any order line, and they do not count toward the order. If no line on a shipment matches the order, the whole shipment fails with Shipment SKU Mismatch.

Quantities

• The quantity shipped for an order line is the total of that line's quantities in every box (ShipmentLine.ShipmentInfo.Qty, or SN102 in each EDI item loop). Earlier shipments for the same order also count, unless they failed or were cancelled or ignored.
• The quantity shipped plus any quantity already cancelled on that order line cannot be more than the quantity ordered, unless your retailer allows over-shipment. If it is more, the shipment fails with a message such as Tried to ship 1 out of 1 ordered (1 cancelled). So you cannot ship a line, or part of a line, that has already been cancelled.
• Through the API, Logicbroker rejects a shipment if every line has a quantity of 0, or if any line has a quantity below 0.

One item in more than one box

• List the item in each box it was packed in, with the same item identifiers and the quantity in that box. In EDI, repeat the item loop under each pack loop and use the same LIN01 line number each time. Logicbroker reads a different LIN01 as a different order line.
• Give each box its own tracking number (ShipmentLine.ShipmentInfo.TrackingNumber, MAN*CP in the EDI pack loop) and its own container code (ShipmentLine.ShipmentInfo.ContainerCode, MAN*GM). Logicbroker treats boxes with the same container code as one box. In EDI, do not send the tracking number only at the shipment level, because REF*CN is for the PRO number.
• If a single unit ships in more than one box (for example, a product that comes in two cartons), put the item's full quantity in the first box and a quantity of 0 in the other boxes. This keeps the boxes from adding up to more than was ordered. Check your retailer's document standards first, because some retailers have their own rules for items shipped in more than one box.

Sending a corrected shipment

• A shipment that failed does not count toward the order. Correct the problem and send a new shipment.
• Give the corrected shipment a new shipment number (ShipmentNumber, BSN02 in EDI). Logicbroker treats an exact copy of a shipment it already received as a duplicate and does not process it.
• A shipment that was accepted still counts toward the order. If it was wrong, contact support before you send a replacement. Otherwise the replacement may fail as an over-shipment. See I need to correct a shipment that already processed.

Retailer-specific checks

Some retailers add their own checks. For example, your retailer may require a tracking number on every box, accept only the ship methods on its list, or not allow you to ship part of a line. You can see your ship method codes under Settings › Shipment Options. To see what a retailer requires, check its document standards under Partners › Document Standards.

Troubleshooting shipments that do not match the order

These situations apply to suppliers in every format: EDI, API, CSV, file import and the portal. The error appears on the failed shipment's events and under Reporting › Events. Failed shipments are listed under Reporting › Failed Documents.

When you contact support about any of these, include your company name, the retailer, the PO number, the shipment's document ID, the exact error and what you already tried.

Shipment failed with "Original Order Not Found"

What it means: Logicbroker could not link the shipment to an order. The error details say "This shipment could not be linked to an existing order. Please verify that the PO number on this shipment is correct."

What to check:

1. Open the failed shipment and note its PartnerPO (PRF01 in EDI).
2. Search your orders in Logicbroker for that PO number.
3. Compare the two values character by character. Look for a missing prefix, an extra digit or a different PO.

The fix: Correct the PO number in your system and send a new shipment with a new shipment number. The failed shipment does not count toward the order.

How to check it worked: The new shipment does not show as Failed. When every line is shipped, the order moves to Ready to Invoice or Complete.

When to contact support: contact support if the PO number on the shipment matches an order you can see in Logicbroker and the shipment still fails.

Shipment failed with "Shipment SKU Mismatch"

What it means: Logicbroker found the order, but no line on the shipment matches a line on the order. The error details say "None of the items found on this shipment can be matched to items on the originating order" and give the order's Logicbroker ID.

What to check:

1. Open the order and the failed shipment side by side.
2. For each shipment line, compare the SupplierSKU, UPC and PartnerSKU with the order line. At least one of them must be the same. Upper and lower case and spaces before or after the value do not matter.
3. Check whether you sent a different item than the one ordered. For example, you shipped a replacement item number, or you shipped the separate parts of a bundle that was ordered as one SKU.

The fix: Send the item identifiers exactly as they appear on the order. Choose one path:

• In the portal, open the failed shipment and select More Actions › Edit. Correct the item identifiers and select Submit. Logicbroker reprocesses the edited shipment.
• Correct the identifiers in your system and send a new shipment with a new shipment number.

More Actions › Retry does not fix this error, because it reprocesses the same shipment unchanged.

How to check it worked: The shipment does not show as Failed, and the order's shipped quantities include the shipment. If only some lines match, Logicbroker ignores the lines that do not match. Check that every line you shipped counted toward the order.

When to contact support: contact support if the identifiers match the order and the shipment still fails, or if your warehouse can only ship the parts of a bundle.

Shipment failed with "Cannot Over-Ship Lines"

Who this applies to: suppliers whose retailer does not allow over-shipment. Through the API, Logicbroker rejects the shipment when you submit it, with the same message.

What it means: For at least one order line, the quantity shipped plus the quantity cancelled is more than the quantity ordered. The message names each line, for example "The following line cannot be shipped because over-shipment is not allowed: SKU 12345: Tried to ship 1 out of 1 ordered (1 cancelled)." The first number is the total shipped for that line, including earlier accepted shipments. The number in brackets is the quantity already cancelled on the order.

What to check:

1. Look at the order's earlier shipments. Shipments that were accepted count toward the order. Shipments that failed, were cancelled, were ignored or are duplicates do not count.
2. Check whether you already cancelled part or all of the line, for example on an acknowledgement.
3. Add up the quantity in every box for the line. If a single unit ships in more than one box, each box with a quantity adds to the total.
4. If the same item is on more than one order line, check that you sent one shipment line per order line, each with its own line number.

The fix: Change the quantity on the shipment so that shipped plus cancelled is no more than ordered.

• If the line was cancelled, remove it from the shipment.
• If one unit ships in more than one box, put the full quantity in the first box and 0 in the other boxes.
• If the order line was already shipped on an accepted shipment, do not ship it again.

Then send the corrected shipment with a new shipment number, or open the failed shipment in the portal, select More Actions › Edit, correct the quantities and select Submit.

How to check it worked: The shipment does not show as Failed, and the order shows the expected shipped quantity for each line.

When to contact support: contact support if an earlier accepted shipment was wrong and you need to replace it. Do this before you send the replacement.

My corrected shipment is treated as a duplicate

What it means: The shipment has the status Duplicate. Logicbroker received an exact copy of a shipment it already had, with the same content and the same reference, so it did not process the new one. A duplicate is not sent to the retailer and does not count toward the order.

What to check:

1. Compare the new shipment with the earlier one. Check that your correction is in the file you sent.
2. Check the shipment number (ShipmentNumber, BSN02 in EDI). If you reused the earlier number, that is the likely cause.

The fix: Make the correction in your system, give the shipment a new shipment number and send it again. More Actions › Retry is only available on failed documents, so you cannot retry a duplicate.

How to check it worked: The new shipment appears with a status other than Duplicate or Failed.

When to contact support: contact support if a shipment with a new shipment number and new content is still marked as a duplicate.

I need to correct a shipment that already processed

Who this applies to: suppliers in every format, when a shipment was accepted with a wrong tracking number, carrier, reference or quantity, or was sent twice.

What it means: An accepted shipment counts toward the order and may already be on its way to the retailer. Logicbroker does not delete documents once they are submitted. More Actions › Retry and More Actions › Ignore only appear while a shipment is Failed. If your account shows More Actions › Change Status, you can set a shipment in any status to Ignored.

What to check:

1. Open the shipment and note its ID# and status.
2. Open the order and look at Related Documents. Check whether there is more than one shipment, and which one has the wrong details.
3. Check whether the retailer already has the wrong details, for example in its own portal or because it told you.

The fix: Choose the path that matches your shipment.

• Your account shows More Actions › Edit on the shipment: select it and confirm that you want to put the shipment in draft. Correct the details and select Submit. If the retailer already received the shipment, contact support first and ask whether the retailer accepts a correction.
• You do not see Edit: contact support. Support can correct the tracking number on the shipment. Support can also move the wrong shipment to Ignored and set the order back to Ready to Ship, so that you can send a new shipment with the right details.
• The same shipment was sent twice: if your account shows More Actions › Change Status, set the extra shipment to Ignored. Otherwise, contact support and give the ID# of the extra shipment. Support can move it to Ignored.
• The retailer already has the wrong details: some retailers cannot take a correction from Logicbroker once the shipment is in their system. In that case, send the correct details to the retailer directly. Support tells you when this applies.

How to check it worked: The wrong shipment shows Ignored, or shows the corrected details. The new or edited shipment does not show as Failed, and the order shows the expected shipped quantity for each line.

When to contact support: Include the shipment's ID#, the PO number, what is wrong and the correct value, for example the correct carrier and tracking number.

Shipment failed with "API Error 422: Invalid fulfillment order line item quantity requested"

Who this applies to: companies whose shipments Logicbroker sends to a Shopify store. The full message reads API Error 422: {"errors":["Invalid fulfillment order line item quantity requested."]}.

What it means: Shopify refused the shipment because the order lines are already fulfilled in the store. This usually happens when someone marked the order as shipped, delivered or complete in Shopify, or when another app already sent a shipment for it. Logicbroker does not fail the shipment if every tracking number on it is already on the Shopify order. So this error usually means the tracking in Shopify is different or missing.

What to check:

1. Open the failed shipment in Logicbroker and note its tracking numbers.
2. Open the same order in Shopify. Check whether it is already fulfilled and which tracking numbers it shows.
3. Check whether the order was also shipped through another channel, for example by hand in Shopify, or in the portal and again through EDI or a shipping app.

The fix:

• If the order is already fulfilled in Shopify and nothing is missing, the failed shipment is not needed. Open it and select More Actions › Ignore, or More Actions › Change Status if that is what your account shows.
• If Shopify has the wrong tracking, correct it in Shopify, then ignore the failed shipment the same way.
• To stop this happening again, ship each order through one channel only.

More Actions › Retry fails again with the same error unless the Shopify order already shows every tracking number on the shipment.

How to check it worked: The shipment shows Ignored, and the Shopify order shows the right tracking.

When to contact support: contact support if the Shopify order is not fulfilled and the shipment still fails with this error.

My shipment did not reach the retailer or my other system

Who this applies to: suppliers and retailers whose shipments Logicbroker sends on to another system, such as a retailer's system, a store or an ERP. The steps are the same for every connection.

What it means: Logicbroker either did not receive the shipment, or received it and could not send it on.

What to check:

1. Open the order and look at Related Documents. If no shipment is listed, Logicbroker did not receive one. Check that your system or shipping app sent it.
2. Open the shipment and check its status. If it shows Failed, expand Events to see the error.
3. Look at Document Processing History on the shipment. It lists each action Logicbroker ran, when it last ran and how many attempts it made.
4. To see errors across many documents, go to Reporting › Events or Reporting › Failed Documents.

The fix: Choose the path that matches the error.

• The error is about the shipment's data, for example a missing field or a code the other system does not know: correct the data and send a new shipment, or use More Actions › Edit on the failed shipment.
• The other system was down or refused the connection: once it is working again, select More Actions › Retry on the failed shipment. If many shipments failed at the same time, contact support. Support can reset them once the connection works again.
• The shipment was sent but the other system shows something different: check with the owner of that system. If it is the retailer, contact the retailer directly.

Invoices for the same order can fail until the shipment is processed. Fix the shipment first.

How to check it worked: The shipment no longer shows as Failed, and the other system shows the shipment and its tracking.

When to contact support: Include the shipment's ID#, the PO number, the other system's name, the exact error from Events and when the problem started.

Details and Sample Files

  "ShipToAddress": {
    "CompanyName": "Warehouse 123"
  }

    "ExtendedAttributes": [
    {
      "Name": "EXAMPLE",
      "Value": "Portal"
    },
    {
      "Name": "EXAMPLE2",
      "Value": "New Value"
    }
  ]

{
  "ShipmentLines": [
    {
      "ItemIdentifier": {
        "SupplierSKU": "V-123123"
      },
      "ShipmentInfos": [
        {
          "DateShipped": "2019-01-01T12:00:00",
          "CarrierCode": "FEDG",
          "ClassCode": "FDEG_GD",
          "ServiceLevelCode": "string",
          "TrackingNumber": "TRK11111",
          "ContainerCode": "00086275400000051594",
          "Qty": 15,
          "ContainerType": "CTN",
          "Height": 1.0,
          "Width": 2.0,
          "Length": 3.0,
          "DimensionUnit": "IN",
          "Weight": 0.0,
          "WeightUnit": "LB"
        },
        {
          "DateShipped": "2019-01-01T12:00:00",
          "CarrierCode": "FEDG",
          "ClassCode": "FDEG_GD",
          "ServiceLevelCode": "string",
          "TrackingNumber": "TRK22222",
          "ContainerCode": "00086275400000051595",
          "Qty": 5,
          "ContainerType": "CTN",
          "Height": 1.0,
          "Width": 2.0,
          "Length": 3.0,
          "DimensionUnit": "IN",
          "Weight": 0.0,
          "WeightUnit": "LB"
        }
      ],
      "Quantity": 20,
      "QuantityUOM": "EA",
      "LineNumber": "1"
    }
  ]
}

{
  "ShipmentInfos": [
    {
      "DateShipped": "0001-01-01T00:00:00",
      "ContainerCode": "00086275400000051600",
      "ContainerType": "PLT",
      "Height": 4.0,
      "Width": 4.0,
      "Length": 5.0,
      "DimensionUnit": "IN",
      "Weight": 0.0,
      "WeightUnit": "LB"
    }
  ],
  "ShipmentLines": [
    {
      "ItemIdentifier": {
        "SupplierSKU": "V-123123"
      },
      "ShipmentInfos": [
        {
          "DateShipped": "2019-01-01T12:00:00",
          "CarrierCode": "FEDG",
          "ClassCode": "FDEG_GD",
          "ServiceLevelCode": "string",
          "TrackingNumber": "TRK11111",
          "ContainerCode": "00086275400000051594",
          "Qty": 15,
          "ContainerType": "CTN",
          "ShipmentContainerParentCode": "00086275400000051600",
          "Height": 1.0,
          "Width": 2.0,
          "Length": 3.0,
          "DimensionUnit": "IN",
          "Weight": 0.0,
          "WeightUnit": "LB"
        },
        {
          "DateShipped": "2019-01-01T12:00:00",
          "CarrierCode": "FEDG",
          "ClassCode": "FDEG_GD",
          "ServiceLevelCode": "string",
          "TrackingNumber": "TRK22222",
          "ContainerCode": "00086275400000051595",
          "ShipmentContainerParentCode": "00086275400000051600",
          "Qty": 5,
          "ContainerType": "CTN",
          "Height": 1.0,
          "Width": 2.0,
          "Length": 3.0,
          "DimensionUnit": "IN",
          "Weight": 0.0,
          "WeightUnit": "LB"
        }
      ],
      "Quantity": 20,
      "QuantityUOM": "EA",
      "LineNumber": "1"
    }
  ]
}

  <ShipToAddress>
    <CompanyName>Merchant Co</CompanyName>
  </ShipToAddress>

  <ExtendedAttributes>
    <ExtendedAttribute>
      <Name>Example</Name>
      <Value>Portal</Value>
    </ExtendedAttribute>
    <ExtendedAttribute>
      <Name>Example2</Name>
      <Value>NewValue</Value>
    </ExtendedAttribute>
  </ExtendedAttributes>

<Shipment xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <ShipmentLines>
    <ShipmentLine>
      <ItemIdentifier>
        <SupplierSKU>V-123123</SupplierSKU>
      </ItemIdentifier>
      <ShipmentInfos>
        <ShipmentInfo>
          <DateShipped>2019-01-01T12:00:00</DateShipped>
          <CarrierCode>FEDG1</CarrierCode>
          <ClassCode>FDEG_GD</ClassCode>
          <ServiceLevelCode>string</ServiceLevelCode>
          <TrackingNumber>TRK11111</TrackingNumber>
          <ContainerCode>00086275400000051594</ContainerCode>
          <Qty>15</Qty>
          <ContainerType>CTN</ContainerType>
          <Height>1</Height>
          <Width>2</Width>
          <Length>3</Length>
          <DimensionUnit>IN</DimensionUnit>
          <Weight>0</Weight>
          <WeightUnit>LB</WeightUnit>
        </ShipmentInfo>
        <ShipmentInfo>
          <DateShipped>2019-01-01T12:00:00</DateShipped>
          <CarrierCode>FEDG1</CarrierCode>
          <ClassCode>FDEG_GD</ClassCode>
          <ServiceLevelCode>string</ServiceLevelCode>
          <TrackingNumber>TRK22222</TrackingNumber>
          <ContainerCode>00086275400000051595</ContainerCode>
          <Qty>5</Qty>
          <ContainerType>CTN</ContainerType>
          <Height>1</Height>
          <Width>2</Width>
          <Length>3</Length>
          <DimensionUnit>IN</DimensionUnit>
          <Weight>0</Weight>
          <WeightUnit>LB</WeightUnit>
        </ShipmentInfo>
      </ShipmentInfos>
      <Quantity>20</Quantity>
      <QuantityUOM>EA</QuantityUOM>
      <LineNumber>1</LineNumber>
    </ShipmentLine>
  </ShipmentLines>
</Shipment>

<Shipment xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <ShipmentInfos>
    <ShipmentInfo>
      <DateShipped>0001-01-01T00:00:00</DateShipped>
      <ContainerCode>00086275400000051600</ContainerCode>
      <ContainerType>PLT</ContainerType>
      <Height>4</Height>
      <Width>4</Width>
      <Length>5</Length>
      <DimensionUnit>IN</DimensionUnit>
      <Weight>0</Weight>
      <WeightUnit>LB</WeightUnit>
    </ShipmentInfo>
  </ShipmentInfos>
  <ShipmentLines>
    <ShipmentLine>
      <ItemIdentifier>
        <SupplierSKU>V-123123</SupplierSKU>
      </ItemIdentifier>
      <ShipmentInfos>
        <ShipmentInfo>
          <DateShipped>2019-01-01T12:00:00</DateShipped>
          <CarrierCode>FEDG1</CarrierCode>
          <ClassCode>FDEG_GD</ClassCode>
          <ServiceLevelCode>string</ServiceLevelCode>
          <TrackingNumber>TRK11111</TrackingNumber>
          <ContainerCode>00086275400000051594</ContainerCode>
          <Qty>15</Qty>
          <ContainerType>CTN</ContainerType>
          <ShipmentContainerParentCode>00086275400000051600</ShipmentContainerParentCode>
          <Height>1</Height>
          <Width>2</Width>
          <Length>3</Length>
          <DimensionUnit>IN</DimensionUnit>
          <Weight>0</Weight>
          <WeightUnit>LB</WeightUnit>
        </ShipmentInfo>
        <ShipmentInfo>
          <DateShipped>2019-01-01T12:00:00</DateShipped>
          <CarrierCode>FEDG1</CarrierCode>
          <ClassCode>FDEG_GD</ClassCode>
          <ServiceLevelCode>string</ServiceLevelCode>
          <TrackingNumber>TRK22222</TrackingNumber>
          <ContainerCode>00086275400000051595</ContainerCode>
          <Qty>5</Qty>
          <ContainerType>CTN</ContainerType>
          <ShipmentContainerParentCode>00086275400000051600</ShipmentContainerParentCode>
          <Height>1</Height>
          <Width>2</Width>
          <Length>3</Length>
          <DimensionUnit>IN</DimensionUnit>
          <Weight>0</Weight>
          <WeightUnit>LB</WeightUnit>
        </ShipmentInfo>
      </ShipmentInfos>
      <Quantity>20</Quantity>
      <QuantityUOM>EA</QuantityUOM>
      <LineNumber>1</LineNumber>
    </ShipmentLine>
  </ShipmentLines>
</Shipment>

N1*ST*Merchant Co~

HL*5*4*I~
LIN*1*VN*49-98760*IN*J07874*UP*123456789012~
SN1**298*EA~

HL*3*2*P~
PO4**********4*3*2*IN~
TD1*CTN*1****G*20*LB~
MAN*CP*564564654654~
MAN*GM*081034001000008795~
HL*4*3*I~
LIN*1*VN*49-98760*IN*J07874*UP*123456789012~
SN1**298*EA~
HL*5*2*P~
PO4**********4*3*2*IN~
TD1*CTN*1****G*20*LB~
MAN*CP*854545488888~
MAN*GM*081034001000008818~
HL*6*5*I~
LIN*1*VN*49-98760*IN*J07874*UP*123456789012~
SN1**1*EA~

HL*3*2*T~
TD1*PLT*1****G*400*LB~
REF*ZH*1Z324323~
MAN*GM*181034001000008808~
HL*4*3*P~
PO4**********4*3*2*IN~
TD1*CTN*1****G*20*LB~
MAN*CP*564564654654~
MAN*GM*081034001000008795~
HL*5*4*I~
LIN*1*VN*49-98760*IN*J07874*UP*123456789012~
SN1**298*EA~
HL*6*3*P~
PO4**********4*3*2*IN~
TD1*CTN*1****G*20*LB~
MAN*CP*854545488888~
MAN*GM*081034001000008818~
HL*7*6*I~
LIN*1*VN*49-98760*IN*J07874*UP*123456789012~
SN1**1*EA~

Id,ShipToAddress.CompanyName
221804,Merchant Co

Id,ExtendedAttribute[Name=EXAMPLE].Value
221804,Portal

ShipmentNumber,PartnerPO,ShipmentLine.LineNumber,ShipmentLine.ItemIdentifier.SupplierSKU,ShipmentLine.ShipmentInfo.TrackingNumber,ShipmentLine.ShipmentInfo.ContainerCode,ShipmentLine.ShipmentInfo.Qty
SH111111111111,PO1112222,1,V-123SKU,TRK1Z000001,081034001000008795,15
SH111111111111,PO1112222,1,V-123SKU,TRK1Z000002,081034001000008765,5

ShipmentNumber,PartnerPO,ShipmentLine.LineNumber,ShipmentLine.ItemIdentifier.SupplierSKU,ShipmentInfo.ContainerCode,ShipmentLine.ShipmentInfo.ShipmentContainerParentCode,ShipmentLine.ShipmentInfo.TrackingNumber,ShipmentLine.ShipmentInfo.ContainerCode,ShipmentLine.ShipmentInfo.Qty
SH111111111111,PO1112222,1,V-123SKU,00086275400000051600,00086275400000051600,TRK1Z000001,081034001000008795,15
SH111111111111,PO1112222,1,V-123SKU,00086275400000051600,00086275400000051600,TRK1Z000002,081034001000008765,5

Field Descriptions