Four Services That Can Win the New Security Budget for Shopify Public Apps
Shopify’s mandatory allowed-address lists create a budget for services that audit addresses, verify migrations, and watch for outages in public apps.
Published 2026. 11. 9.
App server addresses are now essential security information
On November 5, 2026, Shopify made an allowed-address list mandatory for all public apps. An allowed-address list ensures that only registered servers can read or change merchant admin data. Apps built directly by merchants are exempt, although Shopify recommends using the feature.
Public apps that use bulk operations—features that read or change products and orders at scale—must configure the list by 11:59 p.m. Eastern Time on November 12. That is 1:59 p.m. Korea Standard Time on November 13. Missing the deadline blocks bulk operations. The deadline for other public apps is 1:59 p.m. Korea Standard Time on November 21.
If an app is not configured by the general deadline, it will be removed from the app store and new installations will be blocked. From January 15, 2027, existing merchants will see warnings. From April 1, requests to access merchant admin data will be denied. Existing customers will not all be disconnected immediately, but new revenue and customer trust are affected first.
Shopify introduced the rule so that a leaked app access credential cannot be used from any server. Requests from outside the list receive a 403 response, meaning access is denied. The feature does not protect against a compromised app server or failures in the app’s own permission checks.
Apps can register up to 100 addresses. Environments with changing addresses can add up to 10 network ranges. Shopify recommends fixed individual addresses over allowing an entire network range. Before enforcing the setting, teams can test which real requests from the previous 30 days would be blocked.
The new budget comes from app operators, not merchants
Consider a company with eight employees running four Shopify public apps: one chief executive, two customer support staff, and five developers, with no dedicated security staff. This is the kind of company that now has a new reason to spend.
Until now, server addresses may have been scattered across developers’ memories, cloud-service settings, and old work documents. The team must document which production and test servers connect to Shopify, enter them in the settings for all four apps, and check whether each uses bulk operations. Missing an old scheduled job or a backup server used only during outages can make normal operations appear healthy.
The risk grows during a server migration. Removing an old address first, or forgetting to add a new one, can stop product synchronization and order processing at the same time. Even if the 30-day test shows no requests expected to be blocked, it does not guarantee that addresses will remain valid at the next redeployment or failover.
Previously, a developer handled this work when time allowed. Now a chief executive or operations lead may approve the cost. They judge success less by technical sophistication than by keeping app-store visibility, allowing new installations, avoiding merchant warnings, and reducing time without an admin-data connection.
An address-management service changes the first step. It can collect each app’s production addresses, test addresses, bulk-operation use, and owner on one screen, identify missing addresses, and present the registration order. Four separate app reviews become one company-level list.
During a migration, it can temporarily allow both old and new addresses, confirm that the new server can both read and make changes, and then remove the old address. If denied-access responses rise after deployment, it can alert the operations lead before customer inquiries arrive. For companies using servers without fixed addresses, the service can also bundle the work of selecting and configuring a fixed-address product.
Some decisions still require people. The app operator must decide which server is truly production, which region takes over during an outage, and whether allowing an entire network range is acceptable. So sell this service not as “taking responsibility for security,” but as “finding omissions and preventing stoppages before changes.”
Companies already pay to reduce address-management work
GoodAccess, a Czech company, sells a service that routes remote employees through one company-only fixed address. Its smallest public configuration, combining five users and a dedicated access point, was about KRW 110,000 per month when simply converted at the exchange rate at the time. It is not a Shopify-app-specific service, but the spending logic is the same: customers pay to reduce the time spent changing addresses themselves.
Veriheal, a U.S. remote healthcare company, spent several hours each week manually reflecting employee addresses in its allowed lists before adopting GoodAccess’s fixed address. The vendor said the time spent handling address issues was almost eliminated. This is a vendor-produced customer case, so the claimed savings need separate verification.
Lithuania-based NordLayer also routes employee connections through dedicated addresses and charges based on user count and dedicated servers. Its public price for five users plus a dedicated-address server was about KRW 130,000 per month when converted at the exchange rate at the time. This is a scale at which a small team can choose a recurring operating cost over repeated manual work.
ID-Pal, an Irish identity-verification company, switched to a dedicated-address approach after directly managing more than 50 addresses registered across multiple systems. NordLayer said the company reduced 40 hours of management work per month. This is also a vendor-produced case, so the key point is not the number itself but that a budget can emerge for services that reduce address-change work.
Four things you can build now
1. Public app address registration audit
- What it does: Collects server addresses and bulk-operation use for each app, then identifies missing settings and the order of deadlines.
- Who uses it: A leader at a Korean app studio running three or more public apps without dedicated security staff.
- Why now: After the deadline, blocked new installations and merchant warnings can become direct revenue problems.
- First screen: Shows cards for app name, bulk-operation use, registered addresses, latest test result, and owner.
2. Pre-migration stoppage check
- What it does: Compares old and new addresses before a server move and explains the order in which to register and remove them.
- Who uses it: An operations team moving Shopify app servers to another provider or region for cost savings or outage response.
- Why now: Once address lists are enabled, an ordinary server migration can disconnect access to merchant data.
- First screen: Places the current address, new address, period when both are allowed, and read-and-change test results on separate lines.
3. Early warning for denied access
- What it does: Identifies the affected app and merchants and alerts the owner when denied-access responses occur in a Shopify connection.
- Who uses it: A small app operator without overnight monitoring staff that first learns about outages through customer inquiries.
- Why now: The same error now requires teams to distinguish among a missing address, a server change, and a Shopify restriction before recovery can be fast.
- First screen: Shows the last successful connection time, failed app, number of affected merchants, and most recent server change.
4. Fixed server address setup service
- What it does: Adds a fixed external address to an app using servers whose addresses can change, then completes Shopify registration.
- Who uses it: A public app operator that chose a simple hosting product where the address may change each time a server runs.
- Why now: Teams can allow a broad network range, but Shopify recommends a narrow fixed address where possible.
- First screen: Shows the current hosting provider, operating country, fixed-address availability, estimated monthly cost, and migration steps.
Why this matters where you are
If you operate apps on another platform, check whether it is introducing similar restrictions on the servers allowed to access merchant or customer data. The deadlines, enforcement sequence, and platform terminology may differ, but the operational work is comparable: identify every real server address, test changes before enforcement, and assign an owner for migrations. A useful product can focus on preventing missed configuration rather than claiming to replace security responsibility.
One person to ask today
Spend 30 minutes with one public-app operator and document, while looking at the relevant screens, one app’s production server address, backup server address, bulk-operation use, and whether its address changes during redeployment. If the operator cannot answer all four within 10 minutes, or must repeatedly check with developers, there may be a problem worth paying for through an address audit or setup service.
Sources
7 sources
Every fact in this article came from the pages below. Check them yourself.
- Announcement of mandatory allowed-address lists for public appsShopifyUsed for the affected apps, first deadline, exemptions, and guidance on extension requests.https://shopify.dev/changelog/posts/ip-allowlists-are-now-required-for-public-apps
- Allowed-address list configuration documentationShopifyUsed for address registration limits, the network-range option, the previous-30-day test, and denied-access behavior.https://shopify.dev/docs/apps/build/dev-dashboard/ip-allowlist?syclid=dbmc1r06d8hs73a7o5t0&utm_source=openai
- Public app security change scheduleShopifyUsed for app-store removal, blocked new installations, merchant warnings, and the 2027 request-denial schedule.https://shopify.dev/changelog/blog/app-security-updates-ip-allowlist-is-now-required?utm_source=openai
- GoodAccess pricingGoodAccessUsed for public pricing for users and a dedicated fixed-address access point.https://www.goodaccess.com/pricing/?utm_source=openai
- Veriheal remote-access security case studyGoodAccessUsed for the vendor’s case study on reducing manual address-management time.https://goodaccess.com/case-studies/veriheal-strengthens-remote-access-security-with-goodaccess/?utm_source=openai
- NordLayer pricingNordLayerUsed for public pricing for users and a dedicated-address server.https://nordlayer.com/pricing/?utm_source=openai
- ID-Pal address-management case studyNordLayerUsed for the vendor’s case study on managing more than 50 addresses and reducing 40 hours per month.https://nordlayer.com/blog/case-study-id-pal-nordlayer/?utm_source=openai