We are working with a merchant and we’ve noticed that Shopify is adding silent line breaks (\n) in shipping address line 1 for a US address.
These are silent, and do not appear on the admin order page on the address, nor the appear in the order confirmation email, but they do appear in the .json version and when pulling the address via the API.
From past experience, I believe I’ve seen this silent line breaks as part of the additional fields for addresses, like Germany where we have street and building number as separate fields, but then in the Admin API they consolidate under address1. (for which we use @shopify/worldwide package) to separate.
Wondering if anyone from Shopify’s address team can have a look? I can share orderId privately with Shopify staff.
These line breaks are affecting downstream systems and fulfillment.
Hi @AndrejMazhe - I ran a controlled test on a development store and could reproduce newline passthrough, but I couldn’t reproduce Shopify adding a line break to clean address input through the Admin order creation path.
I created two otherwise identical US orders using Admin REST API version 2026-04. The control used 123 Repro Street and stayed single-line in both REST and Admin GraphQL. The second used a literal Line Feed (LF) in 123 Repro Street\nUnit 4, and that LF was returned unchanged by REST and shippingAddress.address1. For this path, the line break was already present when the address was written rather than being added by the API read layer.
I’ll send you a DM for the order details and creation path so we can identify where the LF entered the order. Thanks for raising this here!
Donal,
I have also tried intentionally adding the \n to the address line, but unlike our case, this one appears both in the admin order page and the confirmation email.
The examples I sent, the \n only creeps into the .json layer and downstream systems, not visible on the admin page nor confirmation email.
I have responded to your DM!
@AndrejMazhe Thanks for sharing the order details. I’ve looked into both orders and have an update.
The additional address fields hypothesis is a good instinct, but it doesn’t explain what you’re seeing here. That feature is region-specific and joins split fields using the Unicode Word Joiner character (U+2060), not a newline. The US isn’t among the supported regions, so the \n isn’t coming from that path. The additional address fields docs cover how that works.
Both affected orders completed through Shop Pay, and they were placed by two different customers two days apart. I also confirmed that the Admin API preserves a \n already present in address1 but doesn’t insert one into clean input, so the line break is entering upstream of the API read layer.
I’ve raised this with our addresses and checkout teams to investigate where the \n originates in the checkout path and whether embedded control characters should be normalized. I’ll follow up here when I hear back from them - thanks again for raising this issue here!
Thanks @Donal-Shopify - keep me updated! 