
Shopify's developer changelog entry of 17 November 2026 changes what B2B customers can read through the Customer Account API. The entry is tagged Security, and it applies on all versions of that API at once. There is no opt-in, and no version pin keeps the old behaviour.
The schema doesn't change, so nothing breaks loudly. A field that used to hold data can now come back null or as an empty list, and no error appears. For a support team, that is the part worth preparing for. When a B2B customer says "my order is gone" or "the company details are blank", the record may not have been deleted at all. The customer may simply no longer be allowed to read it.
According to Shopify's changelog entry, customers now read "only the company data and the orders for companies that they belong to." The entry spells out three effects.
CompanyContact.locations returns an empty list unless the contact belongs to the current customer. A customer still reads the locations they have a role in, through their own contact's locations field, Company.locations and Company.location(id:).taxIdentifier) and the contact fields contacts and roleAssignments.order(id:) and draftOrder(id:) refuse that company's orders and draft orders. The customer's order lists, customer.orders and customer.draftOrders, leave out that company's orders and draft orders. The customer's personal orders are still listed.Shopify's guidance to developers is short. Apps that read a location's tax or contact data through another contact's locations, or through an order's purchasingEntity, should expect null or an empty list where the customer has no role. Apps that show a customer's order history will see it leave out orders placed for a company the customer no longer belongs to. Shopify also states that developers don't need to change their queries.
The entry gives no reason for the change beyond its Security tag.
The Customer Account API reads data on behalf of a signed-in customer. It serves their own account view, not the Shopify admin. So the change shows up first on the customer's side of the screen, and the first person to hear about it is often whoever answers the support inbox.
Because the schema is unchanged and nothing errors, a blank field looks the same whatever the cause. To the customer and to an agent reading a screenshot, all of these look alike:
Only the first means anything is gone. If an agent tells the customer "that order no longer exists" when the real answer is "your access to it changed", the customer is misinformed. Someone will then have to unpick that later.
When a B2B customer reports missing orders or empty company details, work through these before giving an answer:
A reply that is accurate and doesn't overpromise might read:
"Thanks for flagging this. We checked, and the order is still on our records; nothing was deleted. Shopify changed what customer accounts can show for company orders and company locations, so what you can see now depends on which company and locations your account is linked to. I've passed this to the team that manages business accounts, and they'll confirm whether your access should be updated."
Change the wording to fit your store. The two things to keep are saying what you actually checked, and not calling the record deleted unless your admin shows that it is.
A change like this produces the same question from several customers, often answered differently by whoever picks it up. Write the checklist once, as an internal note or a knowledge base article, so every agent works from the same steps. It's worth recording which Shopify changelog entry it rests on and the date, 17 November 2026, so the next person can re-check it at the source.
If you are setting that up, DeskLeap brings tickets, live chat and a knowledge base into one place. The platform is 100% free with unlimited human agents; an optional AI Agent add-on is $29/mo each.
Source: Shopify developer changelog, "Updated B2B location access in the Customer Account API", dated 17 November 2026, read 18 November 2026.