Hi,
I’ve been trying to query orders in order to map the data and update it in our company’s systems.
I am mapping order status together with line items and their status, lot numbers and serial numbers.
For some line items that are configured as kits - I can get several lot numbers for a single line_item_id and I wasn’t able to find a way to distinguish which items from the kit belong to every lot.
Is there a way for us to work with that? Am I approaching this problem the wrong way?
Hello @RLaslau!
Would you mind sharing with me the workflow you do for pulling data with the calls and fields?
You can get to the lot from the line item, but there might be faster or cheaper ways credit-wise.
Have a great day!
TomasFD
Hi @tomasfd,
What I’m trying to do is to query ShipHero for order updates every 24 hours
Then I process the data and update the orders in our system (While also being connected to UPS webhooks for shipment updates)
This is the request that I’m sending:
{
orders(updated_from: "2024-01-08", updated_to: "2024-01-09") {
request_id
complexity
data(first: 10) {
edges {
node {
order_number
partner_order_id
shop_name
fulfillment_status
ready_to_ship
line_items {
edges {
node {
id
sku
partner_line_item_id
quantity
product_name
fulfillment_status
quantity_shipped
quantity_pending_fulfillment
quantity_allocated
backorder_quantity
shipped_line_item_lots {
line_item_id
lot_id
lot_name
lot_expiration_date
}
serial_numbers {
id
legacy_id
line_item_id
serial_number
scanned
created_at
updated_at
}
}
}
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}
}
And my issue is with these sort of responses:
"node": {
"sku": "SOMEKIT",
"quantity": 1,
"quantity_allocated": 0,
"quantity_pending_fulfillment": 0,
"backorder_quantity": 0,
"shipped_line_item_lots": [
{
"line_item_id": "TGluZUl0ZW06MTA3MjczMjM0Mg==",
"lot_name": "319 1B",
"lot_expiration_date": null
},
{
"line_item_id": "TGluZUl0ZW06MTA3MjczMjM0Mg==",
"lot_name": "329 1f",
"lot_expiration_date": null
},
{
"line_item_id": "TGluZUl0ZW06MTA3MjczMjM0Mg==",
"lot_name": "331 5G",
"lot_expiration_date": null
},
{
"line_item_id": "TGluZUl0ZW06MTA3MjczMjM0Mg==",
"lot_name": "329 5A",
"lot_expiration_date": null
}
],
"serial_numbers": [],
"id": "TGluZUl0ZW06MTA3MjczMjM0Mg==",
"partner_line_item_id": "19584.1",
"fulfillment_status": "fulfilled"
}
As you can see, each item of the kit has the same line item id - but they don’t have the same lot name.
So in our systems I’m unable to know which item this is and update accordingly.
Hello @RLaslau
I now get what you mean. You cannot identify each lot to an SKU when the original SKU is a regular kit.
I’m opening an internal conversation to find the best way to make this information available.
I will keep you updated as this progresses.
Have a great day!
TomasFD
Thank you very much!
Thank You Tomas.
Actually I am seeing the same problem without kits.
If I have an order that pulled for one single SKU from 2 different lots, the line_item will show the SKU and quantity for one lot, but then under line_item_lots show BOTH lots, not the actual lot the quantity refers to.
For a given order, the line_item in shipments shows the quantity for the SKU shipped from that lot, but then in the lots it will show both lots, not the one that’s being pulled from. Looks like there is an incorrect join here.
How does one tie back the correct lot to the correct quantity pulled from that lot? It’s strange that the same line_item_id has different quantities.
uery FetchOrderDetails($orderId: String!) {
order(id: $orderId) {
data {
id
order_number
shipments {
line_items {
edges {
node {
quantity
line_item_id
line_item {
id
sku
shipped_line_item_lots {
line_item_id
lot_expiration_date
lot_id
id
}
}
}
}
}
}
}
}
}
Result:
{
"node": {
"quantity": 79,
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"line_item": {
"id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"sku": "VEG2",
"shipped_line_item_lots": [
{
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"lot_expiration_date": "2026-09-22",
"lot_id": "TG90OjcyMzcyNA==",
"id": "U2hpcHBlZExpbmVJdGVtTG90OjEwNTA2MTcxMw=="
},
{
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"lot_expiration_date": "2026-06-11",
"lot_id": "TG90OjUxMTU1Mg==",
"id": "U2hpcHBlZExpbmVJdGVtTG90OjEwNTA2MTcxNg=="
}
]
}
}
},
{
"node": {
"quantity": 65,
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"line_item": {
"id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"sku": "VEG2",
"shipped_line_item_lots": [
{
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"lot_expiration_date": "2026-09-22",
"lot_id": "TG90OjcyMzcyNA==",
"id": "U2hpcHBlZExpbmVJdGVtTG90OjEwNTA2MTcxMw=="
},
{
"line_item_id": "TGluZUl0ZW06MTY4NjA0NDExNQ==",
"lot_expiration_date": "2026-06-11",
"lot_id": "TG90OjUxMTU1Mg==",
"id": "U2hpcHBlZExpbmVJdGVtTG90OjEwNTA2MTcxNg=="
}