POS Order Transaction References Draft Register Instead of Checkout Register

GraphQL Admin API Troubleshooting
1

Summary:

When a cart is saved as a draft on one POS register and later completed on another register, the resulting order’s transactions.device.id incorrectly references the register where the draft was created, not the register where the actual checkout occurred.

Register IDs involved:

  • Register #1

    transactions[0].device.id = gid://shopify/PointOfSaleDevice/5270110306

  • Register #3

    transactions[0].device.id = gid://shopify/PointOfSaleDevice/5307170914

Steps to Reproduce:

  1. On Register #3:

    • Compose a cart

    • Save the cart as a draft

  2. On Register #1:

    • Load the previously created draft

    • Complete checkout (e.g., accept cash payment)

  3. Query the created order via API.

Actual Behavior:

The order’s transactions[0].device.id points to Register #3 (where the draft was saved).

Expected Behavior:

The order’s transactions[0].device.id should point to Register #1, where the actual checkout and payment/transaction occurred.

Impact:

  • Misleading POS analytics and device-level reporting

  • Downstream systems attribute the payment to the wrong POS register

Happy to provide further details if required

Best
Christof

2

Hi @Christof_Zirkler,

What you’re describing here was actually a known issue that our developers have been investigating the last couple weeks, and actually they just pushed a fix for this to update the device attribution to the actual device used at checkout, about an hour ago.

Can I ask if you’re still able to replicate this behaviour, if so please do wait up to 24 hours to make sure the fix is fully deployed, and if it’s still occurring then, please provide us with a checkout token/url/id, or cart token, where this is occurred and we can help look into it further.

4

Hi @Kellan-Shopify

Thanks for jumping in so promptly.
I just tried it again. Both devices are on 11.0.3.
Behaviour is unchanged (still incorrect).

Could you guys have a look again please? Thanks.

cc @Brian_Edwards

5

The issue still exists, revenue is attributed towards the wrong POS register.
cc @Kellan-Shopify @Brian_Edwards

6

Hi @Christof_Zirkler,

I’ve looked into this further discussing this with our developers internally, and we can confirm that a fix has been made for this behaviour, though at this time we do need to wait for a new version of the POS app to be released.

The fix should be included in the 11.2 version which will begin rollout on the app stores on March 16th. After the new version is released you should be able to update your POS App and receive the fix.

Additionally, we do ask that you please refrain from tagging people that have not been involved in a thread, as per our Community Code of Conduct.

Do not tag individuals unless they have previously engaged with the topic, and do not tag groups .

7

Hi Kellan, thanks for your reply and the release date, that’s good to hear.
I tagged Brian, as he asked me offline to be included in the Convo.

1 Like