Bug: fulfillmentCreate message no longer shows in order history

GraphQL Admin API Troubleshooting
1

Using the latest version of 2025-07, the fulfillmentCreate mutation no longer shows the supplied message in the order history. I’m not sure when this stopped being shown to the user, but it definitely did show at some point in the not too distant past.

Example code:

const response = await this.admin.graphql(
  `#graphql
  mutation fulfillmentCreate($fulfillment: FulfillmentInput!, $message: String) {
    fulfillmentCreate(fulfillment: $fulfillment, message: $message) {
      fulfillment {
        id
      }
      userErrors {
        field
        message
      }
    }
  }`,
  {
    variables: {
      fulfillment: {
        lineItemsByFulfillmentOrder: {
          fulfillmentOrderId: fulfillmentOrderId
        },
        trackingInfo: {
          company: trackingCompany,
          number: trackingNumber,
          url: trackingUrl
        },
        notifyCustomer: true
      },
      message: 'Test message to show in order history',
    },
  },
);

And the order history:

Screenshot 2025-08-14 160007
Screenshot 2025-08-14 1600071577×777 58.7 KB

When a message is supplied for other fulfillment mutations, e.g. acceptFulfillmentOrder, rejectFulfillmentOrder, then any supplied message is shown in the order history as expected.

3

Hey @gavinharriss,

I’m testing and I see the same as you. I’m checking to see if this is expected or not. Do you by chance have a screenshot of a past order where this is showing in the timeline?

4

Unfortunately I couldn’t find any old orders showing the message as previously I added a message in very rare circumstances. I only noticed the bug as I now intend to show a message always for fulfilled orders, adding the warehouse order number from the 3PL warehouse for easier tracking between systems if staff need to investigate an order.

5

Thanks for checking Gavin. Looking here we haven’t been able to find any recent changes that would have altered this behaviour.

Considering alternatives, would it work to use order metafields to store this message?

6

Perhaps the bug isn’t in the Admin GraphQL API but in Shopify itself with how it’s rendering the order history to the user? Maybe it’s not showing for specific message types anymore, which would explain why I couldn’t find an old order showing the message, which I’ve definitely seen shown in the past.

Is there a better place to raise these bug reports if this forum isn’t the place to do so?

I’ll take a look at the order metafields. I haven’t played with them yet, but I didn’t think they would show up in the order history which is the natural place for the message I’m adding to appear.

7

Hey Gavin,

Just to clarify, we do have an internal issue opened to look in to this further, so this is a good place to report these when you notice it.

Metafields won’t show in the order history timeline, but will show in the metafields below that.

8

Thanks for the clarification, much appreciated. I’ll just hang off for the bug fix in this instance as the message I’m adding is just useful for traceability between systems as a nice to have in this case.

Thanks for looking into this and raising the bug report.