Invalid hasMultipleFulFillments field on Customer Account API Order?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 443
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 24
Description
What is the location of your example repository?
No response
Which package or tool is having this issue?
hydrogen-react
What version of that package or tool are you using?
2026.4.3
What version of React Router 7 are you using?
7.16.0
Steps to Reproduce
The Customer Account API types include the field hasMultipleFulfillments here:
When I tried to use it in a query, everything looked fine in the code but Hydrogen complained:
╭─ error ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ In Hydrogen's `customerAccount.query`: │
│ │
│ Field 'hasMultipleFulfillments' doesn't exist on type 'Order' │
│ Request ID: 4ebd321c-7d7b-4169-a418-e389b58ac37e-1784818071 │
│ │
│ To debug the query `Order`, try it in GraphiQL. │
│ │
│ To investigate the issue, examine this stack trace: │
│ at loader (app/routes/account.orders.$orderId.tsx:20) │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
I also couldn't find this field in older/newer versions of the web docs so it might be a leftover from a long time ago?
Expected Behavior
API types don't include outdated/missing fields.
Actual Behavior
API types include a not existing hasMultipleFulfillments field.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at packages/hydrogen-react/src/customer-account-api-types.d.ts around lines 5151-5152 and compare the declared Order fields with the current Customer Account API documentation or GraphiQL schema. Remove or correct the outdated field declaration, then verify that the generated types no longer expose hasMultipleFulfillments and that the relevant package checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100